Regional Jet 200 ER/LR (CRJ200)
Air Traffic Control Fully Certified
Other / Unknown; Situational Awareness
ATC Issue All Types; Conflict Ground Conflict; Critical; Deviation / Discrepancy - Procedural Published Material / Policy
Air Traffic Control Issued New Clearance; Flight Crew Executed Go Around / Missed Approach
Airport; Human Factors; Procedure
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].
On arrival to PHL we were asked if we could accept Runway 26 instead of 27R. We had already run the numbers and accepted the visual approach to Runway 26. After landing we were instructed to turn left on Taxiway Delta and hold short of Runway 27R for landing traffic. I should add that this instruction was a change from our original instructions after exiting [Runway] 26; but I don't recall the instructions anymore. After the landing traffic we were instructed to taxi onto Runway 27R; cross Runway 35; and after some indecision by the Controller; instructed to exit at Lima. Traffic was on a 4 mile final and we were asked to expedite. Captain expedited onto and down the runway as I looked at the airport diagram to find Lima. As we were passing the intersection of 27R/35 we heard someone call out 'traffic on runway; going around'. The Captain and I looked out the left side window and saw another CRJ executing a balked landing maneuver on Runway 35. It appeared to be 100 to 200 FT above the runway. We were just past the intersection at this time and I don't believe a collision would have occurred had the other aircraft landed; but it might have been close. We then continued to and exited at Taxiway Lima. The other crew made the right choice in going around. Throughout this occurrence I don't recall hearing any communications between ATC and the traffic landing on [Runway] 35; but probably was focusing on the inbound traffic to [Runway] 27R and the jumbled instructions from the Controller. ATC advised us of traffic landing on [Runway] 27R; but did not advise us of traffic landing on [Runway] 35. Being in a hurry and trying to help ATC we failed to check for any traffic landing on [Runway] 35. Thankfully the other crew broke the chain of events that could have led to an accident.I feel that the Controller had a high workload at the time; and our having to go to a west gate confused the matter. I don't think he realized we weren't going to Terminal [X]. His instructions for taxi after landing were changed several times. He also did not advise us of traffic landing on Runway 35. The obvious suggestion; and failure on our part; is to always check for traffic to the left and right of any runway or taxiway to be crossed; and verify each direction is clear of other aircraft; vehicle or ramp equipment.
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.