Narrative:

I was working hmtr and was somewhat busy and it was somewhat complex. I had three air carriers all descending on the dsnee arrival and I had just worked out a sequence. There were some outlying thunderstorms around the area; but I don't think they were too much of a factor. There might have been one or two VFR aircraft that were enroute and a couple of skydiving aircraft in the sector. Aircraft X departed ont on the RAJEE1 departure and I took the handoff from ralr where the pilot climbs to 7;000 to stay under the dsnee arrivals which descend to 8;000. When aircraft X checked in I saw the conflict and reluctantly climbed aircraft X via the departure except to maintain 14;000. I say reluctantly because I just don't like the climb vs the descend via in this case because it's setting the pilot up for failure; exactly what happened here.after issuing the clearance to climb via; I listened for the read back. I went and exchanged traffic to both aircraft (and included a gulfstream that was behind aircraft Y). I intently watched because it's such a hot spot with this arrival vs departure. I think I was in the middle of calling traffic to the gulfstream when I noticed aircraft X climbing. I saw 7;100; 7;300 and in mid transmission issued a traffic alert and an immediate descent clearance. I believe I was blocked once or twice maybe even three times so I restated my traffic alert and descent clearance. I heard someone say the word 'TCAS;' but I don't know if someone got a TCAS RA or if someone was just trying to say they saw someone on their TCAS. I even want to say aircraft X had aircraft Y in sight. Once aircraft X descended back to 7;000 and cleared the other traffic I used an unrestricted climb to 14;000. I notified my front line manager (flm) of the situation and subsequently issued the brasher warning to aircraft X.to me this is an optimization of airspace and procedures in the metroplex (oapm) issue. We're setting them up for failure. The crossing restriction at rajee is the most frequently broken crossing restriction of all the descend/climb via's in the empire airspace. I don't know why. Even more puzzling is why the aircraft X pilot busted his altitude restriction when he knew there was traffic. I want to say that I had even told the pilot of the gulfstream specifically that aircraft X was going to stay level until crossing his course hoping to clue the aircraft X pilot should he have climbed through his restriction. It was probably too late at that point.I'd also like to take this opportunity to say the fix rajee should be on the empire map permanently. You can access it via depressing a series of buttons; which is helpful; but personally; I think it should be a fix that's permanently displayed. It's rather important. Especially seeing as how we still have a handful of other fixes that we don't ever or very rarely ever use. To add to that; there's zero doubt in my mind that aircraft X had passed or was even close to the rajee fix (that's not on the map) where he could have climbed.a side note; after talking with the ralr controller about this scenario (several minutes after this all happened); he said that aircraft X had leveled off at 4;000 initially and had to be told to climb and maintain 7;000. Apparently he didn't check in climbing via the RAJEE1. He might have had the old departure that ont had used for years plugged into his FMS. Or possibly ont clearance delivery read him the wrong departure. I checked the flight plan; the data block; everything showed to me he was on the RAJEE1 departure.

Related reports:

Google
 

Original NASA ASRS Text

Title: SCT Controller and air carrier flight crew reported missing a crossing restriction when given a climb via clearance.

Narrative: I was working HMTR and was somewhat busy and it was somewhat complex. I had three air carriers all descending on the DSNEE arrival and I had just worked out a sequence. There were some outlying thunderstorms around the area; but I don't think they were too much of a factor. There might have been one or two VFR aircraft that were enroute and a couple of skydiving aircraft in the sector. Aircraft X departed ONT on the RAJEE1 departure and I took the handoff from RALR where the pilot climbs to 7;000 to stay under the DSNEE arrivals which descend to 8;000. When Aircraft X checked in I saw the conflict and reluctantly climbed Aircraft X via the departure except to maintain 14;000. I say reluctantly because I just don't like the climb vs the descend via in this case because it's setting the pilot up for failure; exactly what happened here.After issuing the clearance to climb via; I listened for the read back. I went and exchanged traffic to both aircraft (and included a Gulfstream that was behind Aircraft Y). I intently watched because it's such a hot spot with this arrival vs departure. I think I was in the middle of calling traffic to the Gulfstream when I noticed Aircraft X climbing. I saw 7;100; 7;300 and in mid transmission issued a traffic alert and an immediate descent clearance. I believe I was blocked once or twice maybe even three times so I restated my traffic alert and descent clearance. I heard someone say the word 'TCAS;' but I don't know if someone got a TCAS RA or if someone was just trying to say they saw someone on their TCAS. I even want to say Aircraft X had Aircraft Y in sight. Once Aircraft X descended back to 7;000 and cleared the other traffic I used an unrestricted climb to 14;000. I notified my Front Line Manager (FLM) of the situation and subsequently issued the Brasher Warning to Aircraft X.To me this is an Optimization of Airspace and Procedures in the Metroplex (OAPM) issue. We're setting them up for failure. The crossing restriction at RAJEE is the most frequently broken crossing restriction of all the descend/climb via's in the Empire airspace. I don't know why. Even more puzzling is why the Aircraft X pilot busted his altitude restriction when he knew there was traffic. I want to say that I had even told the pilot of the Gulfstream specifically that Aircraft X was going to stay level until crossing his course hoping to clue the Aircraft X pilot should he have climbed through his restriction. It was probably too late at that point.I'd also like to take this opportunity to say the fix RAJEE should be on the Empire map permanently. You can access it via depressing a series of buttons; which is helpful; but personally; I think it should be a fix that's permanently displayed. It's rather important. Especially seeing as how we still have a handful of other fixes that we don't ever or very rarely ever use. To add to that; there's zero doubt in my mind that Aircraft X had passed or was even close to the RAJEE fix (that's not on the map) where he could have climbed.A side note; after talking with the RALR controller about this scenario (several minutes after this all happened); he said that Aircraft X had leveled off at 4;000 initially and had to be told to climb and maintain 7;000. Apparently he didn't check in climbing via the RAJEE1. He might have had the old departure that ONT had used for years plugged into his FMS. Or possibly ONT clearance delivery read him the wrong departure. I checked the flight plan; the data block; everything showed to me he was on the RAJEE1 departure.

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.