NTSB investigations: Douglas DC-9-32
15 cases on aircraft the registry lists as Douglas DC-9-32. 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
| 1971 | 1 |
|---|---|
| 1973 | 1 |
| 1981 | 2 |
| 1984 | 2 |
| 1987 | 1 |
| 1990 | 1 |
| 1992 | 1 |
| 1995 | 2 |
| 1996 | 2 |
| 1999 | 1 |
| 2000 | 1 |
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.aircraft_model_code IN ('3022066'))
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.aircraft_model_code IN ('3022066'))
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 DCA01MA005Accident · Minor injuriesMajor investigationFinal reportDouglas DC-9 · Atlanta, GAthe leakage of lavatory fluid from the airplane's forward lavatory onto electrical connectors, which caused shorting that led to a fire. Contributing to the accident were the inadequate servicing of the lavatory and the failure of maintenance to ensure…NTSB CHI99IA136Incident · No injuriesIncident investigationFinal reportMcDonnell Douglas DC-9-32 · Dubuque, IAthe frozen elevator control. Factors to the incident were the rain and the low temperature.NTSB DCA96MA054Accident · 110 fatalClass 1 · MajorFinal reportDouglas DC-9-32 · Miami, FLwhich resulted from a fire in the airplane's class D cargo compartment that was initiated by the actuation of one or more oxygen generators being improperly carried as cargo, were (1) the failure of SabreTech to properly prepare, package, and identify…NTSB FTW96FA118Accident · Minor injuriesClass 1 · FieldFinal reportMcDonnell Douglas DC-9-32 · Houston, TXthe captain's decision to continue the approach contrary to Continental Airlines (COA) standard operating procedures that mandate a go-around when an approach is unstabilized below 500 feet or a ground proximity warning system alert continues below 200 feet…NTSB CHI96IA059Incident · No injuriesIncident investigationFinal reportDouglas DC-9-32 · Saint Louis, MOloss of induction air into the engine inlets resulting in simultaneous loss of power on both engines. Factors relating to this incident were: disconnection of the airplane's hydraulic pumps and generators, slush on the runway and the hydroplaning condition.NTSB ATL95MA106Accident · Serious injuriesClass 1 · MajorFinal reportDouglas DC-9-32 · Atlanta, GAfailure of Turk Hava Yollari maintenance and inspection personnel to perform a proper inspection of a 7th stage high compressor disc, thus allowing the detectable crack to grow to a length at which the disc ruptured, under normal operating conditions,…NTSB NYC92LA076Accident · 1 fatalLimited investigationFinal reportMcdonnell Douglas DC-9-32 · Dayton, OHA failed wheel rim following an inadvertent over inflation by the mechanic. Additional causes were the failure of the mechanic to be aware of the pressure being used and his failure to follow procedures. A factor related to the accident was the failure of the…NTSB CHI90IA166Incident · No injuriesIncident investigationFinal reportMcdonnell Douglas DC-9-32 · Chicago, ILThe pilot-in-command's inadequate weather evaluation. Factors in the incident were the weather and artcc's failure to issue a weather advisory.NTSB BFO88IA012Incident · No injuriesIncident investigationFinal reportMcdonnell Douglas DC-9-32 · Baltimore, MDTwa flt 388 (DC-9, N924L) was in clouds climbing to 7000' when Baltimore (bwi) TRACON adzd that an acft (Piper PA-28R) was straight ahead at 3 mi dscndg fm 6700'. Flt 388 had passed 6000' & the capt requested a traffic avoidance vector. The TRACON ctlr…NTSB FTW85IA011Incident · No injuriesIncident investigationFinal reportCessna Citation 550 · Houston, TXN3322L inadvertently crossed the active rwy 04 at the time N107T became airborne on takeoff from that rwy. A near miss occurred as the captain and 1st officer of N107T observed N3322L on the rwy and made a max performance climb over the top of N3322L. N3322L…NTSB ATL84IA160Incident · No injuriesIncident investigationFinal reportDouglas DC-9-32 · Mount Vernon, ILKansas city ARTCC (zkc) had cleared ozark flt 709 (a DC-9, N923L) to cruise at FL270. While proceeding ese near the edgeof the zkc area, the DC-9 converged on zorro 11 (a flt of 3 F-4'S). The F-4'S had been cleared by indianaplolis ARTCC (zid) to proceed…NTSB MKC81FA051Accident · No injuriesClosedDouglas DC-9 · St.Louis, MONTSB FTW81DA092Accident · Serious injuriesClosedDouglas DC-9 · New Orleans, LANTSB DCA74AZ011Accident · Serious injuriesClosedDouglas DC-9 · Chattanooga, TNNTSB MIA72AM014Accident · No injuriesClosedDouglas DC-9 · Savannah, GA