FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ANC19FA018 · Beech A60

5 May 2019 · Santa Rosa, NM, United States

Beech A60 · Accident: aerodynamic stall/spin while maneuvering

From Arlington Municipal Airport (GKY) to Santa Fe Municipal Airport (SAF)

Report a problem

Event

NTSB case
ANC19FA018
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

Beech A60

Aircraft type
Beechcraft 60
Category
Airplane
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
N102SN
Operator
Unknown
Onboard fatalities
Unknown
Route
From Arlington Municipal Airport (GKY), Arlington, TXTo Santa Fe Municipal Airport (SAF), Santa Fe, NM
Aircraft age
About 46 years (built 1973)
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
Maneuvering · low-altitude flying
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
Aerodynamic stall/spin
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
  • Aircraft › Aircraft systems
  • Personnel issues › Task performance

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The pilot was performing a personal cross-country flight. While en route to the intended destination, the pilot contacted air traffic control to report that the airplane was having a fuel pump issue and requested to divert to the nearest airport. The pilot stated that the request was only precautionary and did not declare an emergency during the flight; he provided no further information about the fuel pump. As the airplane approached the diversion airport, witnesses observed the airplane flying low and rolling to the left just before impacting terrain, after which a postcrash fire ensued.

An examination of the airframe revealed no preimpact mechanical malfunctions or failures that would have precluded normal operation. A postaccident examination and review of recorded data indicated that the left engine was secured and in the feather position, and that the right engine was operating at a high RPM setting.

The left engine-driven fuel pump was found fractured. Further examination of the fuel pump revealed fatigue failure of the pressure relief valve. The fatigue failure initiated in upward bending on one side of the valve disk and progressed around both sides of the valve stem. As the cracks grew, the stem separated from the disk on one side and began to tilt in relation to the disk and the valve guide due to the non-symmetric support, which caused the lower end of the stem to rub against the valve guide, creating wear marks. The increasing stem tilt would have impinged against the valve guide, and the valve might have begun to stick in the closed position. If the valve were stuck in the closed position, it would not be able to open, and the outlet fuel pressure could rise above the set point pressure. Because the pump was driven by the engine, there would not be a way for the pilot to shut it off, disconnect it, or bypass it. Instead, the fuel pressure would continue to rise until the valve were to unstick. Thus, the pilot was likely experiencing variable fuel pressure as the valve became stuck and unstuck.

Examination of the spring seat and the diaphragm plate, which were in contact with each other in the fuel pump assembly, revealed wear marks on the surface of each component, with one mark on the diaphragm plate and two wear marks on the spring seat. The two wear marks on the spring seat were distinct features separated by material with no wear indications in between. The only way that these wear marks could have occurred were if the spring seat was separated from the diaphragm plate and reinstalled in a different orientation. Thus, it is likely that the pilot had encountered a fuel pump problem before the accident flight and that someone tried to troubleshoot the problem.

The last radar data point indicated that the airplane was traveling at a groundspeed of about 98 knots, and had passed north of the airport, traveling to the southwest. The minimum control speed for the airplane with single-engine operation was 88 knots. However, it is likely that if the pilot initiated a left turn back toward the airport, that the right engine torque and the 14 knot wind with gusts to 24 knots would have necessitated a higher speed. Because appropriate control inputs and airspeed were not maintained, the airplane rolled in the direction of the feathered engine (due to the left fuel pump problem), resulting in a loss of control.

The pilot's toxicology report was positive for cetirizine, sumatriptan, gabapentin, topiramate, and duloxetine. All of these drugs act in the central nervous system and can be impairing alone or in combination. Although this investigation could not determine the reason(s) for the pilot's use of these drugs, they are commonly used to treat chronic pain syndromes or seizures. It is likely that the pilot was experiencing some impairment because of multiple impairing medications and was unable to successfully respond to the in-flight urgent situation and safely land the airplane.

Probable cause

The pilot's loss of airplane control due to his failure to maintain appropriate control inputs and airspeed after shutting down an engine because of a progressive failure of the pressure relief valve in the fuel pump, which resulted in variable fuel pressure in the engine. Contributing to the loss of control was the pilot's use of multiple impairing medications.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ANC19FA018
Event ID
20190505X10250
Case number
ANC19FA018
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: 4e1921ea0db77821ef50793b780a8663ef875ce146e463e2ea2e5451927a98c7; retrieved 2026-09-15T06:57:29.786Z.