The U.S. aircraft register, updated daily
Accidents · NTSB CEN16LA067 · Final report

Hawker 400 accident near Telluride, Colorado, December 23, 2015

On December 23, 2015 at about 9:15 pm local time, a Hawker 400, registered XAMEX, was substantially damaged in an accident during landing (landing roll) near Telluride, Colorado (Telluride airport). It was flown under foreign airline rules (Part 129). No one was hurt; 7 people were on board or involved. The weather was instrument conditions (cloud, fog or low visibility).

The NTSB's probable cause their words, unchanged

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.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
December 23, 2015 · about 9:15 pm local time
Place
Telluride, Colorado · Telluride · map
Type
Accident
Injuries
No one was hurt; 7 people were on board or involved.
Weather
instrument conditions (cloud, fog or low visibility)
Aircraft
Hawker 400 XP
Registration
XAMEX · no longer on the register · serial RK396
Damage
Substantial damage
Flight
Flight · foreign airline rules (Part 129)

The NTSB's narrative final · quoted from the NTSB record

The pilots were conducting an international chartered flight in the small, twin-engine jet with five passengers onboard.  Since the weather at the destination was marginal, the flight crew had discussed an alternate airport in case weather conditions required a missed approach at their destination. As the airplane neared the non-towered destination airport, the flight crew received updated weather information, which indicated 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 that they received 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 on the equipment that contained the information. At the time of the accident, 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. 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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Air traffic event during approach
  2. Ground collision during landing (landing roll) defining event

The NTSB's findings

  • cause Personnel issues › Action/decision › (general) › (general) › ATC personnel
  • cause Environmental issues › Operating environment › Air traffic/operating proc › (general) › Availability of related info
  • cause Environmental issues › Operating environment › Air traffic/operating proc › (general) › Effect on operation
  • cause Environmental issues › Operating environment › Air traffic/operating proc › Approach control procedure › Effect on operation
  • cause Environmental issues › Operating environment › Communication system › VHF/HF radio › Compliance w/ procedure
  • cause Personnel issues › Action/decision › Action › Lack of action › Pilot
  • cause Personnel issues › Task performance › Communication (personnel) › Lack of communication › Pilot
  • Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Low visibility › Effect on personnel
  • factor Personnel issues › Task performance › Workload management › (general) › ATC personnel
  • factor Environmental issues › Operating environment › Air traffic/operating proc › (general) › Availability of related info

Pilot

  • Certificate: airline transport pilot
  • Ratings: multi-engine land; instrument: airplane
  • Flight time: 7,113 hours in all; 1,919 in this make and model; 2,360 as pilot in command
  • Last flight review: October 8, 2015
  • Medical certificate: Class 1 (without waivers/limitations)
  • Seat: rgt
  • Injury: no injuries

Co-pilot

  • Certificate: airline transport pilot
  • Ratings: multi-engine land; instrument: airplane
  • Flight time: 8,238 hours in all; 1,412 in this make and model; 1,816 as pilot in command
  • Last flight review: August 31, 2015
  • Medical certificate: Class 1 (without waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 5,744.2 hours
  • Last inspection: continuous airworthiness programme, July 25, 2015
  • Landing gear: retractable
  • Engine 1: Pratt & Whitney JT15D (turbofan); 0 hours total
  • Engine 2: Pratt & Whitney JT15D (turbofan); 0 hours total

The flight

  • Departed from: KELP El Paso TX
  • Destination: KTEX Telluride CO
  • Flight plan: IFR
  • Runway 9, 7,111 ft by 150 ft
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Wind: from 100° at 3 knots
  • Visibility: 1.8 statute miles
  • Sky: overcast at 2,200 ft
  • Temperature: 23°F (-5°C), dew point 18°F (-8°C)
  • Altimeter: 29.50 inHg
  • Observation at 9:15 pm from KTEX

Injuries

FatalSeriousMinorNone
Flight crew2
Passengers5

Documents from the investigation the NTSB's docket: the evidence folder behind the report

11 documents, released by the NTSB on April 20, 2017. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.