ERA22LA215 · Cessna 414 UNDESIGNAT
Air Travel Management Cessna 414 UNDESIGNAT · Accident: flight control system malfunction/failure during takeoff
From Joseph A. Hardy Connellsville Airport (VVS) to an unrecorded destination
Event
- NTSB case
- ERA22LA215
- 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
Cessna 414 UNDESIGNAT
- Aircraft type
- Cessna 414
- 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
- N46TA
- Operator
- Air Travel Management
- Onboard fatalities
- Unknown
- Route
- From Joseph A. Hardy Connellsville Airport (VVS), Connellsville, PATo not recorded
- Aircraft age
- About 50 years (built 1972)
- 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
- Takeoff
- 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 › Experience/knowledge
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, who was also a mechanic, had been troubleshooting an autopilot issue before the accident flight. He had removed and reinstalled the autopilot mode control unit in the cockpit panel and planned to complete a local maintenance test flight. The pilot initiated the flight, completed a normal run-up, and reported that nothing was abnormal with the flight controls. During takeoff and after reaching the airplane’s rotation speed, the pilot was unable to move the control wheel aft so that the elevator would move toward the airplane-nose-up direction. The pilot subsequently aborted the takeoff, but insufficient runway remained, and the airplane overran the runway and collided with trees. The fuselage and wings sustained substantial damage. Postaccident examination of airplane’s left-side cockpit avionics stack, which contained a GPS and radio unit, found that the avionics trays had sagged downward, resulting in the elevator bellcrank to become lodged within the lowest avionics tray. Further, the avionics trays were missing metal straps designed to secure the rear weight of the GPS and radio units to the structure of the airframe. The avionics tray and elevator bellcrank exhibited significant scraping and metal polishing, which indicated that rubbing contact between the sagging avionics tray and the elevator bellcrank had likely been occurring for some time before the accident flight. Neither the pilot nor the passenger (who was also a mechanic) reported observing any anomalies with the flight controls during the preflight run-up but did report that the airplane hit a dip in the runway as the airplane approached its the rotation speed. Thus, this movement likely moved the tray further downward and into the movement area of the elevator bellcrank. The Federal Aviation Administration had published advisory circular guidance advising mechanics to ensure that avionics units (including GPS and radio units) were properly secured with rear or side metal straps connected to a structural element on the aircraft. Review of maintenance records found no recent references to work involving the affected avionics or the securing of their avionics trays. The pilot had maintained the airplane for several years and signed off multiple annual inspections. During a postaccident interview, the pilot explained that he was not aware of the need to secure metal side or rear straps on avionics trays. Thus, because the pilot did not realize the need to properly secure the avionics trays to structural airplane elements, the trays eventually contacted the elevator bellcrank and precluded normal operation of the airplane’s pitch controls.
Probable cause
The pilot/mechanic’s failure to properly secure two airplane avionics units, which resulted in the trays supporting the units to sag downward and become lodged in the movement area of the elevator bellcrank during the accident takeoff.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA22LA215
- Event ID
- 20220503105031
- Case number
- ERA22LA215
- 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: 58d24445f34696ea46b18ea8a61f2dc8202120ae63b56073ff65c51c5f637067; retrieved 2026-09-16T15:11:48.633Z.