A320
Air Traffic Control Fully Certified
Situational Awareness
ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
General None Reported / Taken
Human Factors; ATC Equipment / Nav Facility / Buildings; Procedure
An A320 departed Runway 25 from LAX on the LOOP SIX departure (non-RNAV SID). A B737-700 departed Runway 24 simultaneously with the A320. The LOOP SIX departure has Runway 25 departures; 'Climb heading 250 to cross SMO VOR/DME R-160 at or below 3;000 [feet]; then turn left heading 235 expect RADAR vectors.' Having received this information long after the event; I don't recall having any issue with this departure. However; upon reviewing the replay; I noticed the following: On the replay display; the centerlines of both runways are displayed; which are not displayed on my scope and it appears that the A320 did turn north of the 250 degree heading for approximately a mile prior to turning to his 235 degree heading. Having worked in the area for 15 years; I am used to occasionally seeing an erroneous RADAR hit that makes it appear the aircraft are off course having the next hit show that the aircraft is indeed in the correct position. Also; the display I reviewed was at a 10 mile range while I look at a 33 mile range on my scope so to see the slight turn north is very difficult. If anything; this was a pilot deviation as indicated by the turn north of the aircraft. The best way to prevent this from happening again is to convene a work group of controllers from LAX Tower and SCT to review and rewrite the departure procedures off of the LAX airport. Possibly preventing simultaneous departures from the 2 complexes; or having the Tower ensure the aircraft on non-RNAV SID's make the turn prior to switching the aircraft to SCT.
SCT Controller was notified of a loss of separation that had been discovered during a post event review long after the fact; the reporter claiming the tools available to the Controller are not as precise as those used during the post event reviews.