A B767 flight crew fails to follow the FMS departure from lax.

Attributes
ACN	427292
Time
Date	199901
Day	Fri
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : lax
State Reference	CA
Altitude	msl bound lower : 1000 msl bound upper : 1000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	B767 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Navigation In Use	Other
Flight Phase	climbout : intermediate altitude
Route In Use	departure other departure sid : sid
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : cfi pilot : flight engineer pilot : instrument pilot : commercial
Experience	flight time last 90 days : 200 flight time total : 15000 flight time type : 5000
ASRS Report	427292
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial
Events
Anomaly	non adherence : clearance other anomaly other other spatial deviation
Independent Detector	aircraft equipment other aircraft equipment : unspecified other flight crewa
Resolutory Action	none taken : detected after the fact
Consequence	Other
Supplementary
Air Traffic Incident	Pilot Deviation

Narrative:

The new FMS departure from runway 25R sucks. The FMS did not capture on the runway and I flew .4 mi past the shoreline before I turned to a 220 degree heading. The old procedure worked fine (220 degree heading at the smo 160 degree radial/shoreline). Callback conversation with reporter revealed the following information: reporter stated his disgust for the departure as it was not accurate. He had flown it once and decided not to use it again. His complaint about the holtz 2 RNAV departure is that it does not give him the ground track that is required. The reporter admitted that the aircraft autoflt system was not properly set up to follow the departure course. The roll control was in heading hold, there was no magenta colored waypoint in front of the aircraft. Captain watched the waypoint go by and made no correction until later. Reporter also complained about missing the crossing altitude on the departure but took no steps to reduce the thrust enough to prevent an overshoot on climb out. Reporter finally stated he had his 'head up his butt.' his report about the event was submitted only because he felt he had a navigation deviation during this departure.

Original NASA ASRS Text

Title: A B767 FLC FAILS TO FOLLOW THE FMS DEP FROM LAX.

Narrative: THE NEW FMS DEP FROM RWY 25R SUCKS. THE FMS DID NOT CAPTURE ON THE RWY AND I FLEW .4 MI PAST THE SHORELINE BEFORE I TURNED TO A 220 DEG HDG. THE OLD PROC WORKED FINE (220 DEG HDG AT THE SMO 160 DEG RADIAL/SHORELINE). CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATED HIS DISGUST FOR THE DEP AS IT WAS NOT ACCURATE. HE HAD FLOWN IT ONCE AND DECIDED NOT TO USE IT AGAIN. HIS COMPLAINT ABOUT THE HOLTZ 2 RNAV DEP IS THAT IT DOES NOT GIVE HIM THE GND TRACK THAT IS REQUIRED. THE RPTR ADMITTED THAT THE ACFT AUTOFLT SYS WAS NOT PROPERLY SET UP TO FOLLOW THE DEP COURSE. THE ROLL CTL WAS IN HDG HOLD, THERE WAS NO MAGENTA COLORED WAYPOINT IN FRONT OF THE ACFT. CAPT WATCHED THE WAYPOINT GO BY AND MADE NO CORRECTION UNTIL LATER. RPTR ALSO COMPLAINED ABOUT MISSING THE XING ALT ON THE DEP BUT TOOK NO STEPS TO REDUCE THE THRUST ENOUGH TO PREVENT AN OVERSHOOT ON CLBOUT. RPTR FINALLY STATED HE HAD HIS 'HEAD UP HIS BUTT.' HIS RPT ABOUT THE EVENT WAS SUBMITTED ONLY BECAUSE HE FELT HE HAD A NAV DEV DURING THIS DEP.

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.