A300 airbus flight crew has track heading deviation during border 5 departure from san.

Attributes
ACN	704392
Time
Date	200607
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : san.airport
State Reference	CA
Altitude	msl single value : 2500
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : sct.tracon
Operator	common carrier : air carrier
Make Model Name	A300
Operating Under FAR Part	Part 121
Navigation In Use	other
Flight Phase	climbout : intermediate altitude climbout : initial
Route In Use	departure sid : brdr
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : flight engineer pilot : atp
Experience	flight time last 90 days : 90 flight time total : 8500 flight time type : 1600
ASRS Report	704392
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Events
Anomaly	non adherence : clearance non adherence : published procedure other spatial deviation
Independent Detector	other controllerb other flight crewa other flight crewb
Resolutory Action	controller : issued advisory flight crew : returned to intended or assigned course flight crew : returned to original clearance
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	Aircraft Flight Crew Human Performance
Primary Problem	Aircraft

Narrative:

Departed runway 9 in navigation mode on the border 5 SID. Both FMS and commercial chart SID depiction showed 'after takeoff fly heading 090 degrees to intercept the mzb 096 degree radial to brows intersection.' takeoff was normal and FMS was directing a 090 degree heading as per the SID. At about 2700 ft MSL; the aircraft deviated from the programmed flight path and started a l-hand turn back to 090 degrees. At the same time socal departure asked if we were in a l-hand turn. I responded that we were correcting back to the right. Socal asked what the problem was because the previous airbus (that departed 15-20 mins before us) had done the same thing. I replied that I thought that it was an FMS or flight director problem. Socal then gave us direct brows intersection. Prior to departure; the flight plan page showed the 090 degree heading til intercepting the radial. When the aircraft started deviating from the 090 degree heading; the first officer's navigation display showed a line (either heading or radial; we weren't sure which) to the left of our position. The captain's navigation display only showed brows intersection. Flight standards is looking into a probable cause for the FMS deviation. Crew could be more vigilant and quicker to respond when aircraft deviates from the programmed flight path.

Original NASA ASRS Text

Title: A300 AIRBUS FLT CREW HAS TRACK HDG DEV DURING BORDER 5 DEP FROM SAN.

Narrative: DEPARTED RWY 9 IN NAV MODE ON THE BORDER 5 SID. BOTH FMS AND COMMERCIAL CHART SID DEPICTION SHOWED 'AFTER TKOF FLY HDG 090 DEGS TO INTERCEPT THE MZB 096 DEG RADIAL TO BROWS INTXN.' TKOF WAS NORMAL AND FMS WAS DIRECTING A 090 DEG HDG AS PER THE SID. AT ABOUT 2700 FT MSL; THE ACFT DEVIATED FROM THE PROGRAMMED FLT PATH AND STARTED A L-HAND TURN BACK TO 090 DEGS. AT THE SAME TIME SOCAL DEP ASKED IF WE WERE IN A L-HAND TURN. I RESPONDED THAT WE WERE CORRECTING BACK TO THE R. SOCAL ASKED WHAT THE PROB WAS BECAUSE THE PREVIOUS AIRBUS (THAT DEPARTED 15-20 MINS BEFORE US) HAD DONE THE SAME THING. I REPLIED THAT I THOUGHT THAT IT WAS AN FMS OR FLT DIRECTOR PROB. SOCAL THEN GAVE US DIRECT BROWS INTXN. PRIOR TO DEP; THE FLT PLAN PAGE SHOWED THE 090 DEG HDG TIL INTERCEPTING THE RADIAL. WHEN THE ACFT STARTED DEVIATING FROM THE 090 DEG HDG; THE FO'S NAV DISPLAY SHOWED A LINE (EITHER HDG OR RADIAL; WE WEREN'T SURE WHICH) TO THE L OF OUR POS. THE CAPT'S NAV DISPLAY ONLY SHOWED BROWS INTXN. FLT STANDARDS IS LOOKING INTO A PROBABLE CAUSE FOR THE FMS DEV. CREW COULD BE MORE VIGILANT AND QUICKER TO RESPOND WHEN ACFT DEVIATES FROM THE PROGRAMMED FLT PATH.

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.