NTSB investigations: Piper PA-30
10 cases on aircraft the registry lists as Piper PA-30, 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 |
|---|---|
| 1983 | 1 |
| 1984 | 1 |
| 1985 | 1 |
| 1986 | 1 |
| 1987 | 1 |
| 1989 | 1 |
| 1992 | 1 |
| 2004 | 1 |
| 2007 | 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 ('7103002')
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 ('7103002')
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 NYC07FA091Accident · 3 fatalField investigationFinal reportPiper PA-30 · Trappe, MDThe pilot's improper decision to fly into an area of thunderstorms, which resulted in a loss of aircraft control and subsequent in-flight breakup. Contributing to the accident was the thunderstorm.NTSB DEN04FA074Accident · 2 fatalField investigationFinal reportPiper PA-30 · Evanston, WYthe pilot's failure to maintain terrain clearance. Contributing factors include snow, low ceiling, icing conditions, and the dark night.NTSB CHI93FA053Accident · 1 fatalField investigationFinal reportPiper PA-30 · Bowman, NDThe non instrument rated private pilot's failure to maintain adequate terrain clearance after inadvertent VFR flight into instrument meteorological conditions.NTSB ATL89FA174Accident · 1 fatalField investigationFinal reportPiper PA-30 · Springfield, TNThe pilot's decision to continue flight into an area of known adverse weather which resulted in his ability to maintain control of the airplane. Contributing factor(s) was: the adverse weather conditions.NTSB NYC87FA204Accident · 4 fatalField investigationFinal reportPiper PA-30 · Lincolnville, METhe plt was making an approach to knox county arpt, rockland me and after receiving a wx report from UNICOM that the local wx was below approach minimums he indicated that he would make a missed approach. There was no further communications from the acft. A…NTSB BFO86FA042Accident · 3 fatalField investigationFinal reportPiper PA-30 · Bowleys Qrtrs, MDDrg arr, TRACON gave the plt the arpt wx & provided vectors for an ILS rwy 32 apch. The plt inquired about a cell that he understood was over the arpt & was advised to standby while the controller (ctlr) checked on it. The ctlr contacted twr psnl who adzd the…NTSB SEA85LA180Accident · Serious injuriesLimited investigationFinal reportPiper PA-30 · Jarbridge, NVShortly after departure the left wing was raised by a gust of wind. During correction the aircraft then yawed right. Almost full aileron was used to maintain level flight. The aircraft then descended to the ground. Inspection of the aircraft revealed no…NTSB DEN85FA043Accident · 3 fatalField investigationFinal reportPiper PA-30-160 · Albuquerque, NMThe flt was en route from forth worth, TX, to santa fe, new Mexico, when the plt decided to divert to Albuquerque. The a/c crashed while being vectored for an ILS approach to rwy 8. The plt received his instrument rating slightly more than 6 mos before the…NTSB NYC83FA049Accident · 2 fatalField investigationFinal reportPiper PA-30 · Atlantic City, NJThe plt had landed at Atlantic City, NJ at aprx 1545 while en route to oxford, CT. Before taking off, he contacted two fss's and both advised that VFR flt was not recommended. The non-instrument rated plt took off at aprx 1920 local time with no flt plan. At…NTSB CHI82DA078Accident · No injuriesFinal reportPiper PA-30 · Valparaiso, INThe pilot reported encountering severe icing conditions after he had canceled his IFR flight plan and had the airport in sight. At that point, he felt that the safest alternative was to continue the approach. The approach was flown at 120 mph with no flaps.…