Air Methods Airbus Helicopters EC 130 T2 accident
Airbus Helicopters EC 130 T2 · Accident: loss of control in flight while maneuvering
From Merkel Field Sylacauga Municipal Airport (SCD) to an unrecorded destination
Event
- NTSB case
- ERA23FA175
- 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
- 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
Airbus Helicopters EC 130 T2
- Aircraft type
- Airbus EC-130
- 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
- N231SH
- Operator
- Air Methods
- Onboard fatalities
- Unknown
- Route
- From Merkel Field Sylacauga Municipal Airport (SCD), Sylacuaga, ALTo not recorded
- Aircraft age
- About 9 years (built 2014)
- 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
- 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
- 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
Witnesses saw a helicopter along the side of a road about 100 ft away and 3 to 4 ft above the ground. The helicopter was hovering and parallel to the road. The helicopter then rapidly ascended and turned toward the road before it moved above the witnesses’ car. After several seconds, the helicopter turned back 180° toward a field, and immediately the pitched nose down and impacted the road behind them. Video from a local deputy sheriff’s dash camera captured the helicopter coming over the trees, going out of view for about one second, then reappearing in a steep, nose-down attitude before impacting the road. The helicopter then slid about 20 ft before coming to rest in the grass. Postaccident examination of the airframe and engine revealed no evidence of any preimpact mechanical malfunctions or failures that would have precluded normal operation. An on-board video/data recorder was recovered from the accident scene. The video revealed that, from the time the helicopter departed on the accident flight to the time the pilot began the hover over a gravel road, the flight was uneventful. During the hover, the helicopter was moving slowly forward, and flight control inputs appeared to be normal for a hover. From the hover, the FLI increased to about 7.4 and the helicopter started to move about 50 ft forward as the altitude increased. Trees were visible forward of the helicopter outside the windscreen. While the altitude increased from about 50 ft to 110 ft above ground level (agl), the attitude indicator increased to a maximum of over 20° nose-up pitch and 20° right roll. There was no appreciable change in pedal or cyclic position by the pilot. The helicopter then went from a nose-high attitude to an excessive nose-low attitude, while continuing to roll to the right to a maximum of 30°. By the time the pilot reacted, his movement of the cyclic, left and aft, was insufficient to bring the helicopter under control. The attitude indicator tumbled, and the primary flight display (PFD) displayed an obstacle indication. The video then showed the helicopter impacted the road at a perpendicular angle. Toxicology testing performed by the FAA’s Forensic Services Laboratory on the pilot revealed cetirizine, cyclobenzaprine, and diphenhydramine, all of which are potential central nervous system (CNS) depressants. Each drug also carries a warning that use with other CNS depressant medications is not advised, as use of these medications in combination may cause sedation, impair concentration, worsen reaction time and vigilance, and worsen psychomotor performance. The pilot’s use of multiple sedating CNS depressants likely worsened this performance deficiency and contributed to his delayed application of appropriate control inputs.
Probable cause
The pilot’s delayed corrective inputs while maneuvering, which resulted in a loss of control. Contributing to the accident was the pilot’s use of multiple sedating medications.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA23FA175
- Event ID
- 20230403106990
- Case number
- ERA23FA175
- 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, 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: d1705978d94e310c2e85db39debba1b4181e05b30906d30abb95287091012e5a; retrieved 2026-09-15T07:58:20.111Z.