Narrative:

Captain's leg. Captain entered present position into FMS/INS system at gate of departure airport (phog). First officer verified present position and route data. While en route to intercept the JULLE4 arrival into hnl, center cleared us to a fix not designated on the julle arrival, then the JULLE4. Captain, while flying manual, entered the oddball fix (sakki) into the FMS and executed 'direct to.' the only problem was that the 'sakki' in the database was 2000 mi from hawaii! Being geographically near 'sakki' intersection, the controller queried us as to if tracking to sakki? We discovered we were going to sakki somewhere else, downgraded to 'radio' and completed the flight uneventfully. When a controller clears a flight to a fix on a different arrival, when departure airport and arrival airports are close by, there will be enhanced possibility of error. Callback conversation with reporter revealed the following information: reporter states the WX was kind of 'funkie.' the captain was new to the area and had no knowledge of the arrs, that was part 1. Part 2 was that the fix which controller assigned is on another arrival chart, the SAKKI4 arrival. Reporter feels controllers should not use a fix which is not on the arrival chart in use. Part 3 is that the FMC opted for a sakki fix which is near japan, not honolulu. All of this made for a very strange few mins. Reporter would like to see a change made whereby controllers use information which is on the arrival chart in use only, and maybe change one of the sakki fixes. Aircraft was an L1011.

Related reports:

Google
 

Original NASA ASRS Text

Title: L1011 FLC IS ASSIGNED A FIX WHICH IS NOT SHOWN ON THE ARR CHART IN USE. ENTERED FIX INTO FMS TO DISCOVER THEY ARE INDICATING A FIX 2000 MI AWAY.

Narrative: CAPT'S LEG. CAPT ENTERED PRESENT POS INTO FMS/INS SYS AT GATE OF DEP ARPT (PHOG). FO VERIFIED PRESENT POS AND RTE DATA. WHILE ENRTE TO INTERCEPT THE JULLE4 ARR INTO HNL, CTR CLRED US TO A FIX NOT DESIGNATED ON THE JULLE ARR, THEN THE JULLE4. CAPT, WHILE FLYING MANUAL, ENTERED THE ODDBALL FIX (SAKKI) INTO THE FMS AND EXECUTED 'DIRECT TO.' THE ONLY PROB WAS THAT THE 'SAKKI' IN THE DATABASE WAS 2000 MI FROM HAWAII! BEING GEOGRAPHICALLY NEAR 'SAKKI' INTXN, THE CTLR QUERIED US AS TO IF TRACKING TO SAKKI? WE DISCOVERED WE WERE GOING TO SAKKI SOMEWHERE ELSE, DOWNGRADED TO 'RADIO' AND COMPLETED THE FLT UNEVENTFULLY. WHEN A CTLR CLRS A FLT TO A FIX ON A DIFFERENT ARR, WHEN DEP ARPT AND ARR ARPTS ARE CLOSE BY, THERE WILL BE ENHANCED POSSIBILITY OF ERROR. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATES THE WX WAS KIND OF 'FUNKIE.' THE CAPT WAS NEW TO THE AREA AND HAD NO KNOWLEDGE OF THE ARRS, THAT WAS PART 1. PART 2 WAS THAT THE FIX WHICH CTLR ASSIGNED IS ON ANOTHER ARR CHART, THE SAKKI4 ARR. RPTR FEELS CTLRS SHOULD NOT USE A FIX WHICH IS NOT ON THE ARR CHART IN USE. PART 3 IS THAT THE FMC OPTED FOR A SAKKI FIX WHICH IS NEAR JAPAN, NOT HONOLULU. ALL OF THIS MADE FOR A VERY STRANGE FEW MINS. RPTR WOULD LIKE TO SEE A CHANGE MADE WHEREBY CTLRS USE INFO WHICH IS ON THE ARR CHART IN USE ONLY, AND MAYBE CHANGE ONE OF THE SAKKI FIXES. ACFT WAS AN L1011.

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.