NTSB investigations: Piper PA-34-200T
9 cases on aircraft the registry lists as Piper PA-34-200T, 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
| 1984 | 1 |
|---|---|
| 1985 | 1 |
| 1987 | 1 |
| 1990 | 1 |
| 1997 | 1 |
| 2002 | 1 |
| 2006 | 3 |
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 ('7103406')
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.aircraft_model_code IN ('7103406')
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 CHI06FA094Accident · 4 fatalField investigationFinal reportPiper PA34-200T · Branson, MOThe pilot's failure to maintain sufficient airspeed, which resulted in an inadvertent stall/spin while maneuvering to return to the departure airport for landing after declaring an emergency for unspecified reasons. Additional factors were the low cloud…NTSB NYC06FA078Accident · 2 fatalField investigationFinal reportPiper PA-34-200T · Old Bridge, NJThe pilot's improper decision to conduct visual approach and landing in instrument meteorological conditions, and his failure to maintain adequate clearance from trees and terrain during the go-around. Factors in the accident were the low cloud ceiling and…NTSB SEA06FA039Accident · 1 fatalField investigationFinal reportPiper PA-34-200T · Burlington, WAThe pilot's failure to maintain the published minimum descent altitude and not adhering to the published missed approach procedures, which resulted in an in-flight collision with trees and terrain. Factors contributing to the accident were low ceilings and…NTSB IAD02FA043Accident · 1 fatalField investigationFinal reportPiper PA-34-200T · Oxford, CTThe pilot's failure to follow the published instrument approach procedure. Factors were the night and low ceiling conditions.NTSB NYC97FA173Accident · 1 fatalField investigationFinal reportPiper PA-34-200T · Hancock, MAThe pilot's failure to maintain adequate terrain clearance and the proper altitude. Contributing was mountainous terrain.NTSB DEN90FA058Accident · 1 fatalField investigationFinal reportPiper PA-34-200T · Pueblo, COThe pilot's failure to maintain a proper glide path and sufficient altitude to clear obstacles.NTSB ATL87FA100Accident · 1 fatalField investigationFinal reportPiper PA-34-200T · Georgetown, DEThe plt was cleared for approach with instructions to close flt plan upon landing. Aprx thirty min later approach control called the fss and asked if the plt had been in contact. The reply was negative. No further action was taken by approach control.…NTSB ATL86FA007Accident · 1 fatalField investigationFinal reportPiper PA-34-200T · Charleston, SCThe aircraft was observed on radar as it approached the joint civil - military airport. It passed over near the center of the airport at about 200 feet AGL. There was no reported communication with the aircraft. Several sighting placed the aircraft under at…NTSB MKC84LA230Accident · No injuriesLimited investigationFinal reportMooney M20C · Hannibal, MON7702M experienced an electrical failure en route & diverted to Hannibal. Plt stated he circled the arpt, saw no traffic& decided to land to the south. N38455 had just landed to the north and was on the rwy when the plt saw N7702M attempting to land in the…