No fatalities

2015-12-23: Beechcraft Beechjet 400 (XA-MEX) — Aerolíneas Ejecutivas — Telluride, United States of America

Telluride, United States of AmericaLanding (descent or approach)

On December 23, 2015, a Beechcraft Beechjet 400 (registration XA-MEX) operated by Aerolíneas Ejecutivas was involved in an aviation accident near Telluride, United States of America during landing or approach. No fatalities were reported. Investigators recorded the probable cause as: The limitations of the air traffic control equipment that prevented the controller's timely recognition of NOTAM information that was effective immediately and resulted in the issuance of an approach clearance to a closed runway. This summary draws on records from the Bureau of Aircraft Accidents Archives (B3A).

Sourcesthe Bureau of Aircraft Accidents Archives (B3A)Primary reportUpdated 1781192611Data APIEditorial standards

A chartered twin-engine jet with five passengers landed on a closed runway and collided with a snow removal vehicle. The controller did not timely recognize a closing NOTAM due to equipment limitations, and pilots did not monitor the airport's common traffic advisory frequency.

Accident Sequence

The pilots were conducting an international chartered flight in a small, twin-engine jet with five passengers onboard. The weather at the destination was marginal, so the flight crew had discussed an alternate airport in case conditions required a missed approach. As the airplane neared the non-towered destination airport, the flight crew received updated weather information indicating that conditions had improved.

Upon contacting the center controller, the crew was asked if they had the weather and NOTAMs for the destination airport. The crew reported receiving the current weather information but did not state if they had NOTAM information. The controller responded by giving the flight a heading for the descent and sequence into the airport. The controller did not provide NOTAM information to the pilots.

About 2 minutes later, airport personnel entered a NOTAM via computer closing the runway, effective immediately, for snow removal. Although the NOTAM was electronically routed to the controller, the controller's system was not designed to automatically alert the controller of a new NOTAM; the controller needed to select a display screen that contained the information. At the time, the controller's workload was considered heavy.

About 8 minutes after the runway closure NOTAM was issued, the controller cleared the airplane for the approach. The flight crew then canceled their instrument flight plan with the airport in sight but did not subsequently transmit on or monitor the airport's common traffic advisory frequency, which was reportedly being monitored by airport personnel and the snow removal equipment operator. The airplane landed on the runway and collided with a snow removal vehicle about halfway down the runway. The flight crew reported they did not see the snow removal equipment.

Contributing Factors

The accident scenario is consistent with the controllers not recognizing new NOTAM information in a timely manner due to equipment limitations, and the pilots not transmitting or monitoring the common traffic advisory frequency. Additionally, the accident identifies a potential problem for flight crews when information critical to inflight decision-making changes while en route, and problems when controller workload interferes with information monitoring and dissemination.

Probable Cause

Probable cause (official findings): The limitations of the air traffic control equipment that prevented the controller's timely recognition of NOTAM information that was effective immediately and resulted in the issuance of an approach clearance to a closed runway. Also causal was the pilots' omission to monitor and transmit their intentions on the airport common frequency. Contributing to the accident was the controller's heavy workload and the limitations of the NOTAM system to distribute information in a timely manner.