 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Tower controller described a very late go-around instruction noting his/her lack of timely instructions.
| Attributes | |
| ACN | 1102552 |
| Time | |
| Date | 201307 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZZZ.Airport |
| State Reference | US |
| Aircraft 1 | |
| Make Model Name | A319 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Landing |
| Route In Use | Visual Approach |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | A320 |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Landing |
| Flight Plan | IFR |
| Person 1 | |
| Function | Supervisor / CIC |
| Qualification | Air Traffic Control Fully Certified |
| Person 2 | |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types |
Narrative:
While working LC3/4 combined at LC4; I had two crj's land runway xxr and exit at taxiway xx. An A319 then landed runway xxr and was rolling out towards the second high speed exit; taxiway xy. I informed the A319 that company traffic was on short final. I then attempted to stop the second crj short of taxiway dy so that the A319 could exit the runway unimpeded. While talking to the crj; I realized that the A319 was not going to be off the runway in time and sent the A320 around. At the time I sent the A320 around; the aircraft was crossing the runway threshold. I then gave the A320 runway heading; a climb to 9 thousand; and handed him off the appropriate departure sector. In the future; I will give priority to the possible go-around situations and initiate the missed approach much sooner (before the landing threshold; when it is obvious that the operation will not work). It is also critical to 'paint a picture for each aircraft involved.' advising the preceding aircraft to plan the first high speed exit and minimal time on the runway for traffic close in trail; and ensuring that the trail aircraft knows of the distance between the preceding aircraft and any speed overtakes.
Original NASA ASRS Text
Title: Tower Controller described a very late go-around instruction noting his/her lack of timely instructions.
Narrative: While working LC3/4 combined at LC4; I had two CRJ's land Runway XXR and exit at Taxiway XX. An A319 then landed Runway XXR and was rolling out towards the second high speed exit; Taxiway XY. I informed the A319 that company traffic was on short final. I then attempted to stop the second CRJ short of Taxiway DY so that the A319 could exit the runway unimpeded. While talking to the CRJ; I realized that the A319 was not going to be off the runway in time and sent the A320 around. At the time I sent the A320 around; the aircraft was crossing the runway threshold. I then gave the A320 runway heading; a climb to 9 thousand; and handed him off the appropriate departure sector. In the future; I will give priority to the possible go-around situations and initiate the missed approach much sooner (before the landing threshold; when it is obvious that the operation will not work). It is also critical to 'paint a picture for each aircraft involved.' Advising the preceding aircraft to plan the first high speed exit and minimal time on the runway for traffic close in trail; and ensuring that the trail aircraft knows of the distance between the preceding aircraft and any speed overtakes.
Data retrieved from NASA's ASRS site as of July 2013 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.