FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Ryan International Airlines Airbus Industrie A320-233 incident

13 Jul 2004 · Atlanta, GA, United States

Airbus Industrie A320-233 · Incident during initial climb

From Hartsfield Jackson Atlanta International Airport (KATL) to Orlando International Airport (KMCO)

Report a problem

Event

NTSB case
ATL04IA156
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 Industrie A320-233

Aircraft type
Airbus A320
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
N951LF
Onboard fatalities
Unknown
Route
From Hartsfield Jackson Atlanta International Airport (KATL), Atlanta, GATo Orlando International Airport (KMCO), Orlando, FL
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
Initial climb
First occurrenceThe 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
Miscellaneous/other
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Minor

Cause areas

  • Company maintenance personnel › Procedures/directives, not followed

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The flight departed runway 27R, and immediately after takeoff, a passenger reported seeing a "cover" come off the No. 1 engine. The captain felt the airplane "shutter," declared an emergency, and returned the airplane to the airport and landed without further incident. Examination of the airplane revealed both sides of the No. 1 engine fan cowl were separated. The inboard fan cowl door was found approximately 7.5 nautical miles west southwest of the airport, and the outboard fan cowl door was found beside the runway. Examination of the latching mechanisms on each cowl door revealed no evidence of failure or mechanical malfunction. A mechanic stated he opened the fan cowl for the No. 1 engine prior to the flight, and he could not recall if the cowl doors were fully latched. A review of data provided by the Transportation Safety Board (TSB) of Canada revealed that, between 1991 and September 2000, there were ten similar cowl door separation events documented worldwide, and each involved the cowl doors having been opened prior to the flight. Examination of the incident airplane revealed it was equipped with the modifications outlined in Airworthiness Directive (AD) 2003-18-06 amendment 39-13297, which mandates the installation of a hold-open device for the cowl doors, as well as a modification of the latch handles to ensure that unfastened latch handles will hang down. A review of the operator's A320/321 preflight checklist revealed it included for each engine, "Check the fan cowl doors." During post-incident examination, a visual walk-around was performed with the undamaged No. 2 engine cowl in various unlatched configurations. Examination revealed unlatched cowl doors can appear closed flush when the hold-open device is overridden in preparation for latching, and unfastened latches that hang down may be obscured from view by the shape of the fan cowl. In response to this incident, Airbus Industrie issued an Operator's Information Telex to "A319/A320/A321 V2500 operators." The telex recommended that, in addition to mandatory compliance with AD 2003-18-06, operators consider the following: "... strictly adhere to AMM Task 71-13-00 for proper latching and closing of fan cowl doors after each maintenance action requiring cowl opening. ... It is essential that a flight crew member visually inspects the fan cowl doors prior to each flight to ensure that they are closed and latched."

Probable cause

The failure of company maintenance personnel to secure the nacelle/cowl doors, which resulted in a separation of the doors during takeoff initial climb.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ATL04IA156
Event ID
20040719X01004
Case number
ATL04IA156
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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, 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: 171da8beb457e7b7a2b632becdb4311ad9553551007502b73e79ea3412107ed0; retrieved 2026-09-18T15:22:08.132Z.