Narrative:

While being vectored to localizer 27 by san approach control; we received an abbreviated terrain warning. We were in a turn to a 240 heading to intercept 27 localizer and descending to 4;000 ft MSL until established on final. Passing approximately 4;400 ft MSL; and in our right turn to final; we received an abbreviated 'terrain; terrain' egpws warning. We were just north of course between okain and vyyda; approximately near the 2;709 ft tower area. We were aware of the terrain; and for that reason the first officer was in a gradual descent. In this particular aircraft; the warning messages over the speaker system are very loud; so when the egpws warning occurred; it definitely got both of our attention. At that moment; I was identifying the localizer frequency with my head down focused on the comm panel. I immediately reached for the controls; but realized the first officer was still flying; so I stopped. He started to bring the power up and disconnected the autopilot; but the warning never continued and stopped prior to him accomplishing these tasks. Clear of the conflict; we both then verified our altitude and looked at the terrain monitoring system; which showed 1;700 ft as a safe altitude and all terrain on the scope was green. We continued the approach without incident. In this case; the system may have performed as required. Although; our only concern is that we were well above minimum vectoring altitude and in a slow descending turn. I'm sure that being in a descent; turning into the rising terrain and maybe even some GPS error all contributed to the warning. We just wanted to let you know about the situation so that others would be aware and/or in case this aircraft had any history of this kind of previous event. Again; we respected the egpws warning and were prepared to perform the terrain avoidance maneuver since it was at night. We did not complete the initial part of the terrain avoidance maneuver because before we could do it; the terrain warning had stopped even prior to 'pull up' and terrain contact was no longer a factor. I think we do a very good job of highlighting these kinds of possible situations. Having flown into san over the last 12 years; having descended over that particular hill many times; and knowing it was there even at that moment; unexpected warnings do occur and every now and then we need to be made aware of these possible events. In the event; this was an erroneous egpws warning do to software or GPS issues. We just wanted to highlight the aircraft in case it has had previous unexplained events.

Related reports:

Google
 

Original NASA ASRS Text

Title: A B737-300 crew reported a partial EGPWS TERRAIN warning at 4;400 FT near a charted 2;709 FT hilltop north of the SAN LOC 27 VYDDA intersection while the aircraft was on profile and in a slight descent.

Narrative: While being vectored to LOC 27 by SAN Approach Control; we received an abbreviated Terrain Warning. We were in a turn to a 240 heading to intercept 27 LOC and descending to 4;000 FT MSL until established on final. Passing approximately 4;400 FT MSL; and in our right turn to final; we received an abbreviated 'Terrain; Terrain' EGPWS Warning. We were just north of course between OKAIN and VYYDA; approximately near the 2;709 FT Tower area. We were aware of the terrain; and for that reason the First Officer was in a gradual descent. In this particular aircraft; the warning messages over the speaker system are very loud; so when the EGPWS Warning occurred; it definitely got both of our attention. At that moment; I was identifying the LOC frequency with my head down focused on the COMM panel. I immediately reached for the controls; but realized the First Officer was still flying; so I stopped. He started to bring the power up and disconnected the autopilot; but the warning never continued and stopped prior to him accomplishing these tasks. Clear of the conflict; we both then verified our altitude and looked at the terrain monitoring system; which showed 1;700 FT as a safe altitude and all terrain on the scope was green. We continued the approach without incident. In this case; the system may have performed as required. Although; our only concern is that we were well above minimum vectoring altitude and in a slow descending turn. I'm sure that being in a descent; turning into the rising terrain and maybe even some GPS error all contributed to the warning. We just wanted to let you know about the situation so that others would be aware and/or in case this aircraft had any history of this kind of previous event. Again; we respected the EGPWS Warning and were prepared to perform the terrain avoidance maneuver since it was at night. We did not complete the initial part of the terrain avoidance maneuver because before we could do it; the Terrain Warning had stopped even prior to 'pull up' and terrain contact was no longer a factor. I think we do a very good job of highlighting these kinds of possible situations. Having flown into SAN over the last 12 years; having descended over that particular hill many times; and knowing it was there even at that moment; unexpected warnings do occur and every now and then we need to be made aware of these possible events. In the event; this was an erroneous EGPWS Warning do to software or GPS issues. We just wanted to highlight the aircraft in case it has had previous unexplained events.

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.