A B737-300 crew, taxiing for takeoff, taxied onto their departure runway without clearance to do so.

Attributes
ACN	564797
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	IMC
Light	Dawn
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	B737-300
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 : 214 flight time total : 12289 flight time type : 5779
ASRS Report	564797
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	incursion : runway non adherence : far non adherence : clearance
Independent Detector	other flight crewa
Resolutory Action	controller : issued new clearance
Consequence	faa : reviewed incident with flight crew other
Supplementary
Problem Areas	Flight Crew Human Performance Weather
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

Okc was operating off the runways 17. Prior to pushback, I asked first officer to calculate performance for runway 31. ATIS called wind 170 degrees at 4 KTS and 3 mi broken. We were cleared to taxi to runway 31 and went via txwys J and F. The visibility had decreased rapidly from the time of our shuttle to the airport and looked to be significantly less than 3 mi, but the apron and txwys were clearly visible. Turning onto taxiway F, the tower started reading the latest WX with 1 mi visibility, though it looked closer to 1/2 mi. First officer started copying the WX, I was thinking about the ramifications of the MEL'ed captain's flight director and anticipating takeoff clearance. In that moment of distraction, I missed seeing the hold short lines. Entering the runway, I realized this was wrong and stopped the aircraft perpendicular to the runway, shy of the centerline. We advised tower of our position. We were cleared for takeoff, completed the 'below the line,' and left for mci.

Original NASA ASRS Text

Title: A B737-300 CREW, TAXIING FOR TKOF, TAXIED ONTO THEIR DEP RWY WITHOUT CLRNC TO DO SO.

Narrative: OKC WAS OPERATING OFF THE RWYS 17. PRIOR TO PUSHBACK, I ASKED FO TO CALCULATE PERFORMANCE FOR RWY 31. ATIS CALLED WIND 170 DEGS AT 4 KTS AND 3 MI BROKEN. WE WERE CLRED TO TAXI TO RWY 31 AND WENT VIA TXWYS J AND F. THE VISIBILITY HAD DECREASED RAPIDLY FROM THE TIME OF OUR SHUTTLE TO THE ARPT AND LOOKED TO BE SIGNIFICANTLY LESS THAN 3 MI, BUT THE APRON AND TXWYS WERE CLRLY VISIBLE. TURNING ONTO TXWY F, THE TWR STARTED READING THE LATEST WX WITH 1 MI VISIBILITY, THOUGH IT LOOKED CLOSER TO 1/2 MI. FO STARTED COPYING THE WX, I WAS THINKING ABOUT THE RAMIFICATIONS OF THE MEL'ED CAPT'S FLT DIRECTOR AND ANTICIPATING TKOF CLRNC. IN THAT MOMENT OF DISTR, I MISSED SEEING THE HOLD SHORT LINES. ENTERING THE RWY, I REALIZED THIS WAS WRONG AND STOPPED THE ACFT PERPENDICULAR TO THE RWY, SHY OF THE CTRLINE. WE ADVISED TWR OF OUR POS. WE WERE CLRED FOR TKOF, COMPLETED THE 'BELOW THE LINE,' AND LEFT FOR MCI.

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.