CEN10CA405 · Cessna 172K
Cessna 172K · Accident: landing area overshoot
From Lakes of the North Airport (4Y4) to Boyne City Municipal Airport (N98)
Narrative check · The NTSB narrative appears to contradict this record's departure or destination. Values are shown as recorded, not corrected; compare with the narrative.
Event
- NTSB case
- CEN10CA405
- 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 172K
- 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
- N79097
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route Narrative disagrees
- From Lakes of the North Airport (4Y4), Lakes of the No, MITo Boyne City Municipal Airport (N98), Boyne City, MI
- 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
- 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
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Prior to arriving in the airport traffic pattern, the pilot heard that other aircraft were landing on runway 09, a 4,000-foot-long by 75-foot-wide runway, and the winds were light and variable. The pilot stated, "I landed long on runway 09." He then attempted to go-around; however, the airplane's nose wheel struck the top of the airport perimeter fence. The airplane flipped over and came to rest inverted. The pilot reported no anomalies with the airplane. According to the pilot, the accident could have been prevented if he had initiated a go-around after the airplane had over-flown the first 1/3 of the runway and had not touched down.
Probable cause
The pilot's failure to attain the proper touchdown point and delayed go-around.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN10CA405
- Event ID
- 20100716X53446
- Case number
- CEN10CA405
- 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: d7da8be21486be21af4bac5c2092895cf05d29e6945def2ab43691f5c32c26fa; retrieved 2026-09-15T14:42:38.976Z.