Date: 201707
Local time of day: 1801-2400
Location: LAS.Airport, NV
Light: Night
Aircraft: A321
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach; Final Approach
Airspace: Class B LAS
ATC / advisory: TRACON L30
Reporter organization: Air Carrier
Reporter function: Pilot Not Flying; First Officer
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Human-Machine Interface
Second reporter function: Pilot Flying; Captain
Anomaly: Inflight Event / Encounter CFTT / CFIT
Detector: Automation Aircraft RA
When detected: In-flight
Result: Flight Crew Executed Go Around / Missed Approach; Flight Crew Took Evasive Action
Contributing factors: Airport; ATC Equipment / Nav Facility / Buildings; Aircraft; Human Factors
Primary problem: Human Factors

Narrative: On descent to LAS approach asked if we had the airport insight which we did. ATC cleared us for a visual approach to 25L we turned to the FAF and stared a shallow descent. At approximately 4;500 ft. the 2;500 RA call this was interpreted as normal since airport elevation is 2;200 ft.  Seconds later the 'Terrain; Terrain' GPWS warning started. The captain immediately performed the escape maneuver. We climbed to 6;000 ft. and asked for vectors to the ILS. Then landed normally.There were several factors that lead us to a low altitude event. First while I have operated in LAS a few times I've never been southwest of the airport past a downwind leg at night. Second the higher terrain east and south made the arrival from the southwest the lower terrain option.  When combined with the lack of terrain depicted on this course we continued. Ultimately we descended too early for our distance from the field.


Second narrative: CAVU weather; A321 basic aircraft with old displays; no EGPWS. Descending on TYSSN4 arrival to 12000; subsequently given a heading approximately 360 (unsure of exact heading) and descend to 8;000. Approximately 23 miles out; ATC queries if we have the field. I reply yes; ATC clears us for the visual 25L. I put the FAF altitude of 3;800 in the alt window and input direct RELIN (FAF) in the FMS. I observe that I am below the abeam altitude of 6;800 at 16 miles; but visually am quite certain there is no terrain between the aircraft and RELIN.  Between 4;000 - 5;000; just after hearing a 2;500 ft. call; we receive a 'Terrain; Terrain' GPWS warning. I am the pilot flying and execute an escape maneuver; climbing to 6;000 ft. I never reference the radio altimeter; but FO says he saw 1;500. I abandon the approach and ask for radar vectors around for the ILS 25L. Landing uneventful.I am quite certain I would have made different decisions on how low to descend if I was in an aircraft with modern EGPWS. At no time do I observe any terrain on the display. I believe the event occurred due to a 4;100' tower 13 miles southeast of the field. There is no 'caution;  obstacle' call; nor 'caution; terrain' call.  I am aware that FM1 clearly states not to accept a night visual if unfamiliar with terrain. I determine that I am familiar and accept the visual clearance. While I have flown into LAS many times from the west; This is the first time I have approached LAS from the southeast; therefore; I actually am not familiar with the terrain. There is a clear loss of situational awareness on the part of the crew indicated by the fact that we did  not take into account the tower southeast of the field.The basic aircraft A321 displays and lower technology contribute to this event. I should not have accepted the visual clearance until established on final approach.  Note: I have read; and am keenly familiar; with previous messages regarding the low altitude; night visual; 'trap' that I fell into. I felt very confident that I was abiding to the guidance of those messages.


Synopsis: A321 flight crew reported they experienced a CFTT incident during a night visual approach to LAS airport. Situational awareness and high terrain were cited as contributing factors.