JAL A359 at Tokyo collided with Coast Guard DH8C on runway and burst into flames
A Japan Airlines A350 collided with a Japan Coast Guard Dash‑8 on the runway at Tokyo’s Haneda Airport, destroying both aircraft and killing five crew on the smaller plane, yet all 379 people on the airliner escaped. Commenters examine how design choices like composite airframes, 90‑second evacuation standards, cabin procedures, and passenger behavior (e.g., not taking luggage, following crew directions) contributed to the outcome. They also debate likely causes such as runway incursion and communication failures, and whether more automation or ground‑based safety systems should supplement traditional radio- and human-centered air traffic control.
Accident context & ATC communication
- Thread agrees: JAL A350 landed on Haneda runway 34R and struck a Japan Coast Guard Dash‑8 that was already on the runway; all 379 on the A350 survived, 5 of 6 on the Dash‑8 died.
- LiveATC timestamps shared: A350 was cleared to land and read back correctly; the Dash‑8 later received taxi instructions, but what exactly it was cleared to do is unclear from the low‑quality recording.
- Several note that, under standard phraseology, nothing short of “cross”, “line up and wait”, or “cleared for takeoff/land” authorizes crossing the hold short line. Some suspect a runway incursion by the Dash‑8, but emphasize the investigation isn’t out.
- Video analysis suggests the Dash‑8 was lined up on the runway for 40+ seconds before impact; some find it surprising neither tower nor A350 crew detected it, but visibility and perspective are debated.
- Runway stop‑bar/guard lights at Haneda were reportedly out of service, removing one safety layer.
Evacuation performance & passenger conduct
- Many call the evacuation remarkably successful: ~400 people off a burning widebody with only minor injuries, slides used, exits on fire side not deployed.
- Others initially claim it was “handled terribly” (no PA order, confusion), but later reports say the PA system was damaged, cabin crew used megaphones/voice, first focused on keeping people seated until safe exits were identified.
- Video from inside shows passengers seated calmly in smoke until instructed; several see this as evidence of good crew control and passenger discipline.
- Strong praise for passengers not taking roll‑aboard luggage, contrasted with Western evacuations where bags and selfies appear in footage.
- Practical advice repeated: keep shoes on, and keep passport/ID, phone, and a payment method on your person; everything else is expendable. Small medically critical items should be on‑body, not in overheads.
Aircraft design, fire, and certification
- Multiple comments highlight how well the carbon‑fiber A350 structure held up after striking another aircraft and being doused in burning fuel.
- The 90‑second evacuation certification rule (with half the exits blocked, in the dark, cabin cluttered) is discussed and credited as crucial; examples like the A380 evacuation test and older cabin‑fire accidents are referenced.
- Debate over whether composite flammability is a serious concern; this event is seen by some as strong evidence current designs work as intended.
Electronics, distraction, and human factors
- Long sub‑thread on whether banning devices during takeoff/landing improves survival:
- One side argues cognitive load and context‑switching mean phones could slow evacuation; cites seconds‑matter examples and evacuation standards.
- Others note passengers on JL516 were actively filming on phones yet still evacuated in time; argue that boredom, sleep, or reading are equally “distracting”, and that in real emergencies people rapidly refocus.
- Another tangent critiques the “everything is 50% because it either happens or not” way of talking about risk as a probability fallacy; micromorts and realistic risk trade‑offs (flying vs driving) are discussed.
Runway safety technology & automation
- Several ask why ATC still relies on analog voice, and propose:
- Digital, authenticated clearances to aircraft computers.
- “TCAS for runways” that locks a runway to one aircraft and warns others.
- Systems that integrate ATC, airport lighting, and on‑board avionics.
- Others push back:
- Aviation is already extremely safe; new automation must meet that bar and avoid new failure modes and complacency.
- Mixed fleets (old GA planes, ground vehicles, military/coast guard aircraft) and global infrastructure make rapid universal upgrades hard.
- Existing systems already address some of this: stop‑bars, Runway Status Lights, RIMCAS/ARIWS, surface radar (ASDE‑X), and on‑board runway awareness systems.
- It’s noted that Haneda has an advanced runway‑status system, but part of it (stop‑bars) was reportedly inoperative at the time.
Cultural and operational observations
- Multiple commenters credit Japanese norms of orderliness and rule‑following for the calm, bag‑free evacuation; some compare this favorably to US/European incidents.
- Others caution against over‑romanticizing culture; point to disasters where excessive deference to authority cost lives, and to the fact that some passengers on JL516 reportedly still tried to retrieve bags before being stopped.
- Discussion touches on window shades (open for external visibility and eye adaptation), masks (ordinary masks seen onboard are not useful against cabin fire smoke), and ARFF response times (claims of “six minutes” are disputed; exact timeline remains unclear).