Narrative:

Aircraft X was landing lax over gramm intersection on the riivr arrival. We were time based metering to lax and the controller at R20 issued a speed of 250 knots to follow another aircraft I was working over konzl. Aircraft X was about 2;000ft high over gramm because of the speed reduction. The controller at feeder vectored aircraft X into my airspace; 19; without a point out. The controller vectored aircraft X past the localizer; which is against the LOA. The feeder controller called R20 and told him he needed the aircraft over gramm at the altitudes in the LOA. The flm for arrivals area at sct also called our flm to tell him we need to have the aircraft make their restrictions. The R20 controller told the feeder controller something like ok or wilco when the coordination took place.we have been having major problems with arrivals area. This morning we had several unsafe situations because of last minute calls from feeder to spin aircraft. We also could not get ahold of them on the line this morning after repeatedly attempting and finally; sector 20 went into holding because of the unsafe situation feeder was placing us in. Many controllers are aware that certain crews that work arrivals area are more jumpy and maybe not as comfortable with high volumes of traffic so we get spun more frequently from that crew. We attempt to accommodate a 'staggered' flow over konzl/gramm in order to avoid being spun; which is not in the LOA. I am aware that not all controllers do this; but I feel most controllers would rather try to give approach what they want and not have to spin several aircraft. If a controller at sct feels that the LOA is not sufficient for flow control or doesn't meet their needs; there are ways to fix this. This needs to be addressed in another manner; not at the sector.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZLA controller describes situation where SCT arrival Controller vectors an aircraft into ZLA's airspace without a point out.

Narrative: Aircraft X was landing LAX over Gramm intersection on the RIIVR arrival. We were Time Based metering to LAX and the controller at R20 issued a speed of 250 knots to follow another aircraft I was working over Konzl. Aircraft X was about 2;000ft high over Gramm because of the speed reduction. The controller at Feeder vectored Aircraft X into my airspace; 19; without a point out. The controller vectored Aircraft X past the localizer; which is against the LOA. The feeder controller called R20 and told him he needed the aircraft over Gramm at the Altitudes in the LOA. The FLM for arrivals area at SCT also called our FLM to tell him we need to have the aircraft make their restrictions. The R20 controller told the feeder controller something like OK or WILCO when the coordination took place.We have been having major problems with Arrivals Area. This morning we had several unsafe situations because of last minute calls from Feeder to spin aircraft. We also could not get ahold of them on the line this morning after repeatedly attempting and finally; sector 20 went into holding because of the unsafe situation Feeder was placing us in. Many controllers are aware that certain crews that work Arrivals area are more jumpy and maybe not as comfortable with high volumes of traffic so we get spun more frequently from that crew. We attempt to accommodate a 'staggered' flow over KONZL/GRAMM in order to avoid being spun; which is not in the LOA. I am aware that not all controllers do this; but I feel most controllers would rather try to give approach what they want and not have to spin several aircraft. If a controller at SCT feels that the LOA is not sufficient for flow control or doesn't meet their needs; there are ways to fix this. This needs to be addressed in another manner; not at the sector.

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.