Boeing 737 Safety Record
Complete NTSB accident and incident history. 1188 events recorded from 1982 to 2026.
| Date | Location | Reg# | Severity | Damage | Probable Cause |
|---|---|---|---|---|---|
| Mar 28, 2017 | Jauja, PE | OB-2036-P | Incident | substantial | Investigation pending |
| Mar 27, 2017 | Ardabil, IR | EP-TBJ | Incident | substantial | Investigation pending |
| Feb 03, 2017 | Edinburgh, UK | TF-BBB | Incident | minor | Investigation pending |
| Feb 01, 2017 | Yogykarta, ID | PK-GNK | Incident | — | Investigation pending |
| Jan 28, 2017 | Leticia, CO | HK-5197 | Incident | substantial | Investigation pending |
| Jan 22, 2017 | Dhaka, IN | VT-JTD | Incident | minor | Investigation pending |
| Dec 12, 2016 | Adelaide, AS | UNK | Incident | — | Investigation pending |
| Dec 02, 2016 | Nagpur, IN | VT-JFP | Incident | — | Investigation pending |
| Oct 27, 2016 | New York, NY | N278EA | Incident | minor |
The first officer's failure to attain the proper touchdown point and the flight crew's failure to call for a go-around, which resulted in the airplane…The first officer's failure to attain the proper touchdown point and the flight crew's failure to call for a go-around, which resulted in the airplane landing more than halfway down the runway. Contributing to the incident were, the first officer's initiation of the landing flare at a relatively high altitude and his delay in reducing the throttles to idle, the captain's delay in manually deploying the speed brakes after touchdown, the captain's lack of command authority, and a lack of robust training provided by the operator to support the flight crew's decision-making concerning when to call for a go-around. |
| Oct 10, 2016 | Surabaya, ID | PK-CKF | Incident | substantial | Investigation pending |
| Sep 13, 2016 | Papua, ID | PK-YSY | Incident | substantial | Investigation pending |
| Aug 27, 2016 | Pensacola, FL | N766SW | Incident | substantial |
A low-cycle fatigue crack in the dovetail of fan blade No. 23, which resulted in the fan blade separating in flight and impacting the fan case. This i…A low-cycle fatigue crack in the dovetail of fan blade No. 23, which resulted in the fan blade separating in flight and impacting the fan case. This impact caused the fan blade to fracture into fragments that traveled farther than expected into the inlet, which compromised the structural integrity of the inlet and led to the in-flight separation of inlet components. A portion of the inlet struck the fuselage and created a hole, causing the cabin to depressurize. |
| Aug 10, 2016 | New York, NY | N3762Y | Incident | substantial | inadvertent collision by ground service vehicle. |
| Aug 05, 2016 | Baltimore, MD | N368SW | Incident | substantial | the tug operators excessive speed during pushback. |
| Aug 02, 2016 | Mbuji Mayi, CF | 9Q-DBJ | Incident | minor | Investigation pending |
| Jul 31, 2016 | Makassar, ID | PK-GMK | Incident | — | Investigation pending |
| Jul 12, 2016 | Mexico City, MX | XA-UNY | Incident | substantial | Investigation pending |
| May 03, 2016 | Ulaanbaatar, MG | EI-CXV | Incident | — | Investigation pending |
| May 02, 2016 | Prishtina, SR | TC-JFY | Incident | — | Investigation pending |
| Apr 10, 2016 | Chiang Mai, TH | HS-LTB | Incident | — | Investigation pending |
| Mar 03, 2016 | Mumbai, IN | VT-JGD | Incident | substantial | Investigation pending |
| Feb 24, 2016 | a Mitad de la Pista del Aeropuerto, MX | C-FIWJ | Incident | — | Investigation pending |
| Feb 17, 2016 | Detroit, MI | N784SW | Incident | minor |
N925NN flight crew's incorrect evaluation of the clearance between the two aircraft, leading to the inadvertent collision of the winglet with the hori…N925NN flight crew's incorrect evaluation of the clearance between the two aircraft, leading to the inadvertent collision of the winglet with the horizontal stabilizer and elevator of N784SW. |
| Jan 07, 2016 | Cluj-Napoca, RO | YR-BAS | Incident | — | Investigation pending |
| Dec 23, 2015 | Gwangju-Si, KS | HL8049 | Incident | — | Investigation pending |