Narrative:

We were 1 NM west of peavine peak descending out of 10000 ft for 9500 ft when I asked rno approach if that was peavine peak at our 12 O'clock position. They confirmed that it was and cleared us for the sparks visual runway 16R approach. We continued the descent to 9500 ft while slowing to 210 KTS, selecting flaps 5 degrees, and lowering the gear. As we passed slightly south and clear of peavine peak, we got a momentary ground proximity caution/alert of 'terrain, terrain' in which we followed company procedures and started the recovery procedure. Just as we began our recovery, the GPWS stopped. It only sounded that one time and since we had been operating in solid VFR conditions for the last 10 mi or so and clearly had the airport, and all terrain in clear view during this time, I elected to re-establish the visual approach and continue to landing. My first officer and I talked about the event after landing and were a little mystified as to why the GPWS had given us a warning. We both agreed that we were well clear of any obstructions but it sill went off. My only thought in this matter is that I didn't want to be too high, so I started configuring the aircraft just west of peavine peak with the gear and flaps 5 degrees out and descending to 9500 ft, it may have thought we were not in the proper landing confign since we were passing over the peak at that time. Normally, I have flaps 5 degrees out, but in this case I wanted to have the gear out also since we showed a pretty good wind out of the north that would have given us a tailwind on the approach until we would lose it on short final. This may have had something to do with the warning, but in any event, we had everything in clear view and had actually passed peavine peak when this took place. As always, I will strive to stay heads up while flying in and out of airports with high terrain. Supplemental information from acn 637655: we had configured the aircraft earlier in the descent and were established on a good profile for the arrival with gear down, flaps at 5 degrees and vvi around 1200-1400 FPM. With both PF and pilot monitoring visual with the ground, and the highest terrain behind the aircraft, the warning was certainly a surprise. Obviously though a parameter in the GPWS for descent rate and ht above ground was met, albeit momentarily. Additionally, to prevent a recurrence and further enhance safety, we plan to include in our future rno arrival briefings a planned minimum altitude and maximum descent rate to fly over peavine peak. Finally, we suggest consideration be given to modifying the published ground track for the sparks visual arrival. Rather than flying directly over the rapidly rising terrain of peavine peak itself, an offset to the north would allow significantly greater ground clearance.

Google
 

Original NASA ASRS Text

Title: B737-300 CREW HAD AN EGPWS TERRAIN WARNING GO OFF OVER PEAVINE PEAK ON THE SPARKS VISUAL AT RNO.

Narrative: WE WERE 1 NM W OF PEAVINE PEAK DSNDING OUT OF 10000 FT FOR 9500 FT WHEN I ASKED RNO APCH IF THAT WAS PEAVINE PEAK AT OUR 12 O'CLOCK POS. THEY CONFIRMED THAT IT WAS AND CLRED US FOR THE SPARKS VISUAL RWY 16R APCH. WE CONTINUED THE DSCNT TO 9500 FT WHILE SLOWING TO 210 KTS, SELECTING FLAPS 5 DEGS, AND LOWERING THE GEAR. AS WE PASSED SLIGHTLY S AND CLR OF PEAVINE PEAK, WE GOT A MOMENTARY GND PROX CAUTION/ALERT OF 'TERRAIN, TERRAIN' IN WHICH WE FOLLOWED COMPANY PROCS AND STARTED THE RECOVERY PROC. JUST AS WE BEGAN OUR RECOVERY, THE GPWS STOPPED. IT ONLY SOUNDED THAT ONE TIME AND SINCE WE HAD BEEN OPERATING IN SOLID VFR CONDITIONS FOR THE LAST 10 MI OR SO AND CLRLY HAD THE ARPT, AND ALL TERRAIN IN CLR VIEW DURING THIS TIME, I ELECTED TO RE-ESTABLISH THE VISUAL APCH AND CONTINUE TO LNDG. MY FO AND I TALKED ABOUT THE EVENT AFTER LNDG AND WERE A LITTLE MYSTIFIED AS TO WHY THE GPWS HAD GIVEN US A WARNING. WE BOTH AGREED THAT WE WERE WELL CLR OF ANY OBSTRUCTIONS BUT IT SILL WENT OFF. MY ONLY THOUGHT IN THIS MATTER IS THAT I DIDN'T WANT TO BE TOO HIGH, SO I STARTED CONFIGURING THE ACFT JUST W OF PEAVINE PEAK WITH THE GEAR AND FLAPS 5 DEGS OUT AND DSNDING TO 9500 FT, IT MAY HAVE THOUGHT WE WERE NOT IN THE PROPER LNDG CONFIGN SINCE WE WERE PASSING OVER THE PEAK AT THAT TIME. NORMALLY, I HAVE FLAPS 5 DEGS OUT, BUT IN THIS CASE I WANTED TO HAVE THE GEAR OUT ALSO SINCE WE SHOWED A PRETTY GOOD WIND OUT OF THE N THAT WOULD HAVE GIVEN US A TAILWIND ON THE APCH UNTIL WE WOULD LOSE IT ON SHORT FINAL. THIS MAY HAVE HAD SOMETHING TO DO WITH THE WARNING, BUT IN ANY EVENT, WE HAD EVERYTHING IN CLR VIEW AND HAD ACTUALLY PASSED PEAVINE PEAK WHEN THIS TOOK PLACE. AS ALWAYS, I WILL STRIVE TO STAY HEADS UP WHILE FLYING IN AND OUT OF ARPTS WITH HIGH TERRAIN. SUPPLEMENTAL INFO FROM ACN 637655: WE HAD CONFIGURED THE ACFT EARLIER IN THE DSCNT AND WERE ESTABLISHED ON A GOOD PROFILE FOR THE ARR WITH GEAR DOWN, FLAPS AT 5 DEGS AND VVI AROUND 1200-1400 FPM. WITH BOTH PF AND PLT MONITORING VISUAL WITH THE GND, AND THE HIGHEST TERRAIN BEHIND THE ACFT, THE WARNING WAS CERTAINLY A SURPRISE. OBVIOUSLY THOUGH A PARAMETER IN THE GPWS FOR DSCNT RATE AND HT ABOVE GND WAS MET, ALBEIT MOMENTARILY. ADDITIONALLY, TO PREVENT A RECURRENCE AND FURTHER ENHANCE SAFETY, WE PLAN TO INCLUDE IN OUR FUTURE RNO ARR BRIEFINGS A PLANNED MINIMUM ALT AND MAX DSCNT RATE TO FLY OVER PEAVINE PEAK. FINALLY, WE SUGGEST CONSIDERATION BE GIVEN TO MODIFYING THE PUBLISHED GND TRACK FOR THE SPARKS VISUAL ARR. RATHER THAN FLYING DIRECTLY OVER THE RAPIDLY RISING TERRAIN OF PEAVINE PEAK ITSELF, AN OFFSET TO THE N WOULD ALLOW SIGNIFICANTLY GREATER GND CLRNC.

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.