NTSB investigations: Piper PA-28-181, 2006

9 cases on aircraft the registry lists as Piper PA-28-181. 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

19652026
NTSB investigations: Piper PA-28-181, 2006 per year, 1965–2026: 787 cases
19651
19661
19681
19711
19722
19741
197616
197716
197829
197923
198028
198136
198221
198324
198410
198533
198626
198723
198821
198910
199020
199119
19929
199319
199420
199522
199612
199717
199820
199916
200010
200115
200210
200310
200420
200515
20069
200714
20088
20098
201011
20117
20128
20137
201412
20159
20168
20178
201813
20198
20206
20219
20227
202319
202415
202513
202611

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 year(c.\"eventDate\") = 2006
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102807', '7102832'))
  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 NYC07CA053Accident · No injuriesData collectionFinal reportPiper PA-28-181 · Cumberland, MDThe pilot's misjudgment of the airplane's distance/altitude during the landing approach.Dec 31, 2006 · N348TF · Substantial damageNTSB CHI06CA239Accident · No injuriesData collectionFinal reportPiper PA-28-181 · Napoleon, MIThe pilot's failure to maintain a proper glidepath during the landing approach, and his excessive airspeed during the landing which resulted in the overrun. A factor was the fence that the airplane impacted.Aug 16, 2006 · N4008Q · Substantial damageNTSB LAX06CA223Accident · No injuriesData collectionFinal reportPiper PA28-181 · Dorris, CAthe pilot's failure to maintain an adequate airspeed during a go-around, which resulted in a stall/mush. A contributing factor was the high density altitude.Jul 3, 2006 · N6413C · Substantial damageNTSB LAX06CA159Accident · Minor injuriesData collectionFinal reportPiper PA-28-181 · Columbia, CAthe pilot's failure to maintain directional control during the landing roll.May 3, 2006 · N441MA · Substantial damageNTSB NYC06CA102Accident · No injuriesData collectionFinal reportPiper PA-28-181 · Jeannette, PAExcessively worn brake pads and rotors, which resulted in a runway overrun and subsequent collision with a tree.Apr 23, 2006 · N6775F · Substantial damageNTSB CHI06CA144Accident · No injuriesData collectionFinal reportPiper PA-28-181 · Logansport, INThe pilot's improper flare and inadequate recovery from a bounced landing.Apr 9, 2006 · N793MA · Substantial damageNTSB LAX06CA272Accident · No injuriesData collectionFinal reportPiper PA-28-181 · Coalinga, CAthe pilot's misjudged landing flare, which resulted in a bounced landing, and his inadequate recovery technique that led to a hard landing.Apr 8, 2006 · N8068J · Substantial damageNTSB NYC06LA066Accident · 1 fatalLimited investigationFinal reportPiper PA-28-181 · Henderson, WVThe pilot's improper decision to attempt the off-airport takeoff; and his improper decision to continue the takeoff after striking a pole during the takeoff roll.Jan 31, 2006 · N8335Y · Substantial damageNTSB SEA06LA044Accident · No injuriesLimited investigationFinal reportPiper PA-28-181 · Brookings, ORThe pilot's inadequate in flight decision by failing to refuel while en route, resulting in fuel exhaustion and the loss of engine power. Trees and no suitable terrain for the landing were factors.Jan 13, 2006 · N35681 · Substantial damage