GATES LEARJET 25C, LEXINGTON, KY.,– AUG. 30, 2002–At 1:07 p.m. EDT Learjet 25C N24CP, on a Part 135 air-ambulance flight, overran Runway 4 while landing at Lexington (Ky.) Blue Grass Airport (LEX). The aircraft was destroyed, the patient was killed and the captain, first officer, flight nurse and another passenger were seriously injured.
Southwest Airlines Flight
BOEING 737-300, BURBANK, CALIF., MARCH 5, 2000–At about 1811 PST Southwest Airlines Flight 1455, a Boeing 737-300 (N668SW), overran the departure end of Runway 8 after landing at Burbank-Glendale-Pasadena Airport (BUR). The airplane touched down traveling approximately 182 kt, and about 20 sec later, traveling approximately 32 kt, collided with a metal blast fence and an airport perimeter wall.
It is usually easier to find fault with a flight crew during an ensuing accident investigation than it was for the crew to make the right decisions instantly as the event unfolded. However, some accidents reveal procedural flaws that forge the first link in a chain of events long before a critical situation arises.
One of the pilots keyed the microphone and shouted, “Brakes, brakes!” shortly before the Careflight Learjet 25 he was in went off the end of the runway and crashed, according to the NTSB’s preliminary report of the August 30 accident. The accident killed one passenger and seriously injured the pilots, a flight nurse and another passenger.
The captain admitted that his aircraft was hot and high on the approach and that he ignored the first officer’s repeated warnings to go around, according to the NTSB’s preliminary report of the May 1 runway overrun accident at Baltimore-Washington International Airport involving a Flight Options Beechjet 400A (N498CW).
Still concerned about landing overrun accidents, the FAA published a new Advisory Circular (91-79) on November 6 to advise pilots and operators about how to avoid such mishaps. While the circular is not mandatory, the FAA recommends that commercial and Part 91 business jet operators incorporate the material into their operations manuals or appropriate documents such as standard operating procedures (SOPs).
RAYTHEON BEECH 400A, BALTIMORE, MD., MAY 1, 2002–Beechjet N498CW, a fractionally owned and operated airplane managed by Flight Options, was substantially damaged during a landing overrun at Baltimore-Washington International Airport. No injuries were reported. The NTSB blamed the captain’s failure to go around.
CESSNA CITATION S550, BIG BEAR, CALIF., AUG. 13, 2002–The NTSB determined that the probable cause of the Citation runway accident was the pilot’s failure to obtain the proper touchdown point, which resulted in an overrun.
The FAA issued Advisory Circular 91-79 for pilots and operators of turbine-powered airplanes to identify, understand and mitigate risks associated with runway overruns during landing. According to FAA and NTSB data, runway overruns during landing account for about 10 incidents or accidents every year, with many accidents resulting in fatalities.
The NTSB last month made an “urgent” recommendation to the FAA in response to the December 2005 fatal runway overrun at Chicago Midway Airport, calling for the agency to require operators to conduct arrival landing-distance assessments before every landing based on existing performance data and actual conditions, and to incorporate a safety margin of at least 15 percent.