Tower controller described a runway incursion event when an aircraft taxiing for departure entered t...

Narrative:

I was training a developmental on ground controller 1. We were on a runway xx/west operation. Complexity was slightly above average with this configuration. Aircraft X called for taxi to runway yyr. My trainee issued taxi instructions to 'aircraft X; runway yyr; taxi via alpha; november; hold short runway xx.' the pilot read back the taxi instructions and the hold short runway xx. As he started his taxi and got on november he did not appear to be slowing down to hold short. My trainee told the aircraft again to hold short. The pilot continued. I told the aircraft to stop. By the time the aircraft stopped the nose of the aircraft was over the runway. There was another aircraft departing at the time about 300 ft above the C550 when they crossed. After the session we stopped by the quality assurance office. They concurred that it was a pilot deviation; and we listened to the tapes hearing him read back the hold short. I was informed today that it is now considered an operational error because the pilot didn't use his call sign during the read back. I think this is stupid because they can't match a pilot's voice to the read back! They would do it if there was a loss of life. Instead I get the error and the pilot who almost kills somebody gets off 'scott free.' the new phraseology for ground has increased the complexity reference issuing instructions and hearing each read back. A lot of the phraseology is excessive. I believe short and simple is easier for the pilots and controllers.

Original NASA ASRS Text

Title: Tower Controller described a runway incursion event when an aircraft taxiing for departure entered the runway without authorization; the event later determined to be an ATC error because the pilot did not use call sign when confirming the hold short instruction.

Narrative: I was training a developmental on Ground Controller 1. We were on a Runway XX/west operation. Complexity was slightly above average with this configuration. Aircraft X called for taxi to Runway YYR. My trainee issued taxi instructions to 'Aircraft X; Runway YYR; taxi via Alpha; November; hold short Runway XX.' The pilot read back the taxi instructions and the hold short Runway XX. As he started his taxi and got on November he did not appear to be slowing down to hold short. My trainee told the aircraft again to hold short. The pilot continued. I told the aircraft to stop. By the time the aircraft stopped the nose of the aircraft was over the runway. There was another aircraft departing at the time about 300 FT above the C550 when they crossed. After the session we stopped by the Quality Assurance office. They concurred that it was a pilot deviation; and we listened to the tapes hearing him read back the hold short. I was informed today that it is now considered an operational error because the pilot didn't use his call sign during the read back. I think this is stupid because they can't match a pilot's voice to the read back! They would do it if there was a loss of life. Instead I get the error and the pilot who almost kills somebody gets off 'scott free.' The new phraseology for Ground has increased the complexity reference issuing instructions and hearing each read back. A lot of the phraseology is excessive. I believe short and simple is easier for the pilots and controllers.

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	928399
Time
Date	201101
Local Time Of Day	1201-1800
Place
Locale Reference	ZZZ.Airport
State Reference	US
Environment
Light	Daylight
Aircraft 1
Make Model Name	Citation II S2/Bravo (C550)
Flight Phase	Taxi
Flight Plan	IFR
Person 1
Function	Ground Local
Qualification	Air Traffic Control Fully Certified
Person 2
Function	Local Ground
Qualification	Air Traffic Control Developmental
Events
Anomaly	Deviation - Procedural Clearance Ground Incursion Runway

Tower controller described a runway incursion event when an aircraft taxiing for departure entered the runway without authorization; the event later determined to be an ATC error because the pilot did not use call sign when confirming the hold short instruction.