CHI02LA028 · Bellanca 17-30A
Bellanca 17-30A · Accident: airframe, component or system failure during takeoff
From Hale County Airport (PVW) to Nevada Municipal Airport (NVD)
Event
- NTSB case
- CHI02LA028
- 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 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
- N76SV
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Hale County Airport (PVW), Plainview, TXTo Nevada Municipal Airport (NVD), Nevada, MO
- 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 · roll/run
- 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
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Fuel starvation
- 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
- Fluid, fuel › Starvation
- Landing gear, steering system › Overload
- Landing gear, steering system › Previous damage
- Pilot in command › Directional control, not possible
- Pilot in command › Fuel consumption calculations, inadequate
- Reason for occurrence undetermined
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane impacted the ground following an aborted landing after a loss of directional control during landing. The pilot reported that the airplane lost engine power during the aborted landing attempt. The pilot reported, "On the take-off roll, just before rotation, the aircraft began to veer to the left." The pilot said that he rotated and retracted the landing gear normally. The pilot stated that he had electrical problems during the flight and when he reached his destination he was unable to establish communications. He said he confirmed that the landing gear was down by calling his father on his cellular telephone. The pilot said that during the landing, when the nose wheel contacted the runway, the airplane again veered to the left. The airplane departed the left side of the runway and the pilot aborted the landing. The airplane struck the visual approach slope indicator during the aborted landing. The airplane climbed to about 60 feet AGL when the engine lost power. The pilot attempted to land on a road and the left wing struck the ground. After the accident, fuel was observed running from beneath the airplane. According to fueling records, the airplane was filled with fuel prior to departure. The flow of fuel was "stemmed" by moving the fuel selector from the right position to the off position. After the airplane was moved to a hangar, the inboard fuel cells were accessed and no fuel was found in the inboard right fuel cell. The outboard fuel cells were broken loose from the aircraft structure. The engine was broken loose from its mount and the propeller was separated from the engine. The forward fuselage was crushed rearward. Examination of the engine revealed compression on all cylinders and spark from the impulse coupled magneto was confirmed. No fuel was found in the fuel distribution valve, or fuel injector lines. The alternator drive belt was broken. The alternator could not be turned by hand. The alternator was removed and examined. The alternator case halves were misaligned and the case exhibited evidence of impact damage. The alternator case bolts were loosened and the alternator shaft rotated freely when misalignment pressures were relieved. The nose wheel steering system consists of two rods attached to the top of a T-bar supported by two bearings mounted on the strut tube. The T-bar is mounted on the forward side of the upper strut tube. The lower end of the T-bar attaches to the steering collar on the nose wheel strut with a link. The link is on the left side of the centerline of the nose wheel strut. The link was fractured and the fracture surfaces exhibited signatures consistent with tension overload failure. No other anomalies were found with respect to the airframe, engine, or systems, that could be identified as existing prior to impact. A witness reported that the airplane was not developing full power during the aborted landing.
Probable cause
The inadequate fuel consumtion calculations by the pilot resulting in fuel starvation during the aborted landing, and the overloaded steering link for undetermined reasons resulting in the lack of directional control during landing. Factors were the electrical system failure for undetermined reasons, the visual approach slope indicator (VASI) system, and the altitude/clearance from the VASI not possible by the pilot.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI02LA028
- Event ID
- 20011120X02269
- Case number
- CHI02LA028
- 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: 2647cb70d3952100bfa7141a6085cacc640abbd46cb1df624d9637f91846cb6f; retrieved 2026-09-21T09:44:20.069Z.