Air carrier X GPWS non adherence to ATC clearance. Evasive action climb.

Attributes
ACN	299819
Time
Date	199503
Day	Tue
Local Time Of Day	1801 To 2400
Place
Locale Reference	atc facility : las
State Reference	NV
Altitude	msl bound lower : 6100 msl bound upper : 6100
Environment
Flight Conditions	Mixed
Light	Night
Aircraft 1
Controlling Facilities	tracon : las
Operator	common carrier : air carrier
Make Model Name	B737-300
Operating Under FAR Part	Part 121
Navigation In Use	Other Other
Flight Phase	descent other
Route In Use	enroute : on vectors
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 150 flight time total : 9000 flight time type : 2000
ASRS Report	299819
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : instrument
Events
Anomaly	non adherence : clearance other spatial deviation
Independent Detector	aircraft equipment other aircraft equipment : unspecified
Resolutory Action	flight crew : took evasive action
Consequence	Other
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	other

Narrative:

Air carrier X being vectored for a visual approach to runway 25L. Level at 6100 ft MSL as cleared. At approximately 5-6 mi out on base for runway 25, received a GPWS alert 'terrain, terrain.' first officer was flying and executed a pull up. We then could see the terrain that was causing the problem -- a 5092 ft peak. At about 6500 ft, first officer leveled off. We were getting too high to make the approach. The GPWS was still screaming 'terrain, terrain,' approach was giving headings. Visual approach clearance, switchover to tower. We also had light-moderate chop. The GPWS finally quit and we made a steep (6500 ft 6 mi out!) approach to runway 25L. MVA was 6100 ft over that obstacle, which is steeply rising terrain. The MVA should be raised to 2000 ft above the obstacle. Unnecessary emergency pullups can hurt flight attendants and passenger. Also, las should quit giving 'high dives' to everyone. Every time I go in there I get a 'high dive.' why? Is this really necessary? The GPWS problem also occurs at san, lax, bur, mfr, slc, and asheville, nc to my knowledge. Minimum vectoring altitudes are not protecting the pilots.

Original NASA ASRS Text

Title: ACR X GPWS NON ADHERENCE TO ATC CLRNC. EVASIVE ACTION CLB.

Narrative: ACR X BEING VECTORED FOR A VISUAL APCH TO RWY 25L. LEVEL AT 6100 FT MSL AS CLRED. AT APPROX 5-6 MI OUT ON BASE FOR RWY 25, RECEIVED A GPWS ALERT 'TERRAIN, TERRAIN.' FO WAS FLYING AND EXECUTED A PULL UP. WE THEN COULD SEE THE TERRAIN THAT WAS CAUSING THE PROB -- A 5092 FT PEAK. AT ABOUT 6500 FT, FO LEVELED OFF. WE WERE GETTING TOO HIGH TO MAKE THE APCH. THE GPWS WAS STILL SCREAMING 'TERRAIN, TERRAIN,' APCH WAS GIVING HDGS. VISUAL APCH CLRNC, SWITCHOVER TO TWR. WE ALSO HAD LIGHT-MODERATE CHOP. THE GPWS FINALLY QUIT AND WE MADE A STEEP (6500 FT 6 MI OUT!) APCH TO RWY 25L. MVA WAS 6100 FT OVER THAT OBSTACLE, WHICH IS STEEPLY RISING TERRAIN. THE MVA SHOULD BE RAISED TO 2000 FT ABOVE THE OBSTACLE. UNNECESSARY EMER PULLUPS CAN HURT FLT ATTENDANTS AND PAX. ALSO, LAS SHOULD QUIT GIVING 'HIGH DIVES' TO EVERYONE. EVERY TIME I GO IN THERE I GET A 'HIGH DIVE.' WHY? IS THIS REALLY NECESSARY? THE GPWS PROB ALSO OCCURS AT SAN, LAX, BUR, MFR, SLC, AND ASHEVILLE, NC TO MY KNOWLEDGE. MINIMUM VECTORING ALTS ARE NOT PROTECTING THE PLTS.

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.