Ground controller reported a runway incursion event during multiple emergency events when he failed ...

Narrative:

I was working ground control. We received a call that a helicopter declared an emergency about 10 miles southwest of the field and was making a straight approach to runway 4 to get on the ground as soon as possible. After the aircraft touched down; runway 4/22 was closed due to the disabled aircraft and airport operations and arff vehicles responded to the aircraft. Aircraft X called for taxi instructions. He was issued his squawk code and instructed to taxi to runway 18L and to cross runway 9 and hold short runway 18L. At the same time; another aircraft was inbound with an emergency; an aircraft without any hydraulic power and I was trying to coordinate with another arff vehicle holding short of runway 18L. Other aircraft were calling for taxiing instructions and clearances; as well as flight data and controller in charge relaying information to me about the emergencies. As I was talking to the arff vehicle; an aircraft X crossed runway 18L without clearance and local controller had to send another aircraft around. After trying to call the aircraft X prior to going onto the actual runway and then again after he got off; he responded. After listening to the tapes; it was evident that the aircraft X did read back the appropriate taxi instructions but never used his call sign. Even with the circumstances that were occurring with 2 emergencies and runway closures and all vehicles trying to coordinate and request to assist; as well as other aircraft calling; it is no excuse to miss a read back instruction. Once I read the taxi instruction to the aircraft X; I should have kept my focus in hearing the read back instead of getting side-tracked with other requests and coordination. I will work harder to make sure the aircraft does use the call sign when reading back hold short instructions a little more closely and this won't happen again.

Original NASA ASRS Text

Title: Ground Controller reported a runway incursion event during multiple emergency events when he failed to use proper phraseology/procedures with a read back.

Narrative: I was working Ground Control. We received a call that a helicopter declared an emergency about 10 miles southwest of the field and was making a straight approach to Runway 4 to get on the ground ASAP. After the aircraft touched down; Runway 4/22 was closed due to the disabled aircraft and Airport Operations and ARFF vehicles responded to the aircraft. Aircraft X called for taxi instructions. He was issued his squawk code and instructed to taxi to Runway 18L and to cross Runway 9 and hold short Runway 18L. At the same time; another aircraft was inbound with an emergency; an aircraft without any hydraulic power and I was trying to coordinate with another ARFF vehicle holding short of Runway 18L. Other aircraft were calling for taxiing instructions and clearances; as well as Flight Data and CIC relaying information to me about the emergencies. As I was talking to the ARFF vehicle; an Aircraft X crossed Runway 18L without clearance and Local Controller had to send another aircraft around. After trying to call the Aircraft X prior to going onto the actual runway and then again after he got off; he responded. After listening to the tapes; it was evident that the Aircraft X did read back the appropriate taxi instructions but never used his call sign. Even with the circumstances that were occurring with 2 emergencies and runway closures and all vehicles trying to coordinate and request to assist; as well as other aircraft calling; it is no excuse to miss a read back instruction. Once I read the taxi instruction to the Aircraft X; I should have kept my focus in hearing the read back instead of getting side-tracked with other requests and coordination. I will work harder to make sure the aircraft does use the call sign when reading back hold short instructions a little more closely and this won't happen again.

Data retrieved from NASA's ASRS site as of July 2013 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	1040210
Time
Date	201210
Local Time Of Day	1201-1800
Place
Locale Reference	ZZZ.Airport
State Reference	US
Aircraft 1
Make Model Name	Small Aircraft Low Wing 2 Eng Retractable Gear
Operating Under FAR Part	Part 91
Flight Phase	Taxi
Route In Use	None
Flight Plan	VFR
Person 1
Function	Ground
Qualification	Air Traffic Control Developmental
Events
Anomaly	ATC Issue All Types Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Ground Incursion Runway

Ground controller reported a runway incursion event during multiple emergency events when he failed to use proper phraseology/procedures with a read back.