FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN14FA369 · Agusta SPA A109E E

17 Jul 2014 · Newkirk, NM, United States

TriState CareFlight Agusta SPA A109E E · Accident: loss of control in flight en route

From Santa Fe Municipal Airport (SAF) to Tucumcari, NM

Report a problem

Event

NTSB case
CEN14FA369
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
3 · 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
Unknown

Agusta SPA A109E E

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
N507CF
Onboard fatalities
Unknown
Route
From Santa Fe Municipal Airport (SAF), Santa Fe, NMTo Tucumcari, NM
Aircraft age
About 14 years (built 2000)
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 · cruise
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
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, not marked as estimated; no uncertainty radius is established.

NTSB narrative

After the commercial pilot received an emergency medical services helicopter flight request, he quickly (in about 20 seconds) assessed the weather conditions and accepted the flight. No records were found indicating that the pilot obtained an official weather briefing before departing on the flight, and the investigation could not determine which weather resources the pilot used to assess the weather. About 8 minutes later, the pilot called the company's operations center to report that the flight was departing; this was the last communication received from the pilot. The helicopter was operating in an area that was known by company pilots, including the accident pilot, to have the potential for low visibility, even though there were no airport weather reporting facilities or Doppler radar coverage in the area.

A review of GPS data showed that, while en route to pick up the patient, the helicopter performed a slight descending 360° turn before continuing toward the hospital. Weather overlays with the GPS track indicated that the helicopter made the 360° turn about the same time that an outflow boundary wave, which could have increased the potential for windshear and strong updrafts and downdrafts and reduced ceilings and visibility. Following the 360° turn, the helicopter proceeded toward the destination. About 14 minutes later, the helicopter turned right and began flying toward a major highway. It is likely that, due to the reduced visibility in the area, the pilot was flying toward the highway to follow the lights toward the city. The helicopter then turned further right and began to climb. As the helicopter entered another outflow boundary wave, it turned left. The left turn tightened, and the helicopter began to rapidly descend into terrain. The helicopter impacted a mesa in a near-level attitude.

A review of a company communication recording showed that, about 17 minutes after the estimated accident time, the operations center attempted to contact the flight crew and was unsuccessful. The company sent three company helicopters to the accident helicopter's last known position; one helicopter pilot flew near the helicopter's site but was unable to see anything, and the two other pilots could not proceed close to the accident site due to clouds and low visibility. The wreckage was subsequently located by local law enforcement. A postaccident examination of the helicopter and engine did not reveal any anomalies that would have prevented normal operation.

Due to mid- and low-level cloud cover, it is likely that no lunar or celestial lighting was available for amplification by the pilot's night vision goggles (NVG). Since the helicopter was not equipped with an infrared spotlight, only cultural light would have been available for NVG amplification. However, the helicopter was operating in a remote, sparsely populated area with minimal cultural light. Although the pilot's recurrent training included recovery procedures from inadvertent entry into instrument meteorological conditions (IMC), and his training records showed that he satisfactorily completed this item on his most recent training flight about 8 months before the accident, the circumstances of the accident are consistent with the pilot's inadvertent visual flight into IMC, which resulted in a loss of helicopter control.

Probable cause

The pilot's inadvertent visual flight into instrument meteorological conditions, which resulted in a loss of helicopter control.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record CEN14FA369
Event ID
20140717X70001
Case number
CEN14FA369
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. 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: 6a25873bacab96ad390189c867f2aee0c77b2ae3ffe668d231f8b659ff376edf; retrieved 2026-09-14T17:21:46.290Z.