37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1398021 |
Time | |
Date | 201610 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | GEG.Tower |
State Reference | WA |
Environment | |
Flight Conditions | VMC |
Light | Dawn |
Aircraft 1 | |
Make Model Name | Large Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Takeoff |
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 | Taxi |
Flight Plan | IFR |
Person 1 | |
Function | Local Ground Flight Data / Clearance Delivery Supervisor / CIC |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (mon) 6 |
Events | |
Anomaly | ATC Issue All Types Conflict Ground Conflict Critical Deviation - Procedural Published Material / Policy |
Narrative:
I was working flight data; ground control; local control and controller in charge combined. Runway 3 and taxiway a were not visible from the tower. I had multiple aircraft requesting taxi at the same time. Aircraft X was cleared for takeoff on runway 3. There was an aircraft taxiing to runway 3 followed by aircraft Z who reported aircraft a in sight. I told aircraft Z to report passing taxiway T7. Aircraft Y called to taxi and I meant to ask them if they had aircraft Z in sight but instead read aircraft X's call sign. Aircraft X said they did not have aircraft Z in sight and I said to hold position; still thinking I was talking to aircraft Y. Aircraft X said they were canceling their takeoff and exiting at taxiway A5. Aircraft X said they were behind aircraft a on taxiway a. I then verified aircraft a was number one; followed by aircraft X; aircraft Z; and then aircraft Y. This was an error on my part for reading the wrong call sign. I think I looked at aircraft X's strip as I was trying to talk to aircraft Y instead.
Original NASA ASRS Text
Title: GEG Tower Controller working all Tower positions combined instructed an aircraft to hold its position. The Controller meant to issue the instruction to a taxiing aircraft; but mistakenly issued it to an aircraft beginning its takeoff roll.
Narrative: I was working Flight Data; Ground Control; Local Control and Controller in Charge combined. Runway 3 and Taxiway A were not visible from the tower. I had multiple aircraft requesting taxi at the same time. Aircraft X was cleared for takeoff on Runway 3. There was an aircraft taxiing to Runway 3 followed by Aircraft Z who reported Aircraft A in sight. I told Aircraft Z to report passing taxiway T7. Aircraft Y called to taxi and I meant to ask them if they had Aircraft Z in sight but instead read Aircraft X's call sign. Aircraft X said they did not have Aircraft Z in sight and I said to hold position; still thinking I was talking to Aircraft Y. Aircraft X said they were canceling their takeoff and exiting at taxiway A5. Aircraft X said they were behind Aircraft A on taxiway A. I then verified Aircraft A was number one; followed by Aircraft X; Aircraft Z; and then Aircraft Y. This was an error on my part for reading the wrong call sign. I think I looked at Aircraft X's strip as I was trying to talk to Aircraft Y instead.
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.