# NTSB investigations: Piper PA-32R-301: Abnormal runway contact

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 ERA22LA259](https://openairdocs.org/ntsb/ERA22LA259.md): Piper PA-32R-301 · Spencer, VA · Accident · No injuries · Class 4 · Limited · Final report · Jun 4, 2022 · N8429X · Substantial damage
  > The pilot’s failure to extend the landing gear before landing. Contributing to the accident was the pilot’s failure to use the landing checklist.
- [NTSB CEN21LA112](https://openairdocs.org/ntsb/CEN21LA112.md): Piper PA-32R-301 · Sparta, MI · Accident · No injuries · Class 3 · Limited · Final report · Jan 12, 2021 · N35718 · Substantial damage
  > The pilot’s failure to maintain the proper glideslope during final approach, which resulted in contact with a snowbank at the approach end of the runway.
- [NTSB GAA19CA069](https://openairdocs.org/ntsb/GAA19CA069.md): Piper PA32R · Versailles, OH · Accident · No injuries · Data collection · Final report · Nov 17, 2018 · N4137W · Substantial damage
  > The pilot's improper landing flare, which resulted in landing on the landing gear first and a subsequent loss of directional control, a runway excursion, and impact with a tree and a fence during an attempted go-around.
- [NTSB GAA18CA281](https://openairdocs.org/ntsb/GAA18CA281.md): Piper PA 32R · Cape Carteret, NC · Accident · No injuries · Data collection · Final report · May 14, 2018 · N25WE · Substantial damage
  > The pilot’s steep approach, which resulted in a hard landing and the collapse of the landing gear during touchdown.
- [NTSB CEN11CA197](https://openairdocs.org/ntsb/CEN11CA197.md): Piper PA-32R-301 · Holdenville, OK · Accident · No injuries · Data collection · Final report · Feb 20, 2011 · N8310L · Substantial damage
  > The pilot’s decision to land with a tailwind and his delay in executing a go around.

## 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 ('7103218')
    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" = '090' 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/090/sequence?model=7103218

---
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.