Date: 201706
Local time of day: 1801-2400
Location: SCT.TRACON, CA
Flight conditions: VMC
Light: Daylight
Aircraft: Challenger CL600
Flight plan: IFR
Flight phase: Initial Climb
Airspace: Class B LAX
ATC / advisory: TRACON SCT
Second aircraft: EMB ERJ 170/175 ER/LR
Reporter organization: Government
Reporter function: Departure
Reporter qualification: Air Traffic Control Developmental
Human factors: Distraction; Human-Machine Interface; Situational Awareness
Second reporter function: First Officer; Pilot Flying
Anomaly: Conflict Airborne Conflict; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance; Flight Crew Returned To Clearance
Contributing factors: Human Factors; Procedure
Primary problem: Human Factors

Narrative: Aircraft X departed LAX Runway 25 complex on the OSHNN7 RNAV SID. On initial contact; I turned Aircraft X to heading 190 to shorten the route for his flight and climb reference other traffic. I observed Aircraft Y; appear to be deviating from the Runway 24 complex departure course for the DARRK1 RNAV SID. I advised the Malibu Radar controller; who was responsible for Aircraft Y that Aircraft Y appeared to be deviating and immediately issued a safety alert to Aircraft X and advised a left turn to heading 160. Aircraft X reported Aircraft Y in sight.This has happened multiple times since the implementation of METRO-PLEX. These conflicts keep reoccurring and are an imminent safety threat.


Second narrative: Aircraft Y; with me as Pilot Flying was notified that we had deviated from our assigned DARRK1 SID RNAV departure from LAX runway 24L and that we had gotten within two miles of another aircraft. ATC then provided us a heading to fly and a number to call. Upon review of the FMS it was determined that the RNAV departure had been input incorrectly as an RNAV departure for runway 25L vice runway 24L.This was my leg as Pilot Flying and with my unfamiliarity with LAX I had incorrectly programmed the FMS for runway 25L DARRK1 SID vice runway 24L DARRK1 SID. Upon my brief; and through the T.O. check I was incorrectly and erroneously fixated and briefed runway 25L vice runway 24L. This error was influenced with a short taxi and a last minute intersection take-off on runway 24L/E7. An aircraft two ahead of us on taxiway E prior to taxiway E6 had an issue that required other aircraft to use taxiway E7 for takeoff and that required rerunning the takeoff numbers for runway 24L/E7. Upon reaching [destination] the Captain called ATC.Contributing factors: 1. Pilot Flying unfamiliarity with LAX contributed with the transposition of runway 25L with runway 24L.2. The distraction of redoing the takeoff data at the last minute was a contributing factor although that should have also been a reminder of the correct runway.3. We had flow into XXX from ZZZ and arrived late and were thus 11 minutes delayed. I believed that this may have also contributed to a feeling of being rushed.Avoiding Recurrence:1. Be more careful with the Before Takeoff check to ensure correct FMS SID is programmed correctly.2. Ensure that the aircraft is flying the correct RNAV and correct if wrong.3. Ask for a delay if given a last minute intersection T.O. or request those numbers ahead of time.4. Better adherence to CRM.5. If feeling rushed; slow down!


Synopsis: SCT Departure Controller and flight crew reported an aircraft departed and turned left instead of right causing an airborne conflict.