# Incident 20080516836479I: Piper PA32300, Osage Beach, MO, May 16, 2008

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: May 16, 2008, 19:00 local time
- Place: Osage Beach, MO
- Airport: Grand Glaize- Osage Beach
- Damage: Minor damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 38.1104° N, 92.6806° W: Placed by OpenAirDocs at GRAND GLAIZE-OSAGE BEACH (K15), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=38.1104&lon=-92.6806&mi=10
- Aircraft: N419PH, registered now (https://openairdocs.org/aircraft/N419PH) (OpenAirDocs)
- Registry model: Piper PA-32-300 (registry code 7103212, https://openairdocs.org/model/piper-pa-32-300) (OpenAirDocs)
- Registry engine: Lycoming IO-540 series (registry code 41530, https://openairdocs.org/engine/lycoming-io-540-series) (OpenAirDocs)
- Reported make and model: PIPER PA32300
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 140 total, 35 in this make and model, 4 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20080516836479I

## Narrative

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

(-23) THE PIC REPORTED THAT HIS LANDING WAS NORMAL UNTIL THE NOSE WHEEL COLLAPSED DURING ROLL-OUT, CAUSING THE PROPELLER TO CONTACT THE RUNWAY.  HOWEVER, ACCORDING TO AN AIRPORT EMPLOYEE WHO WITNESSED THE INCIDENT, THE FIRST LANDING ATTEMPT RESULTED IN A GO-AROUND.  DURING THE APPROACH, THE WITNESS STATED THAT IT APPEARED THAT THE NOSE GEAR CONTACTED THE RUNWAY FIRST.  THE AIRPLANE ROSE BACK IN THE AIR, AND THEN IT APPEARED THAT EITHER THE AIRPLANE STALLED OR THE PILOT TRIED TO FORCE IT ON.  IN ANY EVENT, WHEN THE AIRPLANE CONTACTED THE RUNWAY AGAIN, THE NOSE GEAR COLLAPSED.  POST-INCIDENT INSPECTION OF THE NOSE GEAR LOWER STRUT ASSEMBLY FRACTURE SHOWED INDICATIONS OF STRESS OVERLOAD, INCLUDING EXCESSIVE SIDE-LOADING.  THERE ALSO APPEARED TO BE FAINT DISCOLORATION ALONG THE FRACTURE EDGE, INDICATING THE POSSIBLITY OF A PRE-EXISTING CRACK.  THIS INCIDENT NR ^PRIVACY DATA OMITTED^, IS CLOSED WITH THIS REPORT.

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.