NTSB investigations: CFM International LEAP-1B28 series
20 cases on aircraft whose registry engine model is CFM International LEAP-1B28 series. Aircraft are matched to the registry by N-number and event date, checked against the reported serial number, make and model, so older matches can be wrong.
Cases per year
| 2022 | 1 |
|---|---|
| 2023 | 4 |
| 2024 | 7 |
| 2025 | 2 |
| 2026 | 6 |
Where
Open the mapLatest cases
Query with SQL
duckdb -csv -c "SELECT c.\"ntsbNumber\", c.\"eventDate\", c.\"eventType\", c.\"eventCity\", c.\"eventStateOrRegion\", a.n_number, a.\"aircraftMake\", a.\"aircraftModel\", c.\"highestInjuryLevel\", c.\"totalFatal\", c.\"completionStatus\", c.report_url
FROM 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c.\"mKey\" AND a.position = 1
WHERE c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('13120'))
ORDER BY c.\"eventDate\" DESC, c.\"ntsbNumber\" DESC"Prints the whole list as CSV. It reads the release’s Parquet files over HTTPS, so there’s nothing to download first. Install DuckDB to run it.
SELECT c."ntsbNumber", c."eventDate", c."eventType", c."eventCity", c."eventStateOrRegion", a.n_number, a."aircraftMake", a."aircraftModel", c."highestInjuryLevel", c."totalFatal", c."completionStatus", c.report_url
FROM 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c."mKey" AND a.position = 1
WHERE c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('13120'))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESCRun it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.
NTSB DCA26WA347IncidentClass 5 · ForeignBoeing 737-8 · Fresno, CANTSB ENG26WA033OccurrenceClass 5 · ForeignBoeing 737 · Cancun, MexicoNTSB DCA26WA216IncidentClass 5 · ForeignBoeing 737-8 · Liberia, Costa RicaNTSB DCA26LA185Accident · Serious injuriesClass 4 · LimitedFinal reportBoeing 737-8 · Providence, RIThe airplane’s encounter with turbulence during descent resulting in a serious injury to a flight attendant.NTSB DCA26LA164Accident · Serious injuriesClass 4 · LimitedFinal reportBoeing 737-8 · Dulles, VAThe tug drivers improper positioning of the airplane during pushback, which resulted in the airplane’s jet blast impacting an active gate area during taxi and the subsequent injury to a maintenance technician. Contributing to the accident was the captain’s…NTSB OPS26LA027Incident · No injuriesClass 4 · LimitedInvestigation openBoeing 737-9 · Newark, NJNTSB DCA25LA230Accident · Serious injuriesClass 4 · LimitedFinal reportBoeing 737 · Phoenix, AZThe abrupt application of brakes during taxi, which resulted in a sudden stop and caused a flight attendant to sustain a serious injury.NTSB DCA25LA156Accident · Serious injuriesClass 4 · LimitedFinal reportBoeing 737-8 · San Diego, CAAn encounter with an area of moderate clear air turbulence associated with the jet stream during cruise.NTSB ENG25WA013OccurrenceClass 5 · ForeignBoeing 737-9 · Cancún, MexicoNTSB DCA24WA308IncidentClass 5 · ForeignBoeing 737-8 · San Francisco, CANTSB DCA24FA300Incident · No injuriesClass 3 · FieldPreliminary reportBoeing 737-9 · Nashville, TNOn September 12, 2024, about 0914 central daylight time (CDT), Alaska Airlines flight 369 (ASA369), a Boeing 737-900, N919AK, rejected their take-off on runway 13 at Nashville International Airport (BNA), Nashville, Tennessee, when Southwest Airlines flight…NTSB DCA24LA206Incident · No injuriesClass 3 · LimitedPreliminary reportBoeing 737-8 · Oakland, CAOn May 25, 2024, about 0744 Pacific daylight time, Southwest Airlines (SWA) flight 746, a Boeing 737-8, N8825Q, experienced a rudder control system anomaly while operating as a Title 14 Code of Federal Regulations Part 121 scheduled domestic passenger flight…NTSB DCA24FA120Accident · No injuriesClass 2 · FieldFinal reportBoeing 737-8 · Houston, TXThe captain's decision not to establish and maintain deceleration devices in accordance with company training and standard operating procedures.NTSB DCA24LA094Incident · No injuriesClass 2 · LimitedFinal reportBoeing 737-8 · Newark, NJMoisture intrusion through the pressure port inlet of the rudder rollout guidance actuator that accumulated and froze during flight at altitude, resulting in jammed rudder pedal movement.NTSB DCA24MA063Accident · Minor injuriesClass 1 · MajorFinal reportBoeing 737-9 · Portland, ORthe in-flight separation of the left mid exit door (MED) plug due to Boeing Commercial Airplanes’ failure to provide adequate training, guidance, and oversight necessary to ensure that manufacturing personnel could consistently and correctly comply with its…NTSB DCA24LA330IncidentClass 2 · LimitedFinal reportBoeing 737-8 · Kenner, LAA partial loss of engine power due to bird ingestion in the No. 1 (left) engine, which resulted in the activation of the load reduction device to prevent vibration. The load reduction device activation resulted in smoke and fumes entering the cockpit.NTSB DCA23LA468Accident · No injuriesClass 4 · LimitedFinal reportBoeing 737-9 · Denver, COOverheated brakes due to the extended taxi at a higher power setting in an attempt to burn off fuel to achieve the proper takeoff weight that resulted in a wheel fire during takeoff.NTSB ENG23LA031Incident · No injuriesClass 3 · LimitedFinal reportBoeing 737-9 · Newark, NJA No. 1 (left) engine fire due a fuel leak that originated from the fuel nozzle 17 b-nut connection that was not properly torqued in accordance with the aircraft maintenance manual procedure.NTSB DCA23WA302IncidentClass 3 · ForeignBoeing 737-8 · Havana, CubaNTSB DCA22LA133Incident · No injuriesClass 3 · LimitedFinal reportBoeing 737-9 · Pittsburgh, PAThe flightcrew’s misidentification of the intended landing runway, which resulted in approach to and landing on the wrong runway. Contributing to the incident was the distraction caused by the dual reset of the flight management computer displays.