NTSB investigations: Piper PA-28-151, 2005

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

19742026
NTSB investigations: Piper PA-28-151, 2005 per year, 1974–2026: 409 cases
197412
197522
197625
197729
197838
197922
198018
198114
19829
198310
198410
19855
19865
19877
198810
19894
199011
19919
19924
19939
19946
199511
19967
19978
19986
19994
20002
20014
20026
20034
20045
20058
20063
20077
20081
20097
20104
20123
20133
20143
20153
20161
20172
20183
20192
20205
20213
20224
20232
20244
20252
20263

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\") = 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 ('7102805', '7104223'))
  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 SEA06CA032Accident · No injuriesData collectionFinal reportPiper PA-28-151 · Emmett, IDThe pilot's inadequate in-flight decision by failing to refuel while en route, resulting in fuel exhaustion and the loss of power. A factor was the fence post.Dec 25, 2005 · N5695V · DestroyedNTSB LAX05FA255Accident · 1 fatalField investigationFinal reportPiper PA-28-151 · San Luis Obispo, CAThe pilot's continued flight into instrument meteorological conditions, and his failure to maintain clearance from the rising hilly terrain. Contributing factors were the pilot's inexperience regarding flying during the dark, nighttime condition, and the low…Aug 2, 2005 · N4401X · DestroyedNTSB CHI05CA205Accident · No injuriesData collectionFinal reportPiper PA-28-151 · Holland, MIThe pilot's failure to maintain adequate airspeed which resulted in a stall, and subsequent collision with trees. Contributing to the accident were the trees.Jul 28, 2005 · N602EA · DestroyedNTSB CHI05CA174Accident · No injuriesData collectionFinal reportPiper PA-28-151 · Willmar, MNThe pilot's improper flare which resulted in a hard landing.Jun 26, 2005 · N9027F · Substantial damageNTSB IAD05LA057Accident · Serious injuriesLimited investigationFinal reportPiper PA-28-151 · Hampton, NHThe pilot's improper decision to depart with a tailwind, and his failure to perform preflight performance calculations.Apr 20, 2005 · N8251F · DestroyedNTSB CHI05LA086Accident · No injuriesLimited investigationFinal reportPiper PA-28-151 · Waunakee, WIThe pilot's inadequate preflight planning and the delay in aborting the landing which resulted in the subsequent insufficient airspeed. Factors associated with the accident were the night light conditions, the fence, and the pole which the airplane contacted.Apr 3, 2005 · N56715 · DestroyedNTSB ATL05CA064Accident · No injuriesData collectionFinal reportPiper PA28-151 · Eastman, GAThe certified flight instructors failure to maintain a visual look out while demonstrating a simulated emergency landing resulting in an in-flight collision with a known transmission wire.Mar 19, 2005 · N32033 · Substantial damageNTSB LAX05CA066Accident · No injuriesData collectionFinal reportPiper PA-28-151 · Tucson, AZthe pilot's failure to maintain directional control during landing rollout.Jan 8, 2005 · N151MM · Substantial damage