NTSB investigations: Piper PA-28-161, 2005

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

19642026
NTSB investigations: Piper PA-28-161, 2005 per year, 1964–2026: 728 cases
19641
19661
19671
19691
19711
19775
197819
197930
198030
198137
198231
198314
198416
198520
198620
198726
198819
198922
199028
199122
199223
199321
199417
199514
199613
199715
199813
199915
200016
200111
200211
20039
200415
200514
200617
20078
200822
20098
201010
201113
20128
20138
20146
20157
20167
20176
201811
201910
20202
20219
20225
20236
20247
20253
20264

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 ('7102803', '7102834'))
  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 LAX06CA045Accident · No injuriesData collectionFinal reportPiper PA-28-161 · Panamint Spring, CAthe pilot's improper in-flight selection of unsuitable terrain for landing.Nov 25, 2005 · N8091H · Substantial damageNTSB NYC06FA029Accident · 2 fatalField investigationFinal reportPiper PA-28-161 · Leesburg, VAThe flight instructor's failure to maintain airspeed, which resulted in an inadvertent stall and subsequent impact with trees and terrain.Nov 9, 2005 · N4171T · Substantial damageNTSB LAX06CA026Accident · No injuriesData collectionFinal reportPiper PA-28-161 · Payson, AZa loss of engine power due to fuel exhaustion, which was caused by the pilot's inadequate preflight and in-flight planning, his inadequate fuel consumption calculations, and his failure to divert to an alternate airport before the fuel situation became…Nov 7, 2005 · N2111P · Substantial damageNTSB LAX06LA023Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Lodi, CAa loss of engine power for undetermined reasons. A factor was the trees.Oct 31, 2005 · N83785 · Substantial damageNTSB MIA06CA011Accident · No injuriesData collectionFinal reportPiper PA-28-161 · Vero Beach, FLThe failure of the pilot to maintain directional control of the airplane during the landing roll resulting in the on-ground collision with runway signs.Oct 19, 2005 · N9234V · Substantial damageNTSB IAD05LA133Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-161 · Babylon, NYA broken piston and exhaust valve tappet which resulted in a total loss of engine power, and a forced landing to unsuitable terrain. A contributing factor was the failure of the operator to overhaul the engine at the manufacturer's recommended interval.Sep 6, 2005 · N8270M · Substantial damageNTSB CHI05LA226Accident · 2 fatalLimited investigationFinal reportPiper PA-28-161 · Culver, INThe loss of engine power while maneuvering due to partial failure of the left magneto, and the flight instructor's failure to maintain sufficient airspeed to avoid a stall. An additional cause was improper maintenance by company maintenance personnel,…Aug 10, 2005 · N4512Q · Substantial damageNTSB LAX05CA230Accident · No injuriesData collectionFinal reportPiper PA-28-161 · Tucson, AZthe student pilot's failure to maintain clearance from a fuel truck, and the flight instructor's inadequate supervision.Jul 12, 2005 · N9886K · Substantial damageNTSB CHI05CA105Accident · No injuriesData collectionFinal reportPiper PA-28-161 · South Bend, INThe student pilot failed to compensate for the crosswind condition and failed to maintain directional control. Factors included the crosswind and the windsock.Apr 25, 2005 · N2833F · Substantial damageNTSB MIA05LA093Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Groveland, FLThe pilot's poorly planned approach during a precautionary landing following partial loss of engine power resulting in a go-around and subsequent in-flight collision with trees. A contributing factor in the accident was the inadequate maintenance by the…Apr 15, 2005 · N270FT · Substantial damageNTSB LAX05CA098Accident · No injuriesData collectionFinal reportPiper PA-28-161 · Chandler, AZthe students pilot's failure to maintain directional control resulting in a collision with the taxiway sign.Feb 17, 2005 · N80565 · Substantial damageNTSB LAX05CA093Accident · No injuriesData collectionFinal reportPiper PA-28-161 · Roosevelt, AZthe pilot's failure to maintain directional control.Feb 10, 2005 · N973EL · Substantial damageNTSB LAX05CA067Accident · No injuriesData collectionFinal reportPiper PA-28-161 · Tucson, AZthe pilot's failure to maintain directional control during landing rollout.Jan 8, 2005 · N8351W · Substantial damageNTSB DFW05LA054Accident · No injuriesLimited investigationFinal reportPiper PA-28-161 · Decatur, TXThe student pilot's failure to maintain obstacle clearance and the instructor's inadequate supervision. Contributing factors were the prevailing dark night conditions, and the power line.Jan 8, 2005 · N9419C · Substantial damage