Controller described a runway separation event when traffic was instructed to turn onto taxiway B re...

Narrative:

Event occurred during a training session where I was the trainer. Aircraft 1 landed on runway xx and was incorrectly instructed by my trainee to make a left turn onto taxiway right and contact ground control. The pilot turned left as instructed but onto taxiway B; as right would have been a right turn; held short of runway yy and contacted ground control as he was told. This left the aircraft still inside the safety area of runway xx with another arrival on short final. By the time ground control switched the pilot back onto local's frequency; and my trainee was able to issue instructions to cross runway yy; the next arrival had already touched down on runway xx; creating a loss of runway separation. The aircraft did not physically touch each other; as aircraft 1 was well on its way across runway yy by the time the next arrival got to taxiway B; and neither pilot made any comments on the frequency. At the time of the incident my attention as a trainer had been focused on initiating a hand off and some necessary coordination with our neighboring facility that the trainee had failed to perform. By the time I had completed the coordination; and realized what was happening; the arrival had already touched down; there was no time to initiate a go-around. This is a fairly common event at this airport; and I understand that there are already plans to move taxiway B further north where it would be long enough to allow an aircraft to be clear of both runways at the same time. As far as my distractions operating the radar; I'll say that there are times when the local controller has to work not only the runways but also perform several other tasks related to aircraft operating within the class D airspace such as initiating and accepting hand offs; setting up and fixing radar tag information (destination/type); traffic calls and point outs to adjacent facilities. This does not usually present a problem; but there are a few times when the VFR helicopter/fixed wing workload spikes; and it can be a challenge to keep everything under control.

Original NASA ASRS Text

Title: Controller described a runway separation event when traffic was instructed to turn onto Taxiway B resulting in less than required separation because of the runway safety areas.

Narrative: Event occurred during a training session where I was the trainer. Aircraft 1 landed on Runway XX and was incorrectly instructed by my trainee to make a left turn onto Taxiway R and contact Ground Control. The pilot turned left as instructed but onto Taxiway B; as R would have been a right turn; held short of Runway YY and contacted Ground Control as he was told. This left the aircraft still inside the safety area of Runway XX with another arrival on short final. By the time Ground Control switched the pilot back onto Local's frequency; and my trainee was able to issue instructions to cross Runway YY; the next arrival had already touched down on Runway XX; creating a loss of runway separation. The aircraft did not physically touch each other; as Aircraft 1 was well on its way across Runway YY by the time the next arrival got to Taxiway B; and neither pilot made any comments on the frequency. At the time of the incident my attention as a trainer had been focused on initiating a hand off and some necessary coordination with our neighboring facility that the trainee had failed to perform. By the time I had completed the coordination; and realized what was happening; the arrival had already touched down; there was no time to initiate a go-around. This is a fairly common event at this airport; and I understand that there are already plans to move Taxiway B further north where it would be long enough to allow an aircraft to be clear of both runways at the same time. As far as my distractions operating the RADAR; I'll say that there are times when the Local Controller has to work not only the runways but also perform several other tasks related to aircraft operating within the Class D airspace such as initiating and accepting hand offs; setting up and fixing RADAR tag information (destination/type); traffic calls and point outs to adjacent facilities. This does not usually present a problem; but there are a few times when the VFR helicopter/fixed wing workload spikes; and it can be a challenge to keep everything under control.

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	977455
Time
Date	201111
Local Time Of Day	1801-2400
Place
Locale Reference	ZZZ.Airport
State Reference	US
Aircraft 1
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	Taxi
Flight Plan	IFR
Aircraft 2
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Phase	Landing
Person 1
Function	Local
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Conflict Ground Conflict Less Severe Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance

Controller described a runway separation event when traffic was instructed to turn onto taxiway B resulting in less than required separation because of the runway safety areas.