NTSB investigations: Piper PA-34-220T
4 cases on aircraft the registry lists as Piper PA-34-220T, where the first occurrence was “In flight encounter with weather”. 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
| 1982 | 1 |
|---|---|
| 1984 | 1 |
| 1985 | 1 |
| 1988 | 1 |
Where
Open the mapLatest 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 ('7103420', '7103223')
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\" = 240))
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 ('7103420', '7103223')
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" = 240))
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 FTW88FA161Accident · 5 fatalField investigationFinal reportPiper PA-34-220T · Carthage, TXDrg a night arrival, the plt rprtd he could make a visual apch. At 2341:37 CDT, the ARTCC controller informed him the destn arpt was straight ahead at 12 mi & requested that he rprt when the arpt was in sight. At 2343:30, he rprtd the rwyin sight & the…NTSB FTW85FA104Accident · 1 fatalField investigationFinal reportPiper PA-34-220T · Victoria, TXThe plt had rented the acft on January 28, 1985, with route of flt unknown. No reported contact was made with the acft. The acft impacted the surface during hours of darkness in instrument meteorological conditions and was demolished. The plt was fatally…NTSB NYC84FA247Accident · 2 fatalField investigationFinal reportPiper PA-34-220T · Newcomb, NYThe flight was operating in accordance with f.a.r. part 135.the plt filed a VFR flt plan and was cruising at an altitude of 5,500 ft when clouds were encountered. The plt attempted to descend to 3,500 but collided with the santanonimountain at an elevation of…NTSB FTW83FA298Accident · 4 fatalField investigationFinal reportPiper PA-34-200T · Canjilon, NMPrior to departing helena, mt at 1209, the plt received a wx briefing from the great falls fss. The dfw 021240Z area forecast, valid until 0700Z on 11/3/82, was not available. The fss briefer made this deficiency known to the plt & recommended that he receive…