Narrative:

Flight was assigned the HOLTZ7 RNAV departure off of lax runway 25R. LNAV was engaged at 400 ft AGL and after the aircraft passed adore; the aircraft was turned to the next fix which was shaef. The FMC database was preloaded with the incorrect coordinates for shaef. The database used shaef (N34 00.7 W117 34.2) instead of shaef (N33 51.3 W118 33.3) which was about 170 degrees and 50 miles left and behind of aircraft position. As the aircraft turned though a heading of about 170 degrees flight crew and ATC noted the discrepancy and first officer requested a vector on course. A heading of 220 was assigned. First officer informed ATC that shaef was incorrectly loaded into database. ATC asked if we could fly to pevee; coordinates were checked; appeared correct and we accepted. Flight continued using the RNAV departure without further incident.callback conversation with reporter revealed the following information: the reporter advised that the two latitude/long coordinates were obtained from the FMC database during a post incident review by the flight crew. The second; and inappropriate; location is near ont. He clarified that the navigation display did; in fact; duplicate the path defined by the incorrect coordinates; thus describing a track direct to the incorrect location followed by a sharp 'vee shaped' track returning to pevee and then to holtz and trm.

Google
 

Original NASA ASRS Text

Title: FLT CREW OF B757-200 EXPERIENCED TRACK DEV ON HOLTZ RNAV SID FROM LAX. RPTS SHAEF WAYPOINT GROSSLY MISLOACTED IN FMS DATABASE.

Narrative: FLT WAS ASSIGNED THE HOLTZ7 RNAV DEP OFF OF LAX RWY 25R. LNAV WAS ENGAGED AT 400 FT AGL AND AFTER THE ACFT PASSED ADORE; THE ACFT WAS TURNED TO THE NEXT FIX WHICH WAS SHAEF. THE FMC DATABASE WAS PRELOADED WITH THE INCORRECT COORDINATES FOR SHAEF. THE DATABASE USED SHAEF (N34 00.7 W117 34.2) INSTEAD OF SHAEF (N33 51.3 W118 33.3) WHICH WAS ABOUT 170 DEGS AND 50 MILES L AND BEHIND OF ACFT POSITION. AS THE ACFT TURNED THOUGH A HDG OF ABOUT 170 DEGS FLT CREW AND ATC NOTED THE DISCREPANCY AND FO REQUESTED A VECTOR ON COURSE. A HDG OF 220 WAS ASSIGNED. FO INFORMED ATC THAT SHAEF WAS INCORRECTLY LOADED INTO DATABASE. ATC ASKED IF WE COULD FLY TO PEVEE; COORDINATES WERE CHKED; APPEARED CORRECT AND WE ACCEPTED. FLT CONTINUED USING THE RNAV DEP WITHOUT FURTHER INCIDENT.CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: THE RPTR ADVISED THAT THE TWO LAT/LONG COORDINATES WERE OBTAINED FROM THE FMC DATABASE DURING A POST INCIDENT REVIEW BY THE FLT CREW. THE SECOND; AND INAPPROPRIATE; LOCATION IS NEAR ONT. HE CLARIFIED THAT THE NAVIGATION DISPLAY DID; IN FACT; DUPLICATE THE PATH DEFINED BY THE INCORRECT COORDINATES; THUS DESCRIBING A TRACK DIRECT TO THE INCORRECT LOCATION FOLLOWED BY A SHARP 'VEE SHAPED' TRACK RETURNING TO PEVEE AND THEN TO HOLTZ AND TRM.

Data retrieved from NASA's ASRS site as of January 2009 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.