Bombardier CL-600-2B16, Vineyard Haven, Mass., Sept. 27, 2009–The Challenger was substantially damaged during a hard landing at Martha’s Vineyard Airport at the end of a Part 91 flight from Denver. According to the crew, the landing was performed with 30 degrees of flap in a 24-knot crosswind with an approach speed of 135 knots.
Southwest Airlines Flight
The underwear bomber’s abortive attempt to blow up a Northwest/Delta flight from Amsterdam to Detroit quickly overshadowed aviation’s other lucky break this past Christmas season–American Flight 331 from Miami to Kingston, Jamaica, which slid off a rain-soaked runway, breaking the fuselage in three places and injuring scores of people.
Hawker Beechcraft King Air A100, Sandy Bay, Saskatchewan, Canada, Jan. 7, 2007–The Transportation Safety Board of Canada has recommended mandatory regular crew resource management (CRM) training for all operators in Canada as a result of the accident that destroyed the King Air after an aborted landing attempt.
Hawker Beechcraft Premier I, Leesburg, Va., Feb. 12, 2008–The probable cause of the accident was the airplane’s runway excursion during landing, following an encounter with ice, according to the Safety Board. The jet touched down after a normal approach near the threshold of the 5,500-foot-long runway at Leesburg Executive Airport at an airspeed of 100 knots.
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.
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).