FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA14CA230 · Cessna 172S

9 May 2014 · Deland, FL, United States

Embry-Riddle Aeronautical University Cessna 172S · Accident: abnormal runway contact during landing

From Deland Municipal Sidney H Taylor Field (DED) to Deland Municipal Sidney H Taylor Field (DED)

Report a problem

Event

NTSB case
ERA14CA230
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
N493ER
Onboard fatalities
Unknown
Route
From Deland Municipal Sidney H Taylor Field (DED), Deland, FLTo Deland Municipal Sidney H Taylor Field (DED), Deland, FL
Aircraft age
About 7 years (built 2007)
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 › Psychological
  • Personnel issues › Task performance

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The flight instructor and the student pilot were practicing short field landings. Following an uneventful first landing, the airplane approached the runway for a second. While on the short final leg of the approach to the runway, the airplane began sinking rapidly. The flight instructor responded by advising the student, "full power." The student pilot thought the flight instructor had said, "pull power," and subsequently reduced engine power to idle. The airplane impacted the runway and bounced back into the air. The flight instructor then took control of the airplane and aborted the landing. Subsequent inspection of the airplane by maintenance personnel revealed that the nose landing gear and engine firewall had been substantially damaged during the landing. Following the accident, the operator reemphasized to their flight instructors the importance of utilizing standard phraseology during training flights, including use of the phrase "go around" to indicate the necessity to abort a landing.

Probable cause

The student pilot's failure to maintain control of the airplane during the landing, and the flight instructor's inadequate supervision of the student pilot resulting in abnormal runway contact and damage to the airplane.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA14CA230
Event ID
20140509X91426
Case number
ERA14CA230
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: 433d0b810f434862bdded75ed64865a6046be7d7784974bf1d3915aa3334fd15; retrieved 2026-09-15T23:36:34.117Z.