NTSB investigations: CFM International CFM56 series, 2005

14 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, 2005 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\") = 2005
    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 DFW06IA025Incident · No injuriesIncident investigationFinal reportBoeing 767-300ER · Houston, TXThe captain's failure to maintain clearance from a parked airplane awaiting for a gate. A contributing factor was that taxi procedures were not issued by ground control to advise the captain that the ramp area where he was taxing was designated as a…Dec 16, 2005 · N319UP · 2 aircraft · Minor damageNTSB DCA06WA001Incident · No injuriesForeign investigationBoeing 737-900 · Calgary, CanadaOct 30, 2005 · N317AS · No damageNTSB NYC06LA016Accident · Serious injuriesLimited investigationFinal reportBoeing 737-832 · Atlantic Ocean (Atlantic Ocean)An encounter with turbulence during cruise flight.Oct 22, 2005 · N378DA · No damageNTSB LAX06LA009Accident · No injuriesLimited investigationFinal reportBoeing 737-7H4 · Phoenix, AZThe failure of the other flight crew to maintain an adequate clearance from obstructions while taxiing.Oct 13, 2005 · N755SA · 2 aircraft · Minor damageNTSB IAD05LA118Accident · No injuriesLimited investigationFinal reportBoeing 737-824 · Newark, NJThe airport's failure to install markings on a parking "block" that bordered the taxiway, which failed to provide adequate clearance between taxiing airplanes and airplanes parked in the block. Factors in the accident were air traffic control's use of the…Aug 8, 2005 · N73270 · 2 aircraft · Substantial damageNTSB CHI05LA179Accident · No injuriesLimited investigationFinal reportBoeing 737-7H4 · Chicago, ILThe pushback tow driver not maintaining visual lookout for the wing walker's visual signal, and the driver not maintaining clearance from the vehicle during the pushback for taxi. Factors to the accident were the standing vehicle behind the airplane, the…Jul 8, 2005 · N494WN · Substantial damageNTSB DEN05IA098Incident · No injuriesIncident investigationFinal reportBoeing 737-524 · Salt Lake City, UTthe left wing walker's failure to maintain an adequate visual lookout. Contributing factors were his inadequate initial training, and the failure of other ground personnel to follow company procedures/directives.Jun 20, 2005 · N24633 · Minor damageNTSB DEN05LA090Accident · Serious injuriesLimited investigationFinal reportAirbus Industrie A-319-114 · Scottsbluff, NEthe inflight encounter with moderate turbulence.Jun 11, 2005 · N302NB · Minor damageNTSB 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.Jun 9, 2005 · EI-ORD · 2 aircraft · No damageNTSB DEN05IA076Incident · No injuriesIncident investigationFinal reportBoeing 737-322 · Denver, COthe improper use of procedure used by the ground personnel resulting in the right wing of the aircraft colliding with the left wing of another aircraft. A factor in this incident was the failure to maintain clearance by the flight crew of the other aircraft.May 17, 2005 · N305UA · 2 aircraft · Minor damageNTSB CHI05MA111Accident · Serious injuriesMajor investigationFinal reportMcDonnell Douglas DC-9-51 · Minneapolis, MNthe Captain of the other aircraft's decision to shutdown the left engine during taxi with no hydraulic pressure on the right side hydraulic system to effectively operate the brakes, steering, or thrust reversers. A factor was the fatigue fracture of the…May 11, 2005 · N763NC · 2 aircraft · Substantial damageNTSB DFW05LA112Accident · Serious injuriesLimited investigationFinal reportBoeing 737-700 · Little Rock, ARAn encounter with moderate turbulence during cruise flight.Apr 29, 2005 · N727SW · No damageNTSB 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…Jan 30, 2005 · N350SW · No damageNTSB 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.Jan 8, 2005 · N16732 · Substantial damage