NTSB investigations: Piper J3C-65, 2005
4 cases on aircraft the registry lists as Piper J3C-65. 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
| 1964 | 91 |
|---|---|
| 1965 | 62 |
| 1966 | 88 |
| 1967 | 58 |
| 1968 | 56 |
| 1969 | 66 |
| 1970 | 49 |
| 1971 | 44 |
| 1972 | 30 |
| 1973 | 28 |
| 1974 | 23 |
| 1975 | 31 |
| 1976 | 39 |
| 1977 | 28 |
| 1978 | 23 |
| 1979 | 22 |
| 1980 | 18 |
| 1981 | 18 |
| 1982 | 12 |
| 1983 | 14 |
| 1984 | 20 |
| 1985 | 22 |
| 1986 | 19 |
| 1987 | 13 |
| 1988 | 18 |
| 1989 | 7 |
| 1990 | 11 |
| 1991 | 13 |
| 1992 | 12 |
| 1993 | 8 |
| 1994 | 10 |
| 1995 | 10 |
| 1996 | 18 |
| 1997 | 10 |
| 1998 | 11 |
| 1999 | 13 |
| 2000 | 10 |
| 2001 | 10 |
| 2002 | 4 |
| 2003 | 9 |
| 2004 | 5 |
| 2005 | 4 |
| 2006 | 8 |
| 2007 | 10 |
| 2008 | 10 |
| 2009 | 7 |
| 2010 | 9 |
| 2011 | 7 |
| 2012 | 4 |
| 2013 | 3 |
| 2014 | 10 |
| 2015 | 4 |
| 2017 | 7 |
| 2018 | 5 |
| 2019 | 9 |
| 2020 | 4 |
| 2021 | 10 |
| 2022 | 5 |
| 2023 | 7 |
| 2024 | 7 |
| 2025 | 4 |
| 2026 | 7 |
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\") = 2005
AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7100510'))
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") = 2005
AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7100510'))
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 ATL05LA117Accident · Minor injuriesLimited investigationFinal reportPiper J3C-65 · Mocksville, NCThe loss of engine power due to fuel system contamination. A factor was trees.NTSB ATL05LA111Accident · 1 fatalLimited investigationFinal reportPiper J3C-65 · Yadkinville, NCThe pilots failure to maintain adequate clearance from object and inadequate visual look-out while maneuvering resulted in an in-flight collision with power lines.NTSB NYC05CA104Accident · No injuriesData collectionFinal reportPiper J3C-65 · Fredericksburg, PAThe pilot's improper engine starting procedures, which resulted in the airplane taxiing unoccupied and impacting a light pole.NTSB IAD05LA042Accident · No injuriesLimited investigationFinal reportPiper J3C-65 · Andover, NJThe pilot receiving instruction's failure to maintain directional control during the landing roll. Factors in the accident were the flight instructors delayed remedial action, and crosswind.