A serious runway-incursion-adjacent event unfolded at Tokyo Haneda Airport in the early morning hours local time, involving ANA Flight 968, a Boeing 767-300 arriving from Shanghai, and a Japan Civil Aviation Bureau (JCAB) Cessna Citation performing what appears to have been a navigation aid calibration flight. According to flight-tracking data and ATC audio circulating on social media, the Citation departed Runway 05 and, rather than climbing per standard departure procedures, executed a sharp 180-degree turn while remaining low—consistent with the low-altitude flight profile typical of ILS/VOR calibration sorties. This maneuver brought it into proximity with the ANA 767, which was on short final to Runway 34R, the same runway where the January 2024 Japan Airlines A350/Coast Guard Dash-8 collision occurred. Reported lateral separation was on the order of 20 meters (roughly 75 feet), though cross-referencing FlightRadar24 data suggests actual planar separation may have been closer to a mile, indicating the vertical/lateral geometry made the encounter appear more alarming in the moment than the raw track data alone would suggest. Both aircraft maneuvered to avoid conflict, and ATC recordings capture what is very likely a TCAS Resolution Advisory (RA) alarm, prompting the 767 to execute a go-around—reportedly twice.
For working pilots, several elements of this event warrant attention regardless of the exact separation distance ultimately confirmed by investigators. First, the presence of an audible RA on the recording is significant: RAs are triggered only when TCAS calculates that a collision is imminent absent corrective vertical maneuvering, and by design they represent one of the last layers of defense before ATC separation standards and see-and-avoid procedures. A double go-around by a widebody on short final, combined with an RA, is not a routine occurrence and will almost certainly draw scrutiny from the Japan Transport Safety Board given the post-Haneda-collision environment. Second, the apparent divergence from standard departure profile—a low, non-climbing turn from a runway feeding directly into approach corridors for the parallel/intersecting runway—raises questions about whether the calibration flight was properly sequenced, whether ATC coordination between tower and approach control accounted for the aircraft's unusual profile, and whether controllers had adequate traffic awareness given the aircraft's non-standard trajectory relative to a "normal" departure.
This incident lands in a context where Haneda's runway safety culture is already under intense scrutiny. The January 2024 collision between a JAL A350 and a Japan Coast Guard Dash-8 on Runway 34R, which killed five Coast Guard crew members, exposed gaps in runway incursion detection, controller phraseology, and crew read-back verification at one of the world's busiest airports. Japanese authorities have since pushed reforms around runway status lights, incursion alerting systems, and controller workload management. An event—even a non-collision one—involving the same runway just over a year and a half later, with a government-operated aircraft again implicated, will likely intensify pressure on JCAB and Haneda's air traffic organization to demonstrate that systemic fixes are actually reducing risk rather than merely adding procedural layers.
More broadly, the episode is a reminder that TCAS RA events, while rare, remain one of the most valuable real-world data points for evaluating separation assurance at high-density airports. Airline pilots operating into slot-constrained, multi-runway environments like Haneda, Heathrow, or JFK should treat this as reinforcement of standard TCAS RA response discipline—prompt, full compliance with RA guidance without hesitation, followed by prompt reporting. For flight operations and safety departments, the case underscores the importance of scrutinizing non-standard aircraft operations (calibration flights, ferry flights, or state aircraft with atypical profiles) sharing airspace with high-frequency commercial traffic, and ensuring ATC coordination protocols explicitly account for aircraft that will not follow textbook departure or arrival profiles. Until JTSB issues findings, operators should treat the lateral-separation figures circulating online as provisional, but the confirmed RA and go-around sequence alone justify treating this as a genuine safety event worth monitoring closely.