B737 flight crew during taxi has a runway incursion at phl.

Attributes
ACN	688637
Time
Date	200602
Local Time Of Day	1201 To 1800
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 carrier
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	ground : taxi
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : flight engineer pilot : instrument pilot : multi engine pilot : atp pilot : commercial
Experience	flight time last 90 days : 25 flight time total : 18000 flight time type : 2000
ASRS Report	688637
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 150 flight time total : 18000 flight time type : 11000
ASRS Report	689050
Events
Anomaly	incursion : runway non adherence : clearance
Independent Detector	other controllerb
Resolutory Action	controller : issued new clearance
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Flight Crew Human Performance ATC Human Performance Airport
Primary Problem	Flight Crew Human Performance

Narrative:

We called ground control and understood we were cleared to cross runway 27R; taxiway north; to runway 27L and this is what the first officer read back. No response from ground so we crossed runway 27R; noticed an aircraft in position for takeoff but no calls or correction from ground. Apparently; the ground controller wanted us to turn left on taxiway K and taxi for takeoff to runway 27R. When we realized there had been a miscom we advised the ground controller we had taxied as we read back and after some checking he advised he had missed readback and as to our question of do we need to write a report; he said 'no harm; no foul.' this still could have been a more serious incident and it reminds me to 'slow down' and ensure by all means possible that what I heard was what was said and meant. Supplemental information from acn 689050: contacted ground control on spot 8. I am not sure what he really said; but what I heard and what I read back was 'taxiway K; taxiway north; cross the right side and contact tower.' after crossing runway 27R; we were informed that we were not cleared to cross runway 27R because that was the departure runway.

Original NASA ASRS Text

Title: B737 FLT CREW DURING TAXI HAS A RWY INCURSION AT PHL.

Narrative: WE CALLED GND CTL AND UNDERSTOOD WE WERE CLRED TO CROSS RWY 27R; TXWY N; TO RWY 27L AND THIS IS WHAT THE FO READ BACK. NO RESPONSE FROM GND SO WE CROSSED RWY 27R; NOTICED AN ACFT IN POS FOR TKOF BUT NO CALLS OR CORRECTION FROM GND. APPARENTLY; THE GND CTLR WANTED US TO TURN L ON TXWY K AND TAXI FOR TKOF TO RWY 27R. WHEN WE REALIZED THERE HAD BEEN A MISCOM WE ADVISED THE GND CTLR WE HAD TAXIED AS WE READ BACK AND AFTER SOME CHKING HE ADVISED HE HAD MISSED READBACK AND AS TO OUR QUESTION OF DO WE NEED TO WRITE A RPT; HE SAID 'NO HARM; NO FOUL.' THIS STILL COULD HAVE BEEN A MORE SERIOUS INCIDENT AND IT REMINDS ME TO 'SLOW DOWN' AND ENSURE BY ALL MEANS POSSIBLE THAT WHAT I HEARD WAS WHAT WAS SAID AND MEANT. SUPPLEMENTAL INFO FROM ACN 689050: CONTACTED GND CTL ON SPOT 8. I AM NOT SURE WHAT HE REALLY SAID; BUT WHAT I HEARD AND WHAT I READ BACK WAS 'TXWY K; TXWY N; CROSS THE R SIDE AND CONTACT TWR.' AFTER XING RWY 27R; WE WERE INFORMED THAT WE WERE NOT CLRED TO CROSS RWY 27R BECAUSE THAT WAS THE DEP RWY.

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