Date: 201703
Local time of day: 1201-1800
Location: ZLA.ARTCC, CA
Light: Daylight
Aircraft: Regional Jet 200 ER/LR (CRJ200)
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Descent
Airspace: Class E ZLA
ATC / advisory: Center ZLA
Second aircraft: Regional Jet 200 ER/LR (CRJ200)
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Troubleshooting; Situational Awareness; Distraction; Confusion; Human-Machine Interface
Second reporter function: Enroute
Anomaly: ATC Issue All Types; Airspace Violation All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Separated Traffic
Contributing factors: Procedure
Primary problem: Procedure

Narrative: I was working R13 and descended Aircraft X to TANDY at 130. The Aircraft (AC) was pointed out to sector 14. The R14 controller and I were surprised that an aircraft on the ORCKA departure auto popped climbing through 121 to 150 in Sector 14's airspace without a point out from SoCal or from Sector 18. We were unsure of who's responsibility that was and as to which controller had actually given the climb instruction or if the AC was climbing via a SID.I think it was the very next aircraft; Aircraft Y; we (R14 and myself and the Controller In Charge) were watching because he had the same departure and sure enough that aircraft also auto popped to Sector 14 and was now traffic from my TANDY arrival. I called the traffic to Aircraft X; who I was talking to; but was unsure of what altitude the other aircraft was climbing to. I then realized a loss of separation was going to occur. I told Aircraft X to maintain visual separation from the traffic and he complied. If these aircraft are climbing out via a SID; that SID is not separated from 14's airspace. SoCal or sector 18; must initiate a point out as those aircraft climbing are traffic for the TANDY and LEENA arrivals. This is an unsafe situation that needs to be addressed as soon as possible. The sector 13 controller will not see the traffic auto pop until it is possibly too late. The aircraft climbing out on the ORCKA will auto pop to sector 14; then 14 has to call traffic to sector 13 for their arrivals.


Second narrative: [Two aircraft] were LAX departures climbing via the ORCKA1 SID. Aircraft X was on the TANDY4 arrival with a restriction to cross TANDY at 130. SCT departures' airspace limit has been reduced by 1000 ft. With sector 14 from 130 to 120. Both departure aircraft entered the confines of sector 14's lateral limits while still climbing without a point out from departures. There was never a loss of standard separation; but that was by luck of the position of the aircraft at the time of the event. The combination of the new climb via departure mixed with the airspace change is what likely caused confusion for the SCT controller. More time to learn and understand all aspects of the departures and airspace would likely help. Also; I'm not sure if one already exists; but an 'at or below' restriction to miss 14's airspace and traffic would be great on the ORCKA1 SID.


Synopsis: ZLA controllers reported an airborne conflict when a departure aircraft entered their airspace without proper handoff from SCT TRACON.