FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA19FA035 · Aerospatiale AS 355F2 F1

30 Oct 2018 · Beekmantown, NY, United States

Catalyst Aviation Aerospatiale AS 355F2 F1 · Accident: dynamic rollover while maneuvering

From Plattsburgh, NY (no airport) to Beekmantown, NY

Report a problem

Event

NTSB case
ERA19FA035
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
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
Visual Meteorological Cond

Aerospatiale AS 355F2 F1

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
N372CA
Onboard fatalities
Unknown
Route
From Plattsburgh, NY (no airport)To Beekmantown, NY
Aircraft age
About 37 years (built 1981)
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 133: Rotorcraft Ext. Load
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
Maneuvering · hover
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
Dynamic rollover
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Pole
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

  • Environmental issues › Conditions/weather/phenomena
  • Environmental issues › Physical environment
  • Personnel issues › Task performance

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

NTSB narrative

The pilot, pilot-rated passenger, and two linemen were conducting a flight to temporarily install a block (a large pulley used for fiber-optic wire) on a utility pole that was part of a set of high-tension power lines. The pilot was seated in the front right seat, and one of the linemen was seated outside of the helicopter on a bench that was externally attached to the right side of the landing gear. The pilot-rated passenger, who was observing the flight for training purposes, was seated in the front left seat, and the other lineman was seated in the aft left seat. The power lines were aligned northwest/southeast, which required the pilot to approach the utility pole on a southeasterly heading so that the pole would be to the right of the pilot and lineman. For the lineman to install the block on the utility pole, the pilot had to hover the helicopter next to the pole. The wind conditions about the time of the accident were such that the helicopter would have encountered a tailwind. The pilot-rated passenger, the lineman seated in the aft left seat, and witnesses on the ground all stated that, while the helicopter was hovering next to the utility pole, the helicopter's right skid struck the pole a few times. The helicopter rolled over, became entangled in energized power lines, and caught fire. All four of the occupants survived the impact with the power lines and jumped to the ground to escape the burning wreckage. The pilot and the lineman seated on the bench did not survive the fall.

A postimpact fire consumed most of the helicopter while it was entangled in the power lines, and sections of the helicopter dropped from the power lines as it burned. Examination of the wreckage and both engines revealed no preimpact mechanical deficiencies that would have precluded normal operation.

The surviving lineman stated that he had flown with the pilot earlier that day and that the pilot had difficulty keeping the helicopter steady due to the strong wind, so the lineman temporarily installed a block before the helicopter returned to the base. Before the accident flight, the pilots, linemen, their foreman, the owner and a representative of the helicopter company and representatives of the linemen's employer held a safety meeting and agreed that, although the wind was too strong to fully install a block, the wind was "okay" to temporarily install another block. Given that the pilot had difficulty holding the helicopter steady while hovering with a tailwind on the previous flight the pilot most likely also had difficulty hovering the helicopter with the tailwind that was present about the time of the accident. The helicopter's subsequent impact with the utility pole resulted in a dynamic rollover into the power lines.

Probable cause

The pilot's failure to keep the helicopter clear of a utility pole while hovering with a tailwind, which resulted in a dynamic rollover into active power lines.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA19FA035
Event ID
20181030X81557
Case number
ERA19FA035
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. 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: 80ee79bfd3e9df6c0be7d2fe925713e3b8a6deae926bfb35f320030d99551e19; retrieved 2026-09-15T06:50:12.699Z.