FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Spirit Airlines Airbus A319 132 incident

15 Feb 2020 · Sacramento, CA, United States

Airbus A319 132 · Incident: electrical system malfunction/failure on approach

From Harry Reid International Airport (KLAS) to Sacramento International Airport (SMF)

Report a problem

Event

NTSB case
ENG20LA016
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
Incident
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
Airline
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

Airbus A319 132

Aircraft type
Airbus A319
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
N521NK
Onboard fatalities
Unknown
Route
From Harry Reid International Airport (KLAS), Las Vegas, NVTo Sacramento International Airport (SMF), Sacramento, CA
Aircraft age
About 14 years (built 2006)
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 121: Air Carrier
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
Approach · IFR initial approach
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
None

Cause areas

No findings designated as a cause are recorded in the NTSB data yet.

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

NTSB narrative

This incident occurred when a Spirit Airlines Airbus A319 experienced a fault with both engine integrated drive generators (IDG) while on approach to the Sacramento International Airport (SMF), Sacramento, California. These faults resulted in the loss of electrical power supplied to both electrical networks (AC BUS 1 and AC BUS 2) leading to the loss of several flight deck displays and systems. Upon the dual loss of power, the ram air turbine (RAT) automatically extended and began driving the emergency generator to provide electrical power to vital services. The airplane landed without further incident, was towed to the gate and passengers deplaned normally.

A review of the airplane’s maintenance records found that the airplane had experienced a similar dual loss of power event during an approach into the Hartsfield-Jackson Atlanta airport (KALT), Atlanta, Georgia on the previous day. The airplane had also experienced a similar loss of power on three different occasions on ground while performing single engine taxi after landing in January 2020.

Each engine’s IDG was controlled by an independent digital computer called a generator control unit (GCU). One of its functions was to protect the IDG and its associated electrical network by monitoring and controlling the frequency and voltage output of its respected IDG. When the GCU detects a fault, it will isolate the IDG from the electrical network, and store the system fault data in its non-volatile memory (NVM). An amber fault message will also illuminate on the respective generator control push button switch indicating the channel is offline.

Post incident analysis of information from the airplane’s GCU revealed that during the incident flight and during the dual loss of power event that occurred on the previous day, both GCU’s recorded fault code 145. This information indicates that the frequency output for both the left and the right engine IDGs were outside of their specified design limits during the incident flight and on the previous day. Analysis of the data also revealed a similar out of limit frequency output from the left engine IDG when the airplane experienced the three loss of power events in January.

Examination and testing of the left engine IDG revealed that an internal component, a fixed cylinder block, was significantly worn beyond its design limits. Wear was observed in the gold-colored liners assembled inside of the bores of the cylinder block. The wear was uneven around the circumference and occurred close to either end of the bores, with the heaviest wear extending up from the bottom of the bores. The gold-colored liners were worn through in some areas in several bores, and silver-colored base metal was visible. The fixed cylinder block and pistons within IDG1 were replaced with serviceable original equipment manufacturer (OEM) parts and the IDG was re-tested. The IDG passed its tests indicating that the wear on the fixed cylinder block and pistons was the reason for the IDG failure during the event flight.

Examination of IDG2 revealed that only one of the cylinder bores of the fixed cylinder block was worn through in a similar fashion to the cylinder block from IDG1. Although testing of this IDG found that it exhibited a significant frequency modulation on its electrical output, the output was not outside of its specified design limit and therefore would not have triggered a fault code 145 to be recorded on the GCU. Nevertheless, several tests showed that the fault code 145 was almost triggered under the following test conditions: 1) A constant speed (or a slow sweep profile) between 6,100 RPM and 6,150 RPM, 2) A high IDG load that seems to increase slightly with the modulation amplitude.

Although Spirit Airlines maintenance had performed troubleshooting on the airplane after each of the previous loss of electrical power events, they were unable to determine any faults with the electrical system, including the IDGs. A review of their maintenance records found that the testing included a run-up of the engines to check electrical loads per their aircraft maintenance manual (AMM), and operational testing of the IDGs. According to Airbus, the introduction section of their A318/A319/A320/A321 troubleshooting manual (TSM) indicated that if an operator cannot find a fault symptom and/or fault isolation procedure necessary to ensure the continued airworthiness of the aircraft they should contact Airbus. Airbus indicated that they were not contacted by Spirit Airlines for assistance on these loss of electrical power events. It is likely that if Spirt Airlines maintenance had contacted Airbus for these loss of electrical power events, they may have identified fault code 145 on the Number 1 GCU and replaced its respective IDG prior to the February 15th event. As a result of this incident, Airbus has improved their TSM by incorporating steps to direct maintenance towards a direct extraction of the post flight report (PFR) and troubleshooting data (TSD) from the GCUs.

Probable cause

A worn component within each engine integrated drive generator (IDG) resulted in the loss of electrical power supplied to several flight deck displays and systems while on approach to landing. The component, a fixed cylinder block, had significant wearing of its reworked brass liners resulting in the IDGs producing a frequency output outside of their specified design limit.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ENG20LA016
Event ID
20200219X42743
Case number
ENG20LA016
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, damage. 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: c2cf9f823c1d6b2f9ff5d4c1ee56eb8f833ca19558342c30a6afde8fcff445f6; retrieved 2026-09-16T11:08:34.254Z.