American Airlines Flight 331

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
American Airlines Flight 331
260px
N977AN at LAX in April 2007, 2 years and 8 months before the accident.
Accident summary
Date 22 December 2009
Summary Runway overrun on landing due to pilot error in inclement weather
Site Kingston, Jamaica
Lua error in package.lua at line 80: module 'strict' not found.
Passengers 148[1]
Crew 6[1]
Injuries (non-fatal) 85[1]
Fatalities 0[1]
Survivors 154 (all)[1]
Aircraft type Boeing 737-823
Operator American Airlines
Registration N977AN
Flight origin Ronald Reagan Washington National Airport
Stopover Miami International Airport
Destination Norman Manley International Airport

On 22 December 2009, an American Airlines Boeing 737-800, operating American Airlines Flight 331 (Washington, D.C.MiamiKingston, Jamaica) and carrying 148 passengers and six crew, overran the runway on landing at Kingston in poor weather. The plane continued on the ground outside the airport perimeter and broke apart on the beach, causing injuries.

Factors contributing to the crash include the speed of the aircraft upon landing and the plane touching down more than 4,000 feet from the start of the runway. Contributing factors included American Airlines' failure to provide training on tailwind landings, and the FAA's failure to implement the NTSB's previous recommendation, following a previous fatal accident involving a tailwind landing attempt, that the FAA require commercial operators to train flight crews on tailwind landings.

Aircraft

The aircraft involved was a Boeing 737-823, registration N977AN.[2] The aircraft had manufacturer's serial number 29550 and made its first flight on 30 November 2001.[3] The aircraft made its first flights under registration N1786B and was delivered to American Airlines on 20 December 2001.[4]

Accident

Hull of American Airlines 331

The flight originated at Ronald Reagan Washington National Airport, Washington, D.C., with a stopover at Miami International Airport, Miami, Florida.[5] At 22:22 local time (03:22, 23 December UTC), the Boeing 737-823 skidded during landing on runway 12 and overran the pavement, sustaining serious damage.[2] Heavy rain was reported at the time.[6][7] After the accident, a special weather report was issued.[8]

Some passengers indicated cabin service was suspended several times during the flight, before being cancelled outright due to turbulence; others report the jet may have landed long on the runway.[9]

It was also announced that some of the airport's approach lights were not working at the time of the accident.[10] Jamaican officials downplayed the role of the malfunctioning lights in the crash, noting that aircrews had been notified and that the actual runway was properly lit.[11] The ground-based navigation aids were evaluated by a check aircraft after the accident and were determined to be functioning normally.[12]

The aircraft sustained substantial damage during the accident, with the entire fuselage fracturing forward and aft of the wing, one wing losing an engine and the other its winglet tip, and the nose section being crushed. The landing gear failed and put the aircraft on its belly. Its momentum carried it through the perimeter fence at freeway speeds,[13] and across Norman Manley Highway before finally coming to rest upright, within meters of Kingston's outer harbor and the open Caribbean Sea.[2] The 737 was damaged beyond economic repair.[14]

Response and investigation

Although the airport was closed after the accident, delaying about 400 travelers, it later re-opened with a reduced runway length available due to the tail section wreckage. Larger flights were diverted to Montego Bay's Sangster International Airport for two days.[15]

An investigation into the accident was launched by the National Transportation Safety Board. They sent a team to assist the Jamaica Civil Aviation Authority officials in the investigation.[16] American Airlines also sent a crash team to assist the other investigators.[17]

Later reports showed the crew had contacted Jamaica Air Traffic Control to request the Instrument Landing System approach for Runway 12, the designated runway broadcast by the Automatic Terminal Information Service for arrivals that night. They were, however, advised of tailwind conditions on Runway 12 and offered a circling approach for landing on Runway 30. "The crew repeated their request for Runway 12 and were subsequently cleared to land on that runway with the controller further advising the crew that the runway was wet."[18]

Jamaican Director General of Civil Aviation Col. Oscar Derby, stated in the week following the accident, that the jet touched down about halfway down the 8,910-foot (2,720 m) runway. He also noted that the 737-800 is equipped with a head-up display. Other factors that were under investigation included "tailwinds, and a rain soaked runway;" the runway in question was not equipped with rain-dispersing grooves common at larger airports. The aircraft held a relatively heavy fuel load at the time of landing; it was carrying enough fuel for a roundtrip flight back to the US.[13]

The FDR later revealed that the aircraft touched down some 4,100 feet (1,200 m) down the 8,910-foot (2,720 m) long runway. Normally touchdown would be between 1,000 feet (300 m) and 1,500 feet (460 m). The aircraft was still traveling at 72 miles per hour (116 km/h) when it departed the end of the runway. The aircraft landed with a 16 miles per hour (26 km/h) tailwind, just within its limit of 17 miles per hour (27 km/h).[19]

After the crash it was announced American Airlines was involved in an FAA review of company landing procedures following three landing incidents in two weeks; in the other two instances plane wingtips touched the ground during landing.[20] During the NTSB's investigation, the flight crew informed the NTSB in post-accident interviews that they had not received any training on conducting landings in tailwind conditions.[1] In addition, the NTSB was told by other American Airlines pilots that they were not given simulator training on tailwind landings or given guidance about runway overrun risks associated with tailwind landings.[1]

Passenger details

According to the U.S. State Department, 76 of the passengers on board were Americans.[11]

Although 92 people were taken to the hospital, there were no life-threatening injuries reported.[21]

Reports from Jamaica indicate that as of December 28, 2009, most passenger and crew property was yet to be returned due to the investigation; American Airlines provided each passenger $5,000 to compensate for the lengthy quarantine of baggage.[22]

Aftermath

On December 7, 2011, the NTSB issued a safety recommendation based on the results of its investigation into the crash of Flight 331.[1] The NTSB recommended that the FAA take actions to ensure adequate pilot training in simulator training programs on tailwind approaches and landings, particularly on wet or contaminated runways, and revise its advisories on runway overrun prevention to include a discussion of risks associated with tailwind landings.[1]

The NTSB also restated its previous recommendation, made following the crash of Southwest Airlines Flight 1248, that the FAA require commercial airline pilots to perform arrival landing distance assessments which include a conservative safety margin before every landing. The NTSB noted that while the FAA had proposed such a rule, operators were still not required to comply and many operators, including American Airlines, were not at the time of the Flight 331 crash.[1] As a result, the NTSB's safety recommendation was reiterated and reclassified as "Open—Unacceptable Response."[1]

On May 2, 2014, the JCAA issued its final report.[23] The final investigation report identified multiple causes and contributing factors to the accident, which included:

  • Flight 331's flight crew was not provided with an accurate and current report on the runway conditions at Kingston.
  • The flight crew did not review the approach options, and as a result, were not aware of a standing water warning at the Kingston airport and did not select the most suitable runway for landing.
  • The flight crew decided to land in heavy rain on a wet runway in a tailwind close to the tailwind landing limit.
  • The flight crew did not use the maximum level of autobrake or flaps available.
  • The aircraft touched down over 4,000 feet from the runway threshold.

Like the NTSB, the JCAA also recommended that flight crews be required to perform arrival landing distance assessments which include a conservative safety margin before every landing, and that actions should be taken to require appropriate flight crew guidance and training regarding tailwind landings.[23]

The pilots' failure to abort the landing and climb to go around has been compared to the later fatal crash of Asiana Airlines Flight 214.[24] In the Asiana Airlines incident, the pilot failed to abort the landing and initiate a "go-around" until it was too late to prevent the crash.[25]

See also

References

  1. 1.00 1.01 1.02 1.03 1.04 1.05 1.06 1.07 1.08 1.09 1.10 Lua error in package.lua at line 80: module 'strict' not found.
  2. 2.0 2.1 2.2 Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. METAR MKJP 230300Z 32008KT 33000 +SHRA BKN014 FEW016CB SCT030 BKN100 21/20 Q1014 RETSRA Wunderground (Translation)
  8. SPECI MKJP 230325Z 32011KT 22000 +SHRA BKN014 FEW016CB SCT030 BKN100 21/19 Q1014 RETSRA Wunderground (Translation)
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. 11.0 11.1 "'Best Christmas' for Pilot of Jet That Crashed in Jamaica." Associated Press at Fox News. Saturday December 26, 2009. Retrieved on December 27, 2009.
  12. http://www.jcaa.gov.jm/NEWS_UPDATES/JCAA%20PRESS%20RELEASE%20FOR%20AMERICAN%20AIRLINES%20FLIGHT%20331%20ACCIDENT%20INVESTIGATION%20.pdf
  13. 13.0 13.1 Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. 23.0 23.1 Lua error in package.lua at line 80: module 'strict' not found. (Archive)
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. Lua error in package.lua at line 80: module 'strict' not found.

External links

External image
image icon Aerial photos of the crashed aircraft at Marvhamm.com