Narrative:

Landed runway 28L, rolled out, was told to taxi on intersecting taxiway to hold short of runway 28R. As we were holding short, 1 arrival landed runway 28R, we were told to cross runway 28R no delay, contact ground after crossing. So, of course, as traffic was on 1/2 mi final and the captain made the decision to cross, he had to use a lot of power (speed) to cross. As he was looking to the right to see the proximity of the landing jet on runway 28R, an rj was taxiing on the parallel taxiway that we were told to join after crossing. In later conversation with tower chief, captain was told the jet was to have held for us. They said over the radio they slowed for a bump in the taxiway. Anyway, it was a near collision, captain taxiing quickly across runway 28R intersection ('no delay'), the jet being right there on the parallel taxiway, but the root of the problem is phl controllers being too aggressive with the runway 28L/right and runway 35 crossing thing. Always, we are spaced out too closely. They're always giving us speed restrs, ie, maximum forward or minimum practical (sometimes on the same approach!) and they aren't really sure if the spacing is going to work until you're on 1/2 mi final. ATC on a hunch -- and the same with ground -- too aggressive. We're professional pilots. We don't mind a 3 min delay for safety. We get paid block-to-block. Look into this problem at phl. Thanks. P.south. I don't have an airport diagram in front of me as I write this, you may call me for exact letters of the taxiway.

Google
 

Original NASA ASRS Text

Title: DHC8-102 CONFLICT ON GND AT PHL WITH CRJ65.

Narrative: LANDED RWY 28L, ROLLED OUT, WAS TOLD TO TAXI ON INTERSECTING TXWY TO HOLD SHORT OF RWY 28R. AS WE WERE HOLDING SHORT, 1 ARR LANDED RWY 28R, WE WERE TOLD TO CROSS RWY 28R NO DELAY, CONTACT GND AFTER XING. SO, OF COURSE, AS TFC WAS ON 1/2 MI FINAL AND THE CAPT MADE THE DECISION TO CROSS, HE HAD TO USE A LOT OF PWR (SPD) TO CROSS. AS HE WAS LOOKING TO THE R TO SEE THE PROX OF THE LNDG JET ON RWY 28R, AN RJ WAS TAXIING ON THE PARALLEL TXWY THAT WE WERE TOLD TO JOIN AFTER XING. IN LATER CONVERSATION WITH TWR CHIEF, CAPT WAS TOLD THE JET WAS TO HAVE HELD FOR US. THEY SAID OVER THE RADIO THEY SLOWED FOR A BUMP IN THE TXWY. ANYWAY, IT WAS A NEAR COLLISION, CAPT TAXIING QUICKLY ACROSS RWY 28R INTXN ('NO DELAY'), THE JET BEING RIGHT THERE ON THE PARALLEL TXWY, BUT THE ROOT OF THE PROB IS PHL CTLRS BEING TOO AGGRESSIVE WITH THE RWY 28L/R AND RWY 35 XING THING. ALWAYS, WE ARE SPACED OUT TOO CLOSELY. THEY'RE ALWAYS GIVING US SPD RESTRS, IE, MAX FORWARD OR MINIMUM PRACTICAL (SOMETIMES ON THE SAME APCH!) AND THEY AREN'T REALLY SURE IF THE SPACING IS GOING TO WORK UNTIL YOU'RE ON 1/2 MI FINAL. ATC ON A HUNCH -- AND THE SAME WITH GND -- TOO AGGRESSIVE. WE'RE PROFESSIONAL PLTS. WE DON'T MIND A 3 MIN DELAY FOR SAFETY. WE GET PAID BLOCK-TO-BLOCK. LOOK INTO THIS PROB AT PHL. THANKS. P.S. I DON'T HAVE AN ARPT DIAGRAM IN FRONT OF ME AS I WRITE THIS, YOU MAY CALL ME FOR EXACT LETTERS OF THE TXWY.

Data retrieved from NASA's ASRS site as of July 2007 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.