37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1281089 |
Time | |
Date | 201507 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ATL.Airport |
State Reference | GA |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Large Transport |
Operating Under FAR Part | Part 121 |
Flight Phase | Taxi |
Route In Use | None |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Large Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Takeoff |
Flight Plan | IFR |
Person 1 | |
Function | Local |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 7.5 |
Events | |
Anomaly | ATC Issue All Types Conflict Ground Conflict Less Severe Deviation - Procedural Clearance Ground Incursion Runway |
Narrative:
While working local control-3; I started crossing after an aircraft departed. I crossed one at south; N5; and T. I then crossed 2 at P. I scanned the runway and observed aircraft clear at all intersections but failed to notice the 2nd aircraft at P had not yet entered the runway. Aircraft Y was about 1000 feet down runway 27R when aircraft X called me and said he had not yet crossed the runway when I cleared aircraft Y for takeoff. I evaluated his position; which did not appear to be past the hold lines and aircraft Y was already passing through 60 kts according to the asde. I told aircraft X to hold position and allowed aircraft Y to continue departure roll. Once airborne I crossed aircraft X first and then proceeded to cross all remaining aircraft at the other intersections. I can't recall how I messed this up. I don't know if aircraft X was slow to taxi or how I didn't account for the second aircraft at P.always use procedures and patterns. I should have only crossed one at P to be consistent with the other intersections. I should be more aware of aircraft that taxi very slowly to make sure they don't get lost in the pack.
Original NASA ASRS Text
Title: ATL Tower Controller reported of crossing two aircraft and then doing other duties. Controller then cleared an aircraft for takeoff; second crossing traffic advised Controller they have not crossed yet. Controller had crossing aircraft hold short of runway allowing departing aircraft to get airborne. Controller thought the second crossing aircraft was slow in its taxi and that is why they forgot about it.
Narrative: While working LC-3; I started crossing after an aircraft departed. I crossed one at S; N5; and T. I then crossed 2 at P. I scanned the runway and observed aircraft clear at all intersections but failed to notice the 2nd aircraft at P had not yet entered the runway. Aircraft Y was about 1000 feet down RWY 27R when Aircraft X called me and said he had not yet crossed the RWY when I cleared Aircraft Y for takeoff. I evaluated his position; which did not appear to be past the hold lines and Aircraft Y was already passing through 60 kts according to the ASDE. I told Aircraft X to hold position and allowed Aircraft Y to continue departure roll. Once airborne I crossed Aircraft X first and then proceeded to cross all remaining aircraft at the other intersections. I can't recall how I messed this up. I don't know if Aircraft X was slow to taxi or how I didn't account for the second aircraft at P.Always use procedures and patterns. I should have only crossed one at P to be consistent with the other intersections. I should be more aware of aircraft that taxi very slowly to make sure they don't get lost in the pack.
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.