Narrative:

We were on the coltr 3 arrival for runway 26. Descending via the coltr 3 to tacoh intersection when ZAB center switched us to abq approach control. Approach gave us a vector to the south of the arrival and instructed us to descend to 12000 ft and slow to 230 knots. We were number 3 for runway 26. We had set up and briefed the RNAV visual for runway 26. They gave us a series of vectors as we got closer to the airport and additional descent clearances. Ultimately they turned us to a 030 heading toward the terrain and cleared us to descend to 8500 ft from 9200 ft. We were now east of the RNAV visual for 26 course; I told the first officer (first officer) to tell them we could not make a visual approach from where we were and would need an immediate turn to the west due to the proximity of the terrain. The controller did not give us a turn so I told the first officer to tell him we were turning left to a 270 heading. The controller then gave us a 260 heading. Another controller came on the radio and said they would vector us out to the north for the right downwind and base for runway 26. I had the first officer tell them we would like to go out to the southwest and fly the RNAV visual approach. The original controller came back on and provided the necessary vectors. We ended up flying the RNAV visual to 26 from just outside of rmero intersection. The remainder of the flight was uneventful. I am submitting this report because I felt this situation could have gotten hazardous quickly. I also felt based on my experience in airline safety that this problem at abq was resolved. Additional information: I flew this same flight two days prior and we went right from the arrival to the RNAV 26 visual the way it is supposed to work.

Google
 

Original NASA ASRS Text

Title: Air Carrier Captain reported being vectored toward terrain on a visual approach into ABQ.

Narrative: We were on the COLTR 3 arrival for Runway 26. Descending via the COLTR 3 to TACOH intersection when ZAB Center switched us to ABQ Approach Control. Approach gave us a vector to the south of the arrival and instructed us to descend to 12000 ft and slow to 230 knots. We were number 3 for Runway 26. We had set up and briefed the RNAV Visual for Runway 26. They gave us a series of vectors as we got closer to the airport and additional descent clearances. Ultimately they turned us to a 030 heading toward the terrain and cleared us to descend to 8500 ft from 9200 ft. We were now east of the RNAV Visual for 26 course; I told the FO (First Officer) to tell them we could not make a Visual Approach from where we were and would need an immediate turn to the west due to the proximity of the terrain. The Controller did not give us a turn so I told the FO to tell him we were turning left to a 270 heading. The Controller then gave us a 260 heading. Another Controller came on the radio and said they would vector us out to the north for the right downwind and base for Runway 26. I had the FO tell them we would like to go out to the southwest and fly the RNAV Visual Approach. The original controller came back on and provided the necessary vectors. We ended up flying the RNAV Visual to 26 from just outside of RMERO intersection. The remainder of the flight was uneventful. I am submitting this report because I felt this situation could have gotten hazardous quickly. I also felt based on my experience in Airline Safety that this problem at ABQ was resolved. Additional information: I flew this same flight two days prior and we went right from the arrival to the RNAV 26 Visual the way it is supposed to work.

Data retrieved from NASA's ASRS site 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.