ERA23LA253 · Beech V35A
Beech V35A · Accident: flight control system malfunction/failure en route
Event
- NTSB case
- ERA23LA253
- 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 V35A
- 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
- N8074R
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From not recordedTo not recorded
- Aircraft age
- About 54 years (built 1969)
- 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
- 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
- Flight control system malfunction/failure
- 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
- Aircraft › Aircraft systems
- Personnel issues › Task performance
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 reported that the purpose of the flight was to test the newly installed autopilot servos and calibrate the fuel flow sensor. The pilot stated that the control surfaces moved as expected during the preflight inspection. Near the end of the flight, the autopilot did not turn to a programmed waypoint. The pilot disconnected the autopilot and took over manual control of the airplane but was unable to prevent an unintended nose-down pitch. Despite verifying the autopilot disconnection, the yoke was unresponsive and the airplane continued to descend on the final approach, striking a light pole about 1,000 ft short of the runway threshold before impacting the ground. Postaccident examination of the airplane revealed that the pitch servo bridle cable clamp had not been properly installed, which resulted in the cable binding when the yoke was pulled aft. The installer had not verified that the required clearance was maintained and did not perform the necessary post-installation control movement checks as specified in the autopilot’s installation instructions. The incorrect positioning of the bridle cable clamp resulted in restricted elevator control, which prevented the pilot from recovering from the nose-down condition during the approach.
Probable cause
Maintenance personnel’s improper installation of the pitch servo bridle cable clamp, which led to binding in the elevator control system that restricted aft yoke movement during the landing approach.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA23LA253
- Event ID
- 20230601192287
- Case number
- ERA23LA253
- 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, cause areas. 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: 98aadb0eb8b40637d53bbb3ae254c7961099f053a58df31ab6ee7e59e6504904; retrieved 2026-09-16T17:40:37.777Z.