A king air flight crew taxies the wrong way and creates a runway incursion at phl, PA.

Attributes
ACN	514213
Time
Date	200106
Day	Mon
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : phl.airport
State Reference	PA
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air taxi
Make Model Name	Super King Air 200 HDC
Operating Under FAR Part	Part 135
Flight Phase	ground : taxi
Flight Plan	IFR
Person 1
Affiliation	company : air taxi
Function	flight crew : captain oversight : pic
Qualification	pilot : atp pilot : instrument pilot : multi engine pilot : cfi
Experience	flight time last 90 days : 120 flight time total : 4500 flight time type : 2500
ASRS Report	514213
Person 2
Affiliation	company : air taxi
Function	flight crew : first officer
Events
Anomaly	incursion : taxiway non adherence : clearance non adherence : far
Resolutory Action	none taken : detected after the fact
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Flight Crew Human Performance ATC Human Performance
Primary Problem	Flight Crew Human Performance

Narrative:

On a part 135 flight at a major airport, the copilot received taxi instructions. The ground controller was very busy and issued instructions very fast. I (captain) assumed he (copilot) understood the clearance. At the first intersection, we turned left. I asked the copilot if we were cleared across a runway (at the time active, but not in use). He said 'yes' so we proceeded across the end of the runway. At this point the ground controller stopped us and stated that we had 'blown' our taxi clearance. We were reissued taxi instructions and told to call ATC upon arrival at our destination since we crossed a runway. I knew from the original instructions that we were to hold short of a different runway, which we did. However, the route which we thought we were supposed to take across a different runway, which we were not told to hold short of. Due to the heavy traffic, the controller issued instructions quickly. We as a crew should have queried and made sure we understood clearly the taxi instructions, which we did not. The controller could have been clrer and be a little slower in delivering his instructions. I, as captain, should have not crossed a runway unless I was absolutely sure that I was cleared to do so. After calling ATC and discussing the matter, no further action was taken.

Original NASA ASRS Text

Title: A KING AIR FLC TAXIES THE WRONG WAY AND CREATES A RWY INCURSION AT PHL, PA.

Narrative: ON A PART 135 FLT AT A MAJOR ARPT, THE COPLT RECEIVED TAXI INSTRUCTIONS. THE GND CTLR WAS VERY BUSY AND ISSUED INSTRUCTIONS VERY FAST. I (CAPT) ASSUMED HE (COPLT) UNDERSTOOD THE CLRNC. AT THE FIRST INTXN, WE TURNED L. I ASKED THE COPLT IF WE WERE CLRED ACROSS A RWY (AT THE TIME ACTIVE, BUT NOT IN USE). HE SAID 'YES' SO WE PROCEEDED ACROSS THE END OF THE RWY. AT THIS POINT THE GND CTLR STOPPED US AND STATED THAT WE HAD 'BLOWN' OUR TAXI CLRNC. WE WERE REISSUED TAXI INSTRUCTIONS AND TOLD TO CALL ATC UPON ARR AT OUR DEST SINCE WE CROSSED A RWY. I KNEW FROM THE ORIGINAL INSTRUCTIONS THAT WE WERE TO HOLD SHORT OF A DIFFERENT RWY, WHICH WE DID. HOWEVER, THE RTE WHICH WE THOUGHT WE WERE SUPPOSED TO TAKE ACROSS A DIFFERENT RWY, WHICH WE WERE NOT TOLD TO HOLD SHORT OF. DUE TO THE HVY TFC, THE CTLR ISSUED INSTRUCTIONS QUICKLY. WE AS A CREW SHOULD HAVE QUERIED AND MADE SURE WE UNDERSTOOD CLRLY THE TAXI INSTRUCTIONS, WHICH WE DID NOT. THE CTLR COULD HAVE BEEN CLRER AND BE A LITTLE SLOWER IN DELIVERING HIS INSTRUCTIONS. I, AS CAPT, SHOULD HAVE NOT CROSSED A RWY UNLESS I WAS ABSOLUTELY SURE THAT I WAS CLRED TO DO SO. AFTER CALLING ATC AND DISCUSSING THE MATTER, NO FURTHER ACTION WAS TAKEN.

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.