Boeing 737 Safety Record
Complete NTSB accident and incident history. 1188 events recorded from 1982 to 2026.
| Date | Location | Reg# | Severity | Damage | Probable Cause |
|---|---|---|---|---|---|
| Oct 19, 2009 | Manchester, UK | G-CELI | Incident | — | Investigation pending |
| Oct 02, 2009 | Kuching, MY | 9M-MMR | Incident | minor | Investigation pending |
| Sep 29, 2009 | Birgi, Trapani, Sicily, Italy, IT | EI-DWD | Incident | minor | Investigation pending |
| Sep 24, 2009 | Bologna, IT | TF-BBD | Incident | — | Investigation pending |
| Sep 08, 2009 | Los Angeles, CA | N670SW | Incident | minor |
The failure of the right main landing gear inboard axle due to fatigue cracking as a result of fretting damage in one of the brake mounting bolt holes…The failure of the right main landing gear inboard axle due to fatigue cracking as a result of fretting damage in one of the brake mounting bolt holes. |
| Aug 21, 2009 | Launceton, Tasmania, AS | VH-VOC | Incident | — | Investigation pending |
| Aug 19, 2009 | Coca, Ecuador, EC | HC-CFD | Incident | minor | Investigation pending |
| Aug 10, 2009 | Tokyo, JA | JA56AN | Incident | substantial | Investigation pending |
| Jul 17, 2009 | Stansted, UK | EI-DLJ | Serious (1) | — | Investigation pending |
| Jul 15, 2009 | Charlotte (CLT), NC | N506AU | Incident | minor |
The failure of the left hand main landing gear was caused by heat induced cracks resulting from abusive grinding/polishing of the chrome plate that wa…The failure of the left hand main landing gear was caused by heat induced cracks resulting from abusive grinding/polishing of the chrome plate that was applied during the last overhaul. |
| Jul 13, 2009 | Charleston, WV | N387SW | Incident | substantial | Fuselage skin failure due to preexisting fatigue at a chemically milled step. |
| Jun 14, 2009 | Diyarbakir, OF | TC-TLA | Minor | — |
An uncommanded elevator surface deflection as a result of a left elevator PCU input arm assembly jam due to FOD lodged between the input arm assembly …An uncommanded elevator surface deflection as a result of a left elevator PCU input arm assembly jam due to FOD lodged between the input arm assembly and the PCU housing. The FOD was a roller element from an elevator upper torque tube output crank bearing, but how or when the roller element liberated from its bearing assembly could not be determined. Contributing to the survivability of this incident was the flight crew’s immediate actions in response to the elevator control system jam. |
| Jun 12, 2009 | Marrakesh Airport, MO | CN-RMX | Incident | — | Investigation pending |
| Jun 03, 2009 | Cleveland, OH | N299WN | Incident | — |
The ground controller did not issue taxi instructions in accordance with FAA Order 7110.65, paragraph 3-7-2. The local controller did not scan the ru…The ground controller did not issue taxi instructions in accordance with FAA Order 7110.65, paragraph 3-7-2. The local controller did not scan the runways prior to issuing a taxi into position and hold instruction to SWA1080 as required by FAA Order 7110.65 paragraph 3-1-12. The local controller did not cancel takeoff clearance for BTA2941 as required by FAA Order 7110.65, paragraph 3-9-10. |
| May 13, 2009 | Houston, TX | N371SW | Minor | minor |
The pilot's inadvertent application of excessive braking after touchdown, which caused the right wheels to lock and several tires to blow and resulted…The pilot's inadvertent application of excessive braking after touchdown, which caused the right wheels to lock and several tires to blow and resulted in a subsequent brake fire. |
| May 02, 2009 | Antalya, TU | F-GFUF | Incident | minor | Investigation pending |
| Apr 29, 2009 | Kwilu, Bandundu, CF | TL-ADM | Fatal (7) | destroyed | Investigation pending |
| Apr 27, 2009 | Guadalajara, MX | XA-MAF | Minor | substantial | Investigation pending |
| Apr 18, 2009 | McAllen, TX | N27722 | Serious (1) | — | The injured passenger's failure to comply with the requirement to remain seated with a fastened seatbelt. |
| Feb 27, 2009 | South Jakarta, OF | PK-YTX | Incident | — | Investigation pending |
| Jan 12, 2009 | East Anglia, UK | G-EZJK | Incident | — | Investigation pending |
| Dec 31, 2008 | Luton Airport, UK | G-EZKB | Incident | — | Investigation pending |
| Dec 28, 2008 | Seattle, WA | N397DA | Incident | substantial |
The failure of the tug operator and wing walker of the other airplane to maintain clearance with this aircraft during the pushback process in dark nig…The failure of the tug operator and wing walker of the other airplane to maintain clearance with this aircraft during the pushback process in dark night. Also causal was the ramp controller's misinterpretation of the other airplane's gate location and her improper clearance for both airplanes to simultaneously push back from nearly opposing gates. |
| Dec 24, 2008 | Seattle, WA | N516AS | Incident | — |
The failure of the deicing crew to follow company procedures by not receiving confirmation from the flight crew before beginning to deice the airplane…The failure of the deicing crew to follow company procedures by not receiving confirmation from the flight crew before beginning to deice the airplane. |
| Dec 21, 2008 | Denver, CO | N18611 | Serious (6) | substantial |
The captain’s cessation of right rudder input, which was needed to maintain directional control of the airplane, about 4 seconds before the excursion,…The captain’s cessation of right rudder input, which was needed to maintain directional control of the airplane, about 4 seconds before the excursion, when the airplane encountered a strong and gusty crosswind that exceeded the captain’s training and experience. Contributing to the accident were the following factors: 1) an air traffic control system that did not require or facilitate the dissemination of key, available wind information to the air traffic controllers and pilots; and 2) inadequate crosswind training in the airline industry due to deficient simulator wind gust modeling. |