NTSB investigations: Piper PA-28-181, 2001

15 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, 2001 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\") = 2001
    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 MIA02LA019Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-181 · Deland, FLThe loss of engine power during takeoff/initial climb due to undetermined reasons.Nov 19, 2001 · N85TT · Substantial damageNTSB ATL02FA008Accident · 3 fatalField investigationFinal reportPiper PA-28-181 · McEwen, TNThe pilot initiated a VFR flight into known IMC conditions which resulted in a loss of control of the airplane due to spatial disorientation. Factors were the low ceilings.Nov 3, 2001 · N43334 · DestroyedNTSB ATL02LA004Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-181 · Brunswick, GAThe pilot's improper inflight planning which resulted in fuel exhaustion, and subsequent loss of engine power. A factor was the none suitable terrain.Oct 24, 2001 · N4149D · Substantial damageNTSB NYC01LA182Accident · No injuriesLimited investigationFinal reportPiper PA-28-181 · Mattituck, NYThe pilot's failure to attain a proper touchdown point. A factor was the tailwind.Jul 21, 2001 · N17AV · Substantial damageNTSB CHI01LA268Accident · Serious injuriesLimited investigationFinal reportPiper PA-28-181 · Gladwin, MIThe pilot's poor decision to exit the airplane onto the wing while the propeller was running.Jul 14, 2001 · N8253A · No damageNTSB SEA01LA130Accident · No injuriesLimited investigationFinal reportPiper PA-28-181 · Tekoa, WAThe non-current pilot's failure to maintain sufficient altitude or clearance with wheat crops on short final, and the flight instructor's inadequate remedial action. Factors included wheat crops and a dirt bank on short final, the runway's lack of a visual…Jul 13, 2001 · N4920F · Substantial damageNTSB CHI01LA187Accident · No injuriesLimited investigationFinal reportPiper PA-28-181 · Brooklyn, MIThe proper touchdown point exceeded, all of the available runway not used, and aircraft control not being maintained by the pilot during the landing. Factors to the accident were the pilot mistaking the taxiway for the runway, the pilot not performing a…Jun 24, 2001 · N8210Z · Substantial damageNTSB LAX01LA214Accident · No injuriesLimited investigationFinal reportPiper PA-28-181 · Sedona, AZthe induction manifold fire resulting from an engine backfire during engine start. The reason for the engine backfire was not determined.Jun 16, 2001 · N4299Q · Substantial damageNTSB CHI01LA166Accident · Minor injuriesLimited investigationFinal reportPiper PA-28-181 · Bloomington, ILThe pilot's failure to maintain aircraft control during the visual approach for landing.Jun 16, 2001 · N75238 · Substantial damageNTSB MIA01LA156Accident · No injuriesLimited investigationFinal reportPiper PA-28-181 · Bennettsville, SCThe pilot failure to obtain the proper touchdown point on the runway resulting in the airplane landing long, over running the runway, colliding with a telephone pole separating the right wing, and coming to rest in the parking lot of a restaurant.Jun 9, 2001 · N3066G · Substantial damageNTSB LAX01FA308Accident · 1 fatalField investigationFinal reportPiper PA-28-181 · Lytle Creek, CAThe pilot's inadequate decision to fly into an area of rising terrain.Jun 4, 2001 · N8253W · Substantial damageNTSB ATL01FA048Accident · 2 fatalField investigationFinal reportPiper PA-28-181 · Jasper, GAThe pilot disregarded preflight weather briefing information, and continued visual flight into known instrument weather conditions and collided with trees.Apr 6, 2001 · N31566 · DestroyedNTSB LAX01LA122Accident · No injuriesLimited investigationFinal reportPiper PA-28-181 · Gila Bend, AZFailure of the CFI to properly supervise the flight and the failure of the dual studen to maintain flying airspeed. A contributing factor was the wind shear encountered.Mar 20, 2001 · N4188E · Substantial damageNTSB SEA01LA056Accident · No injuriesLimited investigationFinal reportPiper PA-28-181 · North Bend, ORThe pilot's failure to maintain clearance from the delivery truck while taxing. The pilot being distracted is a factor.Feb 25, 2001 · N8133C · Substantial damageNTSB LAX01LA094Accident · No injuriesLimited investigationFinal reportPiper PA-28-181 · San Diego, CAFuel starvation due to the pilot inadvertently shutting off its supply on approach for landing.Feb 9, 2001 · N8122G · Substantial damage