FTW96LA106 · Bellanca 17-30A
Bellanca 17-30A · Accident: airframe, component or system failure
From E80 to an unrecorded destination
Event
- NTSB case
- FTW96LA106
- 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
- N4109B
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From E80To 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
- Unknown
- 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
- Landing gear, main gear attachment › Loose
- Landing gear, main gear attachment › Previous damage
- Maintenance › Inadequate
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot had purchased the airplane on 12/14/95 and had flown it about 23 hours since that date. During that time, he noted a transient instability in directional control during landing roll. During a landing on 1/13/96, he could not maintain directional control after touchdown, and the aircraft departed the side of the runway. No damage was found as a result of the runway departure; however, damage to the wing structure was found adjacent to the left main landing gear attach point. Also, the right main landing gear was found loose in its mounts, and its torque link was improperly shimmed. The right main landing gear problems could be found only by jacking the aircraft with the gear hanging free. There was evidence that over an undetermined period of time, the landing gear had been loose, and the resultant damage occurred.
Probable cause
previous damage, looseness of the main landing gear, and inadequate maintenance.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW96LA106
- Event ID
- 20001208X05147
- Case number
- FTW96LA106
- 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: a8865912385f599d658a8071b216b067e1d8ce6f63a3632bbe33ee29594ea536; retrieved 2026-09-22T22:53:20.715Z.