FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

IAD01FA015 · Beech F90

24 Nov 2000 · Lynchburg, VA, United States

Virginia Aviation Beech F90 · Accident: propeller failure/malfunction during initial climb

From Lynchburg Regional Airport - Preston Glenn Field (LYH) to an unrecorded destination

Report a problem

Event

NTSB case
IAD01FA015
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

Beech F90

Aircraft type
Beechcraft 90
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
N94U
Onboard fatalities
Unknown
Route
From Lynchburg Regional Airport - Preston Glenn Field (LYH), Lynchburg, VATo 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
Initial climb
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
Propeller failure/malfunction
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, adjustment, improper
  • Propeller feathering › Inadvertent activation

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot was conducting a post-maintenance test flight. An overhauled engine had been installed on the right side of the airplane, and both propeller assemblies had been subsequently re-rigged. Ground checks were satisfactory, although the right engine propeller idled 90-100 rpm higher than the left engine propeller. Test flight engine start and run-up were conducted per the checklist, with no anomalies noted. Takeoff ground roll and initial climb were normal; however, when the airplane reached about 100 feet, it stopped climbing and lost airspeed. The pilot could not identify the malfunction, and performed a forced landing to rough, hilly terrain. Upon landing, the landing gear collapsed and the engine nacelles were compromised. The airplane subsequently burned. Post-accident examination of the airplane revealed that the propeller beta valves of both engines were improperly rigged, and that activation of the landing gear squat switch at takeoff resulted in both propellers going into feather. The maintenance personnel did not have rigging experience in airplane make and model. As a result of the investigation, the manufacturer clarified maintenance manual and pilot handbook procedures.

Probable cause

Improper rigging of both propeller assemblies by maintenance personnel, which resulted in the inadvertent feathering of both propellers after takeoff. Factors included a lack of rigging experience in airplane make and model by maintenance personnel, unclear maintenance manual information, and unsuitable terrain for the forced landing.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record IAD01FA015
Event ID
20001215X45419
Case number
IAD01FA015
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, 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: 151ce3640811985a3658cd66c45c7fd351a7c0b75e34d088f0c75c64482adb16; retrieved 2026-09-22T12:18:48.858Z.