Japan's airport control towers stop using 'No.1' instruction for plane takeoffs
Japan’s move to stop air traffic controllers from telling pilots they are “number one” for takeoff follows the fatal runway collision at Haneda, raising questions about how small phrasing ambiguities can contribute to disaster. Commenters examine how standardized phraseology (“cleared for takeoff,” “line up and wait”), language barriers, and cockpit visibility limits intersect with human error and situational awareness. Many argue that while pilots and controllers are heavily trained, growing traffic density makes stronger technological safeguards—such as surface radar, incursion alert systems, and better cockpit displays—increasingly necessary.
Context: Haneda Collision & “Number 1” Ban
- Thread centers on the Haneda runway collision where ATC told the Coast Guard plane: “Number 1, taxi to holding point C5.”
- Coast Guard crew reportedly believed they were cleared to enter the runway; they lined up and advanced power just before impact with the JAL A350 landing on the same runway.
- Japan’s decision to stop using “Number 1” before takeoff is seen as a temporary, precautionary measure; some expect it might return once operations normalize.
Phraseology, Miscommunication, and Human Factors
- Several commenters argue “Number 1” is normally harmless sequencing info and should not imply takeoff clearance; others say it may encourage misinterpretation, especially for less-experienced crews or in mixed military/civil environments.
- Strong emphasis that only explicit phrases like “cleared for takeoff,” “line up and wait,” and “hold short” should govern runway entry.
- Some suggest wording like “Taxi to C5 and hold” would have been clearer.
- Disagreement over how visible an aircraft on the runway is at night; some insist it should have been seen, others note cockpit blind spots and poor visual contrast.
- Multiple comments stress accidents are rarely just “pilot error” but chains of human and systemic failures.
Technology, Automation, and Runway Safety Systems
- Discussion of surface surveillance systems (ASDE‑X, RIMCAS, stop‑bar lighting, runway‑incursion systems).
- Haneda reportedly had relevant equipment, but some elements were NOTAMed as inoperative.
- Debate over adding automated runway-occupancy warnings to cockpits:
- Pro side: GPS/ADS‑B and radar already show positions; “hard but very doable,” and even imperfect systems could prevent some accidents.
- Caution side: predicting whether a runway “will be clear” is complex; naive systems would generate constant false alarms, overloading crews and being ignored.
- Cost and scale constraints noted: avionics upgrades are expensive; benefits are limited until nearly all aircraft are equipped.
Language, Numbers, and Communication Standards
- Broader exploration of how languages adapt words and numbers to reduce confusion (e.g., “niner,” “fife,” “tree,” “zwo,” alternative French and Japanese number forms).
- Clarified that English is strongly favored but not absolutely mandatory worldwide; local languages are sometimes used, though Japan is said to be strict about English on frequency.
- Some see “Number 1” as semantically ambiguous (“you’re next” vs “go now”), arguing for unambiguous, non-idiomatic alternatives.
Broader Critiques of ATC & Scaling
- Concern that a critical safety system still rests heavily on human memory and voice over unreliable radios, even as traffic density increases.
- Some call for a top-to-bottom modernization of ATC and ground control, while others warn against over-reactive complexity and emphasize careful, system-wide design.