B737-300 flight crew has runway incursion at okc.

Attributes
ACN	554481
Time
Date	200207
Day	Tue
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : okc.airport
State Reference	OK
Altitude	agl single value : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : abq.tower
Operator	common carrier : air carrier
Make Model Name	B737 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	ground : taxi
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 225 flight time total : 13000 flight time type : 7000
ASRS Report	554481
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Experience	flight time last 90 days : 225 flight time total : 16200 flight time type : 5400
ASRS Report	554480
Events
Anomaly	incursion : runway non adherence : clearance
Independent Detector	other controllera
Resolutory Action	none taken : detected after the fact
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

After arriving at the aircraft and struggling with an inoperative fuel gauge (dipping the tank, etc), having to change the accuload for a different way, we finally pushed. We were cleared to runway 17R. I have been used to going to runway 17L. I had my taxi chart out, but felt that I knew where we were going in order to get to runway 17R. We exited the ramp at taxiway C. We should have turned onto taxiway a at A6. As we approached taxiway a, I saw the signs indicating runway 17R. I got somewhat confused, thinking that runway 17R was straight, and that the runway we were paralleling was runway 17R when in actuality it was runway 12/30. We crossed the runway after clearing both directions and seeing no traffic in either direction -- either on the ground or in the air, and with no hold short clrncs given. Upon exiting on the west side of the runway, ground informed us we had just crossed an active runway and to turn and re-cross the runway. Again, no traffic involved, either in the air or on the ground. We proceeded to cross back to the east side of runway 17R, taxied to the end and were cleared for takeoff with no further comment from tower or ground.

Original NASA ASRS Text

Title: B737-300 FLC HAS RWY INCURSION AT OKC.

Narrative: AFTER ARRIVING AT THE ACFT AND STRUGGLING WITH AN INOP FUEL GAUGE (DIPPING THE TANK, ETC), HAVING TO CHANGE THE ACCULOAD FOR A DIFFERENT WAY, WE FINALLY PUSHED. WE WERE CLRED TO RWY 17R. I HAVE BEEN USED TO GOING TO RWY 17L. I HAD MY TAXI CHART OUT, BUT FELT THAT I KNEW WHERE WE WERE GOING IN ORDER TO GET TO RWY 17R. WE EXITED THE RAMP AT TXWY C. WE SHOULD HAVE TURNED ONTO TXWY A AT A6. AS WE APCHED TXWY A, I SAW THE SIGNS INDICATING RWY 17R. I GOT SOMEWHAT CONFUSED, THINKING THAT RWY 17R WAS STRAIGHT, AND THAT THE RWY WE WERE PARALLELING WAS RWY 17R WHEN IN ACTUALITY IT WAS RWY 12/30. WE CROSSED THE RWY AFTER CLRING BOTH DIRECTIONS AND SEEING NO TFC IN EITHER DIRECTION -- EITHER ON THE GND OR IN THE AIR, AND WITH NO HOLD SHORT CLRNCS GIVEN. UPON EXITING ON THE W SIDE OF THE RWY, GND INFORMED US WE HAD JUST CROSSED AN ACTIVE RWY AND TO TURN AND RE-CROSS THE RWY. AGAIN, NO TFC INVOLVED, EITHER IN THE AIR OR ON THE GND. WE PROCEEDED TO CROSS BACK TO THE E SIDE OF RWY 17R, TAXIED TO THE END AND WERE CLRED FOR TKOF WITH NO FURTHER COMMENT FROM TWR OR GND.

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.