Narrative:

Aircraft X was under the control of socal TRACON; arrivals area; when it entered sector 21 airspace west of pdz passing through 16;500 (I own 140 and above; sct owns 130 and below) without a point out. This same aircraft also entered area B; sector 18's airspace without a point out. This is simply one example of a systemic problem with la arrival traffic on the mid shift not being pointed out from the sct arrivals area to area east. Again; this issue exists only on the mid shift; not during the day.I have personally attempted over the last year to resolve this issue in a more friendly and informal manner by trying to work outside official channels (i.e. Communicating with controllers from sct outside work; having a flm that used to work there reach out to someone they knew; all in the effort to keep things friendly) but the problem persists. Other controllers who work mid shifts on other nights of the week are having the same issues. I don't know what else to do at this point other than to file this report.if the traffic is not being kept inside sct airspace; we would like to receive a point out on the traffic. After reviewing the lax redeye 2 STAR; it seems that the problem is that the altitudes on the STAR do not contain the aircraft within the vertical limits of sct airspace. As a result; whatever clearance is being issued by sct (descend via? Some other crossing restriction?) results in an airspace deviation if the aircraft doesn't start down early or if the controller does not manage the descent with some other clearance to keep the traffic inside their airspace. Re-working the altitudes of the STAR to contain the traffic within sct airspace would be a longer-term solution.

Google
 

Original NASA ASRS Text

Title: ZLA Controller reports of airspace violations that happen on the mid-shift with SCT controllers violating ZLA's airspace.

Narrative: Aircraft X was under the control of SoCal TRACON; Arrivals area; when it entered Sector 21 airspace west of PDZ passing through 16;500 (I own 140 and above; SCT owns 130 and below) without a point out. This same aircraft also entered Area B; Sector 18's airspace without a point out. This is simply one example of a systemic problem with LA arrival traffic on the mid shift not being pointed out from the SCT Arrivals area to Area E. Again; this issue exists only on the mid shift; not during the day.I have personally attempted over the last year to resolve this issue in a more friendly and informal manner by trying to work outside official channels (i.e. communicating with controllers from SCT outside work; having a FLM that used to work there reach out to someone they knew; all in the effort to keep things friendly) but the problem persists. Other controllers who work mid shifts on other nights of the week are having the same issues. I don't know what else to do at this point other than to file this report.If the traffic is not being kept inside SCT airspace; we would like to receive a point out on the traffic. After reviewing the LAX Redeye 2 STAR; it seems that the problem is that the altitudes on the STAR do not contain the aircraft within the vertical limits of SCT airspace. As a result; whatever clearance is being issued by SCT (descend VIA? some other crossing restriction?) results in an airspace deviation if the aircraft doesn't start down early or if the controller does not manage the descent with some other clearance to keep the traffic inside their airspace. Re-working the altitudes of the STAR to contain the traffic within SCT airspace would be a longer-term solution.

Data retrieved from NASA's ASRS site 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.