# Accident 20030618015459A: Cessna 172S, Melbourne, FL, June 18, 2003

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: June 18, 2003, 09:44 local time
- Place: Melbourne, FL
- Airport: Melbourne Regional
- Damage: Substantial damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 28.1097° N, 80.7378° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=28.1097&lon=-80.7378&mi=10
- Aircraft: N53352, registered now (https://openairdocs.org/aircraft/N53352) (OpenAirDocs)
- Registry model: Cessna 172S (registry code 2072439, https://openairdocs.org/model/cessna-172s) (OpenAirDocs)
- Reported make and model: CESSNA 172S
- Reported engine: CONT IO360*
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 85 total, 5 in this make and model, 5 in the last 90 days
- NTSB investigation: [NTSB MIA03CA125](https://openairdocs.org/ntsb/MIA03CA125) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20030618015459A

## Narrative

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

(-23) DURING LANDING ON RUNWAY 27L AT MLB, PILOT BOUNCED, THEN LOST CONTROL DEPARTING THE RUNWAY TO THE RIGHT SIDE, HIT A DITCH AND CAME TO REST IN THE INVERTED POSITION.

## 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 MIA03CA125](https://openairdocs.org/ntsb/MIA03CA125), Jun 18, 2003: Cessna 172S (N53352), Melbourne, FL, substantial damage. Probable cause: The pilot's improper flare and inadequate recovery from a bounced landing. Contributing factors were the pilot's failure to maintain directional control and his failure to execute a go-around.

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.