DEN84LA080 · Bellanca 17-30A
Bellanca 17-30A · Accident: airframe, component or system failure during takeoff
From an unrecorded airport to Roy Hurd Memorial Airport (E01)
Event
- NTSB case
- DEN84LA080
- 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
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
- N4096B
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo Roy Hurd Memorial Airport (E01), MONAHANAS, TX
- 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
- Takeoff
- 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
- Airframe, component or system failure
- 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
- Throttle/power lever, cable › Jammed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PLT NOTICED THE THROTTLE STICKING ON TAKEOFF AND TRIED TO ABORT THE TAKEOFF BUT THE THROTTLE WAS BINDING. THE ACFT TOOKOFF AT A BELOW NORMAL SPEED AND HAD TO BE LANDED. SUBSEQUENTLY, THE ACFT IMPACTED THE GROUND & SEVERAL TREES. AN ENGINEER SAID THE THROTTLE FRICTION SHOULD HAVE BEEN NOTICEABLE TO THE PLT FOR SOME TIME PRIOR TO THE ACCIDENT. A MECHANIC SAID THE CABLE IS SUPPOSE TO BE INSPECTED ON THE ANNUAL INSPECTION FOR 'FREEDOM OF MOVEMENT'. THE LAST ANNUAL WAS APRX 8 MOS BEFORE THE ACCIDENT.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record DEN84LA080
- Event ID
- 20001214X38749
- Case number
- DEN84LA080
- 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: 59145de02622325a51a0c209b2f91d6aedbf884e5a3355779042bc65f06a2b7b; retrieved 2026-09-23T20:54:38.810Z.