NTSB investigations: CFM International CFM56 series
18 cases on aircraft whose registry engine model is CFM International CFM56 series, where the first occurrence was “Miscellaneous/other”. 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
| 1988 | 1 |
|---|---|
| 1990 | 1 |
| 1995 | 1 |
| 1997 | 4 |
| 1999 | 2 |
| 2000 | 1 |
| 2002 | 1 |
| 2004 | 2 |
| 2005 | 3 |
| 2007 | 2 |
Where
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 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\" = 430))
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" = 430))
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 ATL07IA078Incident · No injuriesIncident investigationFinal reportAirbus Industrie A319-111 · Atlanta, GAThe mechanics failure to follow procedures and directives in securing the lower engine cowling after maintenance, and the failure of the first officer to follow the checklist to ensure the engine cowling was secured during the walk around inspection resulting…NTSB DEN07IA058Incident · No injuriesIncident investigationFinal reportBoeing 737-522 · Denver, COThe snowplow driver's failure to follow procedures/directives by crossing an active runway without clearance, resulting in a runway incursion and near collision with an airplane during its landing roll.NTSB NYC05IA095Incident · No injuriesIncident investigationFinal reportAirbus Industrie A330-301 · Boston, MAThe local east controller's failure to follow FAA Order 7110.65, para 3-9-8 and Boston Tower Order 7110.11, Standard Operating Procedures, which resulted in a runway incursion during takeoff involving two transport category airplanes.NTSB SEA05IA040Incident · No injuriesIncident investigationFinal reportBoeing 737-3H4 · Seattle, WAThe flight crew's failure to maintain an adequate visual lookout while on final for a visual approach. Factors include the failure of both airport operations personnel and the local FAA Airports Inspector to insure that some form of identification marking was…NTSB DEN05LA048Accident · Minor injuriesLimited investigationFinal reportBoeing 737-724 · Gunnison, COthe snowplow driver's failure to see the airplane during plowing operations. Factors contributing to the accident were the snowplow driver's excessive speed and the snow.NTSB DEN04IA124Incident · No injuriesIncident investigationFinal reportBoeing 737-500 · Denver, COthe inaccurate radar information due to the failure of the Airport Movement Area Surveillance radar resulting in the tower calling for the airplane to abort the takeoff, subsequently causing tire and brake damage to the airplane.NTSB SEA04IA045Incident · No injuriesIncident investigationFinal reportBoeing 737-300 · Seattle, WAThe First Officer's misidentification of the parallel taxiway as the active runway, resulting in the need for a sidestep maneuver while on short final for a full-stop landing. Factors include sun-glare from wet paved surfaces, a visual illusion created by the…NTSB CHI03LA031Accident · Serious injuriesLimited investigationFinal reportAirbus Industrie A320-211 · Minneapolis, MNThe cabin flight crew not verifying the galley service cart had been properly stowed prior to departure, which resulted in the inadvertent deployment of the galley service cart during initial climb after takeoff.NTSB MIA00LA169Accident · Serious injuriesLimited investigationFinal reportBoeing 737-500 · Nashville, TNThe passenger's onboard disturbance and self-evacuation from the parked aircraft, resulting in injuries. A factor in the accident was the lack of backup electrical power to the terminal which necessitated a lengthy ground hold.NTSB ANC00IA010Incident · No injuriesIncident investigationFinal reportBoeing 737-400 · Juneau, AKThe failure of the flight crew to provide a recommended landing traffic advisory, and the failure of flight service station personnel to provide a flight advisory to the arriving airplane concerning men and equipment operating on the runway. Factors in the…NTSB NYC99LA076Accident · Serious injuriesLimited investigationFinal reportBoeing 737-300 · Newark, NJThe flight attendant's failure to follow cabin door opening procedures.NTSB SEA98IA027Incident · No injuriesIncident investigationFinal reportBoeing 737-522 · Eugene, ORA checklist procedure was not followed. The initiation of an evacuation was a factor.NTSB LAX97IA243Incident · No injuriesIncident investigationFinal reportBoeing 737-522 · Ontario, CAa laser light source of undetermined origin directed toward the cockpit window of an aircraft in-flight by a person or persons unknown.NTSB FTW97IA187Incident · No injuriesIncident investigationFinal reportBoeing 737-524 · Corpus Christi, TXThe flightcrew's inadequate in-flight planning and decision, and their failure to refer to the navaids needed for the instrument approach procedure. A factor was the lack of a minimum safe altitude warning from approach control.NTSB LAX97IA161Incident · Minor injuriesIncident investigationFinal reportBoeing 737-500 · Rialto, CAa laser light source of undetermined origin, directed by unknown person(s) toward the cockpit window of the aircraft, while the aircraft was on an approach to land.NTSB LAX96IA032Incident · Minor injuriesIncident investigationFinal reportBoeing 737-5H4 · Las Vegas, NVThe flying pilot's inadvertent exposure to an unidentified ground-based laser beam. A factor in the incident is the lack of appropriate standards by the FAA and FDA for laser light exposure levels to aircrew in navigable airspace.NTSB DCA90IA048Incident · No injuriesIncident investigationFinal reportAirbus Industrie A320-211 · Chicago, ILThe pilot(s) allowed the aircraft to rotate to an excessive nose high attitude, either during a takeoff or landing.NTSB SEA88IA121Incident · No injuriesIncident investigationFinal reportMcdonnell Douglas DC-8-73F · Seattle, WACrew noted inflight indications of loss of hydraulic fluid, then carried out standard procedures per crew manual. Emerg hyd sys used to lower flaps for lndg. Acft landed with four right brakes locked. The tires blew and the wheels were ground flat.…