TRACON refuses a vector to runway after 2 requests by air carrier during night operation.

Attributes
ACN	476334
Time
Date	200006
Day	Thu
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : tus.airport
State Reference	AZ
Altitude	msl single value : 6500
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Controlling Facilities	tracon : u90.tracon
Operator	common carrier : air carrier
Make Model Name	MD-88
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	descent : approach
Route In Use	approach : visual arrival : vfr
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp pilot : commercial pilot : instrument pilot : multi engine pilot : private
Experience	flight time last 90 days : 200 flight time total : 13000 flight time type : 5000
ASRS Report	476334
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : instrument pilot : multi engine
Events
Anomaly	non adherence : published procedure other anomaly other
Independent Detector	other flight crewa
Resolutory Action	none taken : unable
Supplementary
Problem Areas	ATC Human Performance
Primary Problem	ATC Human Performance

Narrative:

ZAB confirmed landing runway at tus to be runway 29R. On switching over to approach control, we were given a heading of 300 degrees to the airport. Dscnts were made to 6500 ft and approach stated only approach was a visual to runway 21. We informed approach that we wanted vectors to final or to base for final, due to no approach procedures for runway 21, but were denied this request. Approach stated runway 21 was at 12 O'clock position at xx mi. We informed controller that we did not see runway 21 from our position and requested vectors, but we were denied again. We stated we had the airport and runway 29R but were instructed to call visual on runway 21. Upon reaching approximately the end of runway 29R, we saw and called visual on runway 21. Approach then cleared us for visual approach to runway 21 with left turn on. We turned right and positioned ourselves for left turn onto final for runway 21. We turned base prior to runways at davis monthan. Tower cleared us to land and we made an uneventful landing. We were concerned about conflict of pattern on runway 21 at tus and approachs at davis monthan but were given no assistance and to the best of our ability avoided all known and possible conflicts. No TA's or further instructions were given to our aircraft.

Original NASA ASRS Text

Title: TRACON REFUSES A VECTOR TO RWY AFTER 2 REQUESTS BY ACR DURING NIGHT OP.

Narrative: ZAB CONFIRMED LNDG RWY AT TUS TO BE RWY 29R. ON SWITCHING OVER TO APCH CTL, WE WERE GIVEN A HDG OF 300 DEGS TO THE ARPT. DSCNTS WERE MADE TO 6500 FT AND APCH STATED ONLY APCH WAS A VISUAL TO RWY 21. WE INFORMED APCH THAT WE WANTED VECTORS TO FINAL OR TO BASE FOR FINAL, DUE TO NO APCH PROCS FOR RWY 21, BUT WERE DENIED THIS REQUEST. APCH STATED RWY 21 WAS AT 12 O'CLOCK POS AT XX MI. WE INFORMED CTLR THAT WE DID NOT SEE RWY 21 FROM OUR POS AND REQUESTED VECTORS, BUT WE WERE DENIED AGAIN. WE STATED WE HAD THE ARPT AND RWY 29R BUT WERE INSTRUCTED TO CALL VISUAL ON RWY 21. UPON REACHING APPROX THE END OF RWY 29R, WE SAW AND CALLED VISUAL ON RWY 21. APCH THEN CLRED US FOR VISUAL APCH TO RWY 21 WITH L TURN ON. WE TURNED R AND POSITIONED OURSELVES FOR L TURN ONTO FINAL FOR RWY 21. WE TURNED BASE PRIOR TO RWYS AT DAVIS MONTHAN. TWR CLRED US TO LAND AND WE MADE AN UNEVENTFUL LNDG. WE WERE CONCERNED ABOUT CONFLICT OF PATTERN ON RWY 21 AT TUS AND APCHS AT DAVIS MONTHAN BUT WERE GIVEN NO ASSISTANCE AND TO THE BEST OF OUR ABILITY AVOIDED ALL KNOWN AND POSSIBLE CONFLICTS. NO TA'S OR FURTHER INSTRUCTIONS WERE GIVEN TO OUR ACFT.

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.