Narrative:

Received taxi clearance from FBO ramp. The clearance was taxi to runway 35 via taxiway a, right turn on taxiway D, taxiway G, cross runway 35 and taxiway east. While on taxiway a, the controller asked us if we could accept an intersection K departure. While checking runway length and reprogramming the FMS computers, we continued taxi. We then proceeded to turn left on taxiway D and proceeded to the taxiway K/runway 35 intersection that was closest to our present position. Proceeded on taxiway D which is depicted on the commercial phl chart as not intersecting runway 26, but depicting as its own taxiway. The runway 26 markings are very vague as to whether this is a portion of the runway or just taxiway. The controller told us to hold our position as we approached taxiway H. The controller then told us that we turned the wrong way. We informed him that we could not accept the intersection departure. He told us to continue taxiing on taxiway D, turn right on taxiway K, cross runway 35, turn left on taxiway east and hold short of runway 27R. We taxied as cleared, then were cleared to cross runway 27R and taxi full length to runway 35. The captain called back to the tower after the flight to discuss whether this was a runway/taxi infraction and was told by the supervisor that this is a common problem in that area of the taxiway and that they are aware of the problem. The taxi route is very confusing. Contributing factors: distrs arose from checking runway length requirements for requested (controller) intersection departure. The assigned taxi clearance requires taxiing the opposite direction from where they wanted us to do the intersection departure.

Related reports:

Google
 

Original NASA ASRS Text

Title: FLC OF A CPR LARGE TWIN EXECUTIVE JET USED THE WRONG TXWY WHILE TAXIING OUT FOR TKOF, CAUSING NOT ONLY A TXWY INCURSION, BUT ALSO A RWY INCURSION WHICH MARKINGS WERE FADED AND INDISTINGUISHABLE.

Narrative: RECEIVED TAXI CLRNC FROM FBO RAMP. THE CLRNC WAS TAXI TO RWY 35 VIA TXWY A, R TURN ON TXWY D, TXWY G, CROSS RWY 35 AND TXWY E. WHILE ON TXWY A, THE CTLR ASKED US IF WE COULD ACCEPT AN INTXN K DEP. WHILE CHKING RWY LENGTH AND REPROGRAMMING THE FMS COMPUTERS, WE CONTINUED TAXI. WE THEN PROCEEDED TO TURN L ON TXWY D AND PROCEEDED TO THE TXWY K/RWY 35 INTXN THAT WAS CLOSEST TO OUR PRESENT POS. PROCEEDED ON TXWY D WHICH IS DEPICTED ON THE COMMERCIAL PHL CHART AS NOT INTERSECTING RWY 26, BUT DEPICTING AS ITS OWN TXWY. THE RWY 26 MARKINGS ARE VERY VAGUE AS TO WHETHER THIS IS A PORTION OF THE RWY OR JUST TXWY. THE CTLR TOLD US TO HOLD OUR POS AS WE APCHED TXWY H. THE CTLR THEN TOLD US THAT WE TURNED THE WRONG WAY. WE INFORMED HIM THAT WE COULD NOT ACCEPT THE INTXN DEP. HE TOLD US TO CONTINUE TAXIING ON TXWY D, TURN R ON TXWY K, CROSS RWY 35, TURN L ON TXWY E AND HOLD SHORT OF RWY 27R. WE TAXIED AS CLRED, THEN WERE CLRED TO CROSS RWY 27R AND TAXI FULL LENGTH TO RWY 35. THE CAPT CALLED BACK TO THE TWR AFTER THE FLT TO DISCUSS WHETHER THIS WAS A RWY/TAXI INFRACTION AND WAS TOLD BY THE SUPVR THAT THIS IS A COMMON PROB IN THAT AREA OF THE TXWY AND THAT THEY ARE AWARE OF THE PROB. THE TAXI RTE IS VERY CONFUSING. CONTRIBUTING FACTORS: DISTRS AROSE FROM CHKING RWY LENGTH REQUIREMENTS FOR REQUESTED (CTLR) INTXN DEP. THE ASSIGNED TAXI CLRNC REQUIRES TAXIING THE OPPOSITE DIRECTION FROM WHERE THEY WANTED US TO DO THE INTXN DEP.

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.