NTSB investigations: Pratt & Whitney JT9D series
6 cases on aircraft whose registry engine model is Pratt & Whitney JT9D series, where the first occurrence was “Airframe/component/system failure/malfunction”. 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
| 1983 | 1 |
|---|---|
| 1993 | 1 |
| 1996 | 1 |
| 1997 | 1 |
| 2000 | 1 |
| 2003 | 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.engine_model_code IN ('52054')
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\" = 130))
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 ('52054')
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" = 130))
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 SEA04IA010Incident · No injuriesIncident investigationFinal reportBoeing 747-100 · Lyon, FranceAn undetermined malfunction in an aircraft system while in cruise flight leading to a fire in the engine number four B Loop portion (Card A16) of the fire detection controls cardfile.NTSB CHI00IA152Incident · No injuriesIncident investigationFinal reportBoeing 767-222 · Lafayette, INThe blocked drain lines in the canted pressure deck and the frozen aileron cable.NTSB MIA97IA147Incident · No injuriesIncident investigationFinal reportBoeing 747-2R7F · Miami, FLdisbonding and separation of the right inboard wing fixed trailing edge panel during cruise flight, which resulted in damage to the inboard fore flap and inboard mid flap, and a subsequent precautionary landing at the departure airport.NTSB IAD96IA098Incident · No injuriesIncident investigationFinal reportBoeing 747-136 · Jamaica, NYfailure of the constant speed drive (CSD) to disconnect from the generator. Contributing to the cause was the failure of the FAA approved overhaul facility to follow the manufacturer's overhaul manual.NTSB NYC93IA184Incident · No injuriesIncident investigationFinal reportBoeing 747-200 · New York, NYThe improper installation of the fairing by company maintenance personnel, resulting in the infligh separation of the fairing in flight.NTSB DEN84IA041Incident · No injuriesIncident investigationFinal reportBoeing 767 · Denver, COOn takeoff roll the no 3 wheel on the right main landing gear fell off the acft. The acft returned and landed without further incident. The wheel bearing was found faileddue to cosmoline contamination.