WPR21LA334 · Bellanca 17-30A
Bellanca 17-30A · Accident: landing gear not configured
From Meadow Lake Airport (KFLY) to an unrecorded destination
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
- WPR21LA334
- 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
- Event fatalities
- Unknown
- 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 17-30A
- Aircraft type
- Bellanca 17
- 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
- N15DQ
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route Possible conflict
- From Meadow Lake Airport (KFLY), Meadow Lake, COTo not recorded
- Aircraft age
- About 46 years (built 1975)
- 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 · flare/touchdown
- 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 gear not configured
- 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 systems
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that, during landing he failed to extend the landing gear and attempted to initiate a go-around. The airplane attained an altitude of about 100 ft above the ground before it would no longer climb and maintain airspeed. The pilot subsequently initiated a forced landing to a nearby field with the landing gear now extended. During the landing roll, the airplane collided with a barbed wire fence, substantially damaging the wings. The pilot reported no mechanical failures or malfunctions with the airplane other than the Auto-Axtion system, a pilot back-up device to automatically lower the landing regardless of the position of the landing gear switch, minimizing the possibility of an accidental gear-up landing did not work. The back-up system was not examined.
Probable cause
The pilot's failure to extend the landing gear
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR21LA334
- Event ID
- 20210903103796
- Case number
- WPR21LA334
- 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, cause areas. 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: 52d747e4d7a0ffe28bc72f70cd938435388eb9b88e1765e2edbd8fb63cb406ab; retrieved 2026-09-16T14:29:05.877Z.