NTSB investigations: Piper PA-28R-200, UT
10 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.
Cases per year
| 1981 | 1 |
|---|---|
| 1988 | 1 |
| 1992 | 1 |
| 1997 | 1 |
| 2003 | 1 |
| 2007 | 1 |
| 2009 | 1 |
| 2010 | 1 |
| 2017 | 1 |
| 2025 | 1 |
Where
Open the mapLatest 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.\"eventStateOrRegion\" = 'UT' 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" = 'UT' 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" DESCRun 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 WPR25FA269Accident · 1 fatalClass 3 · FieldPreliminary reportPiper PA-28R-200 · Alta, UTOn August 31, 2025, about 1720, mountain daylight time a Piper PA28-200R, N1147X, was substantially damaged when it was involved in an accident near Alta, Utah. The pilot was seriously injured, and the passenger sustained fatal injuries. The airplane was…NTSB WPR17LA183Accident · Minor injuriesClass 3 · LimitedFinal reportPiper PA 28R-200 · West Jordan, UTThe pilot's failure to account for operation at high density altitude at or near the airplane’s maximum gross weight, which led to degraded engine performance and prevented the airplane from achieving an adequate airspeed for a positive rate of climb,…NTSB WPR10CA266Accident · No injuriesData collectionFinal reportPiper PA-28R-200 · St. George, UTThe pilot's inadequate compensation for the crosswind conditions and failure to maintain directional control during landing.NTSB WPR09LA417Accident · No injuriesLimited investigationFinal reportPiper PA28R · Wendover, UTThe failure of the pilot to attain and maintain an airspeed sufficient for normal landing gear retraction during initial climb. Contributing to the accident was the pilot's failure to use the airplane's manual override landing gear system, misidentifying that…NTSB LAX08FA001Accident · 2 fatalField investigationFinal reportPiper PA-28R-200 · Cedar City, UTThe pilot's failure to maintain aircraft control while in cruise flight due to spatial disorientation. Contributing to the accident were the dark conditions.NTSB DEN03FA038Accident · 4 fatalField investigationFinal reportPiper PA-28R-200 · La Sal, UTthe loss of engine power (total) due to fuel starvation, the pilot not following procedures/directives (fuel management procedures), and the pilot's inadequate preflight planning/preparation for the flight. Contributing factors were the pilot's inadequately…NTSB SEA97FA105Accident · 3 fatalField investigationFinal reportCessna 182 · Clinton, UTInadequate prior arrangements for formation flight by the pilot-in-command of the Cessna 182, N5434B, and his subsequent failure to see-and-avoid the Piper PA-28R, N5270T. Factors were: the Cessna pilot's visibility of the Piper impaired by the sun;…NTSB 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.NTSB DEN88FA098Accident · 3 fatalField investigationFinal reportPiper PA-28R-200 · Pintura, UTThe plt and two pax departed overton, NV destined for sundance, WY. Witnesses stated that the acft took off under an overcast and followed interstate 15 northbound. A witness driving on the interstate said that he saw N2738R at aprx 600 ft AGL over the…NTSB DEN81FA017Accident · 1 fatalClosedPiper PA-28R · Wendover, UT