NYC05CA073 · Cessna 172N
Flight Services of Medina Cessna 172N · Accident: overrun during landing
From Medina Municipal Airport (1G5) to Reader-Botsford Airport (67D)
Event
- NTSB case
- NYC05CA073
- 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 172N
- 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
- N1086F
- Operator
- Flight Services Of Medina
- Onboard fatalities
- Unknown
- Route
- From Medina Municipal Airport (1G5), Medina, OHTo Reader-Botsford Airport (67D), Wellington, OH
- 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
- First occurrenceThe 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
- Overrun
- 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
- Pilot in command › Go-around, not performed
- Pilot in command › Proper touchdown point, not obtained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The airplane was landing on runway 18, a 2,850-foot-long, 100-foot wide, turf runway. The pilot attempted to touchdown near a hangar; however, the airplane floated. The airplane then touched down about 400 feet from the end of the runway. The airplane overran the runway, traveled into a wet field, and came to rest inverted. The reported wind at an airport located approximately 10 miles north of the accident site, at 1153, was from 340 degrees at 8 knots.
Probable cause
The pilot's failure to obtain the proper touchdown point, and his failure to initiate a go-around, which resulted in an overrun during landing. A factor in the accident was the tail wind.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC05CA073
- Event ID
- 20050505X00557
- Case number
- NYC05CA073
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. 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: f1e7d5941b008b08f8a2367672af4c5bffe8b95ae9de415bace7eedaca7f4617; retrieved 2026-09-22T06:02:42.420Z.