Lufthansa Airbus A319 112 incident
Airbus A319 112 · Incident: electrical system malfunction/failure en route
From Frankfurt Main Airport (FRA) to Amsterdam Airport Schiphol (AMS)
Event
- NTSB case
- ENG24LA009
- 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
- Ongoing
- 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
- Airline
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Not recorded
Airbus A319 112
- 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
- D-AIBG
- Operator
- Lufthansa
- Onboard fatalities
- Unknown
- Route
- From Frankfurt Main Airport (FRA), FrankfurtTo Amsterdam Airport Schiphol (AMS), Amsterdam
- 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
- Non-U.S., Commercial
- 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 · descent
- 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
On November 10, 2023 at 0713 UTC, a Lufthansa Airbus A319, registration D-AIBG, experienced the loss of both electrical generators during approach to Amsterdam Airport Schiphol, Netherlands. The airplane’s ram air turbine deployed automatically. The airplane landed without further incident or injuries reported by any of the occupants. The flight, Lufthansa 986,was an IFR flight from Frankfort Airport, Germany to Amsterdam Airport Schiphol.
According to the preliminary flight data recorder information, the aircraft was in descent at an altitude of approximately 31,500 feet when Generator 2 and then Generator 1 failed. After Generator 1 failed, the airplane entered an emergency electrical configuration and the ram air turbine (RAT) deployed. Information from the flight data recorder was interrupted for approximately 4 minutes; when the airplane exited from the emergency electrical configuration, the flight recorder was recovered.
The airplane’s two Integrated Drive Generators (IDG) and two Generator Control Units (GCU) were removed for further examination.
The Dutch Safety Board delegated the investigation to the National Transportation Safety Board as the State of Design and Manufacture of the IDGs and GCUs.
Verbatim NTSB factual narrative from the NTSB dataset
Sources
NTSB record ENG24LA009
- Event ID
- 20240105193615
- Case number
- ENG24LA009
- 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 UTC date the NTSB stores; the local time zone is not recorded, so the local date may differ by a day.
- API snapshot SHA-256: af952e69f333b6ad35e6ea8541563d335d8b7d8e51c393e4556a667557f790ce; retrieved 2026-09-16T18:25:04.271Z.