ERA23LA017 · Cessna 172 S
Embry-Riddle Aeronautical University Cessna 172 S · Accident: abnormal runway contact during landing
From Daytona Beach International Airport (DAB) to an unrecorded destination
Event
- NTSB case
- ERA23LA017
- 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
- 0
- 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 172 S
- 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
- N455ER
- Onboard fatalities
- Unknown
- Route
- From Daytona Beach International Airport (DAB), Daytona Beach, FLTo not recorded
- Aircraft age
- About 7 years (built 2015)
- 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
- Abnormal runway contact
- 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 › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot under instruction was flying a practice power-off 180° maneuver from the downwind leg at the accident airport. The flight instructor stated that on final approach the airplane’s airspeed was slow and the flight path was low. He stated that since the purpose of the flight was to evaluate student’s piloting skills, he allowed the approach to proceed and did not tell the student to add power or go around. The airplane landed firmly at the runway threshold and the horizontal stabilizer impacted a runway threshold light. Postaccident examination revealed that the horizontal stabilizer sustained substantial damage. The flight instructor reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation and that a go-around maneuver should have been initiated when the approach became unstable.
Probable cause
The pilot's unstable approach, which resulted in a hard landing and impact with a runway threshold light. Also causal was the flight instructor’s failure to take remedial action to prevent the hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA23LA017
- Event ID
- 20221013106116
- Case number
- ERA23LA017
- 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, coordinates, cause areas. 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: 66f3b94690d76156cf7d0cdf331ba4c6cccff1f6033dfc8683f4e71796bd1bf2; retrieved 2026-09-16T16:16:25.422Z.