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: | Wednesday 29 November 2017 |
Time: | 12:06 LT |
Type: | Boeing 737-932ER |
Owner/operator: | Delta Air Lines |
Registration: | N852DN |
MSN: | 31963/5743 |
Year of manufacture: | 2016 |
Engine model: | CFM International CFM56-7B27E |
Fatalities: | Fatalities: 0 / Occupants: 169 |
Other fatalities: | 0 |
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: | Indianapolis International Airport, IN (IND/KIND) |
Destination airport: | Atlanta Hartsfield-Jackson International Airport, GA (ATL/KATL) |
Investigating agency: | NTSB |
Confidence Rating: | Accident investigation report completed and information captured |
Narrative:The flight crew was conducting an instrument landing system approach to runway 9R. When the airplane was about 3.5 miles from the runway threshold and at an altitude of about 1,230 ft above ground level (agl), the first officer (the pilot flying) disconnected the autopilot, after which the airplane began to deviate to the right of the localizer course. When the airplane was at an altitude of about 500 ft agl, the first officer disconnected the autothrottle; at 300 ft agl, he began correcting to the left to return to the center of the localizer course. When the airplane reached the decision altitude (200 ft agl), the airplane was drifting toward the taxiway N extended centerline, which was parallel to, and about 650 ft to the left of, the runway 9R centerline.
Radar data indicated that the airplane was 1 mile from the runway 9R threshold at the time that the airplane aligned with taxiway N. When the airplane was at an altitude of 120 ft agl and was 600 ft to the left of the runway 9R centerline and 50 ft to the right of the taxiway N centerline, the first officer initiated a go-around after the captain's (the monitoring pilot) command. The airplane descended to about 50 ft above the western end of the taxiway before it began to climb. Engine power increased while the airplane was above and aligned with taxiway N. The airplane was then vectored for an instrument landing system approach for runway 10. The flight crew subsequently landed the airplane uneventfully.
Another airplane (a Boeing MD-88) was taxiing westbound on taxiway N at the time of the incident approach. According to radar data, the airplanes, at their closest distances, were separated by 286 ft horizontally and 257 ft vertically.
The approach became unstabilized when the first officer improperly adjusted the airplane's heading and flew outside of the localizer course. The airline's procedures indicated that an approach would be considered to be stabilized if it maintained, among other things, a 'lateral flight path while in the landing configuration.â The manual warned that, if a stabilized approach could not be established and maintained, pilots were to initiate a go
Accident investigation:
|
| |
Investigating agency: | NTSB |
Report number: | DCA18IA026 |
Status: | Investigation completed |
Duration: | 4 years and 5 months |
Download report: | Final report |
|
Sources:
NTSB DCA18IA026
Location
Revision history:
Date/time | Contributor | Updates |
02-Jun-2023 14:19 |
ASN Update Bot |
Added |
The Aviation Safety Network is an exclusive service provided by:
CONNECT WITH US:
©2024 Flight Safety Foundation