TCAS Resolution Advisory triggered by unauthorized climb in Pilatus PC12

Casualties unknown • 7 NM N/NE MOLUS, CH

A near-collision occurred near MOLUS when a Pilatus PC12 climbed unexpectedly due to autopilot issues, triggering a TCAS alert on a Crossair Europe Saab 340.

What happened

On May 16, 2001, at approximately 13:35 UTC, an air traffic incident occurred 7 NM N/NE of MOLUS. A private Pilatus PC12, registration HB-FOT, was operating a flight from Zurich to Valence. The aircraft had been cleared to maintain flight level 230. Simultaneously, a Crossair Europe Saab 340B, registration ECC757, was flying a commercial service from Marseille to Basel Mulhouse at flight level 240.

During the flight, the pilot of HB-FOT requested to maintain flight level 230 for a period of time. Meanwhile, the crew of ECC757 requested a slight heading change to avoid thunderstorm activity. Shortly after, the pilot of ECC757 reported a TCAS/ACAS Resolution Advisory (RA), indicating that the aircraft had encountered a conflict with opposing traffic. The investigation revealed that HB-FOT had climbed to flight level 234, encroaching on the altitude of the oncoming Saab 340B.

The investigation

Investigators examined the radar data and radio communications from the Geneva Area Control Centre (sectors INE and INS). The investigation established that the two aircraft passed with a minimum separation of 600 feet at a distance of 1.1 NM.

Air traffic controllers utilized the Short Term Conflict Alert (STCA) system, which alerted the radar controller to the proximity of the two aircraft. The investigation also reviewed the flight logs and the pilot's explanation regarding the aircraft's deviation from its assigned altitude. While the controllers and the crew of ECC757 did not file formal air traffic incident reports, the radar controller filed an official ATIR (Air Traffic Incident Report).

Probable cause

The incident was caused by the unexpected and uncontrolled climb of the Pilatus PC12, which occurred after the autopilot disconnected while the aircraft was navigating through a thunderstorm.

Frequently asked questions

What happened in the 2001-05-16 SAAB SF34 accident near 7 NM N/NE MOLUS, CH?

A near-collision occurred near MOLUS when a Pilatus PC12 climbed unexpectedly due to autopilot issues, triggering a TCAS alert on a Crossair Europe Saab 340.

What aircraft was involved and where did it happen?

The accident on 2001-05-16 involved a SAAB SF34, registration UNKNOWN, at 7 NM N/NE MOLUS, CH.

What was the probable cause of the accident?

The incident was caused by the unexpected and uncontrolled climb of the Pilatus PC12, which occurred after the autopilot disconnected while the aircraft was navigating through a thunderstorm.

Investigation report by the Swiss Transportation Safety Investigation Board (STSB / SUST). Original record: https://www.sust.admin.ch/inhalte/AV-berichte/A040.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.