# Accident 20080524838819A: Piper PA34200T, Sandusky, OH, May 24, 2008

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: May 24, 2008, 17:55 local time
- Place: Sandusky, OH
- Airport: Griffing Sandusky
- Damage: Substantial damage
- Phase of flight: Final Approach
- Operating rules: General operating rules (Part 91)
- Location: 41.4333° N, 82.6522° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=41.4333&lon=-82.6522&mi=10
- Aircraft: N31982, a cancelled registration (https://openairdocs.org/deregistered/N31982-2010-01-22) (OpenAirDocs)
- Registry model: Piper PA-34-200T (registry code 7103406, https://openairdocs.org/model/piper-pa-34-200t) (OpenAirDocs)
- Registry engine: Continental TSIO-360 series (registry code 17019, https://openairdocs.org/engine/continental-tsio-360-series) (OpenAirDocs)
- Reported make and model: PIPER PA34200T
- Reported engine: CONT TSIO360*
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 371 total, 27 in this make and model, 14 in the last 90 days
- NTSB investigation: [NTSB CHI08CA140](https://openairdocs.org/ntsb/CHI08CA140) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20080524838819A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(-23) THE PILOT STATED, THAT "AFTER A MISSING A PRACTICE VOR APPROACH HE ENTERED AND FLEW A NORMAL LEFT TRAFFIC PATTERN FOR RUNWAY 09 AT KSKY.  THE PILOT NOTED THAT ALL WAS NORMAL, BUT HE NOTICED HIS AIRSPEED WAS SLOWING ON FINAL APPROACH".  HIS LAST AIRSPEED CHECK WAS ON SHORT FINAL AND HE DECIDED HE WAS TO SLOW "ABOUT 70 KNOTS" AN ATTEMPT WAS MADE TO ARREST THE SINK RATE BY FLARING.  NO ATTEMPT AT ADDING POWER WAS MADE OR CONSIDERED.  THE AIRCRAFT ENTERED A STALL AT ABOUT 10' AGL AND IMPACTED NOSE LOW SHORT OF THE RUNWAY.  THE INVESTIGATION OF THIS ACCIDENT SUPPORTS THE PILOTS STATEMENT.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB CHI08CA140](https://openairdocs.org/ntsb/CHI08CA140), May 24, 2008: Piper PA-34-200T (N31982), Sandusky, OH, substantial damage. Probable cause: The pilot misjudging the flare and not maintaining airspeed during the landing.

## Other reports on N31982 (1)

Matched to the same aircraft by N-number and date.

- [Incident 20061009021349I](https://openairdocs.org/incident/20061009021349I), Oct 9, 2006: Piper PA34200T (N31982), Bowling Green, KY, Minor damage. (-23) The pilot in command was flight instructor [privacy data omitted] who was giving multi engine/instrument flight instruction to [privacy data omitted].…

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

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