Final NTSB investigations: GE CFM56 series
13 cases on aircraft whose registry engine model is GE 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
| 1991 | 1 |
|---|---|
| 1992 | 1 |
| 1997 | 2 |
| 1998 | 1 |
| 1999 | 1 |
| 2003 | 1 |
| 2004 | 1 |
| 2006 | 2 |
| 2007 | 1 |
| 2009 | 1 |
| 2010 | 1 |
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.\"completionStatus\" = 'Completed'
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('30016'))
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."completionStatus" = 'Completed'
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('30016'))
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 WPR10LA134Accident · Serious injuriesLimited investigationFinal reportBoeing 737-7H4 · Santa Clarita, CAThe pilot’s abrupt airplane pitch change maneuver. Contributing to the accident was the flight crew’s failure to maintain the heading specified by the air traffic controller, which would have avoided the near collision course with an unidentified airplane…NTSB DCA09FA047Accident · Minor injuriesField investigationFinal reportAirbus A320 · Denver, COThe first officer’s excessive pitch-up of the airplane while landing with a tailwind, which resulted in a tailstrike following a bounced landing. Contributing to the bounced landing were a high descent rate and excessive thrust resulting from the first…NTSB DEN08IA022Incident · No injuriesIncident investigationFinal reportDouglas DC-8-73F · Wichita, KSFailure of the recirculation fan motor end ball bearing.NTSB CHI07FA020Accident · No injuriesField investigationFinal reportAirbus A-320-200 · Chicago, ILThe pilot-in-command of the other airplane failed to maintain clearance with the parked airplane during taxi for takeoff.NTSB CHI06LA161Accident · No injuriesLimited investigationFinal reportBoeing 737-300 · New York, NYThe foreign object damage to the horizontal stabilizer during taxi as a result of improper airport maintenance by contract maintenance personnel. The aluminum plate was a factor.NTSB CHI04LA126Accident · Serious injuriesLimited investigationFinal reportBoeing 737-300 · St. Louis, MOThe inadvertent encounter with turbulence which resulted in the injury to the flight attendant.NTSB NYC03CA169Accident · Serious injuriesData collectionFinal reportBoeing 757-251 · Wadsworth, OHAn in-flight encounter with turbulence.NTSB MIA99FA252Accident · No injuriesField investigationFinal reportBoeing B737-300 · West Palm Beach, FLThe fatigue fracture and separation of the high pressure turbine forward rotating air seal due to a manufacturing defect in a bolt hole that was not detected by the engine manufacturer due to inadequate and ineffective inspection techniques. Contributing to…NTSB MIA98IA193Incident · No injuriesIncident investigationFinal reportBoeing 737-7H4 · Birmingham, ALThe improper electronic control unit software logic that permitted the electronic control unit to lock on a failed hydromechanical resolver, which failed due to damage to a wire that was incurred during the manufacturing process, resulting in an uncommanded…NTSB CHI97LA162Accident · Serious injuriesLimited investigationFinal reportBoeing 737-300 · Valparaiso, INa delay by the pilot of the other aircraft in turning on his mode C transponder.NTSB LAX97FA164Accident · Serious injuriesField investigationFinal reportBoeing 737-3S3 · Las Vegas, NVinadequate service provided by the TRACON controller, by issuing a radar vector to the Boeing 737 flight, which resulted in inadequate separation from a Beech 99 that the controller had just terminated from radar service; and failure of the controller to…NTSB NYC93IA017Incident · No injuriesIncident investigationFinal reportBoeing 737-300 · Pittsburgh, PAThe high cycle fatigue failure of blades on the stage 1 high pressure compressor, which resulted in blade fracture and subsequent internal engine damage and fire.NTSB NYC92LA018Accident · Serious injuriesLimited investigationFinal reportBoeing 737-4B7 · Boston, MAA latch failure on a door in the aft galley which allowed a liquor kit to roll forward.