B767-300 captain reported his FMC failed to navigate to tralr on the STAAV6 departure out of lax.

Attributes
ACN	1297019
Time
Date	201509
Local Time Of Day	0601-1200
Place
Locale Reference	LAS.Airport
State Reference	NV
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	B767-300 and 300 ER
Operating Under FAR Part	Part 121
Flight Phase	Climb
Route In Use	SID STAAV6
Flight Plan	IFR
Component
Aircraft Component	FMS/FMC
Person 1
Function	Captain Pilot Not Flying
Qualification	Flight Crew Air Transport Pilot (ATP)
Events
Anomaly	Aircraft Equipment Problem Less Severe Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types

Narrative:

Loaded the STAAV6 departure during preflight. Noticed waypoint tralr did not load. Since this point was on the published SID and listed as a point in the release I added the point. While flying the SID as we passed waypoint staav enroute to waypoint tralr the aircraft started a right turn indicating it was 3.5 miles left of course. I directed the first officer to manually fly the AC to tralr which he did. The FMC did not recognize tralr as a fly to point even though it was depicted on the navigation display directly in front of us; instead it was navigating to nicle the next point after tralr. I questioned la center if there has been any problems with aircraft flying over tralr on the SID and he answered yes but didn't know why.it appears as some kind of FMC recognition problem with waypoint tralr.need to look into this waypoint FMC mix up. I really don't know what happened.

Original NASA ASRS Text

Title: B767-300 Captain reported his FMC failed to navigate to TRALR on the STAAV6 departure out of LAX.

Narrative: Loaded the STAAV6 departure during preflight. Noticed waypoint TRALR did not load. Since this point was on the published SID and listed as a point in the release I added the point. While flying the SID as we passed waypoint STAAV enroute to waypoint TRALR the aircraft started a right turn indicating it was 3.5 miles left of course. I directed the FO to manually fly the AC to TRALR which he did. The FMC did not recognize TRALR as a fly to point even though it was depicted on the NAV display directly in front of us; instead it was navigating to NICLE the next point after TRALR. I questioned LA Center if there has been any problems with aircraft flying over TRALR on the SID and he answered yes but didn't know why.It appears as some kind of FMC recognition problem with waypoint TRALR.Need to look into this waypoint FMC mix up. I really don't know what happened.

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