ASN Wikibase Occurrence # 69375
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information.
If you feel this information is incomplete or incorrect, you can submit corrected information.
| Date: | Monday 19 October 2009 |
| Time: | 05:05 LT |
| Type: |  Boeing 767-332ER |
| Owner/operator: | Delta Air Lines |
| Registration: | N185DN |
| MSN: | 27961/576 |
| Year of manufacture: | 1995 |
| Total airframe hrs: | 70009 hours |
| Engine model: | Pratt & Whitney PW4000 Series |
| Fatalities: | Fatalities: 0 / Occupants: 194 |
| Aircraft damage: | None |
| Category: | Serious incident |
| Location: | Atlanta Hartsfield-Jackson International Airport, GA (ATL/KATL) -
 United States of America
|
| Phase: | Approach |
| Nature: | Passenger - Scheduled |
| Departure airport: | Rio de Janeiro/Galeão-Antonio Carlos Jobim International Airport, RJ (GIG/SBGL) |
| Atlanta Hartsfield-Jackson International Airport, GA (ATL/KATL) | |
| Investigating agency: | NTSB |
| Confidence Rating: |  Accident investigation report completed and information captured |
During the flight one of the three required flight deck crew members became ill and was considered to be incapacitated. The remaining two crew members conducted the entire night flight without the benefit of a customary break period. Throughout the flight the crew made comments indicating that they were fatigued and identified fatigue as their highest threat for the approach, but did not discuss strategies to mitigate the consequences of fatigue. At the time of the incident, the crew had been on duty for about 12 hours and the captain had been awake for over 22 hours, while the first officer had been awake for at least 14 hours.
During the descent and approach, the flight crew was assigned a number of runway changes; the last of which occurred near the final approach fix for runway 27L. While the flight was on final approach, the crew was offered and accepted a clearance to sidestep to runway 27R for landing. Although the flight crew had previously conducted an approach briefing for two different runways, they had not briefed the approach for runway 27R and were not aware that the approach light system and the instrument landing system (ILS) were not available to aid in identifying that runway. When the crew accepted the sidestep to runway 27R, the captain, who was the flying pilot, saw the precision approach path indicator and lined the airplane up on what he said were the brightest set of lights he could see. During the final approach, the first officer was preoccupied with attempting to tune and identify the ILS frequency for runway 27R. Just prior to the airplane touching down, the captain realized they were landing on a taxiway. The airplane landed on taxiway M, 200 feet north of, and parallel to, runway 27R.
Postincident flight evaluations of the airport lighting indicated that there were a number of visual cues that could have misguided the captain to align with taxiway M instead of runway 27R while on final approach. These cues included numerous taxiways signs along the sides of taxiway M which, from the air, appeared to be white and could be perceived as runway edge lights. In addition, the blue light emitting diode (LED) lights used on the eastern end of taxiway M were perceived to be brighter than the adjacent incandescent lights on the airfield and the alternating yellow and green lights in the ILS critical area provided the appearance of a runway centerline. The postincident flight evaluations indicated that when the approach lights or the ILS for runway 27R were available and used, it was clearlyevident when the airplane was not aligned with the runway.
Probable Cause: The flight crew's failure to identify the correct landing surface due to fatigue. Contributing to the cause of the incident were (1) the flight crew's decision to accept a late runway change, (2) the unavailability of the approach light system and the instrument landing system for the runway of intended landing, and (3) the combination of numerous taxiway signs and intermixing of light technologies on the taxiway.
Accident investigation:
 |
|
Sources:
NTSB OPS10IA001
FAA register: 2. FAA: http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?omni=Home-N-Number&nNumberTxt=185DN
History of this aircraft
Other occurrences involving this aircraft
| 25 June 1996 | N185DN | Delta Air Lines | 0 | New York-John F. Kennedy International Airport, NY (JFK) | |
min |
| 14 July 2011 | N185DN | Delta Air Lines | 0 | Boston-Logan International Airport, MA (BOS) | |
min |
Revision history:
| Date/time | Contributor | Updates |
|---|---|---|
| 23-Oct-2009 03:05 | Ruthyruth | Added |
| 29-Jun-2016 22:30 | Dr.John Smith | Updated [Time, Registration, Cn, Location, Departure airport, Destination airport, Source, Damage, Narrative] |
Corrections or additions? ... Edit this accident description
The Aviation Safety Network is an exclusive service provided by:
Quick Links:
| ASN Home | Send Correction / Feedback |
| FSF Home | Disclaimer | Copyright |
| Contact Us | Privacy Policy |
| Press / Media |
CONNECT WITH US:
©2024 Flight Safety Foundation