NTSB investigations: CFM International CFM56 series

255 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, newest first

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'))
  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 SEA98IA027Incident · No injuriesIncident investigationFinal reportBoeing 737-522 · Eugene, ORA checklist procedure was not followed. The initiation of an evacuation was a factor.Dec 26, 1997 · N918UA · No damageNTSB MIA97IA237Incident · Minor injuriesIncident investigationFinal reportBoeing 737-300 · Tampa, FLin-flight collision with a bird.Aug 21, 1997 · N602SW · Minor damageNTSB 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.Jul 15, 1997 · N956UA · No damageNTSB 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.May 11, 1997 · N16618 · No damageNTSB 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.Apr 17, 1997 · N930UA · No damageNTSB SEA97IA071Incident · No injuriesIncident investigationFinal reportMcDonnell Douglas DC-8-71F · Portland, ORimproper installation of four attach bolts on the elevator drive torque tube.Mar 12, 1997 · N830BX · No damageNTSB ANC97LA015Accident · Serious injuriesLimited investigationFinal reportBoeing 737-400 · Yakutat, AKan in-flight encounter with unforecast severe clear air turbulence.Dec 22, 1996 · N775AS · No damageNTSB CHI97IA034Incident · No injuriesIncident investigationFinal reportAirbus Industrie A-320-211 · Romulus, MIrestricted movement of the autopilot mode engagement/disengagement lever bearing in the rudder artificial feel and trim unit. A factor relating to this incident was: company management not implementing the respective service bulletin.Nov 24, 1996 · N310NW · No damageNTSB LAX97LA051Accident · Serious injuriesLimited investigationFinal reportBoeing 737-500 · Bishop, CAa clear air turbulence encounter.Nov 20, 1996 · N916UA · No damageNTSB MIA96LA220Accident · Serious injuriesLimited investigationFinal reportBoeing 737-300 · Chattanooga, TNclear air turbulence, which was encountered during cruise flight and resulted in injuries to passengers.Aug 29, 1996 · N392US · Minor damageNTSB CHI96IA207Incident · No injuriesIncident investigationFinal reportAirbus Industrie A-320 · Boston, MAan undetermined intermittent fault in the trimmable horizontal stabilizer actuator system.Jun 14, 1996 · N347NW · No damageNTSB LAX96LA222Accident · No injuriesLimited investigationFinal reportBoeing 737-322 · San Francisco, CAinadequate visual lookout by the United Airlines tug driver during the pushback operation. Contributing factors were: the driver's reduced ability to observe the American B-767 due to the nighttime condition, and United Airlines management's failure to ensure…Jun 7, 1996 · N371UA · 2 aircraft · Substantial damageNTSB LAX96IA184Incident · No injuriesIncident investigationFinal reportBoeing 737-300-3H4 · Ontario, CAThe repair facility's improper assembly of the landing gear oleo strut during overhaul.Apr 30, 1996 · N331SW · Minor damageNTSB CHI96IA109Incident · No injuriesIncident investigationFinal reportAirbus Industrie A320-211 · Detroit, MIa defective diode in the number two stabilizer actuator that produced an intermittent loss of electrical motor power during transient, closed loop control of the actuator. A factor was the intermittent open circuit in the elevator servo controller…Mar 18, 1996 · N340NW · No damageNTSB SEA96LA026Accident · Serious injuriesLimited investigationFinal reportBoeing 737-522 · Portland, ORAn unexpected encounter with unforecast moderate high level windshear and turbulence as the flight attendant was performing his duties during descent.Nov 25, 1995 · N953UA · No damageNTSB NYC96IA022Incident · No injuriesIncident investigationFinal reportBoeing 737-3B7 · Portland, MEa bird strike during takeoff, which resulted in failure of several fan blades in the right engine and a partial loss of engine power.Nov 2, 1995 · N373US · Minor damageNTSB 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.Oct 31, 1995 · N508SW · No damageNTSB DCA96IA005Incident · No injuriesIncident investigationFinal reportBoeing B-737-500 · San Francisco, CAThe inadvertant stall for undertermined reasons.Oct 29, 1995 · N904UA · No damageNTSB MIA95IA214Incident · No injuriesIncident investigationFinal reportBoeing 737-3B7 · Fort Lauderdale, FLLow electrical resistance of the autopilot aileron actuator for unspecified reasons which resulted in an uncommanded roll to the right.Aug 25, 1995 · N373US · No damageNTSB FTW95IA348Incident · No injuriesIncident investigationFinal reportBoeing 737-3H4 · Lubbock, TXinstallation of an incorrect bearing in the number three main wheel by the wheel assembly supplier, which led to subsequent failure of the wheel bearing and separation of the wheel during takeoff.Aug 18, 1995 · N309SW · Minor damageNTSB FTW95FA319Accident · No injuriesField investigationFinal reportBoeing 737-3A4 · Dallas, TXFailure of the flightcrews of the Boeing 737, N675AA, and the Cessna 401, N31DB, to see and avoid each other. Factors were: the failure of 737 flightcrew to respond to the traffic advisory given by the ground controller identifying potentially conflicting…Jul 28, 1995 · N675AA · 2 aircraft · Minor damageNTSB MIA95IA187Incident · No injuriesIncident investigationFinal reportBoeing 737-3B7 · Orlando, FLContamination of the wiring harness and electrical connectors to the E-1-2 and E-1-3 shelf disconnect brackets in the electronics compartment, which resulted in an electrical fault and an uncommanded roll malfunction of the autopilot. A factor relating to the…Jul 18, 1995 · N390US · No damageNTSB CHI95LA170Accident · No injuriesLimited investigationFinal reportAirbus Industrie A-320-211 · St Paul, MNthe captain's not maintaining crew/group coordination. Factors were the captain's diverted attention and his not maintaining visual separation.Jun 3, 1995 · N326US · Substantial damageNTSB NYC95IA114Incident · No injuriesIncident investigationFinal reportBoeing 767-383ER · Newark, NJthe pilot of the B-767, LNRCK, misjudged clearance between his airplane and the B-737, N13624, resulting in an on-ground collision.May 20, 1995 · LNRCK · 2 aircraft · Minor damageNTSB MIA95LA133Accident · Serious injuriesLimited investigationFinal reportBoeing 737-300 · Tallahassee, FLThe failure of a passenger to comply with flight crew instructions to remain seated with her seat belt fastened which resulted in her being injured while walking in the aisle during a turbulence encounter.May 19, 1995 · N60312 · No damageNTSB NYC95IA106Incident · No injuriesIncident investigationFinal reportDouglas DC-8-71 · Louisville, KYpreexisting crack(s) on the inside surface of the right main landing gear cylinder, and the subsequent fracture of the cylinder, which resulted in a collapse of the right main landing gear.May 13, 1995 · N707UP · Minor damageNTSB CHI95IA342Incident · No injuriesIncident investigationFinal reportAirbus Industrie A320-211 · Minneapolis, MNinadequate design of the fly-by-wire flight control system which allowed false signals from the sidestick transducer units to generate uncommanded rolls.Apr 28, 1995 · N331NW · No damageNTSB CHI95IA138Incident · No injuriesIncident investigationFinal reportAirbus Industrie A320-211 · Washington, DCthe pilot's excessive use of the flight controls during the landing approach, the company's disregard of information provided by the airplane manufacturer, and the company's failure to identify a potentially hazardous conditions based on the information…Apr 27, 1995 · N331NW · No damageNTSB LAX95IA086Incident · No injuriesIncident investigationFinal reportBoeing 737-300 · Albuquerque, NMmaintenance personnel inadvertently overservicing the left main landing gear strut with nitrogen that, during rotation with the aircraft weight on the strut reduced, gave the pilots a rolling sensation to the right.Jan 24, 1995 · N155AW · No damageNTSB FTW95IA083Incident · No injuriesIncident investigationFinal reportBoeing 737-3A4 · Houston, TXEncounter with wake turbulence.Jan 1, 1995 · N326SW · No damageNTSB CHI95LA049Accident · Serious injuriesLimited investigationFinal reportDouglas DC-8-71F · Chicago, ILthe failure of the ground crew to maintain an appropriate center of gravity while downloading cargo from the airplane. A factor was the ground crew's failure to follow established downloading procedures.Nov 30, 1994 · N826BX · Minor damageNTSB FTW95IA053Incident · No injuriesIncident investigationFinal reportBoeing B-737-300 · Houston, TXThe failure of maintenance personnel to follow the taxi checklist resulting in the hydraulic pumps not being turned on.Nov 26, 1994 · N14336 · Minor damageNTSB MIA94LA214Accident · Serious injuriesLimited investigationFinal reportBoeing 737-400 · Atlantic Ocean (Atlantic Ocean)The inflight encounter with turbulence in clouds.Sep 19, 1994 · N433US · No damageNTSB CHI93IA354Incident · No injuriesIncident investigationFinal reportBoeing 737-300 · St. Louis, MOa failure of the left outboard foreflap due to the loss of the bolts that hold the inboard sequencing carriage to the foreflap attach lug.Sep 8, 1993 · N350SW · Minor damageNTSB DEN93IA044Incident · No injuriesIncident investigationFinal reportBoeing 737-522 · Denver, COThe pilot-in-command's failure to maintain adequate separation from the Boeing 757, and his failure to stay above the probable path of the Boeing's wake vortices, which resulted in the vortex encounter. Factors related to the accident were: the crosswind, and…Apr 24, 1993 · N905UA · No damageNTSB NYC93LA040Accident · 1 fatalLimited investigationFinal reportBoeing 737-300LR · Flushing, NYA lack of adequate clearance between the walker and tug which resulted in the walker being struck by the tug when he fell for unknown reason(s). A factor related to the accident was the lack of a policy to stay clear of the tug, towbar, and nosewheel of the…Dec 8, 1992 · N516AU · No damageNTSB FTW92LA200Accident · Serious injuriesLimited investigationFinal reportBoeing 737-300 · Springfield, MOThe encounter with severe turbulence while deviating around convective activity.Aug 3, 1992 · N357SW · No damageNTSB LAX90IA293Incident · No injuriesIncident investigationFinal reportBoeing 737-322 · Los Angeles, CAImproper maintenance service by a company employee who allowed a foreign object (flashlight) to remain in the landing gear extend/retract linkage during a night servicing before the flight.Aug 21, 1990 · N305UA · Minor damageNTSB 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.Aug 10, 1990 · N306US · Minor damageNTSB FTW90LA156Accident · Serious injuriesLimited investigationFinal reportBoeing B-737-300 · Corpus Christi, TXThe airplane's unexpected encounter with clear air turbulence.Aug 9, 1990 · N327SW · No damageNTSB MKC90IA070Incident · Minor injuriesIncident investigationFinal reportBoeing 737-300 · Wichita, KSImproper installation of level arm.Mar 17, 1990 · N17317 · Minor damageNTSB LAX90LA122Accident · No injuriesLimited investigationFinal reportBoeing 737-300 · Santa Ana, CAThe pilot's improper rotation during takeoff.Mar 17, 1990 · N306AW · Substantial damageNTSB CHI90IA070Incident · No injuriesIncident investigationFinal reportBoeing B737-300 · Cedar Rapids, IAThe failure of all four main landing gear tires on takeoff due to the parking brake being locked.Jan 20, 1990 · N338UA · Minor damageNTSB ATL89IA187Incident · No injuriesIncident investigationFinal reportBoeing 737-400 · Greensboro, NCFailure of the line mechanic, a check mechanic, and first officer to identify and remove the wheel chock from the wheel well during the required inspections.Aug 2, 1989 · N413US · Minor damageNTSB DCA89MA034Accident · No injuriesMajor investigationFinal reportBoeing 737-300 · Oakland, CAIgnition of puddled fuel from a blocked combustor drain line, and a slow start during which fuel was misted and blown out the tail pipe. An existing tailwind at the gate allowed the fuel to wet the tail surfaces and be ignited during the APU start. The…Mar 17, 1989 · N12318 · Substantial damageNTSB FTW88IA141Incident · No injuriesIncident investigationFinal reportBoeing 737-300 · Kenton, DEA flameout of the #1 engine occurred due to water ingestion when the aircraft penetrated a vip level 5 thunderstorm and encountered heavy rain while descending with the throttles a flight idle. The engine suffered overtemperature damage to the turbine section…Jul 26, 1988 · N14336 · Minor damageNTSB 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.…Jun 30, 1988 · N791FT · Minor damageNTSB 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 damageNTSB 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 damageNTSB FTW87LA082Accident · Serious injuriesLimited investigationFinal reportBoeing 737-300 · Midland, TXWhile penetrating a line of thunderstorms at 35,000 en route to Midland, TX, from dallas, TX, severe turbulence was encountered. One flight attendant had just sat down but had not fastened his seat belt and was thrown to the floor sustaining serious injuries.Mar 17, 1987 · N314SW · No damage