NTSB investigations: Piper PA-36-300, 1996
5 cases on aircraft the registry lists as Piper PA-36-300. 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
| 1977 | 3 |
|---|---|
| 1978 | 5 |
| 1979 | 5 |
| 1980 | 4 |
| 1981 | 6 |
| 1984 | 3 |
| 1985 | 2 |
| 1986 | 2 |
| 1987 | 1 |
| 1988 | 1 |
| 1989 | 1 |
| 1990 | 2 |
| 1991 | 1 |
| 1992 | 1 |
| 1993 | 1 |
| 1994 | 1 |
| 1995 | 1 |
| 1996 | 5 |
| 1998 | 1 |
| 2000 | 2 |
| 2001 | 1 |
| 2002 | 1 |
| 2003 | 1 |
| 2008 | 1 |
| 2011 | 1 |
| 2012 | 1 |
| 2013 | 1 |
| 2017 | 1 |
| 2026 | 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 year(c.\"eventDate\") = 1996
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7103612'))
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 year(c."eventDate") = 1996
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7103612'))
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 SEA97LA010Accident · 1 fatalLimited investigationFinal reportPiper PA-36-300 · Prosser, WAfailure of the pilot to maintain clearance from the terrain, while en route to an apple orchard that he intended to spray. A factor relating to the accident was: the turbulent wind condition over the hills.NTSB FTW97LA029Accident · No injuriesLimited investigationFinal reportPiper PA-36-300 · Stanton, TXPilot's failure to maintain clearance with a wire resulting in the separation of the rudder and a loss of aircraft control.NTSB FTW96LA353Accident · No injuriesLimited investigationFinal reportPiper PA-36-300 · Hale Center, TXthe pilot's inadequate preflight planning/preparation and failure to obtain and/or maintain adequate airspeed after takeoff, which resulted in an inadvertent stall/mush. The overweight condition of the airplane and high density altitude were related factors.NTSB FTW96LA264Accident · No injuriesLimited investigationFinal reportPiper PA-36-300 · Littlefield, TXThe total loss of engine power due to the failure of the number 5 and 6 connecting rods. A factor was the lack of suitable terrain for the forced landing.NTSB FTW96LA126Accident · Minor injuriesLimited investigationFinal reportPiper PA-36-300 · Andrews, TXthe mechanic's improper overhaul of the engine. Factors were: the pilot in command's inability to maintain visual lookout due to oil on the windscreen and unsuitable terrain for the forced landing.