Date: 201204
Local time of day: 1801-2400
Location: LAX.Airport, CA
Aircraft: Falcon 2000
Operator: Corporate
Operating under: Part 91
Flight plan: IFR
Flight phase: Initial Climb
Airspace: Class B LAX
ATC / advisory: Tower LAX
Second aircraft: B737 Undifferentiated or Other Model
Reporter organization: Government
Reporter function: Local
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness; Communication Breakdown
Second reporter function: Pilot Flying; Captain
Anomaly: Conflict Airborne Conflict; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Became Reoriented
Contributing factors: Aircraft; Human Factors
Primary problem: Human Factors

Narrative: I cleared a Falcon 2000 for take off on Runway 25R on the HOLTZ9 RNAV departure with way points. As I was working my departure line up; using visual separation where needed; and working the arrival traffic on Runway 25L; I was scanning my RADAR before changing the Falcon to Departure frequency. I then noticed that the Falcon was drifting north of course when at that point; he was suppose to begin a left turn heading approximately 220. At that point I issued a Traffic Alert to the Falcon for traffic off his right wing climbing off the north complex Runway 24L. I told him to turn left heading 180 immediately. I then called the Local 2 Controller to issue the alert; but he stated that the departing aircraft was already transferred to Departure frequency. I then coordinated the 180 heading on the Falcon. I observed the turn on the Falcon and then issued Departure frequency. I am not sure what I would recommend simply because I am not sure whether or not the pilot loaded the correct way points from the runway he used or not. We were having problems with this airline doing the same thing on departure. It's possible that since the aircraft was probably assigned Runway 25L since he taxied from the area off of Taxiway Alfa and the nearest runway is Runway 25L; he may have loaded the wrong runway on his FMS when I in fact departed him from Runway 25R. I don't recall whether or not I vividly stated that he would depart Runway 25R instead of Runway 25L. If in fact the aircraft loaded the wrong data from the wrong runway; I don't suspect that the aircraft would turn right if Runway 25L was loaded. Maybe if he loaded Runway 24L or 24R in his FMS; the plane would in fact start a slight right turn. Nonetheless; maybe if we verified the way point to RNAV aircraft; it would lessen the possibility of human factor mistakes and provide another link in the chain.


Second narrative: Departing LAX on the Holtz 9 SID. FMS setup to depart Runway 25L got a runway change to 25R. After departing from 25R FMS was commanding a right turn and should have taken us left. After correcting to left a vector was giving by ATC. After reviewing with crew; it was determined that somewhere in the runway change programming the auto sequence was inhibited; and that led to the wrong vectoring from FMS.


Synopsis: LAX Controller described a potential conflict when a departure from Runway 25R on the HOLTZ9 SID initiated a wrong turn; the pilot reporter noting an incorrect aircraft FMS departure runway entry may have caused the event.