NTSB investigations: Pratt & Whitney JT8D-1
4 cases on aircraft whose registry engine model is Pratt & Whitney JT8D-1, where the first occurrence was “In flight collision with object”. 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
| 1985 | 1 |
|---|---|
| 1987 | 1 |
| 1989 | 1 |
| 1998 | 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 ('52044')
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\" = 220))
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 ('52044')
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" = 220))
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 FTW98IA208Incident · No injuriesIncident investigationFinal reportBoeing 727-25C · Colorado Sprngs, COAn inadvertent inflight collision with a flock of large birds.NTSB FTW89IA152Incident · No injuriesIncident investigationFinal reportBoeing 727-231 · Kenner, LAInaccurate operators procedures/directives and the improper takeoff performance data computed by the captain. Poor flight crew coordination was considered a factor as well a wrong runway selection for the computed takeoff data.NTSB LAX87MA125Accident · No injuriesMajor investigationFinal reportBoeing 727-224 · Los Angeles, CAAfter a ngt lndg on north side of Los Angeles intl arpt, Cessna 310, N98834, was taxied south (s) to delta cargo area. Bfr rchg s rwys (25L & 25R), the plt stopped short of kilo ramp bhnd another acft (N61C) & contacted s gnd ctlr (GC-1). He was told to hold…NTSB MKC86LA025Accident · No injuriesLimited investigationFinal reportBoeing 727-23 · Bellevue, NEDuring a night arrival, a Boeing 727, operating as American flt 334, was vectored for an apch to rwy 32L. While descending thru about 5000 ft MSL, aprx 12 mi south of the arpt, the acft reportedly collided with a flock of snow geese. The ATC controller had…