B737-300 captain inadvertently taxied onto active runway prior to clearance.

Attributes
ACN	564468
Time
Date	200211
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	Marginal
Weather Elements	Rain Fog
Light	Dawn
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	B737-300
Operating Under FAR Part	Part 121
Flight Phase	ground : taxi
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Experience	flight time last 90 days : 240 flight time total : 10500 flight time type : 5000
ASRS Report	564468
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	incursion : runway non adherence : clearance non adherence : far
Independent Detector	other flight crewa
Resolutory Action	controller : issued new clearance none taken : detected after the fact
Supplementary
Problem Areas	Flight Crew Human Performance
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

After finishing all the after start procedures, we contacted ATC and advised them we were ready to taxi. They cleared us to runway 17R. At that time the captain requested runway 31, so I called ground and requested runway 31 and they authority/authorized it. Then, they changed the ATIS, so I pulled the opc and got all the input from it back to the FMC. By the time I finished the procedure, we were already at the approach end of runway 31, inside the runway and without clearance. I called ATC and advised them that we just had an incursion onto runway 31 without clearance. Tower instructed us to execute the takeoff on runway 31. We executed the takeoff without any further incidents. Contributing factors: low visibility, change in runways after start of taxiing, change in ATIS, 1 pilot doing the taxi, same controller for ground and tower, very short taxi. Corrective actions: even with 3 mi visibility, we should not have continued the taxi until all data had been input in the FMC.

Original NASA ASRS Text

Title: B737-300 CAPT INADVERTENTLY TAXIED ONTO ACTIVE RWY PRIOR TO CLRNC.

Narrative: AFTER FINISHING ALL THE AFTER START PROCS, WE CONTACTED ATC AND ADVISED THEM WE WERE READY TO TAXI. THEY CLRED US TO RWY 17R. AT THAT TIME THE CAPT REQUESTED RWY 31, SO I CALLED GND AND REQUESTED RWY 31 AND THEY AUTH IT. THEN, THEY CHANGED THE ATIS, SO I PULLED THE OPC AND GOT ALL THE INPUT FROM IT BACK TO THE FMC. BY THE TIME I FINISHED THE PROC, WE WERE ALREADY AT THE APCH END OF RWY 31, INSIDE THE RWY AND WITHOUT CLRNC. I CALLED ATC AND ADVISED THEM THAT WE JUST HAD AN INCURSION ONTO RWY 31 WITHOUT CLRNC. TWR INSTRUCTED US TO EXECUTE THE TKOF ON RWY 31. WE EXECUTED THE TKOF WITHOUT ANY FURTHER INCIDENTS. CONTRIBUTING FACTORS: LOW VISIBILITY, CHANGE IN RWYS AFTER START OF TAXIING, CHANGE IN ATIS, 1 PLT DOING THE TAXI, SAME CTLR FOR GND AND TWR, VERY SHORT TAXI. CORRECTIVE ACTIONS: EVEN WITH 3 MI VISIBILITY, WE SHOULD NOT HAVE CONTINUED THE TAXI UNTIL ALL DATA HAD BEEN INPUT IN THE FMC.

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.