A corporate jet crew makes an approach to wrong runway at oak, co.

Attributes
ACN	573973
Time
Date	200302
Day	Wed
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : oak.airport
State Reference	CA
Altitude	agl single value : 400
Environment
Flight Conditions	Marginal
Weather Elements	Rain
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : nct.tracon tower : oak.tower
Operator	general aviation : corporate
Make Model Name	Small Transport, Low Wing, 2 Turboprop Eng
Operating Under FAR Part	Part 91
Navigation In Use	other
Flight Phase	descent : approach landing : go around
Route In Use	arrival : on vectors
Flight Plan	IFR
Person 1
Affiliation	company : corporate
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 90 flight time total : 12000 flight time type : 3000
ASRS Report	573973
Person 2
Affiliation	company : corporate
Function	flight crew : first officer
Events
Anomaly	non adherence : clearance non adherence : published procedure other anomaly other other spatial deviation
Independent Detector	other controllera
Resolutory Action	controller : issued new clearance controller : issued alert flight crew : executed go around
Supplementary
Problem Areas	Flight Crew Human Performance Environmental Factor
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

On our short trip from ksfo to koak, as soon as we were established on the departure, I (PNF) tuned in ATIS at koak. It was a very long recording. By the time I had listened to all of it, we were all ready getting vectors for the VOR runway 9R. We dialed in the frequency, radial MDA, and radar altimeter settings. Quickly briefed the approach as the course was alive. At about 5 mi out, we were switched to tower control. At that time, I called airport in sight. We were asked if we could land runway 9L. As the runways were wet we could not see the numbers until 1-1/2 mi from the end of runway 11. I was busy completing checklist and getting runway layout as we were completing approach. At the time we realized we were on the wrong runway, the controller called for us to climb and turn left. As we did, we crossed over the field and landed runway 27R. Contributing factors -- short flight, large workload, runway wet, very long ATIS at koak not enough time to brief runway layout, we were asked for best speed to runway. Prevention -- request longer final, approach monitoring by ATC. There needs to be a maximum length for ATIS recordings.

Original NASA ASRS Text

Title: A CORPORATE JET CREW MAKES AN APCH TO WRONG RWY AT OAK, CO.

Narrative: ON OUR SHORT TRIP FROM KSFO TO KOAK, AS SOON AS WE WERE ESTABLISHED ON THE DEP, I (PNF) TUNED IN ATIS AT KOAK. IT WAS A VERY LONG RECORDING. BY THE TIME I HAD LISTENED TO ALL OF IT, WE WERE ALL READY GETTING VECTORS FOR THE VOR RWY 9R. WE DIALED IN THE FREQ, RADIAL MDA, AND RADAR ALTIMETER SETTINGS. QUICKLY BRIEFED THE APCH AS THE COURSE WAS ALIVE. AT ABOUT 5 MI OUT, WE WERE SWITCHED TO TWR CTL. AT THAT TIME, I CALLED ARPT IN SIGHT. WE WERE ASKED IF WE COULD LAND RWY 9L. AS THE RWYS WERE WET WE COULD NOT SEE THE NUMBERS UNTIL 1-1/2 MI FROM THE END OF RWY 11. I WAS BUSY COMPLETING CHKLIST AND GETTING RWY LAYOUT AS WE WERE COMPLETING APCH. AT THE TIME WE REALIZED WE WERE ON THE WRONG RWY, THE CTLR CALLED FOR US TO CLB AND TURN L. AS WE DID, WE CROSSED OVER THE FIELD AND LANDED RWY 27R. CONTRIBUTING FACTORS -- SHORT FLT, LARGE WORKLOAD, RWY WET, VERY LONG ATIS AT KOAK NOT ENOUGH TIME TO BRIEF RWY LAYOUT, WE WERE ASKED FOR BEST SPD TO RWY. PREVENTION -- REQUEST LONGER FINAL, APCH MONITORING BY ATC. THERE NEEDS TO BE A MAX LENGTH FOR ATIS RECORDINGS.

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.