NTSB investigations: Piper PA-28R-200

24 cases on aircraft the registry lists as Piper PA-28R-200, where the first occurrence was “In flight collision with terrain/water”. 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-28R-200 per year, 1982–2026: 24 cases
19822
19831
19841
19852
19861
19891
19901
19911
19923
19931
19942
19951
19961
19971
19982
20011
20022

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 ('7102811')
      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\" = 230))
  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 FTW02FA262Accident · 2 fatalField investigationFinal reportPiper PA-28R-200 · Chromo, COThe flight instructor's failure to maintain clearance with the mountainous terrain during the cross-country flight. A contributing factor was the dark night light conditions.Sep 24, 2002 · N6227J · DestroyedNTSB LAX02FA255Accident · 2 fatalField investigationFinal reportPiper PA-28R-200 · Echo Summit, CAThe pilot's decision to continue the flight into the rising mountainous terrain, and subsequent failure to maintain clearance with the trees. Contributing factors were the rising mountainous terrain, and the high density altitude,Aug 19, 2002 · N7794C · DestroyedNTSB SEA01LA133Accident · Minor injuriesLimited investigationFinal reportPiper PA-28R · Cut Bank, MTThe pilot's failure to maintain a speed above stall velocity (Vs) during the after-takeoff climb. Factors include a high density altitude, and a dust devil/whirlwind located along the route of departure.Jul 10, 2001 · N8475C · Substantial damageNTSB LAX99FA028Accident · 3 fatalField investigationFinal reportPiper PA-28R-200 · Bishop, CAThe failure of the pilot-in-command, after encountering a downdraft, to maneuver and maintain clearance from mountainous terrain. Physical impairment due to hypoxia was a factor in the accident.Nov 6, 1998 · N2737R · DestroyedNTSB LAX98FA189Accident · 4 fatalField investigationFinal reportPiper PA-28R-200 · Lytle Creek, CAthe pilot's intentional VFR descent into instrument meteorological conditions, resulting in a collision with mountainous terrain.Jun 8, 1998 · N16344 · DestroyedNTSB FTW97FA100Accident · 3 fatalField investigationFinal reportPiper PA-28-200 · Lone Wolf, OKthe pilot's impairment of judgment and performance due to drugs, his resultant improper planning/decision, and his failure to maintain sufficient altitude (clearance above a lake), while performing aerobatic flight. Factors relating to the accident were: the…Feb 3, 1997 · N33322 · DestroyedNTSB SEA96FA170Accident · 3 fatalField investigationFinal reportPiper PA-28R-200 · Libby, MTcollision with rising mountainous terrain for unknown reason(s).Jul 26, 1996 · N3071R · DestroyedNTSB ATL95FA128Accident · 2 fatalField investigationFinal reportPiper PA-28R-200 · Raleigh, NCThe pilot's failure to follow proper IFR procedures by descending below the decision height. Factors relating to the accident were the weather conditions and the dark night.Jul 5, 1995 · N15743 · DestroyedNTSB BFO95FA020Accident · 2 fatalField investigationFinal reportPiper PA-28R-200 · Nesquehoning, PAthe non-instrument-rated pilot's poor in-flight decision to continue VFR flight into instrument meteorological conditions, at night, and his failure to maintain sufficient altitude to ensure clearance from obstructions/terrain. Related factors were the…Dec 13, 1994 · N33049 · DestroyedNTSB FTW95FA002Accident · Serious injuriesField investigationFinal reportPiper PA-28R-200 · Pagosa Springs, COThe pilot's continued flight into known adverse weather. Factors were the pilot's lack of familiarity with the geographic area, the turbulence and high density altitude.Oct 1, 1994 · N1480X · DestroyedNTSB MIA93LA092Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Walls, MSThe pilot-in-command's delay in aborting the landing.Mar 24, 1993 · N55919 · Substantial damageNTSB SEA93FA025Accident · 1 fatalField investigationFinal reportPiper PA-28R-200 · Cedar City, UTClearance from mountainous terrain was not maintained. Factors to the accident were: dark night condition, snow showers, and intentional flight into known adverse weather.Nov 23, 1992 · N5108S · DestroyedNTSB LAX92LA398Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Avalon, CAThe pilot's intentional flight at an altitude which provided insufficient clearance from the water.Sep 15, 1992 · N33SM · Substantial damageNTSB BFO92LA043Accident · No injuriesLimited investigationFinal reportPiper PA-28R · Manville, NJThe pilot's failure to maintain obstacle clearance.Mar 21, 1992 · N9348N · Substantial damageNTSB NYC92LA040Accident · No injuriesLimited investigationFinal reportPiper PA28R-200 · Piqua, OHThe pilot allowed the airplane to get too low on short final and struck the terrain short of the runway. Factors in the accident were the proper glide path was not maintained, resulting in the intended touchdown point not being attained.Dec 7, 1991 · N55786 · Substantial damageNTSB FTW91FA010Accident · 1 fatalField investigationFinal reportPiper PA-28R-200 · Kingsland, TXThe pilot's failure to avoid flying into the mountain.Oct 26, 1990 · N41586 · DestroyedNTSB LAX90FA031Accident · 1 fatalField investigationFinal reportPiper PA-28R-200 · Camarillo, CAImproper IFR procedure by the pilot, and his failure to maintain the minimum descent altitude (mda) for that segment of the VOR approach. Factors related to the accident were: darkness, low ceiling, fog, haze, the pilot's lack of recent instrument experience,…Nov 13, 1989 · N2723R · DestroyedNTSB BFO87FA004Accident · 2 fatalField investigationFinal reportPiper PA-28R-200 · Mount Pleasant, MDThe acft was on the second apch attempt for ILS rwy 23 when the accident occurred- on the first attempt the pilot flew outbound instead of inbound on the localizer course. For the second attempt the pilot was cleared for a full apch for ILS rwy 23; which…Oct 26, 1986 · N4347X · DestroyedNTSB MKC86LA012Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Gardner, KSThe pilot stated that he was landing on runway 8 with a right crosswind and had the right wing down for wind correction. The right wheel impacted a lip on the approach end of the runway, 6 inches below the level of the runway. The right gear collapsed, the…Oct 17, 1985 · N43429 · Substantial damageNTSB MIA85IA197Incident · No injuriesIncident investigationFinal reportPiper PA-28R-200 · Ft. Pierce, FLThe landing check list was not properly followed and both pilots neglected to extend the landing gear in preparation for landingJun 19, 1985 · N5033T · Minor damageNTSB NYC84LA304Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Monticello, NYAccording to the plt, he was flying instrument approaches to touch and go landings and neglected to extend the landing gear. The automatic gear extension system extended the left main gear before the acft landed.Sep 5, 1984 · N4363T · Substantial damageNTSB LAX84LA027Accident · Minor injuriesLimited investigationFinal reportPiper PA-28R-200 · San Diego, CAAfter departing north island nas (naval air station), the plt attempted to change frequencies, but the megahertz (mhz) tuning knob came off at a setting of 122.1 mhz. He could still use the knob for tuning tenths of a mhz, so he contacted San Diego fss on…Oct 23, 1983 · N5021S · DestroyedNTSB ATL83FLG03Accident · Minor injuriesFinal reportPiper PA-28R-200 · Cleveland, SCThe plt stated he was VFR on top of a broken cloud layer & decided to descend through an opening. After descending clear of the clouds he was in a pass with hills on each side & not enough room to turn around. He continued north along the highway hoping the…Dec 24, 1982 · N9327N · DestroyedNTSB LAX82DA348Accident · No injuriesFinal reportPiper PA-28R-200 · Prescott, AZAccording to the pilot, he planned a fuel stop at needles, CA, but was unaware that services were not available until after arrival. He departed needles with low fuel in both tanks and attempted to reach Prescott, AZ before dark. However, darkness occurred…Sep 19, 1982 · N7675C · Substantial damage