Plane crash map Locate crash sites, wreckage and more

N911AE accident description

Missouri map... Missouri list
Crash location 39.123056°N, 94.592777°W
Nearest city Kansas City, MO
39.099727°N, 94.578567°W
1.8 miles away
Tail number N911AE
Accident date 28 Jan 2005
Aircraft type Learjet 35A
Additional details: None

NTSB Factual Report


On January 28, 2005, at 2217 Central Standard Time (CST), a Learjet 35A, N911AE, operated by Business Aviation Management Group Inc. (d.b.a. Million Air), overran runway 19 during landing rollout at Charles B. Wheeler Downtown Airport (MKC), Kansas City, Missouri. The airplane received substantial damage when it impacted airport property and terrain. Night instrument meteorological and contaminated runway conditions prevailed at the time of the accident. The Title 14 Code of Federal Regulations (CFR) Part 91 positioning flight was operating on an instrument rules flight plan with a filed alternate destination of Lincoln Airport (LNK), Lincoln, Nebraska. The pilot and copilot were uninjured. The flight originated from Salt Lake City International Airport (SLC), Salt Lake City, Utah, at 1905 Mountain Standard Time, and was en route to Kansas City International Airport (MCI), Kansas City, Missouri, when it diverted to MKC.

The positioning flight was to pick up five passengers at MCI for a return Title 14 CFR Part 135 flight to SLC. At 2102 CST, the Learjet 35A was on approach to MCI when a McDonnell Douglas MD83 slid off runway 19L at taxiway E during an after landing taxi resulting in the closure of MCI for approximately 90 minutes. The Learjet 35A then diverted to MKC.

A Federal Aviation Administration (FAA) partial transcript of transmissions from MKC Air Traffic Control Tower (TWR), N911AE, FLX745 (Cessna 210 Centurion), Airport Vehicles (ARPT) 5, 10, 24, 26, and MCI Approach Control (APP) follows.

2206:50 CST; TWR; and ah airport five

2206:59 CST; ARPT 5; airport five

2207:01 CST; TWR; airport five why don't you guys ahead ah start to ah exiting on runway one niner and all vehicles please report clear traffic on nine mile final

2207:03 CST; ARPT 5; airport five we copy

2207:10 CST; TWR; look like I am going to have three right in a row inbound and I'll get you guys going again

2207:12 CST; ARPT 24; airport twenty four is clear

2207:33 CST; FLX745; downtown tower flight express seven forty five on the I L S for one niner

2207:33 CST; ARPT 5; airport five is clear

2207:35 CST; TWR; flight express seven forty five downtown tower continue inbound at the present time I do have plows on the runway they will be exiting here shortly

2207:36 CST; FLX 745; ah roger flight express seven forty five

2207:37 CST; TWR; o k ah I had a couple of you are stepping on each other I know that twenty four is clear, twenty five is clear who else

2207:38 CST; ARPT 26; airport twenty six

2207:39 CST; ARPT 10; airport ten is clear

2207:41 CST; ARPT 5; airport five is clear

2207:47 CST; TWR; roger understand all vehicles are clear of the runway thank you hold short of runway one niner for landing traffic you can proceed onto runway three two one just remain clear of the intersection to runway one

2208:02 CST; TWR; flight express seven forty five is cleared to land on runway one niner and r v r is ah better than six thousand five hundred the runway has been plowed fifty feet either side of the centerline

2208:09 CST; FLX745; roger cleared to land flight express seven forty five understand they just plowed the runway

2208:24 CST; TWR; affirmative and once your down just ah I'd appreciate any pilot reports you can give me regarding ice and [braking] action

2208:30 CST; FLX745; roger flight express seven forty five

2208:41 CST; TWR; approach downtown

2208:43 CST; APP; approach

2208:45 CST; TWR; hey our runway one niner has been plowed fifty feet ah either side of the centerline

2208:46 CST; APP; o k

2208:47 CST; TWR; but I don't have a [braking] action yet

2208:48 CST; APP; alright t t

2208:49 CST; TWR; d x

2211:12 CST; FLX745; ah tower the ride down was pretty good there's quite a bit of fog right before you get to the runway though

2211:20 CST; TWR; roger thanks

2211:22 CST; FLX745; icing was just a trace of rime

2211:23 CST; TWR; roger thanks

2211:32 CST; N911AE; downtown tower lear jet one one alpha echo at two thousand six hundred on the I L S one niner

2211:38 CST; TWR; lear niner one one alpha echo downtown tower runway one niner cleared to land centurion ahead reported a trace of rime on the decent runway has been plowed fifty feet either side of the centerline

2211:48 CST; N911AE; o k ah cleared to land runway one niner and any [braking] reports

2212:00 CST; TWR; one alpha echo I am sorry I was on another frequency say again

2212:03 CST; N911AE; ah any [braking] reports on runway one niner one alpha echo

2212:06 CST; TWR; I'll have it for you in just a second

2212:07 CST; N911AE; thank you

2212:21 CST; TWR; flight express seven forty five how's the [braking] action

2212:22 CST; FLX745; ah we are just slipping just a little bit it's pretty good I'd say it's moderate to ah (unintelligible)

2212:27 CST; TWR; understand that breaking action is fair

2212:29 CST; FLX745; ah yea I'd call it fair

2212:35 CST; TWR; o k use caution down from there it hasn't been touched at all foxtrot looks like it's been plowed proceed into the ramp this frequency good night

2212:37 CST; FLX745; roger we'll stay with you flight express seven forty five

2212:43 CST; MKLC TWR; lear one alpha echo centurion that just landed reported [braking] action fair and I'd appreciate a [braking] action report from you also

2214:48 CST; N911AE; will do one alpha echo

2217:45 CST; TWR; lear one alpha echo tower

2217:48 CST; N911AE; o k we are all right

2217:49 CST; MKC TWR; o k are you off the runway sir

2217:51 CST; N911AE; we are

2218:04 CST; TWR; one alpha echo understand you are on your way to the ramp I don't have you in sight sir

2218:09 CST; N911AE; one alpha echo off the end of the runway pass the localizer

2218:14 CST; TWR; o k understand you are off the end of the runway

2218:18 CST; N911AE; we have departed the end of the runway through the perimeter fence

The copilot stated that following the closure of MCI, APP indicated at least a one-hour holding time was to be expected and numerous aircraft were diverting to Omaha. The copilot asked APP if MKC was available and was issued a clearance to MKC. He obtained Automated Terminal Information Service (ATIS) Echo, which reported a visibility of 1/2 statute mile (sm) with light snow and freezing fog. He told APP that MKC was below approach minimums and requested clearance to their alternate, LNK. After turning to a direct route to LNK, APP reported ATIS information Foxtrot as: 1 1/4 sm visibility in light snow and mist; sky condition as few at 1,000 feet above ground level (agl) and scattered at 1,800 feet agl with instrument landing system (ILS) 19 approach in use. They were then cleared to MKC.

The copilot stated that he heard TWR talking to an aircraft that just landed regarding braking action. The copilot stated TWR then reported braking action to the Learjet 35A as fair but did not specify the aircraft type that reported the braking action. The copilot stated that the approach was flown "stabilized" with a speed of REF + 30 until flaps were selected, then REF + 10 for the remainder of the approach, slowing to REF + 5 over the fence. The glideslope was followed to touchdown, about 1,000 feet from the threshold. The touchdown was made to the right. The deceleration appeared "normal" as brakes were applied, until 1,500 - 2,000 feet from the departure end of the runway when the speed appeared to "stabilize" about 20-30 knots. The copilot stated that he called for maximum braking and they both noted the brakes were "ineffective" at slowing the airplane and they knew that they would not stop by the end of the runway.

The pilot of FLX745 stated that he was cleared for approach and heard TWR asking the snow removal crew to get clear of the runway. As he broke out of the clouds, he could see the runway was not completely cleared; however, it was cleared enough to make a landing. As he neared the runway, he heard the Learjet 35A pilot asking for a braking action report, and TWR said to the Learjet 35A, "as soon as the Centurion lands, I will give you one." His landing was "normal," but he didn't use brakes until just prior to turning off runway 19 at taxiway D. He taxied with additional power to get through deeper snow on the taxiway because it had not been plowed. He taxied onto runway F, which was plowed, and completed his taxi to the ramp at hanger 8. As he was unloading cargo from the airplane, the pilot of FLX75 noticed that the Learjet 35A missed the high-speed turn off to the left of runway 19 and continued at a very high rate of speed until he heard a "thud" when the Learjet 35A impacted the airport fence.

The MKC assistant manager stated that he reported for work at 2130 CST with the intention to relieve the airport manager at 2300 CST.

About 2150 CST, the assistant airport manager contacted TWR to begin snow removal operations. TWR said that they could start with runway 01 as a Hawker was in the final stage of preflight in hangar 1. There was approximately 1 1/2 - 2 inches of wet snow on all surfaces. After a few passes plowing runway 01-19, about 50 feet of the runway 01-19 was plowed on either side of the centerline.

About 2205 CST, TWR called to clear the runway for the Hawker's departure. The Hawker departed from runway 01 without incident. After the Hawker's departure, snow removal was resumed and another 15 feet on either side of runway 01-19 centerline was cleared for a total of 130 feet.

About 2210 CST, TWR called to clear the runway for an arrival of a Cessna 210 Centurion. The assistant airport manager, who was also assisting in the snow removal operations, notified TWR that the runway was plowed 130 feet wide and the condition was 1/4 inch wet snow. The Cessna 210 Centurion landed and reported that the braking action was fair. TWR requested that the snow plowing equipment continue holding for another arrival. The assistant manager was holding on runway 19 ILS hold short marking, and the two snowplow trucks were on the [south] end of the taxiway G. It was foggy and the assistant manager was facing west while waiting for the Learjet 35A to land.

About 2215 CST, the Learjet 35A broke out of the fog, and the assistant airport manager noticed that the Learjet 35A was too high. The assistant manager continued monitoring the short final approach until the Learjet 35A crossed the runway 19 threshold. The assistant manager estimated that it appeared as if the Learjet 35A was still airborne beyond taxiway F before it disappeared in the fog.

About 2230 CST, a Notice to Airman (NOTAM) was issued closing MKC until further notice.

The MKC manager stated that he remained on duty at MKC throughout the afternoon and evening monitoring weather, IDS-4, Intellicast and Meteorologix radar depictions, weather briefings from National Weather Service Pleasant Hill, and MCI runway surface sensors.

At 1930 CST, MKC security completed a runway braking action test using a Tapley mechanical decelerometer; all runway 01-19 readings were above 40. The runways were wet with no measurable accumulation.

About 2000 CST, light snow with trace accumulation was observed at MKC.

At 2013 CST, an airport field condition NOTAM was issued. Runway 01-19 Tapley Mu values were reported as above 40 with wet snow on the runway. TWR was updated with a surface condition report and Mu values. IDS-4 was updated with a field condition report.

At 2030 CST, the MKC snow crew was called in.

At 2105 CST, MKC security completed a runway braking action test using a Tapley mechanical decelerometer. Runway 19 Mu values were reported as 21-22-22 with 1/2 inch wet snow on the runway.

At 2120 CST, an airport field condition report NOTAM was issued. Runway 19 Mu values were reported as 21-22-22 with 1/2 inch wet snow on the runway. TWR was updated with a surface condition report, Mu values, and was told "braking action was overall poor although this later information does not meet the criteria for NOTAM reporting purposes." IDS-4 was updated with a field condition report.

At 2200 CST, snow removal commenced on runway 01 with two plow trucks under the direction of the assistant manager.

About 2210 CST, TWR instructed snow removal personnel and equipment to clear runway 01-19 for two arrivals. The assistant manager advised TWR over ground radio that runway 01-19 was plowed full-length 130 feet wide down the centerline and reported surface conditions as 1/4 inch wet snow on the runway. The assistant manager also observed, but did not report, the pavement surface temperature appeared to be above freezing.

Shortly after clearing the runway, the assistant manager observed the first aircraft arrival, a Cessna 210 Centurion, land on runway 19. The assistant airport manager was momentarily off frequency and did not hear a braking action report but was told later that it was fair.

About 2215 CST, a Learjet broke out of the cloud base and made its approach to runway 19. The MKC assistant manager was holding short at the runway 19 ILS hold line and did not see the airplane touch down as he lost view of it in the darkness, snow, and fog. The assistant manager estimated that the airplane was still airborne south of taxiway F when he lost sight of it. The assistant manager then heard on ground frequency that the airplane ran off the departure end of runway 19. He advised TWR over ground radio that the MKC was closed and went to the scene.

Winds were reported as calm with 3/4 sm visibility and air temperature of 31 degrees Fahrenheit (F). MCI was reporting an air temperature of 31 degrees F with runway surface sensors reading 32.3 degrees F.

The airplane departed the runway roughly on centerline, traversed the gravel runway safety area, impacted the west side of the ILS localizer antenna array, impacted the chain link perimeter fence dragging approximately 180 feet of fence with it, crossed Lou Holland Drive, penetrated the steel guard rail on the south side of the road, and came to rest on the north slope of a flood levee within a few feet of one of the nonstandard approach lights for runway 01.


The 1977 Gates Learjet Corporation LR-35A, serial number 109, was certified under Title 14 CFR Part 25, Airworthiness Standards: Transport Category Airplanes. The airplane was registered to Keystone Aviation (d.b.a. Million Air) on September 13, 2000, and was listed under the operator's air carrier certificate.

The Weight and Balance/Equipment Change List for the airplane dated March 11, 2004, indicates a new empty weight and balance of 10,004.8 lbs and a gross weight of 18,300 lbs. On-scene cockpit documentation by the FAA revealed that the fuel totalizer indicated 3,285 lbs of fuel consumed from SLC to MKC. The operator reported the airplane had 6,200 lbs of fuel when it departed SLC.

The thrust reverser system was listed as inoperative on the minimum equipment list (MEL) as a "category C' item. According to the MEL, a category C item "shall be repaired within three (3) consecutive calendar days (72 hours), excluding the day the malfunction was recorded in the aircraft maintenance record/logbook."

The Discrepancy Item Master List shows an entry dated January 19, 2005, and an expiration date of January 28, 2005, listing the thrust reverser system. A letter by the Million Air Director of Maintenance, dated January 27, 2005, to the FAA's Salt Lake City Flight Standards District Office (FSDO), states that the expiration date of the thrust reverser MEL item was made due to "the test equipment needed to effect the repairs are currently unavailable and in the process of being made available to us. The new time for the completion of required repairs and expiration of the MEL will be Feb 7, 2005."

The Learjet 35A/36A Flight Manual contains an addendum for Learjet 35/35A/36/36A with Century Wing that contains wet/contaminated runway data. All contaminated runway landing performance data is based upon the following performance conditions:

-No tailwind component

-The runway gradient must be between -1.0% and +2.0%

-Flaps -40 degrees

-Anti-skid - On

Contaminated runway distance is calculated by mu

NTSB 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.

© 2009-2020 Lee C. Baker / Crosswind Software, LLC. For informational purposes only.