Narrative:

I was working ground control east/west combined for approximately an hour. The traffic level and complexity were both extremely low. I had only one aircraft on my frequency which was air carrier X. Air carrier X called for taxi and I instructed him to taxi to runway 9L via K3 and kilo; which is pretty standard. Local control had more aircraft on frequency than I did. Local east instructed air carrier Y to cross runway 9L at november; again which is standard. Taxiway november and kilo intersect so basically if there are two aircraft one must give way. According to the ground control SOP; the local controller is responsible to give way to ground traffic unless coordinated. There was no coordination done so I expected the local controller to give way; which he did not. Air carrier Y stopped short of kilo because he noticed air carrier X was not stopping. Air carrier Z was then cleared for takeoff because the local controller believed that air carrier Y was clear of the runway. The issue of air carrier Y and air carrier Z was not brought to anyone's attention until the pilot called the tower and was furious about air carrier X cutting him off and air carrier Z departing runway 9L. He explained that air carrier X cut him off from kilo and he had to stop; and when the aircraft on the runway started takeoff roll he had to move forward to clear the hold line. Coordination; coordination; coordination. It was the local controller's responsibility to either give way to the taxiing aircraft or coordinate the ground controller to give way. If this would have happened; the crossing aircraft (air carrier Y) would not have been impeded on his way back to the gate; thus preventing the possible runway separation error.

Related reports:

Google
 

Original NASA ASRS Text

Title: PHL Controller described a conflict event between traffic exiting the runway and traffic taxiing for departure. The reporter indicates that local SOP's were not followed leading to the event.

Narrative: I was working Ground Control East/West combined for approximately an hour. The traffic level and complexity were both extremely low. I had only one aircraft on my frequency which was Air Carrier X. Air Carrier X called for taxi and I instructed him to taxi to Runway 9L via K3 and Kilo; which is pretty standard. Local Control had more aircraft on frequency than I did. Local East instructed Air Carrier Y to cross Runway 9L at November; again which is standard. Taxiway November and Kilo intersect so basically if there are two aircraft one must give way. According to the Ground Control SOP; the Local Controller is responsible to give way to ground traffic unless coordinated. There was no coordination done so I expected the Local Controller to give way; which he did not. Air Carrier Y stopped short of Kilo because he noticed Air Carrier X was not stopping. Air Carrier Z was then cleared for takeoff because the Local Controller believed that Air Carrier Y was clear of the runway. The issue of Air Carrier Y and Air Carrier Z was not brought to anyone's attention until the pilot called the Tower and was furious about Air Carrier X cutting him off and Air Carrier Z departing Runway 9L. He explained that Air Carrier X cut him off from Kilo and he had to stop; and when the aircraft on the runway started takeoff roll he had to move forward to clear the hold line. Coordination; coordination; coordination. It was the Local Controller's responsibility to either give way to the taxiing aircraft or coordinate the Ground Controller to give way. If this would have happened; the crossing aircraft (Air Carrier Y) would not have been impeded on his way back to the gate; thus preventing the possible runway separation error.

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.