FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA23FA346 · Beech C-99

22 Aug 2023 · Litchfield, ME, United States

Wiggins Airways Beech C-99 · Accident: system/component malfunction/failure (non-power) en route

From Auburn Lewiston Municipal Airport (LEW) to an unrecorded destination

Report a problem

Event

NTSB case
ERA23FA346
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
2 · 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 C-99

Aircraft type
Beechcraft C-99
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
N55RP
Onboard fatalities
Unknown
Route
From Auburn Lewiston Municipal Airport (LEW), Lewiston, METo not recorded
Aircraft age
About 41 years (built 1982)
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
System/component malfunction/failure (non-power)
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

  • Aircraft › Aircraft systems

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The newly hired pilot and an experienced flight instructor were conducting the third flight of the pilot’s initial training. After conducting an instrument approach in visual meteorological conditions, they conducted a missed approach and the airplane proceeded to a holding pattern at 3,000 ft, consistent with a normal training profile. As the airplane was completing the first turn in the holding pattern, it pitched over and accelerated. The airplane impacted wooded terrain in a nose-down attitude in excess of 20°, a slight right bank, and at an airspeed exceeding 250 knots. No distress calls were heard from the crew, who were not communicating with air traffic control at the time and were not required to. The highly fragmented wreckage was indicative of a high-energy impact. The engines and propellers were separated during the impact sequence and showed evidence of operation at high power. All structural components of the airframe were found within the confines of the debris field. The airplane was equipped with a dual electric horizontal stabilizer trim system. The horizontal stabilizer was driven concurrently by two arms (cylinder rods) on the horizontal stabilizer actuator, mounted in the aft fuselage. An examination of the wreckage revealed that the right-side cylinder rod end became disconnected before the accident; the connecting bolt, nut, and washers were missing. This hardware also secured the control rod for the motion-indicating gearbox (MIG) that provided the pilots with aural and visual indications in the cockpit of stabilizer movement and takeoff trim position; disconnection of the MIG would have resulted in missing or incorrect reporting of the stabilizer and trim positions to the flight crew. Although either actuator cylinder rod was capable of independently operating the stabilizer trim, the airplane manufacturer considered operation with only one cylinder rod a “limited emergency operation” mode. The horizontal stabilizer trim was likely near the full-nose-down position at impact. The investigation was not able to determine the effects of the pitch trim operating with only one cylinder rod attached for an undetermined but possibly extended duration. Functional testing of the components was not possible due to impact damage. A pilot receiving instruction and flight instructor in another airplane performing maneuvers near the holding pattern reported observing the accident airplane make an abrupt turn to their right, which they described as a near-miss. The investigation reviewed flight track data from both flights to evaluate the possibility that the abrupt maneuver performed in response to the near-miss was related to the accident; however, of the accident airplane’s flight track showed the airplane maintaining the holding pattern for another 8 miles after the near-miss and before the descent and collision with terrain.

Probable cause

A horizontal stabilizer pitch trim anomaly that was not identified in the available evidence.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA23FA346
Event ID
20230823192925
Case number
ERA23FA346
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, 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: 0d91eb2aa29307d3bed74594967b8940da3e328d97022c34ce9680485eaf9048; retrieved 2026-09-15T08:05:09.001Z.