# Accident 20031121037519A: Cessna 172S, Orlando, FL, November 21, 2003

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: November 21, 2003, 13:50 local time
- Place: Orlando, FL
- Airport: Orlando Executive Airport
- Damage: Substantial damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 28.5456° N, 81.3328° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=28.5456&lon=-81.3328&mi=10
- Aircraft: N378FA, a cancelled registration (https://openairdocs.org/deregistered/N378FA-2019-03-05) (OpenAirDocs)
- Registry model: Cessna 172S (registry code 2072439, https://openairdocs.org/model/cessna-172s) (OpenAirDocs)
- Registry engine: Lycoming IO-360-L2A (registry code 41597, https://openairdocs.org/engine/lycoming-io-360-l2a) (OpenAirDocs)
- Reported make and model: CESSNA 172S
- People aboard: 1
- Fatal injuries: 0
- Pilot certificates: Student
- Pilot flight hours: 37 total, 35 in this make and model, 15 in the last 90 days
- NTSB investigation: [NTSB MIA04CA028](https://openairdocs.org/ntsb/MIA04CA028) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20031121037519A

## Narrative

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

(-23) PILOT MADE HARD LANDING RETURNING FROM SOLO CROSS COUNTRY FLIGHT. DAMAGED NOSE GEAR, PROP, FIREWALL, BELLY SKIN.

## 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 MIA04CA028](https://openairdocs.org/ntsb/MIA04CA028), Nov 21, 2003: Cessna 172S (N378FA), Orlando, FL, substantial damage. Probable cause: The student pilots improper landing flare and his improper recovery from a bounced landing resulting in a hard landing and damage to the airplane.

## Other reports on N378FA (2)

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

- [Accident 20110215002769A](https://openairdocs.org/incident/20110215002769A), Feb 15, 2011: Cessna 172S (N378FA), Daytona Beach, FL, Substantial damage. During touchdown on runway 7L at Daytona Beach international airport, the student pilot of N378FA inducted "porpoise" oscillations resulting in a prop strike,…
- [Incident 20090315007309I](https://openairdocs.org/incident/20090315007309I), Mar 15, 2009: Cessna 172S (N378FA), Daytona Beach, FL, Minor damage. On March 15, 2009, at 1130 eastern daylight time, a Cessna CE-172-S, N378FA, experienced the loss operational control during landing on runway 25L at kdab, in…

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.