A non-GPS B767-300 departed on the lax runway 25R holtz 9 RNAV and had a map shift at about 600 ft w...

Narrative:

[We] departed lax on the holtz 9. Aircraft had the left eec on MEL which required both eec's to be turned off and also required that thrust be set manually for takeoff without the use of auto-throttles for departure. Clearance delivery had changed the routing and departure from LAXX6 to the holtz 9. Our weight and balance document had commanded a packs off takeoff for runway 25R. Weather was SCT160 270/07KT 10 SM. An aircraft full alignment was performed at the gate approximately 20 minutes from push and NOTAMS were read. Waypoints; speed; and altitude constraints were verified by both pilots for the HOLTZ9 and the captain briefed the altitude restrictions/hold downs for our departure; this was his leg. He selected LNAV and VNAV during his preflight brief. Taxi out was busy with multiple aircraft being re-sequenced for departure while on taxi-out. The HSI/map showed the aircraft symbol in the appropriate spot while taxing onto the runway. Takeoff was performed with my concentration on fine tuning the thrust levers; verifying packs where off; and making my call outs. At 500 ft I verbalized that LNAV had captured and climbout appeared normal straight ahead. At 900 ft the captain commented that the flight director was commanding a turn to the northwest toward dockr. I was setting climb power and the flaps when I noticed that the captain had made a smaller than commanded turn partially toward dockr. At that point he commented that our track/turn didn't feel right and immediately corrected back toward runway heading. Just after that ATC (socal) gave us a turn toward the south to the fix pevee or one near it (they made no mention or comment if we had deviated from course). The packs were placed on and the after takeoff checklist was completed. No other navigational errors or map shifts were noted for the remainder of the flight. Preventive measure I'm not sure what could have been done differently in this high workload environment. I have never experienced a map shift before. Possible limit non-GPS aircraft from close-in RNAV departures (especially with no updating until airborne) or increased training or awareness of possibility of map shift at lax.

Original NASA ASRS Text

Title: A non-GPS B767-300 departed on the LAX Runway 25R HOLTZ 9 RNAV and had a map shift at about 600 FT which the crew recognized as causing an erroneous heading command. They quickly corrected back to track with no comment from ATC.

Narrative: [We] departed LAX on the HOLTZ 9. Aircraft had the left EEC on MEL which required both EEC's to be turned OFF and also required that thrust be set manually for takeoff without the use of auto-throttles for departure. Clearance Delivery had changed the routing and departure from LAXX6 to the HOLTZ 9. Our weight and balance document had commanded a Packs OFF takeoff for Runway 25R. Weather was SCT160 270/07KT 10 SM. An Aircraft full alignment was performed at the gate approximately 20 minutes from push and NOTAMS were read. Waypoints; speed; and altitude constraints were verified by both pilots for the HOLTZ9 and the Captain briefed the altitude restrictions/hold downs for our departure; this was his leg. He selected LNAV and VNAV during his preflight brief. Taxi out was busy with multiple aircraft being re-sequenced for departure while on taxi-out. The HSI/Map showed the aircraft symbol in the appropriate spot while taxing onto the runway. Takeoff was performed with my concentration on fine tuning the thrust levers; verifying packs where off; and making my call outs. At 500 FT I verbalized that LNAV had captured and climbout appeared normal straight ahead. At 900 FT the Captain commented that the Flight Director was commanding a turn to the northwest toward DOCKR. I was setting climb power and the flaps when I noticed that the Captain had made a smaller than commanded turn partially toward DOCKR. At that point he commented that our track/turn didn't feel right and immediately corrected back toward runway heading. Just after that ATC (SOCAL) gave us a turn toward the south to the fix PEVEE or one near it (they made no mention or comment if we had deviated from course). The Packs were placed ON and the after takeoff checklist was completed. No other navigational errors or map shifts were noted for the remainder of the flight. Preventive Measure I'm not sure what could have been done differently in this high workload environment. I have never experienced a map shift before. Possible limit non-GPS aircraft from close-in RNAV departures (especially with no updating until airborne) or increased training or awareness of possibility of map shift at LAX.

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

Attributes
ACN	989571
Time
Date	201201
Local Time Of Day	1201-1800
Place
Locale Reference	LAX.Airport
State Reference	CA
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	B767-300 and 300 ER
Operating Under FAR Part	Part 121
Flight Phase	Initial Climb
Route In Use	Direct SID HOLTZ NINE
Flight Plan	IFR
Component
Aircraft Component	FMS/FMC
Person 1
Function	Pilot Not Flying First Officer
Qualification	Flight Crew Air Transport Pilot (ATP) Flight Crew Flight Instructor Flight Crew Instrument Flight Crew Multiengine Flight Crew Flight Engineer
Experience	Flight Crew Last 90 Days 68 Flight Crew Total 8500 Flight Crew Type 1693
Events
Anomaly	Aircraft Equipment Problem Less Severe Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance Deviation - Track / Heading All Types

A non-GPS B767-300 departed on the lax runway 25R holtz 9 RNAV and had a map shift at about 600 ft which the crew recognized as causing an erroneous heading command. They quickly corrected back to track with no comment from ATC.