FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA22FA207 · Bell Helicopter Textron Canada 429

26 Apr 2022 · Elba, NY, United States

Mercy Flight Bell Helicopter Textron Canada 429 · Accident: abrupt maneuver while maneuvering

From CVQ · Batavia, NY to an unrecorded destination

Report a problem

Event

NTSB case
ERA22FA207
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

Bell Helicopter Textron Canada 429

Aircraft type
Bell 429
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
N507TJ
Operator
Mercy Flight
Onboard fatalities
Unknown
Route
From CVQ · Batavia, NYTo not recorded
Aircraft age
About 5 years (built 2017)
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
Maneuvering
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
Abrupt maneuver
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 propeller/rotor
  • Personnel issues › Action/decision
  • Personnel issues › Psychological
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The flight instructor was providing recurrent training to the operator’s pilots. During the first training flight of the day, a pilot who received instruction from the flight instructor described that the instructor told him to perform a vortex ring state (VRS) recovery maneuver, which the pilot accomplished, but shortly afterwards, the instructor requested that the pilot perform the maneuver again. During the second entry into VRS, the helicopter developed a very high descent rate, and the pilot was surprised when the flight instructor pilot did not intervene as the helicopter got deeper into the state. The pilot, feeling uncomfortable at that point, exited the very high descent rate on his own rather than waiting for further guidance from the instructor. The remainder of the first flight was uneventful. The second training flight of the day was the accident flight. A review of the recovered parametric data for this flight showed that the helicopter had been performing training maneuvers, and that shortly before the accident the helicopter was operating within the VRS envelope with a vertical descent rate between -800 to -1,300 feet per minute (fpm). This was consistent with the instructor directing the accident pilot to enter VRS for training purposes. Shortly thereafter, multiple abrupt control inputs were recorded, which including a forward cyclic input, followed by a nearly full-aft cyclic input within 1 second, as well as a concurrent full-down collective input with an increasing left pedal input. Based on contact signatures found on the helicopter’s main rotor blades and tailboom after the accident, it is likely that these abrupt control inputs resulted in the main rotor blades contacting the tail boom and the subsequent in-flight breakup of the helicopter. The parametric data and physical evidence observed during a postaccident examination of the wreckage revealed no evidence of any mechanical malfunctions or failures of the helicopter that would have precluded recovery from VRS. Based on this information, the reasons why the pilot(s) might have applied these abrupt control inputs could not be determined. Given the contextual commentary from the pilot of the previous training flight, it is likely the flight instructor did not provide adequate information to the accident pilot on how he would receive training for VRS, to include how they would identify, enter, and exit VRS.

Probable cause

The pilots’ inappropriate flight control inputs while in vortex ring state, which resulted in main rotor blade contact with the tail boom and a subsequent in-flight breakup. Also causal was the flight instructor’s inadequate monitoring of the flight.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA22FA207
Event ID
20220426105004
Case number
ERA22FA207
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: 836af34493fec57d472775568d3be28da64dd4ae24b92695aeac857f130b3783; retrieved 2026-09-15T07:43:36.960Z.