FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Castle Aviation Swearingen SA226 AT accident

10 Dec 2021 · Bedford, NH, United States

Swearingen SA226 AT · Accident: loss of control in flight on approach

From Essex County Airport (CDW) to an unrecorded destination

Report a problem

Event

NTSB case
ERA22FA086
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
1 · 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
Charter & commuter
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

Swearingen SA226 AT

Aircraft type
Swearingen SA226
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
N54GP
Onboard fatalities
Unknown
Route
From Essex County Airport (CDW), Caldwell, NJTo not recorded
Aircraft age
About 46 years (built 1975)
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 135: Air Taxi & Commuter
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 · IFR final approach
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
Loss of control in flight
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 power plant
  • Personnel issues › Action/decision

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

NTSB narrative

During an instrument approach at night in a twin-engine turboprop airplane, the pilot reported an engine failure, but did not specify which engine. About 9 seconds later, the airplane impacted terrain about ¼-mile short of the runway and a postcrash fire consumed a majority of the wreckage. During that last 9-second period of the flight, the airplane’s groundspeed slowed from 99 kts to 88 kts, as it descended about 400 ft in a slight left turn to impact (the airplane’s minimum controllable airspeed was 92 kts). The slowing left turn, in conjunction with left wing low impact signatures observed at the accident site were consistent with a loss of control just prior to impact. Postaccident teardown examination of the left engine revealed that the 1st stage turbine rotor had one blade separated at the midspan. The blade fracture surface had varying levels of oxidation and the investigation could not determine if the 1st stage turbine blade separation occurred during the accident flight or a prior flight. The 2nd stage turbine was operating at temperatures higher than the 1st stage turbine, which was consistent with engine degradation over a period of time. Additionally, the 2nd stage turbine stator assembly was missing vane material from the 6 to 12 o’clock positions, consistent with thermal damage. All of these findings would have resulted in reduced performance of the left engine, but not a total loss of left engine power. The teardown examination of the right engine did not reveal evidence of any preimact anomalies that would have precluded normal operation. Examination of both propellers revealed that all blade angles were mid-range and exhibited evidence of little to no powered rotation. Neither propeller was in a feathered position, as instructed by the pilot operating handbook for an engine failure. If the pilot had perceived that the left engine had failed, and had he secured the engine and feathered its propeller (both being accomplished by pulling the red Engine Stop and Feather Control handle) and increased power on the right engine, the airplane’s performance should have been sufficient for the pilot to complete the landing on the runway.

Probable cause

The pilot’s failure to secure and feather the left engine and increase power on the right engine after a perceived loss of engine power in the left engine, which resulted in a loss of control and impact with terrain just short of the runway. Contributing to the accident was a reduction in engine power from the left engine due to a 1st stage turbine blade midspan separation and material loss in the 2nd stage stator that were the result of engine operation at high temperatures for an extended period of time.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA22FA086
Event ID
20211211104386
Case number
ERA22FA086
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: local date, investigation status, cause areas. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2021-12-11.
  • API snapshot SHA-256: 5bb9c597ef2153a6758f4139f5672152658abb93f74da57ec26312138dd9513c; retrieved 2026-09-15T07:38:49.779Z.