# NTSB investigations: Piper PA-28R-201: Runway excursion

NTSB aviation accident and incident investigations since 1962: the probable cause, findings, aircraft, crew, weather and docket of each, linked to the FAA registry and the FAA’s own reports.

## Latest cases

- [NTSB CEN26LA186](https://openairdocs.org/ntsb/CEN26LA186.md): Piper PA-28R-201 · West Chicago, IL · Accident · No injuries · Class 4 · Limited · Final report · May 13, 2026 · N31401 · Substantial damage
  > The pilot’s improper decision to attempt an intersection takeoff and delay to abort the takeoff which resulted in a subsequent runway excursion.
- [NTSB GAA24WA151](https://openairdocs.org/ntsb/GAA24WA151.md): Piper PA28R · West End, Bahamas · Accident · No injuries · Class 5 · Foreign · Apr 12, 2024 · N60SU · Substantial damage
- [NTSB CEN20LA321](https://openairdocs.org/ntsb/CEN20LA321.md): Piper PA28R · Seiling, OK · Accident · No injuries · Class 3 · Limited · Final report · Aug 1, 2020 · N9765C · Substantial damage
  > The pilot’s incorrect takeoff performance calculations and delayed aborted takeoff, which resulted in a runway excursion and collision with trees.
- [NTSB WPR14CA018](https://openairdocs.org/ntsb/WPR14CA018.md): Piper PA 28R-201 · Las Vegas, NV · Accident · No injuries · Data collection · Final report · Oct 16, 2013 · N3836M · Substantial damage
  > The collapse of a main landing gear for reasons that could not be determined due to no postaccident examination of the airframe.
- [NTSB WPR12LA247](https://openairdocs.org/ntsb/WPR12LA247.md): Piper PA28R · Peoria, AZ · Accident · No injuries · Limited investigation · Final report · May 29, 2012 · N963WW · Substantial damage
  > A loss of engine power for reasons that could not be determined because postaccident examination did not reveal any anomalies that would have precluded normal operation.
- [NTSB WPR11CA314](https://openairdocs.org/ntsb/WPR11CA314.md): Piper PA-28R-201 · Spanish Fork, UT · Accident · No injuries · Data collection · Final report · Jul 4, 2011 · N47869 · Substantial damage
  > The pilot's improper landing flare, inadequate recovery from a bounced landing and failure to maintain directional control.

## The whole list in SQL

Runs in DuckDB 1.2 or later on the release's Parquet files over HTTPS:

```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."mKey" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.aircraft_model_code IN ('7102816', '7102833')
    AND EXISTS (SELECT 1 FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' s WHERE s.case_mkey = x.case_mkey AND s.aircrafts_position = x.position AND s."tier2Number" = '300' AND s.case_mkey IN (SELECT case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_events.parquet' WHERE "isDefiningEvent")))
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESC
```

This list as a web page: https://openairdocs.org/ntsb-events/300/sequence?model=7102816

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.