# Accident 20030725021689A: Cessna 172P, Huntingburg, IN, July 25, 2003

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: July 25, 2003, 13:00 local time
- Place: Huntingburg, IN
- Airport: Huntingburg Airport
- Damage: Minor damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 38.2489° N, 86.9536° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=38.2489&lon=-86.9536&mi=10
- Aircraft: N99040, registered now (https://openairdocs.org/aircraft/N99040) (OpenAirDocs)
- Registry model: Cessna 172P (registry code 2072436, https://openairdocs.org/model/cessna-172p) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172P
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 1,079 total, 229 in this make and model, 28 in the last 90 days
- NTSB investigation: [NTSB CHI03LA229](https://openairdocs.org/ntsb/CHI03LA229) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20030725021689A

## Narrative

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

(-23) THE AIRPLANE BOUNCED DURING LANDING AND THE PROPELLER STRUCK THE RUNWAY.

## 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 CHI03LA229](https://openairdocs.org/ntsb/CHI03LA229), Jul 25, 2003: Cessna 172P (N99040), Huntingburg, IN, substantial damage. Probable cause: The pilot's inadequate flare and the failure to perform a go-around during landing. The planned approach with a quartering tailwind were contributing factors.

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.