NTSB investigations: Piper PA-28R-200, OK

13 cases on aircraft the registry lists as Piper PA-28R-200. 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.

Defining event

Finding

Phase of flight

Aircraft model

Cases per year

19712026

NTSB investigations: Piper PA-28R-200, OK per year, 1971–2026: 13 cases
1971	1
1976	2
1977	1
1979	1
1981	2
1983	1
1986	1
1989	1
1994	1
1997	1
2012	1

Where

Open the map

Latest cases

Query with SQL

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."eventStateOrRegion" = 'OK' AND c."eventCountry" = 'USA' AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102811')) ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC

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.\"eventStateOrRegion\" = 'OK' AND c.\"eventCountry\" = 'USA'
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102811'))
  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.

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."eventStateOrRegion" = 'OK' AND c."eventCountry" = 'USA'
  AND c."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102811'))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC

Run it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.

NTSB CEN12CA671Accident · No injuriesData collectionFinal reportPiper PA-28R-200 · Goldsby, OKThe commercial pilot did not attain the proper touchdown point during the landing, which resulted in a premature touchdown and an impact with the edge of the runway surface.Aug 29, 2012 · N7602C · Substantial damage NTSB 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 · Destroyed NTSB FTW95LA070Accident · Serious injuriesLimited investigationFinal reportPiper PA-28R-200 · Oklahoma City, OKThe loss of engine power due to fuel starvation as a result of improper fuel selector position. Factors were the dark night and lack of suitable terrain for the forced landing.Dec 22, 1994 · N2874R · Substantial damage NTSB FTW89LA098Accident · No injuriesLimited investigationFinal reportPiper PA-28R-200 · Edmond, OKImproper maintenance performed by the company mechanic who failed to tighten the oil sump plug, and also failed to safety it.May 24, 1989 · N3940X · Substantial damage NTSB FTW86LA157Accident · Serious injuriesLimited investigationFinal reportPiper PA-28R-200 · Afton, OKThe pilot stated he was making a precautionary landing at night due to engine roughness and impacted electrical transmission wires. Investigation failed to disclose any reason for the reported engine roughness.Aug 30, 1986 · N214PR · Substantial damage NTSB FTW83FA406Accident · 1 fatalField investigationFinal reportPiper PA 28R-200 · Copan, OKThe acft collided with an electric transmission line and burned during an emergency landing. The flt had been in progress only an hour when the plt lost his engine oil pressure and his engine failed. ATC gave him a heading to the nearest arpt but he could not…Aug 31, 1983 · N1292T · Destroyed NTSB FTW81FPM18Accident · No injuriesClosedPiper PA-28R · Jay, OKAug 6, 1981 · N4509X · Substantial damage NTSB FTW81FPM06Accident · No injuriesClosedPiper PA-28 · Atoka, OKJan 4, 1981 · N8824E · Substantial damage NTSB FTW79FPM15Accident · No injuriesClosedPiper PA-28R · Tulsa, OKSep 27, 1979 · N1073X · Substantial damage NTSB FTW77FA073Accident · 3 fatalClosedPiper PA-28R · Hugo, OKAug 28, 1977 · N33862 · Destroyed NTSB FTW76DPD61Accident · No injuriesClosedPiper PA-28R · Idabel, OKSep 30, 1976 · N1986T · Substantial damage NTSB FTW76AF070Accident · 1 fatalClosedPiper PA-28R · Boswell, OKMar 11, 1976 · N33767 · Destroyed NTSB FTW71FPJ40Accident · 1 fatalClosedPiper J3C · Lindsay, OKApr 21, 1971 · N42682 · Destroyed