A phl tower controller and a CRJ200 first officer describe a conflict at the intersection of runway ...

Attributes
ACN	1099856
Time
Date	201307
Local Time Of Day	1801-2400
Place
Locale Reference	PHL.Airport
State Reference	PA
Aircraft 1
Make Model Name	Regional Jet 200 ER/LR (CRJ200)
Operating Under FAR Part	Part 121
Flight Phase	Taxi
Route In Use	None
Flight Plan	IFR
Aircraft 2
Make Model Name	Regional Jet 200 ER/LR (CRJ200)
Operating Under FAR Part	Part 121
Flight Phase	Landing
Route In Use	Visual Approach
Flight Plan	IFR
Person 1
Function	Local
Qualification	Air Traffic Control Fully Certified
Person 2
Function	Pilot Not Flying First Officer
Events
Anomaly	ATC Issue All Types Conflict Ground Conflict Critical Deviation - Procedural Published Material / Policy

Narrative:

I was on local east and I had to taxi ground traffic down a portion of my arrival runway between [runways] 27R and 35 arrivals (intersection) from taxiway delta to lima due to all other taxiways to the ramp being blocked or occupied. I prepped the traffic; thought I had enough time. It appeared the aircraft was going to be clear when a crj advised going around due to traffic on the runway. I then issued the go-around myself to include climbout instructions runway heading to maintain 3;000 ft. [The go-around was due to] the layout of the airfield; with lack of taxiways and staging of aircraft due to swap blocked access to the ramp. I was pretty much forced to taxi the aircraft down the runway because another aircraft was shut down on the main taxiway to the ramp during a busy departure push during a busy swap [strategic weather avoidance program].

Original NASA ASRS Text

Title: A PHL Tower Controller and a CRJ200 First Officer describe a conflict at the intersection of Runway 27R and Runway 35 requiring another CRJ landing Runway 35 to go around.

Narrative: I was on Local East and I had to taxi ground traffic down a portion of my arrival runway between [runways] 27R and 35 arrivals (intersection) from Taxiway Delta to Lima due to all other taxiways to the ramp being blocked or occupied. I prepped the traffic; thought I had enough time. It appeared the aircraft was going to be clear when a CRJ advised going around due to traffic on the runway. I then issued the go-around myself to include climbout instructions runway heading to maintain 3;000 FT. [The go-around was due to] the layout of the airfield; with lack of taxiways and staging of aircraft due to swap blocked access to the ramp. I was pretty much forced to taxi the aircraft down the runway because another aircraft was shut down on the main taxiway to the ramp during a busy departure push during a busy swap [strategic weather avoidance program].

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.

A phl tower controller and a CRJ200 first officer describe a conflict at the intersection of runway 27R and runway 35 requiring another crj landing runway 35 to go around.