NTSB investigations: Piper PA-28-235

7 cases on aircraft the registry lists as Piper PA-28-235, where the first occurrence was “Hard landing”. 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

19822026
NTSB investigations: Piper PA-28-235 per year, 1982–2026: 7 cases
19821
19841
19871
19891
19931
19941
19991

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 ('7102810')
      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\" = 200))
  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 IAD99LA053Accident · No injuriesLimited investigationFinal reportPiper PA-28-235 · Zanesville, OHThe pilot not maintaining a proper descent rate and an inadequate flare.Jul 18, 1999 · N235TL · Substantial damageNTSB LAX94LA108Accident · No injuriesLimited investigationFinal reportPiper PA-28-235 · Lovelock, NVThat the pilot's failure to maintain adequate airspeed while on final approach which resulted in an inadvertent stall during the flare.Jan 29, 1994 · N8760W · Substantial damageNTSB CHI93LA088Accident · No injuriesLimited investigationFinal reportPiper PA-28-235 · Lafayette, INThe pilot-in-command's decision to initiate flight into known icing conditions which resulted in an accummulation of airframe ice. The icing conditions and the pilot's disregard of the weather advisory were factors.Feb 6, 1993 · N8784W · Substantial damageNTSB DEN89FA192Accident · 2 fatalField investigationFinal reportPiper PA-28-235 · Bullfrog, UTImproper flare by the pilot, his failure to maintain runway alignment, and the improper remedial action which resulted in a loss of control. The high density altitude and objects (runway light and smudge pot) were considered to be contributing factors.Aug 12, 1989 · N9084W · DestroyedNTSB NYC87LA159Accident · No injuriesLimited investigationFinal reportPiper PA-28-235 · Toms River, NJThe flight was involved in short field landing practice. On the third landing, the pilot allowed the aircraft to stall above the runway surface and then touch down hard, damaging the outboard sections of the wings.May 16, 1987 · N9443W · Substantial damageNTSB FTW84LA260Accident · No injuriesLimited investigationFinal reportPiper PA-28-235 · Odessa, TXDuring the takeoff ground roll the plt noticed the inop airspeed indicator but continued the takeoff. The acft bounced during the long fast landing and traveled off the right side of the rwy. The plt corrected back to the left and the acft touchdown hard off…May 31, 1984 · N16461 · Substantial damageNTSB MKC82DA144Accident · No injuriesFinal reportPiper PA-28-235 · Springfield, MOAfter passing over an imaginary obstacle during a short field landing, the student flared high without adding sufficientpower causing the acft to increase the descent rate. The CFI took control but was too late resulting in a hard landing.Aug 10, 1982 · N7904C · Substantial damage