|37000 Feet||Browse and search NASA's
Aviation Safety Reporting System
|Local Time Of Day||0601 To 1200|
|Locale Reference||airport : fll|
|Altitude||agl bound lower : 0|
agl bound upper : 0
|Operator||general aviation : personal|
|Make Model Name||Skyhawk 172/Cutlass 172|
|Operating Under FAR Part||Part 91|
|Flight Phase||climbout : takeoff|
|Affiliation||government : faa|
|Function||controller : ground|
controller : clearance delivery
controller : flight data
|Experience||controller non radar : 7|
|Affiliation||government : faa|
|Function||controller : local|
|Qualification||controller : non radar|
|Anomaly||conflict : ground less severe|
non adherence : required legal separation
|Independent Detector||other controllera|
|Resolutory Action||none taken : insufficient time|
|Miss Distance||horizontal : 1800|
vertical : 0
|Primary Problem||ATC Human Performance|
|Air Traffic Incident||Operational Error|
The problem arose while I was working ground control/FD/clearance delivery and controller in charge combined. I had 2 vehicles on frequency with similar call signs: maintenance X and admin X. Admin X was on the north side of runway 8 at the approach end of taxiway left in the vicinity of taxiway F. Maintenance X was at the approach end of runway 13 in the vicinity of taxiway F. I had talked to both vehicles prior to the event and was confused as to which vehicle was using which call sign. When maintenance X called and requested relocation from taxiway F and approach end of runway 13 to taxiway a and taxiway left I immediately focused on the vehicle at the approach end of runway 8 with the thought that he wanted to cross the runway and continue his work on the same taxiway on the other side of the runway. The fact that the vehicle said he was at the approach end of runway 13 escaped my attention. When I coordinated with local control to cross runway 8 at the approach end of runway 8 behind a touch and go cessna I did not expect and was very surprised when the other vehicle crossed farther down the runway approximately 1800 ft in front of the departing aircraft. Contributing factors were the similar call signs, the extra workload of working 4 combined position, and my confusion on the identify of the vehicles. Corrective action to be taken would be to change the call signs of one of the vehicles to be less confusing and to be sure of which vehicle is talking before issuing crossing clearance.
Original NASA ASRS Text
Title: RPTR WORKING 4 POS IN THE TWR INCLUDING GND CTL, CLRED THE WRONG VEHICLE TO CROSS A RWY WHEN A C172 WAS ON TKOF ROLL. 2 VEHICLES WERE ON GND CTL FREQ AND THE RPTR MISINTERPRETED WHICH VEHICLE CALLED AND AT WHAT LOCATION ON THE ARPT. LTSS OCCURRED.
Narrative: THE PROB AROSE WHILE I WAS WORKING GC/FD/CD AND CIC COMBINED. I HAD 2 VEHICLES ON FREQ WITH SIMILAR CALL SIGNS: MAINT X AND ADMIN X. ADMIN X WAS ON THE N SIDE OF RWY 8 AT THE APCH END OF TXWY L IN THE VICINITY OF TXWY F. MAINT X WAS AT THE APCH END OF RWY 13 IN THE VICINITY OF TXWY F. I HAD TALKED TO BOTH VEHICLES PRIOR TO THE EVENT AND WAS CONFUSED AS TO WHICH VEHICLE WAS USING WHICH CALL SIGN. WHEN MAINT X CALLED AND REQUESTED RELOCATION FROM TXWY F AND APCH END OF RWY 13 TO TXWY A AND TXWY L I IMMEDIATELY FOCUSED ON THE VEHICLE AT THE APCH END OF RWY 8 WITH THE THOUGHT THAT HE WANTED TO CROSS THE RWY AND CONTINUE HIS WORK ON THE SAME TXWY ON THE OTHER SIDE OF THE RWY. THE FACT THAT THE VEHICLE SAID HE WAS AT THE APCH END OF RWY 13 ESCAPED MY ATTN. WHEN I COORDINATED WITH LCL CTL TO CROSS RWY 8 AT THE APCH END OF RWY 8 BEHIND A TOUCH AND GO CESSNA I DID NOT EXPECT AND WAS VERY SURPRISED WHEN THE OTHER VEHICLE CROSSED FARTHER DOWN THE RWY APPROX 1800 FT IN FRONT OF THE DEPARTING ACFT. CONTRIBUTING FACTORS WERE THE SIMILAR CALL SIGNS, THE EXTRA WORKLOAD OF WORKING 4 COMBINED POS, AND MY CONFUSION ON THE IDENT OF THE VEHICLES. CORRECTIVE ACTION TO BE TAKEN WOULD BE TO CHANGE THE CALL SIGNS OF ONE OF THE VEHICLES TO BE LESS CONFUSING AND TO BE SURE OF WHICH VEHICLE IS TALKING BEFORE ISSUING XING CLRNC.
Data retrieved from NASA's ASRS site as of July 2007 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.