Slc ground controller described runway incursion event; indicating instructions issued were not in a...

Narrative:

I was working the ground control east position. Due to the weather and runway use plan we were departing all turn departures off of runway 16R. I issued taxi instructions to aircraft Y to taxi via K; hold short runway 17 at K5. The read back was full and correct. I then was scanning the east side taxiways trying to pick the aircraft up visually. I then noticed an asde-X target moving towards the runway at K2 without a data block. I went over to the local east controller; and pointed out the aircraft; who then canceled the takeoff clearance of aircraft X that was on departure roll. I issued instructions for the aircraft Y to exit the runway; which he did. He then complied with all other instructions and departed without incident. Recommendation; issued phraseology not in accordance with the 7110.65. I issued 'taxi via K hold short runway 17 at K5 and expect runway 16R for departure'. I did this because I have issued the instruction per the 7110.65 and had numerous problems in this same area; including several runway incursions. I was intending to give this aircraft progressive instructions. I believe that in circumstances such as this that there needs to some latitude for ground controllers to use more effective phraseology when controlling aircraft near trouble spots.

Original NASA ASRS Text

Title: SLC Ground Controller described runway incursion event; indicating instructions issued were not in accordance with 7110.65; reporter claiming use of 7110.65 phraseology has contributed to past incursion mishaps.

Narrative: I was working the Ground Control East position. Due to the weather and runway use plan we were departing all turn departures off of Runway 16R. I issued taxi instructions to Aircraft Y to taxi via K; hold short Runway 17 at K5. The read back was full and correct. I then was scanning the east side taxiways trying to pick the aircraft up visually. I then noticed an ASDE-X target moving towards the runway at K2 without a Data Block. I went over to the Local East Controller; and pointed out the aircraft; who then canceled the takeoff clearance of Aircraft X that was on departure roll. I issued instructions for the Aircraft Y to exit the runway; which he did. He then complied with all other instructions and departed without incident. Recommendation; issued phraseology not in accordance with the 7110.65. I issued 'taxi via K hold short Runway 17 at K5 and expect Runway 16R for departure'. I did this because I have issued the instruction per the 7110.65 and had numerous problems in this same area; including several runway incursions. I was intending to give this aircraft progressive instructions. I believe that in circumstances such as this that there needs to some latitude for ground controllers to use more effective phraseology when controlling aircraft near trouble spots.

Data retrieved from NASA's ASRS site as of April 2012 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.

Attributes
ACN	873699
Time
Date	201002
Local Time Of Day	1801-2400
Place
Locale Reference	SLC.Tower
State Reference	UT
Aircraft 1
Make Model Name	Small Transport Low Wing 2 Turbojet Eng
Operating Under FAR Part	Part 91
Flight Phase	Takeoff
Flight Plan	IFR
Aircraft 2
Make Model Name	Small Transport Low Wing 2 Turboprop Eng
Operating Under FAR Part	Part 91
Flight Phase	Taxi
Flight Plan	IFR
Person 1
Function	Local
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Conflict Ground Conflict Less Severe Deviation - Procedural Clearance Ground Incursion Runway

Slc ground controller described runway incursion event; indicating instructions issued were not in accordance with 7110.65; reporter claiming use of 7110.65 phraseology has contributed to past incursion mishaps.