FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA13FA026 · Aerospatiale AS 355 F2

17 Oct 2012 · Erwinna, PA, United States

Catalyst Aviation Aerospatiale AS 355 F2 · Accident: loss of control in flight during initial climb

From 4PN5 · Erwinna, PA to Wings Field (LOM)

Report a problem

Event

NTSB case
ERA13FA026
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
Unknown
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
Instrument Meteorological Cond

Aerospatiale AS 355 F2

Aircraft type
Aerospatiale AS-355
Category
Helicopter
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
C-FXGM
Onboard fatalities
Unknown
Route
From 4PN5 · Erwinna, PATo Wings Field (LOM), Philadelphia, PA
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
Initial climb
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
Substantial

Cause areas

  • Environmental issues › Conditions/weather/phenomena
  • Personnel issues › Action/decision

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

According to the operator, the airline transport-rated pilot sent a text indicating that he was intending to depart on a scheduled repositioning flight from a helipad located behind the pilot's home to an airport located about 25 nautical miles southwest. Data recovered from a handheld GPS device showed that the helicopter lifted off from the helipad and began accelerating forward while turning right and maintaining a relatively constant altitude. During the 27 seconds of recorded flight that followed, the helicopter's right turn rate increased, shortly decreased slightly, and then significantly increased again as the helicopter began to descend. The helicopter subsequently impacted trees and terrain.

Although the weather reporting stations closest to the accident site and at the destination airport generally reported that visual meteorological conditions prevailed, the presence of calm wind, near-coincident temperatures and dew points, and the clear night sky favored the formation of patch radiation fog and/or dew on the surface. Visible satellite imagery captured about 1 hour after the accident depicted a band of low stratiform clouds or fog/mist over the accident site and along the adjacent river valley. Additionally, several witnesses near the helipad reported that the lighting and weather conditions about the time of the accident were "dark" and "foggy." Postaccident examination of the wreckage revealed no evidence of any preimpact mechanical malfunctions or failures of the airframe or engine that would have precluded normal operation.

The helicopter was not equipped to operate in instrument meteorological conditions (IMC). Although the airline transport-rated pilot possessed airplane and helicopter instrument ratings, his most recent instrument proficiency check was completed about 8 months before the accident in an airplane, not a helicopter, and no evidence was found indicating that he was current or proficient in operating a helicopter in IMC. Regardless, the fog should have been an indication to the pilot that IMC existed, and he should not have decided to operate the helicopter in such conditions. The flight profile and the presence of radiation fog during dark night conditions, which would have obscured visual references such as the trees, are consistent with the pilot having experienced spatial disorientation, specifically a vestibular illusion known as the "graveyard spiral."

Probable cause

The pilot’s decision to depart under visual flight rules in dark night instrument meteorological conditions, which resulted in subsequent spatial disorientation, uncontrolled descent, and impact with trees and terrain.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA13FA026
Event ID
20121017X91940
Case number
ERA13FA026
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. 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: 53bcdd9ca93f5c0ff9c9df9276731e783040fc10ede8e1d96979d3a0977f2ad9; retrieved 2026-09-14T15:46:21.031Z.