TCAS resolution advisory prevents mid-air collision near Zurich

Casualties unknown • 10 NM East of KLO/DVOR, CH

An airborne collision avoidance system (ACAS) prevented a serious near-collision between a Boeing 737 and a Fokker 100 after air traffic controllers failed to identify a conflict.

What happened

On June 17, 2006, at approximately 10:20 UTC, a serious airprox incident occurred near Zurich, 10 NM east of the KLO/DVOR. The incident involved an Air Berlin Boeing 737-86J, registration D-ABAP, operating flight BER 1315, and a Hapag-Lloyd Express Fokker 100, registration D-AGPP, operating flight HLX 3680.

The Fokker 100 was flying from Cologne/Bonn to Genoa at a flight level of 250, a deviation from its planned altitude of 310 for operational reasons. Meanwhile, the Boeing 737 was descending through flight level 300 toward flight level 250. As the two aircraft approached a crossing point, the air traffic controller in the Zurich Upper Sector issued a descent instruction to the Boeing 737, directing it to descend to 250 with a high rate of descent.

Shortly before the Short Term Conflict Alert (STCA) triggered, the controller provided traffic information to the Fokker 100 crew. Simultaneously, the ACAS/TCAS systems on both aircraft generated Resolution Advisories (RA). The crew of the Boeing 737 performed a descent, while the Fokker 100 crew executed a climb to flight level 254. The aircraft crossed paths at approximately 10:19:59 UTC, with the Boeing 737 passing through 238 and the Fokker 100 at 253.

The investigation

SUST examined the communications and radar data from the Zurich Upper and Lower East sectors. The investigation focused on the air traffic controller's actions and the coordination between sectors. The investigation found that the controller in the Upper Sector was managing a high volume of traffic and was heavily focused on maintaining separation with another aircraft.

Radar data confirmed that the Boeing 737 was descending through the flight level of the Fokker 100. The investigation also reviewed the role of the Radar Planner, who was occupied with coordination tasks and failed to notice the developing conflict. The investigation concluded that the pilots of both aircraft responded immediately and correctly to the ACAS instructions, which prevented a collision.

Findings

  • The primary cause of the incident was that the air traffic controller failed to consider one of the aircraft in the traffic flow.
  • The controller was preoccupied with maintaining separation with a different aircraft, which led to overlooking the flight path of the Fokker 100.
  • The Radar Planner was engaged in heavy coordination work and did not provide the necessary redundancy to detect the conflict.
  • A high frequency of radio transmissions (14 exchanges in 95 seconds) may have contributed to the controller's loss of situational awareness regarding the Fokker 100.
  • The ACAS/TCAS resolution advisories were critical in preventing the collision.

Probable cause

The air traffic controller failed to monitor the flight path of the Fokker 100 while focused on managing other traffic, leading to a loss of situational awareness regarding the impending conflict.

Frequently asked questions

What happened in the 2006-06-16 FOKKER F100 accident near 10 NM East of KLO/DVOR, CH?

An airborne collision avoidance system (ACAS) prevented a serious near-collision between a Boeing 737 and a Fokker 100 after air traffic controllers failed to identify a conflict.

What aircraft was involved and where did it happen?

The accident on 2006-06-16 involved a FOKKER F100, registration D-AGPP, at 10 NM East of KLO/DVOR, CH.

What was the probable cause of the accident?

The air traffic controller failed to monitor the flight path of the Fokker 100 while focused on managing other traffic, leading to a loss of situational awareness regarding the impending conflict.

Investigation report by the Swiss Transportation Safety Investigation Board (STSB / SUST). Original record: https://www.sust.admin.ch/inhalte/AV-berichte/1982_d.pdf. This page is a structured re-presentation; facts and quotes are in the Swiss Transportation Safety Investigation Board (STSB), Switzerland.

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 40,000+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.