FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CHI05FA059 · Learjet 35A

28 Jan 2005 · Kansas City, MO, United States

Business Aviation Management Group Learjet 35A · Accident: overrun during landing

From Salt Lake City International Airport (SLC) to Charles B. Wheeler Downtown Airport (MKC)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
CHI05FA059
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
0 · 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
Instrument Meteorological Cond

Learjet 35A

Aircraft type
Learjet 35
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
N911AE
Onboard fatalities
Unknown
Route Possible conflict
From Salt Lake City International Airport (SLC), Salt Lake City, UTTo Charles B. Wheeler Downtown Airport (MKC), Kansas City, MO
Aircraft age
Not recorded
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 · landing roll
First occurrenceThe 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
Overrun
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Airport facilities, runway/landing area condition › Other

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The Learjet 35A received substantial damage on impact with airport property and terrain during a landing overrun on runway 19 (7,002 feet by 150 feet, grooved asphalt) at Charles B. Wheeler Downtown Airport (MKC), Kansas City, Missouri. The airplane was operated by a commercial operator as a positioning flight to Kansas City International Airport (MCI), Kansas City, Missouri, with a filed alternate destination of Lincoln Airport (LNK), Lincoln, Nebraska. Night instrument meteorological conditions prevailed at the time of the accident. LNK was a certificated airport with a snow removal plan and was served by runway 17R (12,901 feet by 200 feet, grooved asphalt and concrete). The flight was en route to MCI to pick up passengers and continue on as an on-demand charter but diverted to MKC following the closure of MCI. MCI was closed due to a McDonnell Douglas MD83 sliding off a taxiway during an after landing taxi on contaminated runway/taxiway conditions. MKC held a limited airport certificate that did not have a snow removal plan and was served by runway 19. Following a precision approach and landing on runway 19 at MKC, the Learjet 35A slid off the departure end of the runway and impacted airport property and terrain. The Learjet 35A was operated with inoperative thrust reversers as per the airplane's minimum equipment list at the time of the accident. About 1:05 hours before the accident, runway 19 Tapley values were recorded as 21-22-22 with 1/2 inch of wet snow. About 17 minutes before the accident, MKC began snow removal operations. About 7 minutes before the accident, the MKC air traffic control tower (TWR) instructed the snow removal vehicles to clear the runway for inbound traffic. TWR was advised by airport personnel that runway 19 was plowed and surface conditions were 1/4 inch of snow of snow; friction values were not taken or reported. While inbound, the Learjet 35A requested any braking action reports from TWR. The first airplane to land was a Cessna 210 Centurion, and the pilot reported braking action to the TWR as "moderate", which was then transmitted by TWR as "fair" from a Centurion in response to the Learjet 35A's query. The Cessna 210 Centurion pilot did not use brakes during landing and did not indicate this to TWR during his braking action report. The Aeronautical Information Manual states that no correlation has been established between MU values and the descriptive terms "good," fair," and "nil" used in braking action reports. The Airport Winter Safety and Operations advisory circular (AC) states that "pilot braking action reports oftentimes have been found to vary significantly, even when reported on the same frozen contaminant surface conditions." The AC also states, "It is generally accepted that friction surveys will be reliable as long as the depth of snow does not exceed 1 inch (2.5 cm) and/or depth of wet snow/slush does not exceed 1/8 inch (3mm). The Learjet 35A flightcrew calculated a landing distance 5,400 feet. Two of the cockpit voice recording channels, which normally contain the pilot and copilot audio panel information, were blank.

Probable cause

The contaminated runway conditions during landing. Contributing factors were the operation of the airplane without thrust reversers, flight to the planned alternate airport not performed by the flightcrew, and the insufficient runway information. Additional factors were the airport property and terrain that the airplane impacted.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CHI05FA059
Event ID
20050210X00173
Case number
CHI05FA059
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2005-01-29.
  • API snapshot SHA-256: 8cbfd23a4d86147654ac733881a7111c15a9163b114aca148de8336a78cf0d83; retrieved 2026-09-22T06:19:20.537Z.