FTW98LA280 · Bellanca 17-30A
Bellanca 17-30A · Accident: airframe, component or system failure during landing
From Nashville International Airport (BNA) to Shreveport Regional Airport (SHV)
Event
- NTSB case
- FTW98LA280
- 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
- N4038B
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Nashville International Airport (BNA), Nashville, TNTo Shreveport Regional Airport (SHV)
- 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
- Landing · landing roll
- 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, gear locking mechanism › Failure, total
- Landing gear, nose gear › Collapsed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that after a 'normal approach' to runway 23 at the Shreveport Regional Airport (SHV), the aircraft pulled 'sharply' to the right during the landing roll. The airplane departed the right side of the runway, struck a taxi sign and taxi light and came to rest in the upright position. The pilot/owner reported that the right wing spar was damaged, and the nose gear 'collapsed in reverse direction.' A local maintenance facility inspected the aircraft and found that the down spring loaded rod assembly had failed, allowing the nose gear to collapse.
Probable cause
The collapsed nose gear as a result of failure of the nose gear locking mechanism.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record FTW98LA280
- Event ID
- 20001211X10322
- Case number
- FTW98LA280
- 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: c8495ab3d4482564aa88a52ba54d6d95d30df9bfd57b8379cbe5e1d7512cea42; retrieved 2026-09-22T17:39:25.143Z.