Northwest Airlines Flight 853
Airbus Industrie A319-114 · Accident: system/component malfunction/failure (non-power) on approach
From LaGuardia Airport (LGA) to Detroit Metropolitan Wayne County Airport (DTW)
Event
- NTSB case
- CHI08LA071
- 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
- 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 Industrie A319-114
- 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
- N349NB
- Operator
- Northwest Airlines
- Onboard fatalities
- Unknown
- Route
- From LaGuardia Airport (LGA), NEW YORK, NYTo Detroit Metropolitan Wayne County Airport (DTW), Detroit, MI
- 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
- 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
- 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
- System/component malfunction/failure (non-power)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft power plant
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The accident flight was the first one for the airplane after having maintenance performed on the number two (right) engine during the previous evening. The first officer reported the engine cowls were flush and he did not see any "hanging" cowl latches when he looked underneath the engine cowls during the preflight. The captain reported the preflight, taxi, and takeoff were normal. During climb out the lead flight attendant informed the pilots that a passenger reported that the number two engine cowling was flapping after takeoff. The captain then began to monitor the N1 vibration indications on the number two engine. He reported that the vibration was approximately double the indication from the number one engine, but the indicator was not flashing, nor had it turned amber. The captain reported that during cruise flight the number two engine vibration decreased and about 20 minutes after they leveled off, the airplane shuddered. He reported the remainder of the flight was normal until they were taxiing after landing and the lead flight attendant called the cockpit stating that "part of the right engine had come off." Half of the engine cowl departed the airplane when it was on a one mile final. The other half departed the airplane as it touched down. Another airplane subsequently contacted this part of the cowling when it landed after the accident airplane. Contract maintenance personnel reported they changed the N1 sensor on the number two engine. They reported they shut the fan cowling, but did not latch it as they still needed to perform an engine run and check for leaks. They performed the engine run and were in the cockpit when another mechanic asked for help on another airplane. The mechanics left the accident airplane to assist the other mechanic. Neither mechanic returned to the accident airplane to either latch or verify that the fan cowling had been latched. The aircraft maintenance manual (AMM) instructions for replacing the N1 sensor states, "Close the fan cowl doors (Ref. AMM TASK 71-13-00-410-040)." This task was not completed prior to the airplane being returned to service. The separated cowling contacted the right side of the horizontal stabilizer which resulted in substantial damage to the stabilizer. In addition, the fan cowl doors, number two engine pylon, the number two engine reverser, and the right wing number one slat were damaged.
Probable cause
The separation of the engine cowling which resulted from maintenance personnel failing to follow maintenance procedures in that they did not latch the engine cowling following the maintenance inspection. A factor associated with the accident was their attention was divereted from the task when another mechanic asked for assistance.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CHI08LA071
- Event ID
- 20080125X00103
- Case number
- CHI08LA071
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (5)
- 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, coordinates. 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: 8ccd11415c601562b92a51bcf23760f62597792c3471ef25176a92276bdd6518; retrieved 2026-09-15T09:20:57.086Z.
- The NTSB's operator name is blank for N349NB; the operator shown is the name the NTSB records it doing business as.