CEN20CA026 · Bellanca 1730 A
Bellanca 1730 A · Accident: loss of control in flight on approach
From Maple Lake Municipal Airport (MGG) to Leaders Clear Lake Airport (8Y6)
Event
- NTSB case
- CEN20CA026
- 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
Bellanca 1730 A
- Aircraft type
- Bellanca 1730
- 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
- N28037
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Maple Lake Municipal Airport (MGG), Maple Lake, MNTo Leaders Clear Lake Airport (8Y6), Clear Lake, MN
- Aircraft age
- About 40 years (built 1979)
- 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
- 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
- Loss of control in flight
- 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
- Personnel issues › Psychological
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot was conducting a night visual flight to an airport with dim runway lighting. The pilot stated that, during the base turn and final approach, his attention was focused inside the cockpit as he rechecked the landing gear, mixture lever, and propeller lever positions. He noticed a sink rate had developed as the landing lights illuminated a row of 50- to 75-ft-tall trees on final approach. The pilot pulled back aggressively on the yoke to clear the trees. The airplane continued to descend and impacted the ground hard short of the runway. The fuselage and firewall sustained substantial damage. The pilot reported that his attention should have been focused more outside the cockpit during the base turn and final approach and that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable cause
The pilot's focus inside the cockpit during the base turn and final approach, which led to a high sink rate developing and a subsequent hard landing short of the runway.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN20CA026
- Event ID
- 20191127X05853
- Case number
- CEN20CA026
- 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: c95cf0ab4d28f94bd5207fe715d1424c3780ac34b8d57635e6fb1a8607607ea7; retrieved 2026-09-16T10:42:06.461Z.