Narrative:

On an approximately 10 mi downwind radar vector into sjc, we were descending from 5000 ft to a clearance of 4000 ft. Descent rate was approximately 1500 FPM with 250 KTS and power to idle. The GPWS went off saying 'terrain' at least 4 times. We did comply with GA power and climb. Terrain warning stopped through about 5300 ft or 5500 ft. Level off due to high rate of climb was at 6500 ft. No conflict occurred. I called the controller on a land line. He informed me that this happens every once in a while. Seems to me that this needs to be corrected. As we were in the clouds, there is no time to analyze the situation. For all I know, there was terrain! Callback conversation with reporter revealed the following information: the reporter was flying the jawws 1 STAR into sjc, setting up for a left turn in for a visual approach to runway 12R. His air carrier has reported back that there is a problem with the GPWS software and the manufacturer is working on it. The reporter believes that bay TRACON lets aircraft down to a marginal altitude over high terrain in the effort to separate traffic into oak and sfo. His air carrier has published special pages for its manuals dealing with GPWS problems for rno and bur, but not sjc. This occurred in mid-afternoon. The reporter was IMC at the time of the alert, but sjc WX was about 2000 ft overcast with light rain. The reporter wishes that he had insisted on an ILS approach rather than vectors for a visual approach. His 'escape maneuver' produced no traffic conflicts.

Google
 

Original NASA ASRS Text

Title: A GPWS SOFTWARE PROB CAUSES AN ACR MLG TO REVERSE ITS DSCNT.

Narrative: ON AN APPROX 10 MI DOWNWIND RADAR VECTOR INTO SJC, WE WERE DSNDING FROM 5000 FT TO A CLRNC OF 4000 FT. DSCNT RATE WAS APPROX 1500 FPM WITH 250 KTS AND PWR TO IDLE. THE GPWS WENT OFF SAYING 'TERRAIN' AT LEAST 4 TIMES. WE DID COMPLY WITH GA PWR AND CLB. TERRAIN WARNING STOPPED THROUGH ABOUT 5300 FT OR 5500 FT. LEVEL OFF DUE TO HIGH RATE OF CLB WAS AT 6500 FT. NO CONFLICT OCCURRED. I CALLED THE CTLR ON A LAND LINE. HE INFORMED ME THAT THIS HAPPENS EVERY ONCE IN A WHILE. SEEMS TO ME THAT THIS NEEDS TO BE CORRECTED. AS WE WERE IN THE CLOUDS, THERE IS NO TIME TO ANALYZE THE SIT. FOR ALL I KNOW, THERE WAS TERRAIN! CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE RPTR WAS FLYING THE JAWWS 1 STAR INTO SJC, SETTING UP FOR A L TURN IN FOR A VISUAL APCH TO RWY 12R. HIS ACR HAS RPTED BACK THAT THERE IS A PROB WITH THE GPWS SOFTWARE AND THE MANUFACTURER IS WORKING ON IT. THE RPTR BELIEVES THAT BAY TRACON LETS ACFT DOWN TO A MARGINAL ALT OVER HIGH TERRAIN IN THE EFFORT TO SEPARATE TFC INTO OAK AND SFO. HIS ACR HAS PUBLISHED SPECIAL PAGES FOR ITS MANUALS DEALING WITH GPWS PROBS FOR RNO AND BUR, BUT NOT SJC. THIS OCCURRED IN MID-AFTERNOON. THE RPTR WAS IMC AT THE TIME OF THE ALERT, BUT SJC WX WAS ABOUT 2000 FT OVCST WITH LIGHT RAIN. THE RPTR WISHES THAT HE HAD INSISTED ON AN ILS APCH RATHER THAN VECTORS FOR A VISUAL APCH. HIS 'ESCAPE MANEUVER' PRODUCED NO TFC CONFLICTS.

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.