Narrative:

Approaching las on the tyssn arrival; we were told to expect vectors for a visual approach runway 19L. The tyssn lines up with [runways] 25L & right. Eventually we were cleared to the tyssn intersection and given late descent clearance and crossing restriction. Soon thereafter we were told to pull up the grnpa 1 arrival and find the trrop intersection. We were cleared to the trrop intersection subsequently and then assigned 210 KTS and eventually 5;200 ft at trrop. Upon hearing ATC clear aircraft for the 'RNAV visual 19L'; the first officer and I discuss and start looking for this procedure as new commercial charts came out this day and we may have not seen it. Can't find the procedure but it seems we're getting task saturated. The first officer is flying and not configuring the aircraft for landing. ATC asks if we see the runway: neither the first officer nor I see the runway amongst the lights of las vegas. As we continue to configure for landing; we both heard the controller say fly present heading. [The captain's] headset jack was inoperative and using the speaker probably impaired communication. By the time we heard ATC tell us to fly runway heading; the aircraft was rapidly approaching the downtown area. I exercised my captain's emergency authority to turn right instead of left on the missed approach in order not to fly within close proximity to the buildings and towers of las vegas. We were then cleared to 7;000 ft and vectored for the RNAV GPS 19L and landed. ATC should assign an appropriate STAR for the runway in use. They should always vector aircraft with sufficient distance and time to configure for a normal approach; especially at night in mountainous areas. They should provide clear instructions if runway is not visible to the pilots by a certain point.

Related reports:

Google
 

Original NASA ASRS Text

Title: A B757-200 flight crew making a night time arrival to LAS was first cleared via the TYSSN RNAV STAR which aligns with Runways 25 and then directed to utilize the GRNPA STAR to locate and fly direct to TRROP and then get vectored to Runway 19L; became disoriented and concerned with respect to proximity to the city and the mountains and initiated a self directed missed approach. They were subsequently vectored for an RNAV (GPS) approach to Runway 19L.

Narrative: Approaching LAS on the TYSSN arrival; we were told to expect vectors for a visual approach Runway 19L. The TYSSN lines up with [runways] 25L & R. Eventually we were cleared to the TYSSN Intersection and given late descent clearance and crossing restriction. Soon thereafter we were told to pull up the GRNPA 1 arrival and find the TRROP Intersection. We were cleared to the TRROP Intersection subsequently and then assigned 210 KTS and eventually 5;200 FT at TRROP. Upon hearing ATC clear aircraft for the 'RNAV Visual 19L'; the First Officer and I discuss and start looking for this procedure as new Commercial Charts came out this day and we may have not seen it. Can't find the procedure but it seems we're getting task saturated. The First Officer is flying and not configuring the aircraft for landing. ATC asks if we see the runway: neither the First Officer nor I see the runway amongst the lights of Las Vegas. As we continue to configure for landing; we both heard the Controller say fly present heading. [The Captain's] headset jack was inoperative and using the speaker probably impaired communication. By the time we heard ATC tell us to fly runway heading; the aircraft was rapidly approaching the downtown area. I exercised my Captain's emergency authority to turn right instead of left on the missed approach in order not to fly within close proximity to the buildings and towers of Las Vegas. We were then cleared to 7;000 FT and vectored for the RNAV GPS 19L and landed. ATC should assign an appropriate STAR for the runway in use. They should always vector aircraft with sufficient distance and time to configure for a normal approach; especially at night in mountainous areas. They should provide clear instructions if runway is not visible to the pilots by a certain point.

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