NYC91LA195 · Beech C50
Beech C50 · Accident: loss of engine power on approach
From Miller Airport (4G3) to an unrecorded destination
Event
- NTSB case
- NYC91LA195
- 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 C50
- Aircraft type
- Beechcraft 50
- 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
- N9674R
- Operator
- John M. Webber · private individual
- Onboard fatalities
- Unknown
- Route
- From Miller Airport (4G3), NORTH BENTON, OHTo 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
- Approach · VFR pattern final
- 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
- Loss of engine power
- 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
- Pilot in command › Propeller feathering, attempted
- Throttle/power lever, linkage › Disconnected
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE TWIN ENGINE AIRPLANE WAS ON FINAL APPROACH AND THE PILOT NOTED THAT THE RIGHT ENGINE WOULD NOT GO BELOW HALF POWER. THE AIRPLANE WAS LANDED AND THE PILOT ELECTED TO ABORT. AFTER ROTATION, THE RIGHT ENGINE FAILED. THE PILOT RAISED THE LANDING GEAR AND ATTEMPETD TO FLY AROUND THE TRAFFIC PATTERN ON ONE ENGINE. THE RIGHT PROPELLER WOULD NOT FEATHER AND THE AIRPLANE WOULD NOT CLIMB. THE PILOT AVOIDED SEVERAL TREE LINES BEFORE DESCENDING GEAR UP INTO A FIELD OF CROPS AND SLID ONTO A ROAD. EXAMINATION OF THE AIRPLANE REVEALED THAT THE CASTLE NUT HAD BACKED OFF THE RIGHT ENGINE'S CARBURETOR AND THE LINKAGE DISCONNECTED. THERE WAS NO COTTER PIN INSTALLED.
Probable cause
ENGINE FAILURE AS A RESULT OF IMPROPER MAINTENANCE AND FAILURE OF THE PROPELLER FEATHERING SYSTEM FOR AN UNDETERMINED REASON. FACTORS WERE AIRCRAFT POOR CLIMB PERFORMANCE AS RESULTED OF THE UNFEATHERED PROPELLER AND OBSTRUCTIONS WHICH PREVENTED A RETURN TO THE AIRPORT.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC91LA195
- Event ID
- 20001212X17681
- Case number
- NYC91LA195
- 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: 2dc20980bf6a7563579b10bf6871f0f41297550a9b55147cd22c512f048d684b; retrieved 2026-09-21T23:29:58.196Z.