MIA95FA053 · LARSON, C.H. COZY MK IV
LARSON, C.H. COZY MK IV · Accident: undershoot on approach
From Avon Park Executive Airport (AVO) to an unrecorded destination
Event
- NTSB case
- MIA95FA053
- 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
- 2 · 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
LARSON, C.H. COZY MK IV
- Aircraft type
- Larson COZY MK
- 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
- N5037
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Avon Park Executive Airport (AVO), Avon Park, FLTo not recorded
- 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 pattern final
- 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
- Undershoot
- 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, static
- 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 › Altitude/clearance, not maintained
- Pilot in command › Distance/altitude, misjudged
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PILOT ADVISED ON THE COMMON TRAFFIC ADVISORY FREQUENCY THAT THE FLIGHT WAS ON A LEFT DOWNWIND FOR THE RUNWAY, CLOSE IN. THE AIRPLANE WAS OBSERVED TO TURN LEFT BASE AND FINAL AND WHILE ON FINAL APPROACH, THE AIRPLANE COLLIDED WITH AN UNMARKED STATIC POWER LINE. THE AIRPLANE THEN IMPACTED THE GROUND NOSE AND RIGHT WING LOW AND CAME TO REST UPRIGHT. THE ENGINE WAS REMOVED FROM THE AIRPLANE, STARTED, AND FOUND TO OPERATE NORMALLY. EXAMINATION OF THE FLIGHT CONTROLS REVEALED NO EVIDENCE OF A PREIMPACT FAILURE OR MALFUNCTION. ACCORDING TO THE FAA, THE POWER LINE WAS NOT REQUIRED TO BE MARKED.
Probable cause
DISTANCE VS. ALTITUDE MISJUDGED BY THE PILOT-IN-COMMAND WHILE ON SHORT FINAL APPROACH. ADDITIONALLY, ALTITUDE/CLEARANCE NOT MAINTAINED WHILE ON SHORT FINAL APPROACH RESULTING IN THE COLLISION WITH AN UNMARKED STATIC POWER LINE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record MIA95FA053
- Event ID
- 20001207X02891
- Case number
- MIA95FA053
- 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: 5d62350d1acd7e8d14cff046e47c919fa047119ac8079167ad7753c5188c9451; retrieved 2026-09-20T23:54:00.197Z.