NTSB investigations: CFM International CFM56 series

6 cases on aircraft whose registry engine model is CFM International CFM56 series, where the first occurrence was “Near collision between aircraft”. 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.

Defining event

Finding

Phase of flight

Aircraft model

Cases per year

19872026

NTSB investigations: CFM International CFM56 series per year, 1987–2026: 6 cases
1987	1
1988	1
2004	1
2006	2
2007	1

Where

Open the map

Latest cases

Query with SQL

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 ('13802') AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 280)) ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC

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 ('13802')
      AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 280))
  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 ('13802')
    AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.case_mkey = x.case_mkey AND o.aircrafts_position = x.position AND o."occurrenceNumber" = 1 AND o."occurrenceCode" = 280))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC

Run 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 OPS07IA009Incident · No injuriesIncident investigationFinal reportBoeing 737-700 · Los Angeles, CAThe LAX north ground controller's failure to properly coordinate with the tower local controller prior to providing taxi instructions that permitted an aircraft to cross an active runway while another aircraft was departing. **This report was modified on…Aug 16, 2007 · C-FUWS · 2 aircraft · No damage NTSB OPS06IA008Incident · No injuriesIncident investigationFinal reportBoeing 737-322 · Chicago, ILThe failure of the ORD tower south local controller to monitor Atlas Air flight 6972 on arrival to runway 14R and subsequently clearing United Airlines flight 1015 for takeoff on intersecting runway 27L causing a loss of separation between the two aircraft.Jul 24, 2006 · N315UA · 2 aircraft · No damage NTSB OPS06IA007Incident · No injuriesIncident investigationFinal reportBoeing 737-300 · Chicago, ILThe probable cause of this incident was the ORD tower local controller's failure to provide sufficient separation between two aircraft departing intersecting runways. Contributing to the incident was the ORD local monitor's failure to monitor the situating…Mar 23, 2006 · N309UA · 2 aircraft · No damage NTSB LAX04IA302Incident · No injuriesIncident investigationFinal reportBoeing 737-7H4 · Los Angeles, CAa loss of separation between Southwest flight 440 and Asiana flight 204 due to the LC2 relief controller's failure to appropriately monitor the operation and recognize a developing traffic conflict. Contributing factors included the FAA's position relief…Aug 19, 2004 · N461WN · No damage NTSB NYC88IA109Incident · No injuriesIncident investigationFinal reportBoeing 737 · Morristown, NJBoeing 737 (N69348) was depg newark intl arpt as a lear jet 24 (N500NH) was depg fm teterboro. Both were being ctld by new york TRACON (newark sector). The strip for the 737 was mismarked as a north departure rather than an east departure. The instructor/full…Mar 19, 1988 · N69348 · 2 aircraft · No damage NTSB CHI88IA015Incident · No injuriesIncident investigationFinal reportBoeing 737-322 · Chicago, ILThe south rwys (32L, 9R, & 4R) were being ctld by the south LCL ctlr (slc) & the north rwys (9L & 4L) were ctld by the north LCL ctlr (nlc). At 1543:26, slc told united flt 973 (Boeing 737) to hold on 32L & expect a 3 min delay bfr tkof. Air Wisconsin flt 954…Oct 29, 1987 · N305UA · 2 aircraft · No damage