BFO89FA060 · Beech V35TC
Beech V35TC · Accident: total loss of engine power (mechanical failure) en route
From Charlotte Douglas International Airport (CLT) to Capital City Airport (CXY)
Event
- NTSB case
- BFO89FA060
- 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
- 1 · 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
Beech V35TC
- Aircraft type
- Beechcraft 35
- 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
- N118FC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Charlotte Douglas International Airport (CLT), Charlotte, NCTo Capital City Airport (CXY), Harrisburg, PA
- 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
- En route · cruise
- 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
- Total loss of engine power (mechanical 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
- 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
- Destroyed
Cause areas
- Other maintenance personnel › Maintenance, installation, improper
- Throttle/power lever, linkage › Disconnected
- Throttle/power lever, linkage › Worn
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
WHILE RECEIVING VFR TRAFFIC ADVISORIES AT 10,500 FT THE PLT REPORTED A TOTAL LOSS OF POWER. THE AIRCRAFT CRASHED IN A WOODED AREA 1/4 MILE NW OF THE CHARLOTTESVILLE ARPT WHILE RECEIVING RADAR VECTORS. INVESTIGATION REVEALED A FAILURE OF THE THROTTLE CONTROL LINKAGE BETWEEN THE THROTTLE AND THE VARIABLE ABSOLUTE CONTROLLER ASSEMBLY DUE TO PROGRESSIVE WEAR. THE FAILURE WOULD HAVE ALLOWED THE THROTTLE PLATE TO VIBRATE TO THE CLOSED POSITION. FURTHER EXAM REVEALED THAT A WAVE WASHER WAS MISSING IN THE LINKAGE ASSEMBLY. THE ENGINE HAD BEEN OVERHAULED AND THE TURBOCHARGER REPLACED 24 AND 12 MONTHS RESPECTIVELY PRIOR TO THE ACCIDENT.
Probable cause
IMPROPER INSTALLATION OF THE THROTTLE AND VARIABLE ABSOLUTE CONTROLLER ASSEMBLIES BY MAINTENANCE PERSONNEL WHICH RESULTED IN A TOTAL LOSS OF ENGINE POWER.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record BFO89FA060
- Event ID
- 20001213X28733
- Case number
- BFO89FA060
- 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: local date, investigation status. Values present in the bulk record are kept.
- The date is the local date; the NTSB stores the UTC date 1989-07-18.
- API snapshot SHA-256: 50a076dcfcf497e0d5f04bd20c177615551107e5575ebad48f6b700777b68f34; retrieved 2026-09-21T03:13:53.421Z.