CEN18LA010 · Bellanca 17-30A
Bellanca 17-30A · Accident: loss of engine power (total) during an emergency descent
From Midland International Air and Space Port (MAF) to Abilene Regional Airport (ABI)
Event
- NTSB case
- CEN18LA010
- 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
- N8234R
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Midland International Air and Space Port (MAF), Midland, TXTo Abilene Regional Airport (ABI), Abilene, TX
- Aircraft age
- About 46 years (built 1971)
- 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
- Emergency descent
- 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
- Loss of engine power (total)
- 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
- Tree(s)
- 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
- Not determined › Not determined
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The commercial pilot stated that there were no anomalies during the preflight inspection of the airplane or before departure. At the time of departure, the left- and right-wing fuel tanks were ½ full, and the fuselage (rear) auxiliary tank was empty. About 18 minutes after departure, both communication radios began to flicker, followed by a loss of electrical power to the avionics; none of the circuit breakers were tripped. While troubleshooting, the pilot reset the alternator circuit breaker, but it did not restore electrical power. He then diverted the flight to an alternate airport, and, during final approach, the engine lost total power. The pilot located a field encircled by trees to perform a forced landing. During the approach to the field, he attempted twice to start the engine but was unsuccessful. The pilot said that he was unable to reach the field, and the airplane impacted trees with the left wing during the approach.
Postaccident examination revealed the airplane's fuel tanks were intact, and the fuel caps were in place and secure. The fuel tank filler necks and bottom of the fuel caps were brown in color consistent with corrosion. The cockpit fuel tank selector was positioned to OFF, and the cockpit auxiliary fuel tank selector was positioned to RIGHT WING. The right-wing tank contained about 9 gallons of fuel; the right-wing auxiliary tank was empty; the left-wing tank contained about 1 gallon of fuel, which was an unusable amount; the left-wing auxiliary tank contained about 8 gallons of fuel; and the rear auxiliary tank was empty. The pilot did not report the positions of the fuel selectors that he had used during the flight.
The fuel lines between the fuel pump and the fuel metering unit and the fuel line between the fuel metering unit and the fuel manifold valve contained no fuel. The fuel manifold cap was removed, and no fuel was present in the manifold housing. The manifold screen did not contain debris, the diaphragm was intact, and the plunger displayed no anomalies.
Testing of the fuel tank sending units revealed inaccuracies in their resistive values that would have resulted in fuel gauge indication inaccuracies. The left-wing auxiliary fuel tank sending unit had no change in resistive value with float position, and the right-wing auxiliary fuel tank sending unit had minimal difference in resistive value between mid- and upper-level float positions. The left- and right-wing fuel tank sending units' resistive values at the upper limit of float travel were similar. The resistive specifications for the airplane were unknown. There was no record that the fuel senders had been replaced since the manufacture of the airplane.
Both magnetos were unable to produce a spark when rotated by hand and during bench testing due to long-term wear of the magneto pick-up brushes. A degraded performance of the magneto should have been evident to the pilot during a preflight run-up check by a greater-than-normal reduction in engine speed when operating on one magneto. There was no record of a magneto inspection in accordance with the magneto manufacturer's maintenance instructions for continued airworthiness.
Although it is possible that the pilot starved the engine of fuel due to improper fuel management or that the magnetos had degraded performance, based on the available information, the investigation could not determine the exact reason for the loss of engine power.
Probable cause
The loss of engine power during a precautionary approach for landing for reasons that could not be determined based on the available information.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN18LA010
- Event ID
- 20171010X02857
- Case number
- CEN18LA010
- 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, coordinates. 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: 2a43123734738a9490568748654737de2804960e6eed4b5b61a6e3bd00065dc6; retrieved 2026-09-16T05:55:23.481Z.