ERA15CA196 · Cessna 172P
Deland Aviation Cessna 172P · Accident: landing area overshoot
From Florida Keys Marathon International Airport (MTH) to Sebastian Municipal Airport (X26)
Event
- NTSB case
- ERA15CA196
- 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 172P
- 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
- N66090
- Operator
- Deland Aviation
- Onboard fatalities
- Unknown
- Route
- From Florida Keys Marathon International Airport (MTH), Marathon, FLTo Sebastian Municipal Airport (X26), Sebastian, FL
- Aircraft age
- About 32 years (built 1983)
- 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
- 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
- Landing area overshoot
- 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
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot stated that due to other traffic ahead in the airport traffic pattern, he purposely entered a high right base leg for runway 10, a 3,199-foot-long asphalt runway. The airplane remained high during the approach and the pilot attempted to land on the last one-half of the runway; however, the airplane was also too fast as the pilot had selected only 10 degrees of flap extension. The airplane subsequently touched down near the end of the runway, traveled over an approximate 500-foot grass area beyond the end of the runway, and struck a fence before coming to rest upright. Examination of the airplane by a Federal Aviation Administration inspector revealed substantial damage to the firewall. The inspector did not observe any preimpact mechanical malfunctions with the airplane, nor did the pilot report any. The recorded wind near the accident site, about the time of the accident, was from 040 degrees at 7 knots.
Probable cause
The pilot's misjudged airspeed and glidepath, which resulted in a landing area overshoot and runway excursion.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA15CA196
- Event ID
- 20150422X44915
- Case number
- ERA15CA196
- 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: 91bd822d7b41f875dbfa25e72aa0318349d1d26967e6ae1e576b3a44d76afe0e; retrieved 2026-09-16T02:15:16.048Z.