ERA20FA074 · Robinson R66
Robinson R66 · Accident: abrupt maneuver en route
From Martin State Airport (MTN) to Buffalo Niagara International Airport (BUF)
Event
- NTSB case
- ERA20FA074
- 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
Robinson R66
- Aircraft type
- Robinson R66
- 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
- N450MC
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Martin State Airport (MTN), Baltimore, MDTo Buffalo Niagara International Airport (BUF), Buffalo, NY
- Aircraft age
- About 1 year (built 2019)
- 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
- 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
- Destroyed
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Not determined › Not determined
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The helicopter pilot was conducting a night cross-country flight in visual meteorological conditions. Recorded data showed that while the helicopter was flying at an altitude of about 2,300 ft mean sea level and at an indicated airspeed of about 107 knots, slight pitch and roll oscillations occurred for about 20 seconds followed by a left roll that continued until the helicopter was inverted. A main rotor blade contacted the tailboom, leading to an in-flight breakup over a residential area. Postaccident examination of the airframe, flight controls, and engine assembly revealed no evidence of a preimpact failure or malfunction.
Because the helicopter’s pitch and roll values changed only minimally before the in-flight upset, the autopilot was likely engaged when the pitch and roll oscillations started. The pitch and roll oscillations might have been the result of the autopilot reacting to an external disturbance, specifically, the moderatetosevere turbulence that was reported in the area. Another possible cause of the pitch and roll oscillations was the pilot manually manipulating the cyclic control. Additionally, an in-flight malfunction of the autopilot’s roll servo actuator could not be ruled out as the source for the pitch and roll oscillations. While any of these scenarios might have precipitated the initial oscillations, none would have precluded the pilot from overriding the autopilot and manually flying the helicopter.
Even though the helicopter was equipped with devices that recorded flight and engine data at a rate of at least one parameter every second, the lack of an on-board crash-resistant cockpit imaging system precluded a determination of the pilot’s actions, or lack of actions, in response to the pitch and roll oscillations. About 6 months after this accident, the National Transportation Safety Board issued a safety recommendation requesting that major helicopter manufacturers, including the manufacturer of the accident helicopter, install crash-resistant flight recorders with cockpit imaging systems for existing helicopters. The helicopter manufacturer responded that it incorporated a cockpit camera system as standard equipment on all similar model helicopters manufactured beginning the year after the accident and offered as a kit for existing helicopters the same year. The cameras were not designed to be crash-resistant.
The pilot was not likely impaired or incapacitated by his diagnosed obstructive sleep apnea given the information about his effective continuous positive airway pressure device use. Also, some or all the ethanol detected in the pilot’s specimens might have been from a source other than ingestion. The possibility of an impairing or incapacitating medical event or impairing effects from the pilot’s use of clonazepam (alone or in combination with ethanol effects) could not be determined from the available evidence. However, no operational evidence indicated that the pilot’s performance was deficient during the flight time preceding the oscillations.
Probable cause
A severe left roll excursion after the onset of pitch and roll oscillations, which were not arrested by the pilot for undetermined reasons. This resulted in main rotor blade contact with the airframe and a subsequent inflight breakup of the helicopter.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA20FA074
- Event ID
- 20200109X20857
- Case number
- ERA20FA074
- 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 2020-01-10.
- API snapshot SHA-256: fb59ccb2405b84971276ca125a7dcf219f51a668a4ec1bd03c15c9d0f3cf9c5f; retrieved 2026-09-15T07:10:32.615Z.