What Happened
On July 31, 2008, East Coast Jets Flight 81 landed at Owatonna Degner Regional Airport in Minnesota, then attempted to take off again before the landing roll was over. The Hawker Beechcraft 125-800A, N818MV, left the runway end, became airborne beyond it, struck an antenna support structure, and crashed. Both pilots and all six passengers died.
The charter had departed Atlantic City, New Jersey, and was operating under Part 135. The captain flew while the first officer handled monitoring duties. An instrument flight plan had been active, but the crew canceled it after the captain reported the runway in sight. Visual weather prevailed at the time of the accident; that did not mean the runway was dry.
The arrival involved discussions about nearby precipitation and the weather radar display. The crew also repeatedly tried to contact the airport’s fixed-base operator about their arrival. During the approach, the first officer was arranging fuel and passenger details while the captain was communicating with air traffic control and configuring the airplane.
At 0942, the captain reported the runway in sight and canceled the instrument flight plan. Landing gear extension followed. The cockpit recording captured landing checklist items, but it also captured the first officer continuing the conversation about ground arrangements. The report identified poor coordination and cockpit discipline as contributing factors, and this overlap showed the workload the crew had created during the approach.
The airplane touched down on runway 30 at about 0945:04. About two and a half seconds later, a sound consistent with the airbrakes moving to OPEN was recorded. That position was not the same as the lift-dump configuration intended to help decelerate the airplane after landing.
At 0945:08, the first officer indicated that lift dump was set, then immediately corrected himself. The captain agreed it was not set. A sound consistent with movement of the handle into DUMP followed.
About ten seconds later, the recording captured a sound consistent with the airbrakes closing. The captain called for flaps, and engine noise increased. The landing roll had become an attempted go-around, with runway already consumed and the airplane needing to accelerate and change configuration again.
The airplane ran off the runway at about 0945:29. It lifted off about five seconds later, roughly 978 feet beyond the runway end. The localizer antenna support structure was about 1,000 feet beyond the runway. The airplane struck it and eventually came to rest in a cornfield about 2,136 feet from the runway end.
Witnesses described an initially normal-looking landing followed by increasing engine power near the end of the runway. Several saw water spray trailing the airplane during the rollout. Their accounts and the recorded sequence placed the decisive change after touchdown, during an increasingly constrained attempt to stop or fly again.
Investigation Findings
The NTSB identified the captain’s decision to attempt a go-around late in the landing roll, with insufficient runway remaining, as the probable cause. That finding was specific. A go-around from an approach and a late attempt to accelerate after landing were not interchangeable situations.
The lift-dump system mattered because this airplane did not have thrust reversers. Its system linked the airbrakes and flaps to reduce lift and help decelerate after landing. The normal OPEN airbrake position and the full DUMP position were distinct. The recording showed confusion about which condition the airplane had reached.
The report described the system’s sequence: the landing flaps had to be at 45 degrees, then the airbrake handle had to move up and aft into DUMP. That extended the flaps and airbrakes farther than their normal ranges. Returning the handle forward deactivated lift dump. These details explained why the crew’s callouts and handle movements were important evidence, rather than merely cockpit terminology.
But the NTSB did not reduce the accident to one switch or handle. The final decision occurred within a wider pattern involving the approach briefing, divided attention, incomplete coordination, and fatigue. The Board concluded that fatigue likely impaired both pilots’ performance. The word likely reflected its assessment of the evidence rather than a direct measurement of alertness in the cockpit.
The captain had about 3,600 total flight hours, including about 1,188 hours in Hawker 125-800A airplanes. The first officer had about 1,454 total hours and about 295 hours in the type. Those qualifications did not prevent the crew from becoming poorly coordinated during this arrival.
The airplane’s landing weight and center of gravity were within limits. Maintenance records did not reveal prior systemic discrepancies with the flight controls or wheel brakes. Those findings helped keep the explanation focused on the landing sequence and operational factors rather than an unsupported claim of a known brake defect.
The Board also included an institutional contributor: the FAA’s failure at the time to require crew resource management training and standard operating procedures for Part 135 operators. That was a finding about the requirements applicable to the accident, not a statement about today’s regulations.
For a pilot studying this flight, the useful point was where the options changed. Before touchdown, a discontinued approach could be planned and flown with altitude and an established flight configuration. During the landing roll, the remaining runway, speed, lift-dump state, and acceleration capability all had to support any decision to fly again. In this accident they did not.
NTSB Probable Cause
The captain’s decision to attempt a go-around late in the landing roll with insufficient runway remaining. Contributing to the accident were (1) the pilots’ poor crew coordination and lack of cockpit discipline; (2) fatigue, which likely impaired both pilots’ performance; and (3) the failure of the Federal Aviation Administration to require crew resource management training and standard operating procedures for Part 135 operators.
Safety Lessons
The following takeaways apply the investigation to flight planning and training. They do not replace the aircraft flight manual or instruction in the airplane.
- Brief the landing through the stop. Include runway condition, actual landing performance, touchdown expectations, deceleration equipment, and the aircraft-specific limits on a rejected landing. Do not let the phrase go-around substitute for a performance assessment.
- Protect monitoring during the arrival. Finish fuel and passenger coordination before the approach or defer it until parked. The monitoring pilot needs enough attention available to verify configuration and challenge deviations as they happen.
- Make configuration callouts verifiable. Train crews to confirm the actual indication and system state, including lift dump where installed. Couple that discipline with realistic fatigue decisions and the operator procedures applicable to the aircraft.
Watch the Full Analysis
Frequently Asked Questions
Q: What caused East Coast Jets Flight 81 to crash?
A: The NTSB identified the captain’s late go-around decision during the landing roll with insufficient runway remaining. Poor crew coordination, likely fatigue impairment, and deficiencies in required operator training and procedures contributed.
Q: Did the Hawker have thrust reversers?
A: N818MV did not have thrust reversers. It used a lift-dump feature involving the flaps and airbrakes to help decelerate after landing.
Q: Where did the airplane become airborne?
A: The NTSB performance study placed liftoff about 978 feet beyond the runway end, shortly before the airplane struck the localizer antenna support structure.
Sources and References
