NTSB investigations: CFM International CFM56 series, 2006

11 cases on aircraft whose registry engine model is CFM International CFM56 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

19702026
NTSB investigations: CFM International CFM56 series, 2006 per year, 1970–2026: 255 cases
19701
19711
19832
19851
19872
19883
19892
19906
19922
19932
19943
199516
19968
19976
19985
19998
20004
200113
20024
20037
20047
200514
200611
20079
200810
20099
201011
20116
20126
20133
20146
201512
201610
20174
20184
20195
20202
20211
20225
20233
20248
20259
20264

Latest 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 year(c.\"eventDate\") = 2006
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('13802'))
  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.

NTSB LAX07LA064Accident · No injuriesLimited investigationFinal reportBoeing 737-7H4 · San Diego, CAFailure of the captain of the other taxiing airplane to maintain clearance from an occupied airplane stopped on the ramp.Dec 27, 2006 · N207WN · 2 aircraft · Minor damageNTSB DEN07IA037Incident · Minor injuriesIncident investigationFinal reportBoeing 737-824 · Colorado Spring, COA short circuit in the primary (non-rechargeable) battery, most likely due to it being recharged. This internal short led to thermal runaway, battery failure, and an explosion.Dec 16, 2006 · N24202 · Minor damageNTSB DEN07IA027Incident · No injuriesIncident investigationFinal reportAirbus Industrie A319-111 · Denver, COThe inadvertent activation of the priority pushbutton on the sidestick by the first officer resulting in a nose down pitch and loss of aircraft control during the landing flare.Oct 23, 2006 · N924FR · No damageNTSB LAX07IA014Incident · No injuriesIncident investigationFinal reportBoeing 737-790 · Los Angeles, CAA complete failure and depressurization of both hydraulic systems due to two separate events: 1) the failure of a engine driven pump on the 'A' system, and 2) the fatigue fracture and failure of a hydraulic line on the 'B' system.Oct 19, 2006 · N614AS · No damageNTSB NYC06LA223Accident · Serious injuriesLimited investigationFinal reportBoeing 737-700 · Hastings, NEThe airplane's in flight encounter with thunderstorm related turbulence.Sep 17, 2006 · N793SA · No damageNTSB MIA06IA133Incident · No injuriesIncident investigationFinal reportBoeing 737-400 · Miami, FLThe pilot's inadvertent application of the left brakes at touchdown. Contributing to the incident was insufficient information in the quick reference handbook on the loss of touchdown protection with an inoperative anti-skid system.Aug 31, 2006 · N425US · Minor damageNTSB NYC06IA207Incident · No injuriesIncident investigationFinal reportBoeing 737-524 · Newark, NJAn overload failure of the airplane's nose landing gear while being towed for repositioning.Aug 21, 2006 · N14655 · Minor damageNTSB NYC06FA184Accident · Minor injuriesField investigationFinal reportBoeing 737-300 · Pittsburgh, PAThe airplane tug driver's inadvertent movement of the tug gear shift lever from forward to reverse, which resulted in the nose landing gear collapse. Contributing to the accident was the defective gear shift lever.Jul 27, 2006 · N529AU · Substantial damageNTSB 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 damageNTSB 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 damageNTSB DFW06FA056Accident · 1 fatalField investigationFinal reportBoeing 737-524 · El Paso, TXthe mechanic's failure to maintain proper clearance with the engine intake during a jet engine run, and the failure of contract maintenance personnel to follow written procedures and directives contained in the airline's general maintenance manual. Factors…Jan 16, 2006 · N32626 · Minor damage