The U.S. aircraft register, updated daily
Accidents · NTSB ENG20LA016 · Final report

Airbus A319 incident near Sacramento, California, February 15, 2020

On February 15, 2020 at about 3:42 pm local time, a 2006 Airbus A319, registered N521NK, was involved in an incident during approach (IFR initial approach) near Sacramento, California (Sacramento International Airpo airport). It was flown under scheduled airline rules (Part 121). No one was hurt; 117 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

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.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
February 15, 2020 · about 3:42 pm local time
Place
Sacramento, California · Sacramento International Airpo · map
Type
Incident
Injuries
No one was hurt; 117 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Airbus A319 132, built 2006 · all A319s on the register
Registration
N521NK · no longer on the register · serial 2797
Damage
Not recorded
Flight
Flight · scheduled airline rules (Part 121)

The NTSB's narrative final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Electrical system malf/failure during approach (IFR initial approach) defining event

The NTSB's findings

  • Aircraft › Aircraft systems › Electrical power system › AC generation system › Failure

Pilot

  • Certificate: airline transport pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 9,400 hours in all; 7,045 in this make and model
  • Last flight review: March 21, 2019
  • Medical certificate: Class 1 (without waivers/limitations)
  • Seat: left
  • Injury: no injuries

Co-pilot

  • Certificate: airline transport pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 4,030 hours in all; 1,455 in this make and model
  • Last flight review: April 29, 2019
  • Medical certificate: Class 1 (with waivers/limitations)
  • Seat: rgt
  • Injury: no injuries

The aircraft

  • Airframe total time: 44,894 hours
  • Last inspection: continuous airworthiness programme
  • Maximum gross weight: 166,449 lb
  • Seats: 152
  • Landing gear: retractable
  • Engine 1: Pratt And Whitney V2524-A5 (turbofan); 49,625 hours total
  • Engine 2: Pratt And Whitney V2524-A5 (turbofan); 46,910 hours total
  • Operator: Spirit Airlines Inc

The flight

  • Departed from: KLAS Las Vegas NV at 2:30 pm
  • Destination: SMF Sacramento CA
  • Flight plan: IFR
  • Runway 34L, 8,598 ft by 150 ft
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Sky: clear
  • Temperature: 0°F (-18°C), dew point 0°F (-18°C)

Injuries

FatalSeriousMinorNone
Cabi3
Flight crew2
Passengers112

Documents from the investigation the NTSB's docket: the evidence folder behind the report

11 documents, released by the NTSB on September 30, 2022. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

#DocumentWhat it is
1 Cockpit Voice Recorder - Specialista��s Factual Report PDF, 4 pages View Download
2 Flight Data Recorder - Specialista��s Factual Report PDF, 22 pages View Download
3 Flight Data Recorder - Attachment 1 (FDR Tabular Data for Flight #1, Compressed) zip file Download
4 Flight Data Recorder - Attachment 2 (FDR Tabular Data for Flight #3, Compressed) zip file Download
5 Maintenance Records PDF, 3 pages View Download
6 Systems Factual Report Attachment 1 Gapcu Nvm PDF, 11 pages View Download
7 Systems Factual Report Attachment 3 GCU3 Nvm PDF, 228 pages View Download
8 Systems Factual Report Attachment 2 GCU2 Nvm PDF, 141 pages View Download
9 Materials Laboratory Factual Report 22-040 PDF, 42 pages View Download
10 Systems Factual Report PDF, 21 pages View Download
11 Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 PDF, 11 pages View Download

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.