Air carrier medium large transport circles wrong way for runway 11 at oak.

Attributes
ACN	173208
Time
Date	199103
Day	Tue
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : oak
State Reference	CA
Altitude	msl bound lower : 1000 msl bound upper : 1500
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	tower : oak tower : mdw
Operator	common carrier : air carrier
Make Model Name	Medium Large Transport, Low Wing, 2 Turbojet Eng
Navigation In Use	Other Other
Flight Phase	descent : approach landing other
Route In Use	approach : circling approach : visual
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : instrument pilot : cfi pilot : commercial pilot : flight engineer
Experience	flight time last 90 days : 200 flight time total : 4000 flight time type : 2000
ASRS Report	173208
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	other anomaly other other spatial deviation
Independent Detector	other flight crewa
Resolutory Action	none taken : detected after the fact
Consequence	Other
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	Operational Deviation

Narrative:

Oak ATIS was reporting wind 130/10. Shortly before reaching OM, oak tower cleared us to land on runway 29, wind 150/15. The maximum tailwind limit of 10 KTS was exceeded, therefore we requested runway 11. The controller's reply was, 'circle to left, cleared to land runway 11.' we interpreted this to mean make left traffic for runway 11. While turning base, the controller informed us that he wanted the approach broken off to the left, not left traffic. Once on the ground, all other aircraft (takeoff and landing) began to request runway 11, which oak seemed unprepared for and reluctant to do. We were then given a taxi clearance (twice) after questioning it that was impossible to do from our position on the airport. On our next departure, 20 mins later, we were given an IFR clearance with an SID specifically stating for use on runways 29, 27R and 27L. Then the ATIS was broadcasting runway 11 in use. After questioning the clearance delivery controller, he said, 'the SID was useless anyway; don't worry about it.' there seems to be an attitude/communications problem at this facility. 'Make right (or left) traffic for runway 11,' would have left no doubt in my mind as to what was expected.

Original NASA ASRS Text

Title: ACR MLG CIRCLES WRONG WAY FOR RWY 11 AT OAK.

Narrative: OAK ATIS WAS RPTING WIND 130/10. SHORTLY BEFORE REACHING OM, OAK TWR CLRED US TO LAND ON RWY 29, WIND 150/15. THE MAX TAILWIND LIMIT OF 10 KTS WAS EXCEEDED, THEREFORE WE REQUESTED RWY 11. THE CTLR'S REPLY WAS, 'CIRCLE TO LEFT, CLRED TO LAND RWY 11.' WE INTERPRETED THIS TO MEAN MAKE LEFT TFC FOR RWY 11. WHILE TURNING BASE, THE CTLR INFORMED US THAT HE WANTED THE APCH BROKEN OFF TO THE LEFT, NOT LEFT TFC. ONCE ON THE GND, ALL OTHER ACFT (TKOF AND LNDG) BEGAN TO REQUEST RWY 11, WHICH OAK SEEMED UNPREPARED FOR AND RELUCTANT TO DO. WE WERE THEN GIVEN A TAXI CLRNC (TWICE) AFTER QUESTIONING IT THAT WAS IMPOSSIBLE TO DO FROM OUR POS ON THE ARPT. ON OUR NEXT DEP, 20 MINS LATER, WE WERE GIVEN AN IFR CLRNC WITH AN SID SPECIFICALLY STATING FOR USE ON RWYS 29, 27R AND 27L. THEN THE ATIS WAS BROADCASTING RWY 11 IN USE. AFTER QUESTIONING THE CLRNC DELIVERY CTLR, HE SAID, 'THE SID WAS USELESS ANYWAY; DON'T WORRY ABOUT IT.' THERE SEEMS TO BE AN ATTITUDE/COMS PROB AT THIS FAC. 'MAKE RIGHT (OR LEFT) TFC FOR RWY 11,' WOULD HAVE LEFT NO DOUBT IN MY MIND AS TO WHAT WAS EXPECTED.

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.