North Memorial Air Care Agusta A109 S accident
Agusta A109 S · Accident: loss of control in flight on approach
From Brainerd Lakes Regional Airport (BRD) to Chandler Field (AXN)
Event
- NTSB case
- CEN16FA372
- 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
- 0 · 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
- Charter & commuter
- 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
Agusta A109 S
- Aircraft type
- Agusta A109
- 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
- N91NM
- Operator
- North Memorial Air Care
- Onboard fatalities
- Unknown
- Route
- From Brainerd Lakes Regional Airport (BRD), Brainerd, MNTo Chandler Field (AXN), Alexandria, MN
- Aircraft age
- About 10 years (built 2006)
- 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
- Approach · IFR missed approach
- 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
- Destroyed
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Aircraft › Aircraft systems
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot and two medical crewmembers were conducting a night instrument flight rules cross-country flight to pick up a patient. During the instrument approach to the destination airport, the weather conditions deteriorated. The pilot was using the helicopter's autopilot to fly the GPS approach to the airport, and the pilot and the medical crew reported normal helicopter operations. Upon reaching the GPS approach minimum descent altitude, the pilot was unable to see the airport and executed a go-around. The pilot reported that, after initiating the go-around, he attempted to counteract, with right cyclic input, an uncommanded sharp left 45° bank . Recorded flight data revealed that the helicopter climbed and made a progressive right bank that reached 50°. The helicopter descended as the right bank continued, and the airspeed increased until the helicopter impacted treetops. The helicopter then impacted terrain on it's right side and came to rest near a group of trees.
Postaccident examinations of the helicopter and flight control systems did not reveal any malfunctions or anomalies that would have precluded normal operation. The helicopter was equipped with a GPS roll steering modification that featured a switch that allowed the pilot to manually select the heading reference source. In case of a malfunction or an erroneous setting, the helicopter's automatic flight control system had at least two limiters in place to prevent excessive roll commands. Further testing revealed that the GPS roll steering modification could not compromise the flight director and autopilot functionalities to the point of upsetting the helicopter attitudes or moving beyond the systems limiters.
Recorded helicopter, engine, and flight track data were analyzed and used to conduct flight simulations. The simulations revealed that the helicopter was operated within the prescribed limits; no evidence of an uncommanded 45° left bank was found. The helicopter performed a constant right climbing turn with decreasing airspeed followed by a progressive right bank with the airspeed and descent rate increasing. In order to recover, the simulations required large collective inputs and a steep right bank; such maneuvers are difficult when performed in night conditions with no visual references, although less demanding in day conditions with clear visual references. The data are indicative of a descending accelerated spiral, likely precipitated by the pilot inputting excessive right cyclic control during the missed approach go-around maneuver, which resulted in a loss of control.
Probable cause
The pilot's excessive cyclic input during a missed approach maneuver in night instrument meteorological conditions, which resulted in a loss of control and spiraling descent into terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN16FA372
- Event ID
- 20160917X62400
- Case number
- CEN16FA372
- 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: b9f23cfc0a4715c8419b304445df8fb3bcae960168baf3204e4e2c2297734583; retrieved 2026-09-16T04:16:37.877Z.