Narrative:

Approaching sns VOR on robie 2 arrival into sjc, was told by ZOA to proceed direct to klide intersection (sjc 123 degree radial, 16.8 DME) and intercept the localizer runway 30L. Although we intended to do that, we instead took up a heading that would take us to a point on the other side of the field (ie, the sjc 303 degree radial, 16.8 DME). During handoff to approach, approach control realized we weren't proceeding as directed. They then directed us to turn right to a heading to intercept the localizer. No traffic conflict resulted. When ATC cleared us to klide, the PNF (me) tried to program klide into the FMC. Klide was not in the database so I had to enter the intersection as a radial and DME. The PF (first officer) said enter sjc 303 degree radial, 17 NM fix. I did that and we then turned to a heading that would take us to (what I thought was) klide. Neither of us realized that we had entered the inbound course rather than the radial. We were proceeding on a heading to the other side of the field. Contributing factors: 1) klide not in database. 2) captain not 'thinking' when he entered what the first officer told him to enter. 3) high workload -- occurred well into descent when a lot of things were happening. 4) not looking at the heading and asking 'does it make sense?' a glance at the approach chart should have shown heading to be between 333-347 degrees from sns and not the 318 degree heading we were flying. Lesson learned: PNF should 'back up' and not just enter what the first officer says.

Related reports:

Google
 

Original NASA ASRS Text

Title: A B737-300 FLC PLACES THE WRONG INFO WITHIN THEIR FMC FOR AN ARR INTO SJC, CA.

Narrative: APCHING SNS VOR ON ROBIE 2 ARR INTO SJC, WAS TOLD BY ZOA TO PROCEED DIRECT TO KLIDE INTXN (SJC 123 DEG RADIAL, 16.8 DME) AND INTERCEPT THE LOC RWY 30L. ALTHOUGH WE INTENDED TO DO THAT, WE INSTEAD TOOK UP A HDG THAT WOULD TAKE US TO A POINT ON THE OTHER SIDE OF THE FIELD (IE, THE SJC 303 DEG RADIAL, 16.8 DME). DURING HDOF TO APCH, APCH CTL REALIZED WE WEREN'T PROCEEDING AS DIRECTED. THEY THEN DIRECTED US TO TURN R TO A HDG TO INTERCEPT THE LOC. NO TFC CONFLICT RESULTED. WHEN ATC CLRED US TO KLIDE, THE PNF (ME) TRIED TO PROGRAM KLIDE INTO THE FMC. KLIDE WAS NOT IN THE DATABASE SO I HAD TO ENTER THE INTXN AS A RADIAL AND DME. THE PF (FO) SAID ENTER SJC 303 DEG RADIAL, 17 NM FIX. I DID THAT AND WE THEN TURNED TO A HDG THAT WOULD TAKE US TO (WHAT I THOUGHT WAS) KLIDE. NEITHER OF US REALIZED THAT WE HAD ENTERED THE INBOUND COURSE RATHER THAN THE RADIAL. WE WERE PROCEEDING ON A HDG TO THE OTHER SIDE OF THE FIELD. CONTRIBUTING FACTORS: 1) KLIDE NOT IN DATABASE. 2) CAPT NOT 'THINKING' WHEN HE ENTERED WHAT THE FO TOLD HIM TO ENTER. 3) HIGH WORKLOAD -- OCCURRED WELL INTO DSCNT WHEN A LOT OF THINGS WERE HAPPENING. 4) NOT LOOKING AT THE HDG AND ASKING 'DOES IT MAKE SENSE?' A GLANCE AT THE APCH CHART SHOULD HAVE SHOWN HDG TO BE BTWN 333-347 DEGS FROM SNS AND NOT THE 318 DEG HDG WE WERE FLYING. LESSON LEARNED: PNF SHOULD 'BACK UP' AND NOT JUST ENTER WHAT THE FO SAYS.

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.