FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

DCA14CA043 · General Atomics MQ-9

27 Jan 2014 · Point Loma, CA, United States

General Atomics MQ-9 · Accident: electrical system malfunction/failure en route

From Sierra Vista Municipal Airport / Libby Army Air Field (FHU) to Sierra Vista Municipal Airport / Libby Army Air Field (FHU)

Report a problem

Event

NTSB case
DCA14CA043
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
Event fatalities
Unknown
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
Government
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

General Atomics MQ-9

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
CBP-159
Onboard fatalities
Unknown
Route
From Sierra Vista Municipal Airport / Libby Army Air Field (FHU), Sierra Vista, AZTo Sierra Vista Municipal Airport / Libby Army Air Field (FHU), Sierra Vista, AZ
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
Public Aircraft
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
Electrical system malfunction/failure
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

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

NTSB narrative

On January 27, 2014, at approximately 11:18 p.m. Pacific Standard Time (PST), a General Atomics MQ-9 unmanned aircraft system (UAS) operated by the U.S. Customs and Border Protection (CBP), registered as CBP159, was substantially damaged following an intentional ditching 23 miles west of Point Loma, California. The aircraft experienced a generator failure approximately one hour prior to the ditching. The crew elected to ditch the aircraft upon determining there was insufficient battery power to transit the aircraft to the nearest recovery site at Fort Huachuca, Arizona. The flight was conducted as a non-military public aircraft operation under the provisions of Title 49 of the United States Code (U.S.C.) Sections 40102 and 40125, and a Federal Aviation Administration (FAA) Certificate of Authorization (COA). The flight operated under instrument flight rules inside Warning Area (W-291) and visual meteorological conditions. There were no injuries.

According to the operator, the aircraft was en route to the assigned operational areas at FL280. An audible alarm sounded followed by the "battery-sourcing current, 28 V bus - voltage approaching lower limit, and "power system/fault- payload shed" warnings. These are all indications of a generator failure. The pilot immediately reversed course and called for the Dual Generator Failure Checklist. The checklist was completed without restoration of generator operation. Throughout the remainder of the flight, the pilot attempted multiple unsuccessful generator resets. The crew analyzed the power supply options and determined that the aircraft lacked sufficient backup battery power to sustain flight for the time required to return to base, which would require a transit across populated areas. The crew proceeded to the Flight Termination Point (FTP) on the eastern side of W-291 to complete an intentional ditching of the aircraft. The aircraft was being controlled via Ku satellite communication (SATCOM) and the crew elected to leave most of the electrical equipment on to ensure sufficient electrical power was available to control the aircraft throughout the ditching evolution.

While en route to the FTP, the pilot descended the aircraft from FL280 to 5,000 feet mean sea level (MSL) and then continued the descent to get below a marine overcast layer that was at approximately 2,000 feet to ensure the intended FTP was clear. Once it was determined that the ditch area was clear of maritime traffic, the pilot positioned the aircraft to the south of the FTP and initiated a descent. At approximately 600 feet MSL, the crew lost link with the aircraft due to a low voltage condition that caused an automatic reset of the Interim Link Manager Assembly (ILMA). After approximately two minutes, the crew was able to re-establish return link and found that the aircraft was climbing through 2,000 feet MSL on its lost link profile (last set to 5,000 feet MSL). The crew re-established the command link and positive control. The pilot maneuvered the aircraft back towards the FTP, actuated the condition lever to stop the engine and completed the ditching. The aircraft impacted the water approximately 1.7 miles north of the FTP, destroying the aircraft.

A full CBP report of this accident is available in the public docket for this case.

Probable cause

intentional controlled ditching of the aircraft due to failure of the starter/generator supplying electrical power to the aircraft.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record DCA14CA043
Event ID
20140128X51154
Case number
DCA14CA043
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: 6b8f4cd7b42e122129025cd02dad85cf465057cfe2f8ad561fae04f307708dd0; retrieved 2026-09-15T23:17:12.890Z.