NTSB investigations: Pratt & Whitney JT8D series

6 cases on aircraft whose registry engine model is Pratt & Whitney JT8D series, where the first occurrence was “Near collision between aircraft”. 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

19872026
NTSB investigations: Pratt & Whitney JT8D series per year, 1987–2026: 6 cases
19872
19891
19911
19941
20001

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 ('52053', '52377')
      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\" = 280))
  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 ANC00IA088Incident · No injuriesIncident investigationFinal reportMcDonnell Douglas MD-82 · Anchorage, AKAn inoperative traffic alert and collision avoidance system (TCAS).Jul 11, 2000 · N935AS · No damageNTSB LAX94IA331Incident · Minor injuriesIncident investigationFinal reportMcdonnell Douglas MD-82 · Reno, NVFailure of the area supervisor/departure controller (supvr/ctlr) to stay at his radar position and ensure that required communications were maintained. Factors related to the incident were: failure of the local tower controller instruct the flightcrew of…Aug 19, 1994 · N954AS · No damageNTSB CHI92IA061Incident · No injuriesIncident investigationFinal reportMcdonnell Douglas DC-10-30 · Chicago, ILThe local controller's not understanding read back of radio communications. Factors include the pilot-in-command of flight 73 not understanding verbal instructions; local controller not visually identifying the aircraft; and inadequate surveillance (FAA) in…Dec 23, 1991 · N142AA · 2 aircraft · No damageNTSB FTW89IA064Incident · No injuriesIncident investigationFinal reportMcdonnell Douglas DC-9-82 · Houston, TXFailure of the TRACON final approach controller to assure radar separation between the aircraft. Factors related to the accident were: inadequate supervision by the ATC supervisor, excessive workload for the controller, unclear instructions by the controller,…Mar 1, 1989 · N820NY · 2 aircraft · No damageNTSB LAX88IA009Incident · No injuriesIncident investigationFinal reportMcdonnell Douglas DC-9-82 · Ontario, CAFailure of the general aviation aircraft to visually identify the transport aircraft. Factures contributing to the incident were: failure of the general aviaiton aircraft to establish communications with ATC prior to entering the arsa and maintaining a poor…Oct 9, 1987 · N413AA · No damageNTSB CHI87IA135Incident · No injuriesIncident investigationFinal reportMcdonnell Douglas DC-9-82 · Chicago, ILAmerican flt 637 was on departure from Chicago-o'hare intl arpt (ord), climbing thru 7300' MSL, when it passed American flt 393 with aprx 500' vertical sepn & 1/4 mi horizontal sepn. This occurred after an air traffic assistant, who was working the clnc…May 30, 1987 · N224AA · No damage