MIA99LA182 · Cessna 172P
Cessna 172P · Accident: in flight collision with object during landing
From Morristown Regional Airport (MOR) to Seymour Air Park (TN20)
Event
- NTSB case
- MIA99LA182
- 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
- 0
- 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
- N5494K
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Morristown Regional Airport (MOR), Morristown, TNTo Seymour Air Park (TN20)
- 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 · aborted
- 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 object
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Wire, transmission (marked)
- 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, delayed
- Pilot in command › Proper touchdown point, not attained
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot stated that he had flown into the airstrip a minimum of 15 times and during the first approach, he recognized that he flight was high. He performed a go-around, orbited the airport 1 time to allow for departing traffic, then reentered the traffic pattern to land. While over the approach end of the runway with the flaps fully extended, he recognized that the flight was again 'high' but thought sufficient runway remained after landing to stop the airplane. The airplane was landed 'too far down the runway to be able to stop...', and he retracted the flaps to 10 degrees, applied full power, and began to climb. During the climb the left main landing gear collided with a marked power line. The airplane then collided with trees, a fence, and came to rest upright. The pilot further stated that there was no engine failure or malfunction. Examination of the airplane by an FAA airworthiness inspector revealed control continuity for roll, pitch, and yaw.
Probable cause
The failure of the pilot to perform a go-around earlier resulting in a long landing, insufficient runway remaining to stop, and subsequent in flight collision with a marked power line during an aborted landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA99LA182
- Event ID
- 20001212X19069
- Case number
- MIA99LA182
- 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. 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: c8925878bb21ceaab1ff7f2d7aafbf8c2d443a3ce042c8a57a2d0e071c773584; retrieved 2026-09-21T20:30:41.330Z.