MIA07CA095 · Cessna 172-M
Cessna 172-M · Accident: in flight collision with terrain/water on approach
From Central Maine/Norridgewock Airport (OWK) to Oxford County Regional Airport (81B)
Event
- NTSB case
- MIA07CA095
- 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 172-M
- 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
- N80132
- Operator
- Kenneth & Brenda Morgan
- Onboard fatalities
- Unknown
- Route
- From Central Maine/Norridgewock Airport (OWK), Norridgewock, METo Oxford County Regional Airport (81B), Oxford, ME
- 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
- Approach · VFR go-around
- 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
- In flight collision with terrain/water
- 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 › Climb, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The student's certified flight instructor stated that the student was on a solo cross country flight. The student's approach to landing was high and he used full flaps to lose altitude. His contact with the runway was past midfield and hard. The student applied full power and retracted the flaps in an attempt to do a go-around. He heard a noise from the engine and reduced power, and the airplane began to sink and drift off the runway. The airplane struck a small bank that was part of the run- up area at the end of the runway on the west side. The contact with the bank snapped off the nose fork. The aircraft continued across the asphalt and the nose gear strut dug in, flipping the aircraft onto its back. Several witnesses also stated the airplane was too high and fast during the landing approach. The airplane bounced back up into the air once it made contact with the runway. Shortly after, the airplane appeared to be out of control and flipped over at impact with the ground at the end of the runway. No mechanical failures or malfunctions to the airplane or any of its systems prior to the accident were reported.
Probable cause
The student pilot's failure to maintain a climb during a go-around resulting in collision with an embankment.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA07CA095
- Event ID
- 20070828X01250
- Case number
- MIA07CA095
- 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: 0ea3e7dbd99f6af160678d969649e611b6b740fde3107b23bc36fc04c3adae26; retrieved 2026-09-21T18:31:25.779Z.