Narrative:

I was working hemet radar combined with norton radar. ZLA 19 was handing off a regional jet on the dsnee arrival; as well as an IFR pilatus; which was descending out of ~15;000. The pilatus appeared to be on a vector to parallel the dsnee arrival. ZLA 19 is supposed to put these arrivals in trail; in a flow as one. The controller didn't coordinate anything; and when I advised my supervisor of the situation; he called the controller (or the supe?) and advised them I would not be taking the pilatus that was off the flow. The pilatus was spun and the crj ended up coming over the dsnee arrival fixes high because of the poor planning with the pilatus. The next arrival; was a B737 on the dsnee that was only given 130; not descending via the arrival.the ZLA controllers continually attempt to come up with ways of not meeting their flows; and putting the burden of in-trail separation on the hemet controllers. When we do not; or cannot; accommodate their poor planning; the results are terrible service to the next controllers and the pilots. If this situation would have happened with a sizlr arrival crossing through; it could have been a lot worse. These situations are going to result in a dangerous situation in this area.the ZLA controllers need guidance on how they need to flow M class airplanes into the airspace. Speed control seems to not be an option for them. The LOA says the aircraft shall be flowed in to hemet in trail and spaced. This needs to start happening. This is just another example of how the hemet sector is being overloaded with too many tasks.

Google
 

Original NASA ASRS Text

Title: SCT TRACON Controller reported that Los Angeles Center Controller did not follow the Letter of Agreement (LOA) with two aircraft inbound to the reporters sector.

Narrative: I was working Hemet radar combined with Norton radar. ZLA 19 was handing off a regional jet on the DSNEE arrival; as well as an IFR Pilatus; which was descending out of ~15;000. The Pilatus appeared to be on a vector to parallel the DSNEE arrival. ZLA 19 is supposed to put these arrivals in trail; in a flow as one. The Controller didn't coordinate anything; and when I advised my supervisor of the situation; he called the Controller (or the supe?) and advised them I would not be taking the Pilatus that was off the flow. The Pilatus was spun and the CRJ ended up coming over the DSNEE arrival fixes high because of the poor planning with the Pilatus. The next arrival; was a B737 on the DSNEE that was only given 130; not descending via the arrival.The ZLA controllers continually attempt to come up with ways of not meeting their flows; and putting the burden of in-trail separation on the Hemet controllers. When we do not; or cannot; accommodate their poor planning; the results are terrible service to the next controllers and the pilots. If this situation would have happened with a SIZLR arrival crossing through; it could have been a lot worse. These situations are going to result in a dangerous situation in this area.The ZLA controllers need guidance on how they need to flow M Class airplanes into the airspace. Speed control seems to not be an option for them. The LOA says the aircraft shall be flowed in to Hemet in trail and spaced. This needs to start happening. This is just another example of how the Hemet sector is being overloaded with too many tasks.

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.