NTSB investigations: Piper J5C

12 cases on aircraft the registry lists as Piper J5C. 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

19662026
NTSB investigations: Piper J5C per year, 1966–2026: 12 cases
19661
19671
19681
19721
19791
19861
19881
19942
19981
20101
20251

Latest 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 ('7100712'))
  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.

NTSB ERA25FA283Accident · 1 fatalClass 3 · FieldPreliminary reportPiper J5C · Rochester, NYOn August 1, 2025, about 1330 eastern daylight time, a Piper J5C, NC 28151, was substantially damaged when it was involved in an accident near Rochester, New York. The passenger was fatally injured, and the pilot was seriously injured. The airplane was…Aug 1, 2025 · N28151 · Substantial damageNTSB ANC10CA072Accident · No injuriesData collectionFinal reportPiper J5C · Skwentna, AKThe pilot's failure to maintain directional control during landing, and his selection of unsuitable terrain for landing.Aug 9, 2010 · N38532 · Substantial damageNTSB ANC98LA033Accident · No injuriesLimited investigationFinal reportPiper J5-C · Valdez, AKThe owner/pilot mechanic's improper overhaul of the engine, and lack of proper lubricating cylinder grease. A factor in the accident was the lack of a suitable area for a forced landing.Mar 30, 1998 · N4769C · Substantial damageNTSB ANC95LA001Accident · No injuriesLimited investigationFinal reportPiper J5C · Anchorage, AKThe loss of engine power for undetermined reasons and the lack of a suitable forced landing area.Oct 4, 1994 · N38532 · Substantial damageNTSB MIA94LA188Accident · Minor injuriesLimited investigationFinal reportPiper J5C · Yazoo City, MSPartial blockage of the carburetor by a wasp nest, which was not visible during preflight, and which resulted in the loss of power.Jul 30, 1994 · N74669 · Substantial damageNTSB ATL88LA166Accident · 1 fatalLimited investigationFinal reportPiper J5C · Gulf Shores, ALA witness reported that the airplane encountered a 'downdraft' while attempting to pick up a banner. The main ldg gear caught the banner pick-up line and carried the banner aloft. The witness radioed the plt to advise him of the situation, but received no…May 6, 1988 · N41333 · Substantial damageNTSB MIA86LA196Accident · No injuriesLimited investigationFinal reportPiper J5C · Daytona Beach, FLThe plt stated that he overflew the arpt to observe the wind direction as indicated by the wind sock. Upon landing on rwy 23, he lost control of the acft due to a left quartering tailwind. The acft then went through a chain link fence & came to rest in a…Jun 29, 1986 · N62074 · Substantial damageNTSB ANC79FA054Accident · 1 fatalClosedPiper J-5C · Karluk, AKMay 27, 1979 · N1035N · Substantial damageNTSB OAK73FJA08Accident · 1 fatalClosedPiper J5C · Kaanapali, HINov 25, 1972 · N62032 · DestroyedNTSB DEN68D0243Accident · No injuriesClosedPiper J5C · Lovington, NMMar 19, 1968 · N52920 · Substantial damageNTSB SEA69F0125Accident · 1 fatalClosedPiper J5C · Seaside, ORJul 14, 1967 · N68295 · DestroyedNTSB NYC67F0114Accident · Minor injuriesClosedPiper J5C · Duanesburg, NYJul 12, 1966 · N9203H · Substantial damage