Key Points
ANA Boeing 767 and government inspection aircraft came within 46 meters vertically at Haneda on August 4.
TCAS on ANA flight triggered resolution advisory, prompting emergency go-around and safe landing 25 minutes late.
Inspection aircraft's TCAS was not functioning; regulators did not classify encounter as serious incident.
Transport ministry will review inspection flight safety procedures at congested Tokyo airport.
An ANA Boeing 767 carrying 197 passengers and crew performed an emergency go-around on August 4 at 5:44 a.m. after its collision avoidance system detected a government inspection aircraft near Tokyo Haneda. The two planes came within 46 meters vertically and 1,106 meters horizontally before the ANA crew climbed to safety. Japan’s Civil Aviation Bureau ruled the encounter does not qualify as a serious incident, though questions remain about why the inspection plane’s TCAS was not functioning.
What happened in the airspace encounter
ANA Flight NH968 from Shanghai Pudong was descending to land on Runway 34R at 5:44 a.m. when a Cessna Citation CJ4 inspection aircraft (registration JA010G), operated by Japan’s Ministry of Land, Infrastructure, Transport and Tourism, departed from Runway 05 and turned right toward the Miura Peninsula. The inspection aircraft crossed the path of the landing ANA Boeing 767-300ER. The ANA crew’s Traffic Collision Avoidance System (TCAS) issued a Resolution Advisory (RA), an instruction to climb immediately. The ANA pilots executed the go-around, climbed to 4,000 feet, and were vectored for another approach. They performed a second go-around from 300 feet before landing safely at 6:10 a.m., 25 minutes behind schedule. All 197 passengers and crew disembarked without injury.
Why the inspection plane’s TCAS did not alert
The government inspection aircraft, known as “Doctor White,” had no TCAS alert during the encounter. According to the transport ministry, the inspection aircraft’s TCAS was not functioning at the time. TCAS II systems on Citation CJ4 aircraft are designed to progressively reduce resolution advisories as altitude decreases, and they stop issuing them entirely below roughly 1,000 feet above ground level. This safety feature prevents the system from commanding maneuvers that could be more dangerous at very low altitudes. At the moment of closest approach, the inspection aircraft was at approximately 295 meters altitude and the ANA aircraft at 330 meters, both below the TCAS RA threshold. Investigators are examining whether the non-functioning TCAS on the inspection aircraft contributed to the loss of separation.
Regulators rule it was not a serious incident
Japan’s Civil Aviation Bureau concluded on August 5 that the encounter does not qualify as a “serious incident” under the Aviation Act, despite the TCAS RA activation on the ANA flight. The bureau stated that both pilots confirmed they had the other aircraft in sight and did not perceive imminent danger. The closest separation occurred after the inspection aircraft had already passed in front of the ANA plane. Because both flight crews maintained visual contact and no imminent collision risk was judged to exist, the encounter fell outside the legal definition of a serious incident. The decision means the Japan Transportation Safety Board will not conduct a formal investigation. However, the transport ministry noted the situation was “not desirable” and stated it will work to improve the safety of the inspection aircraft’s operations.
Air traffic control and coordination questions
Air traffic controllers had informed the inspection aircraft’s crew that ANA Flight NH968 was approaching, according to the ministry. The inspection aircraft received takeoff clearance from Runway 05 at 5:41 a.m., and the conflict occurred three minutes later. The incident raises questions about how the two aircraft came to be on converging tracks despite controller notification. Weather conditions were clear with no visibility problems. The encounter has prompted scrutiny of coordination procedures between inspection flights and commercial traffic at Japan’s busiest airport, which handles both domestic and international operations on multiple runways simultaneously.
Impact on ANA and passenger operations
The August 4 incident was the second go-around for ANA Flight NH968. The first go-around was unrelated to the inspection aircraft encounter. The flight ultimately landed safely after the third approach. ANA reported the incident to the transport ministry as required. The airline has not issued a public statement on the encounter. For investors in ANA, the incident underscores operational risks at congested airports and the critical role of collision avoidance systems, though no injuries or aircraft damage occurred.
Final Thoughts
The August 4 near-miss at Haneda highlights the importance of functioning TCAS systems and clear air traffic coordination, even though Japan’s regulator ruled it not a serious incident. ANA’s crew responded correctly to the collision alert, and all passengers landed safely. The transport ministry will review inspection flight procedures.
FAQs
The aircraft came within 46 meters vertically and 1,106 meters horizontally. The ANA Boeing 767 was descending to land when the inspection plane crossed its path.
The inspection aircraft’s TCAS was not functioning at the time of the encounter. TCAS systems also stop issuing alerts below roughly 1,000 feet above ground level for safety reasons.
No. Japan’s Civil Aviation Bureau ruled on August 5 that it was not a serious incident because both pilots had the other aircraft in sight and did not perceive imminent danger.
ANA Flight NH968 carried 197 people total: 187 passengers and 10 crew members. All landed safely with no injuries.
Disclaimer:
The content shared by Meyka AI PTY LTD is solely for research and informational purposes. Meyka is not a financial advisory service, and the information provided should not be considered investment or trading advice.
About Author

Danny Kontos
Co FounderDanny Kontos has been a stock investor since 2007 and co-founded Meyka in 2023. He keeps a small, focused portfolio and only moves when the numbers are hard to argue with. He has waited years on a single position before. Before Meyka, he ran a web hosting company and a mortgage lending platform, so he knows what a well-run business actually looks like under the hood. This article did not come from a news cycle. It came from someone who has been watching this space for a long time.
What brings you to Meyka?
Pick what interests you most and we will get you started.
I'm here to read news
Find more articles like this one
I'm here to research stocks
Ask Meyka Analyst about any stock
I'm here to track my Portfolio
Get daily updates and alerts (coming March 2026)