Haneda runway collision, Tokyo 2024: taxi clearance, readback and runway entry, a case study

On 2 January 2024, Japan Airlines Flight 516, an Airbus A350-900, collided after landing on runway 34R at Tokyo Haneda with a Japan Coast Guard DHC-8-300 that had entered and stopped on the runway. As of 6 November 2026, the investigation is still open, and the JTSB has issued first and second interim reports rather than a final report.

Controller workstation in a tower cab overlooking a runway — This case turns on one of aviation's simplest but most important barriers: do not cross a runway hold-short point without an explicit clearance.

Key facts

Date and local time	2 January 2024, about 17:47 JST
Aircraft type	Airbus A350-941 and Bombardier DHC-8-315
Registration	JA13XJ and JA722A
Operator and type of operation	Japan Airlines scheduled passenger flight, and Japan Coast Guard flight preparing to transport earthquake relief supplies
Route or purpose of the flight	JAL 516 from New Chitose to Haneda, and Coast Guard departure from Haneda
Phase of flight	Landing roll for the A350, runway entry and holding for the DHC-8
People on board	379 on the A350, 6 on the DHC-8
Outcome	The DHC-8 was destroyed; five of its six crew died and the captain was seriously injured. The A350 was also destroyed by fire. All 379 on the A350 evacuated; one passenger was seriously injured and four had minor injuries.
Investigating authority and case number	Japan Transport Safety Board, aircraft accident investigation concerning JA722A and JA13XJ
Report status	First interim report published 25 December 2024, second interim report published 25 December 2025, final report not yet published in the material reviewed

What happened

Taxi toward runway C: The Coast Guard aircraft taxied across the airport toward departure runway 34R. Earlier on the route, the crew had correctly read back and mutually confirmed other hold-short instructions, including hold short of runway 34L and hold short before taxiway C.
17:45:14: After transfer to Tower East, the Coast Guard aircraft received, “Number one, taxi to holding point C5.” Four seconds later the first officer read back, “To holding point C5, JA722A. Number one, thank you.”
How the crew took it: The first interim report says it is highly probable the captain and first officer recognized that instruction to taxi to the runway holding point as clearance to enter the runway. The captain later stated he understood the tower had instructed them to enter runway 34R from taxiway C5 and wait.
Checklist cue: Immediately after that instruction, the captain had the first officer perform the Before Takeoff Checklist, which in that operation was normally done after clearance to enter the runway.
17:46:13: The aircraft passed the runway holding point at C5, entered runway 34R, and stopped there.
At the same time: JAL 516 had already been cleared to land on runway 34R. The tower did not recognize that the Coast Guard aircraft had entered and was holding on the runway, and the A350 crew did not recognize it until just before the collision.
17:47: The landing A350 collided with the DHC-8 during the landing roll.

What the investigators are looking at

As of 6 November 2026, this remains an open investigation. The first JTSB interim report said it was highly probable that the Coast Guard captain and first officer recognized the instruction to taxi to holding point C5 as clearance to enter the runway, then entered and stopped on runway 34R.

The same report listed likely factors still under analysis. These included the crew's hurry to depart, the aircraft being told it was number one for departure, the captain's belief that the relief mission had priority, the captain's response to the first officer's readback, confirming only "C5" and "Number one", the reduced time created by the change to an intersection departure from C5, the crew's lack of awareness of the arriving A350, radio communications received while entering the runway, and the fact that the stop bar lights were not operational.

On the air traffic control side, the first interim report said a runway occupancy monitoring support warning was issued 7 seconds after the Coast Guard aircraft passed the holding point marking and continued until 1 second after the collision, but Tower East did not recognize the displayed warning. The warning was visual only at Haneda at the time, with no auditory alarm, and the JTSB said there were no regulations or curriculum-based training on how controllers should handle such a warning.

The second interim report said the JTSB was continuing analysis of the pilots' psychological factors, pilot-to-pilot and pilot-to-ATC communication, and visual aids for deciding whether to enter the runway. It added analysis items including fatigue and labor management of the captain, the captain not having flown the type within 30 days before the accident, the first officer correctly reading back the instruction while also performing a checklist normally associated with runway-entry clearance, the absence of a sterile cockpit rule at the Haneda Air Station, and the possibility that there was no mutual confirmation that final approach was clear before runway entry.

The chain of events

A runway collision almost never comes from one broken link. In this case, the JTSB's interim reports point to several barriers that may have failed or been weakened at the same time.

Hold-short misread: Investigators say it is highly probable the instruction to taxi to holding point C5 was understood on board as clearance to enter runway 34R. The first barrier was the clearance itself as heard and interpreted.
Sequencing as permission: The phrase “Number one” appears to have mattered. For a crew under time pressure, being first for departure may have reinforced an expectation of immediate runway entry, even though sequencing is not runway-entry clearance.
Readback without catch: The first officer’s readback matched the taxi-to-holding-point instruction, and no further tower-aircraft exchange followed. A correct readback is necessary, but this case shows it is not enough if the mental model in the cockpit is different.
Checklist cue: The captain called for the Before Takeoff Checklist immediately after the instruction. Investigators are examining whether that action helped lock in the crew’s belief that they had already been cleared onto the runway.
Runway entry barrier: The aircraft then passed the holding point and entered the runway. The second interim report says investigators are examining visual assistance for deciding whether to enter, and the first report notes the stop bar lights were not operational.
No final approach cross-check: The second interim report says investigators are examining the possibility that there was no mutual confirmation on board that the final approach path was clear before runway entry. That is a classic last-chance barrier.
Controller warning not noticed: The tower’s runway occupancy monitoring support system generated a visual warning shortly after the runway entry, but it was not recognized. The JTSB is examining the controllers’ continuous monitoring, the history of how the support system was introduced, and how rules and training for its use were actually implemented.

Pilot wearing a headset in a parked training aircraft cockpit — For student pilots, this case is fundamentally about phraseology, mutual confirmation, and stopping at the hold-short line until the clearance is explicit.

What to learn from it

This accident involved airline and Coast Guard crews at a major airport, but the lessons for a PPL or radio student are very direct. They sit in your Communications, Human Performance, and Operational Procedures training.

Taxi to holding point is not enter runway: A hold-short clearance means exactly that, stop at the holding point marking and wait. In your own flying, do not turn sequencing information, expectations, or urgency into a clearance that was never given.
Read back the limit, then believe your own readback: The first officer correctly read back “to holding point C5”. The student-pilot lesson is that readback is not only for ATC, it is also for you and anyone beside you in the cockpit. If your readback says holding point, your aircraft stops at the holding point unless and until a new clearance comes.
Number one means order, not authority: “Number one” can tell you who goes first. It does not authorize line-up, runway entry, or takeoff. Student pilots should separate sequencing words from clearance words every time they taxi.
Use a runway-entry challenge and response: Before crossing a hold-short line, say what the clearance is, point to the traffic threat, and confirm final is clear. The second interim report specifically says investigators are examining whether there was no mutual confirmation that final approach was clear before runway entry.
Do not let cockpit task flow rewrite the clearance: Checklists are helpful, but they can also anchor your thinking. If you start a checklist that you usually do after runway-entry clearance, pause and ask whether the actual clearance you received really matches that action.

Train what would have broken the chain

These learning goals from the PPL syllabus cover the points above. Train each one with lessons, radio scenarios and practice questions.

1
Communications 2.d.iii.1
The student should be able to specify which parts of messages need to be reread.
Open in the syllabus
2
Operational Procedures 2.b.4
The student should be able to describe procedures that prevent runway incursions (e.g., stop bars, clearances, prompt runway vacating, staying alert).
Open in the syllabus

Train it before you need it

Create a free account to work through these learning goals with lessons, radio scenarios and practice questions.