FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA14FA168 · Piper PA-44-180

24 Mar 2014 · Brunswick, GA, United States

Atp USA Piper PA-44-180 · Accident: loss of control in flight en route

From Concord-Padgett Regional Airport (JQF) to Jacksonville Executive at Craig Airport (CRG)

Report a problem

Event

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

Piper PA-44-180

Aircraft type
Piper PA-44
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
N923RS
Operator
Atp USA
Onboard fatalities
Unknown
Route
From Concord-Padgett Regional Airport (JQF), Concord, NCTo Jacksonville Executive at Craig Airport (CRG), Jacksonville, FL
Aircraft age
About 35 years (built 1979)
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
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 systems
  • Personnel issues › Psychological
  • Personnel issues › Task performance

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

NTSB narrative

The pilots of the twin-engine airplane were conducting a cross-country instrument flight rules (IFR) flight. Although both pilots were instrument-rated and IFR-current, the right seat pilot had only 8.8 hours of actual instrument experience, and the left seat pilot had only 1.8 hours of actual instrument experience. While en route and likely operating in IFR conditions, radio and radar contact were lost after the airplane entered a descending, 180-degree right turn. Examination of the wreckage at the accident site revealed signatures consistent with an in-flight breakup of the airframe. The horizontal situation indicator (the only vacuum-system-driven flight instrument that was recovered) exhibited signatures showing that it was likely not operational when the airplane impacted the ground. Both of the engine-driven vacuum pumps exhibited fractured rotors. Although physical examination of the vacuum pumps could not determine whether the rotors fractured before or during impact, the inoperative horizontal situation indicator suggests that both pumps had failed before the impact.

The operator reported that the vacuum pump mounted to the airplane's right engine was not operational before the airplane was dispatched on the accident flight and that the pilots had been advised of this deficiency. The operator used the Part 91 minimum equipment limitations for flights, which permitted dispatching the airplane with only one of the two engine-driven vacuum pumps operational. However, the Federal Aviation Administration's master minimum equipment list for the airplane for Part 91 operators, advises operators to limit the airplane to daytime visual flight rules flights when only one of the two vacuum pumps is operational. The operator's decision to dispatch the airplane with a known mechanical deficiency and no operational limitations reduced the safety margin for the flight and directly contributed to the accident.

It is likely that the left vacuum pump failed en route rendering the vacuum-driven flight instruments inoperative. Given the pilots' minimal flight experience operating in IFR conditions combined with the difficulty of detecting and responding to the loss of attitude information provided by the vacuum-driven flight instruments, it is likely that the pilots became spatially disoriented and lost control of the airplane, resulting in the subsequent inflight breakup. No definitive determination could be made as to which of the two pilots was acting as pilot-in-command of the airplane at the time of the loss of control.

Probable cause

An inflight failure of the airplane's only operating vacuum pump, which resulted in the loss of attitude information provided by vacuum-driven flight instruments. Also causal was the pilots' failure to maintain control of the airplane while operating in instrument flight rules (IFR) conditions, likely due to spatial disorientation, following the failure of the vacuum pump. Contributing to the accident was the operator's decision to dispatch the airplane with a known inoperative vacuum pump into IFR conditions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA14FA168
Event ID
20140324X00546
Case number
ERA14FA168
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: 89ec22927c6d5fed0e0d1a323e0987cf5d07ea20a5a3e15781d0cb55954e4c4a; retrieved 2026-09-14T16:12:05.422Z.