37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1487721 |
Time | |
Date | 201710 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | MEM.Airport |
State Reference | TN |
Environment | |
Flight Conditions | VMC |
Aircraft 1 | |
Make Model Name | Widebody Transport |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach |
Route In Use | Visual Approach |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Large Transport |
Operating Under FAR Part | Part 121 |
Flight Phase | Takeoff |
Route In Use | None |
Flight Plan | IFR |
Person 1 | |
Function | Local |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Ground Incursion Runway |
Narrative:
Aircraft Z was on a visual approach to runway 27; aircraft Y was ready to depart runway 36L; aircraft X was on a visual approach to runway 36L. Aircraft Z was asked to keep his speed up as much as possible. Aircraft X was told to continue and reduce to final approach speed. Aircraft Y was instructed to line up and wait and told about the traffic and when he could expect to depart. Aircraft X was also informed when to expect landing clearance. Once aircraft Z crossed the runway 27 threshold and touched down aircraft Y was cleared for takeoff. Aircraft Y was airborne about midfield when I observed aircraft X initiate a go-around. Aircraft X immediately started a left hand turn; but never verbally communicated a pilot initiated go-around. I instructed aircraft Y to fly runway heading and climb and maintain 5;000 feet so as not to conflict with aircraft X in the left turn. I then instructed aircraft X to turn left heading 270 and climb and maintain 3;000 feet.if I had not waited for aircraft Z to touch down and used the arrival departure window (adw) procedure more effectively aircraft Y would have been further down the runway thus possibly negating the need for aircraft X to initiate a go-around. Also; I could have just waited to depart aircraft Y.
Original NASA ASRS Text
Title: MEM Tower Local Controller reported they had to issue last minute instructions to separate an arriving aircraft which initiated a go-around just as a departure was airborne.
Narrative: Aircraft Z was on a visual approach to Runway 27; Aircraft Y was ready to depart Runway 36L; Aircraft X was on a visual approach to Runway 36L. Aircraft Z was asked to keep his speed up as much as possible. Aircraft X was told to continue and reduce to final approach speed. Aircraft Y was instructed to line up and wait and told about the traffic and when he could expect to depart. Aircraft X was also informed when to expect landing clearance. Once Aircraft Z crossed the Runway 27 threshold and touched down Aircraft Y was cleared for takeoff. Aircraft Y was airborne about midfield when I observed Aircraft X initiate a go-around. Aircraft X immediately started a left hand turn; but never verbally communicated a pilot initiated go-around. I instructed Aircraft Y to fly runway heading and climb and maintain 5;000 feet so as not to conflict with Aircraft X in the left turn. I then instructed Aircraft X to turn left heading 270 and climb and maintain 3;000 feet.If I had not waited for Aircraft Z to touch down and used the Arrival Departure Window (ADW) procedure more effectively Aircraft Y would have been further down the runway thus possibly negating the need for Aircraft X to initiate a go-around. Also; I could have just waited to depart Aircraft Y.
Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.