A Possible answer to Runway Incursions and similar tragedies
What we have now at major airports is a highly complex and confusing taxiing "road system" with confusing signage, no traffic cops and very few traffic lights. The traffic gets quite heavy at times, human errors are inevitable and you can end up on a racetrack headed the wrong way. What is required is a system that can, as far as possible, rule out human error actually causing an accident.
If each runway take-off entry or intermediate taxi-in crossing-point intersection had a holding-point treadle (weight-actuated) incursion alarm blatting out on Tower and Ground frequencies, each incipient incursion would immediately be notified (by an attention-getting warbling tone) to pilots on both the Tower and Ground Movement Frequency (for pilots in the pattern, on ILS finals, taxiing and lined up on the runway or rolling). Any taxiing pilot who thought he’d triggered that VHF audible alarm would immediately stop/check his position. In fact, all taxiing aircraft and those about to roll would be mandated to do so (i.e., stop and check for the hazard aircraft or vehicle). An aircraft taking off in poor visibility (below decision speed) would abort.
Vehicular traffic (sweepers, follow-me vehicles, fire trucks, etc.) would also trigger alerts and themselves be warned immediately of their infractions (working on the principle that all authorized vehicles will be radio-equipped and maintaining a listening watch on Ground and/or Tower).
The treadles, twin pressure-sensitive transducers a few feet apart (and similar to traffic counters seen everywhere on the highways), and associated logic circuitry and plumbing, are not that daunting a technological prospect. The installation could feature an adjacent nosewheel-activated strobe light . That would immediately pinpoint the perpetrator and also alert the offending crew, even in bad visibility.
If you wanted to make it even more reliable and indicative, you could have a green/amber/red light at each take-off runway entry taxiway treadle - directed at the next take-off candidate:
Red: Treadle armed and ready to trigger.
Green: Disarmed and clear to cross.
Amber: Unserviceable fault annunciator (dead treadle operations in progress).
Because the problem is runway incursions, you have to put the burglar alarm on the runway itself (i.e. its access points).
I can think of no other way that would ensure that the only trustworthy common denominator (airplane weight) will be able to do what the human element in the equation is demonstrably unable to reliably do.
Quest: When would it be disarmed for runway(s) in use?
Quest: Can you think of any other enhancements? Perhaps using the aircraft's own lighting to identify the intruder?
Challenge: PICK THE FLAW IN THIS type of anti-incursion SYSTEM (if any).
Cost? Controller inability to operate? Loopholes in the system? Legal Problems? Pilot Opposition? Slowing of Operations?
Cost of such a system? - A lot less than a runway collision and probably of the order of $15M to $25M per airport (depending upon size, number of parallel runways etc)
Disadvantages? It would need to be trialled and could only be implemented once all treadles were in place. Treadles? All USN VP Air Stations have them for actuation of their aircraft rinse-racks. They could tell you the cost (ask NAS Moffet, NAS Barbers Point or Alameda). Alternatively ask the Highways Dept.
The need to await aircraft taxiing in from the runway to clear an armed treadle could be avoided by having a two treadle (i.e. paired) system. Aircraft entering runways would trigger the warbler of an armed system by an A-B progression, and aircraft clearing the runway on taxi-in to the ramp would not, because they would represent a B-A progression across the treadle pair. (and this B-A inbound crossing would also present a reassuring green light to the ATCO in poor visibility).
What's my name for the system? I call it DREADLE. It speaks volumes.
It is about time the FAA started thinking laterally and moving away from the super-techno solutions (inspired by the corporate weenies looking to cash in on a crisis). Dreadle also works most invaluably in low visibility operations, and addresses the fact that pilots busy in the cockpit during taxi (and not looking out as much as they perhaps should) would never miss its unsubtle prompt. And you cannot get more timely a warning, for all concerned, than an automated treadle-operated VHF warbler.
When an ATCO issues a clearance to land (or take-off), he is trusting normally upon his elevated vantage point to see that the runway is clear - but the incident/accident files are full of instances where it wasn't (and not just talking LAHSO operations here). When he issues that clearance he should have the assurance that comes with having Dreadle-armed that runway (so that any incursion will be heard by all concerned - and straightaway without any lethal delay). A trite point - but an interesting legal one when they hold an ATCO accountable for a runway collision (or near collision).
And it's also well past time that the FAA effectively addressed this highest of the high hazard areas. I like low-tech (per the KISS Principle) and DREADLE is something that pilots (US or visiting / ATPL or PPL) will easily understand. A cautionary treadle-triggered warbler over the VHF first up gives rise to "Oh God, I hope that's not us, check up quickly." (for taxiing brethren). Of course for the crew on take-off and those on approach, they instantly know that something's up and will be in a better position to retrieve their situation before tragedy strikes. If you think about it, the only universal medium that puts ATC, Crash-fire-rescue and all pilots on frequency onto the alert simultaneously (with nil further correspondence required) is their commonly shared frequencies (which will be one of Ground or Tower for those in contention). Firemen always monitor TWR freq as well as Ground. It should also be mentioned that the warbler would not be any ear-splitting shriek, simply a background-identifiable superimposed and modulated tone. It could have that well known sexy voice whispering throatily (every 10 seconds) "Runway incursion alert, check your position". I suggest a five seconds on / ten seconds off transmission cycle and a low-power transmitter so that it can easily be over-transmitted if necessary (and/or cancelled by the ATCO if he sees a need to transmit) or has NB'd the cause (culprit) - and needs to transmit in order to resolve it (or announce: "Runway incursion alert resolved and cancelled at time ....."). A low-power transmitter not only makes it over-transmittable but also keeps it short-range within the family (those within about a ten mile radius that have the "need to know"). Putting it on 121.5MHZ (distress freq) wouldn't be as good an idea - simply because not all pilots monitor that. It should be on both of the two primary freqs in use - to be bullet-proof. One of the issues that would need to be resolved is the treadle trigger-weight threshold (for bug-smashers?).
Another beauty of it (as I see it) is that ATCO's and pilots are always in a competitive environment as far as "not screwing it up" goes. The potential embarrassment factor might be sufficient to preclude the majority of incursions - which are simply due to inattention. And of course the other well-worn principle in the world of acronyms and overflowing glossaries is: "Give it a catchy name and it will be on everyone's lips - and the World will beat a path to your door". At least I think that's how it's supposed to work. But hopefully it might set the ball rolling in a different direction and tend to concentrate that introspective FAA mindset on the true nature of the problem.
"Aircraft on short final. Line up and hold behind the landing aircraft". Not an unusual situation at all, so to cover the question of just when the ATCO should disarm Dreadle (in order to permit this aircraft to enter the runway and line-up), I'd have to amend the landing-rollout disarm situation as being "landing aircraft's nosewheel on". That should satisfy the nit-pickers and minimize residual threat exposure. It could even be "main-wheels on" - but in any case, it would need to be closely coordinated by the ATCO in order to minimize false alarms.
Of course the odd man out (reference that recent incursion by a chopper in the UK that caused a 757 abort) would be the helicopter. But unless it's mandated that they must always roll over the runway entry holding point on wheels, that's the only identifiable flaw in the theory (so far).
Seeing an adjacent red light switch to green would be a backup confirmation to a crew that they now have their line-up clearance (at least). But of course it would not avoid a repeat Tenerife - except inasmuch as any aircraft backtracking to clear the runway would cause the ATCO to KEEP the runway armed (and his own red light would be a reminder that the runway was danger-ground)
SQ006 Accident: How would this system have prevented last October’s fatal crash of Singapore Airlines Flight SQ 006, when the pilot attempted to take off on a closed runway? Taipei ATC was using that closed runway as an exit taxi-route so they couldn't really block it off - but there was another (Dreadle) solution available. B-A progression would have worked (and allowed aircraft to exit via taxiing along an "armed" disused runway). BUT A-B treadle progression would have immediately alerted ATC (and the crew.... and also the crew that watched them do it and said nothing) that some hapless soul was lining up on the wrong runway (having just entered the out-of-use runway for line-up - thereby triggering an A-B alert). The cost of that Taipei accident alone would cover installation of Dreadle at 20 other airports. So runneth the affordability question.
Dreadle sites and arming selections would have to be "nutted out" for each airport because they each have their own design features and particular prevalence for incursions as a result of taxiway complexity and prevailing poor visibility (plus foreign pilot through-put). At present the FAA appears to be pinning its hopes to a surface radar system, however that's got a fallible, distractable human interpreting it (and it may only be his secondary duty). They are also running awareness programs - but in my view that's like praying for rain. In my opinion, if the ATCO is responsible for avoiding runway incursion accidents he needs the backup of being able to "arm" his runway against intruders. Once the visibility is way down and there's lots of traffic out there, each aircraft doing its own thing, coming perhaps from different sides of a terminal hub and different runway exit-points, it's simply unrealistic and unfair for a tower operator and surface movement controller to be "responsible" for that traffic (which can often be sight unseen in poor visibility). You only have to look at the alarming increase in the incidence of incursions to understand why it is the number one accident prevention priority - and always will be.
Unfortunately, as long as the FAA avoids any biting of the bullet, there will always be a major incursion accident just around the next corner. Collisions always involve double the number of casualties because there will normally be two aircraft - and at least one aircraft is going to be fully fueled. That's the nature of the beast. When you look back at Tenerife and project forward to the A380 (as a participant), the cost of that potential accident justifies whatever expense needs to be outlaid - albeit only at selected airports (half O'Hare traffic density and upwards is as good a rule of thumb as any). (However initially they should pick a suitable airfield (with an existing incursion problem) and trial an installation. In no way could it ever be one-eighth as complex (or expensive) as the introduction of a new radar system. The software for it could be written by a school-kid.
Input Commentary / Suggestions: To the email address below please.