ERA13CA335 · Cessna 172S
Phoenix East Aviation Cessna 172S · Accident: hard landing
From Daytona Beach International Airport (DAB) to New Smyrna Beach Municipal Airport (EVB)
Event
- NTSB case
- ERA13CA335
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Cessna 172S
- Aircraft type
- Cessna 172
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N121CW
- Operator
- Phoenix East Aviation
- Onboard fatalities
- Unknown
- Route
- From Daytona Beach International Airport (DAB), Daytona Beach, FLTo New Smyrna Beach Municipal Airport (EVB), New Smyrna Beach, FL
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Landing · flare/touchdown
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Hard landing
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The student pilot reported that he was on his first solo flight. During his first landing as he flared the airplane, it landed hard and bounced on the runway multiple times. As the student pilot attempted to regain control of the airplane, the propeller contacted the runway. The student pilot brought the airplane to a full stop, and taxied off of the active runway to his awaiting instructor to inspect the airplane. They did not see any damage, and flew the airplane back to their home base. During a maintenance inspection it was discovered that the firewall was buckled. The student pilot reported no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause
The student pilot's improper landing flare and subsequent inadequate recovery from a bounced landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA13CA335
- Event ID
- 20130726X05005
- Case number
- ERA13CA335
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: c6420f8b721cd9b34abbf7a77edb1b3fdebac3ce83834040ddeee89389d02094; retrieved 2026-09-15T22:19:40.464Z.