FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN14FA099 · Canadair Ltd CL 600 2B16 601

5 Jan 2014 · Aspen, CO, United States

Canadair Ltd CL 600 2B16 601 · Accident: loss of control in flight during landing

From Tucson International Airport (TUS) to Aspen-Pitkin County Airport (Sardy Field) (ASE)

Report a problem

Event

NTSB case
CEN14FA099
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
1 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Canadair Ltd CL 600 2B16 601

Aircraft type
Canadair CL-600
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N115WF
Operator
Unknown
Onboard fatalities
Unknown
Route
From Tucson International Airport (TUS), Tucson, AZTo Aspen-Pitkin County Airport (Sardy Field) (ASE), Aspen, CO
Aircraft age
About 20 years (built 1994)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Landing
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Loss of control in flight
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Destroyed

Cause areas

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The airplane, with two flight crewmembers and a pilot-rated passenger on board, was on a cross-country flight. The departure and en route portions of the flight were uneventful. As the flight neared its destination, a high-altitude, terrain-limited airport, air traffic control (ATC) provided vectors to the localizer/distance measuring equipment (LOC/DME)-E approach to runway 15. About 1210, the local controller informed the flight crew that the wind was from 290º at 19 knots (kts) with gusts to 25 kts. About 1211, the flight crew reported that they were executing a missed approach and then requested vectors for a second approach. ATC vectored the airplane for a second LOC/DME-E approach to runway 15. About 1221, the local controller informed the flight crew that the wind was from 330° at 16 kts and the 1-minute average wind was from 320° at 14 kts gusting to 25 kts.

The initial part of the airplane's second approach was as-expected for descent angle, flap setting, and spoilers. During the final minute of flight, the engines were advanced and retarded five times, and the airplane's airspeed varied between 135 kts and 150 kts. The final portion of the approach to the runway was not consistent with a stabilized approach. The airplane stayed nose down during its final descent and initial contact with the runway. The vertical acceleration and pitch parameters were consistent with the airplane pitch oscillating above the runway for a number of seconds before a hard runway contact, a gain in altitude, and a final impact into the runway at about 6 g.

The weather at the time of the accident was near or in exceedance of the airplane's maximum tailwind and crosswind components for landing, as published in the airplane flight manual. Given the location of the airplane over the runway when the approach became unstabilized and terrain limitations of ASE, performance calculations were completed to determine if the airplane could successfully perform a go-around. Assuming the crew had control of the airplane, and that the engines were advanced to the appropriate climb setting, anti-ice was off, and tailwinds were less than a sustained 25 kts, the airplane had the capability to complete a go-around, clearing the local obstacles along that path.

Both flight crewmembers had recently completed simulator training for a type rating in the CL-600 airplane. The captain reported that he had a total of 12 to 14 hours of total flight time in the airplane type, including the time he trained in the simulator. The copilot would have had close to the same hours as the captain given that they attended flight training together. Neither flight crew member would have met the minimum flight time requirement of 25 hours to act as pilot-in-command under Part 135. The accident flight was conducted under Part 91, and therefore, the 25 hours requirement did not apply to this portion of their trip. Nevertheless, the additional flight time would have increased the crew's familiarity with the airplane and its limitation and likely improved their decision-making during the unstabilized approach. Further, the captain stated that he asked the passenger, an experienced CL-600-rated pilot. to accompany them on the trip to provide guidance during the approach to the destination airport. However, because the CL-600-rated pilot was in the jumpseat position and unable to reach the aircraft controls, he was unable to act as a qualified pilot-in-command.

Probable cause

The flight crew's failure to maintain airplane control during landing following an unstabilized approach. Contributing to the accident were the flight crew's decision to land with a tailwind above the airplane's operating limitations and their failure not to conduct a go-around when the approach became unstabilized.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN14FA099
Event ID
20140106X95024
Case number
CEN14FA099
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 301c13c77487146ae9af29a3ef1879e2005850583852b9812fb126bbe9c88cab; retrieved 2026-09-14T16:09:28.836Z.