FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CareFlite Agusta SPA A109E accident

30 Sept 2012 · Eastland, TX, United States Possible conflict

Agusta SPA A109E · Accident: loss of control in flight while maneuvering

From Granbury Regional Airport (GDJ) to Eastland Municipal Airport (ETN)

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's location. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
CEN12FA670
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
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
Instrument Meteorological Cond

Agusta SPA A109E

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
N144CF
Operator
CareFlite
Onboard fatalities
Unknown
Route
From Granbury Regional Airport (GDJ), Granbury, TXTo Eastland Municipal Airport (ETN), Eastland, TX
Aircraft age
Not recorded
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
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
  • Not determined › Not determined
  • Personnel issues › Task performance

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

NTSB narrative

The emergency medical service helicopter was dispatched on a 30-minute flight to pick up a patient at a hospital. Due to area weather forecasts of marginal visual meteorological conditions (VMC) to instrument meteorological conditions (IMC) conditions, the pilot had the flight dispatcher file an instrument flight rules (IFR) flight plan in the event that he had to execute an IFR approach at his destination. The first 20 minutes of the flight were conducted in VMC about 2,500 ft mean sea level (msl) and were uneventful. During the final 10 minutes of the flight, the helicopter was nearing IMC, which included high overcast and midlevel scattered to broken clouds with light to moderate rain showers and reduced visibility. The pilot began a climb to 4,000 ft msl and then contacted an air traffic controller to activate the IFR flight plan. During this time, both the flight paramedic and flight nurse told the pilot that they were not comfortable entering the worsening weather conditions. Upon reaching 4,000 ft msl, the pilot engaged the autopilot in altitude hold mode, and the helicopter then abruptly pitched down 90 degrees and began spinning with the airspeed increasing. The pilot identified a disagreement between the pilot and copilot attitude director indicators, turned the autopilot off, and moved his scan to the backup attitude director indicator. The pilot then attempted an unusual attitude recovery by initiating back pressure on the cyclic control; however, the helicopter continued to descend rapidly through the bottom of the cloud base very close to the ground. The helicopter subsequently touched down in a level attitude, bounced several times, and skidded to a stop. All three occupants were assisted from the wreckage by ground personnel.

Examination of the flight control systems did not reveal any anomalies that might have contributed to the accident. A review of the helicopter's maintenance history revealed that other company pilots had reported several occurrences of uncommanded pitch-and-roll anomalies with the helicopter during the previous several years. Maintenance inspections after these occurrences could not duplicate the reported problems, and the helicopter was always returned to service after successful flight control systems check flights. After the accident, the autopilot system, gyros, and servo components were examined, and no preimpact anomalies were found; however, the solid-state components could not be tested for functionality due to damage. The reason for the reported in-flight control anomaly could not be determined.

The flight paramedic and flight nurse said that they lost visual reference to the ground during the in-flight upset. Therefore, it is possible that the transition from VMC to IMC led to the pilot becoming spatially disoriented while he was trying to recover from the reported upset and that this prevented him from recovering from it; however, investigators could not definitively determine if the pilot became spatially disoriented. Regardless, it is likely that an earlier transition from VFR to IFR flight before encountering IMC would have given the pilot a better chance to recover from the reported autopilot system-induced anomaly and would have reduced the possibility of his becoming spatially disoriented.

Probable cause

The loss of helicopter control after an in-flight upset, which occurred when the pilot selected the autopilot’s altitude hold mode; the reason for the reported in-flight control anomaly could not be determined during postaccident helicopter examinations. Contributing to the accident was the pilot's delay in transitioning to instrument flight rules flight before entering instrument meteorological conditions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN12FA670
Event ID
20121005X85658
Case number
CEN12FA670
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: 8ceade027d225fc5f5431a8925532f76ff8160b5569131243010f9c457302e9c; retrieved 2026-09-15T20:06:19.419Z.