Narrative:

I was working the mulford/grove (3g/3m) sectors combined. I received aircraft X descending via the EMZOH1 arrival except maintaining 060 after myshn from the sunol (3s) sector. When aircraft X came onto my frequency he checked in just descending via on the runway 30 transition. I responded with descend via the EMZOH1 arrival to reduce verbiage from having these new procedures and many pilots misunderstanding restrictions with the optimization of airspace and procedures in the metroplex (oapm) descend via procedures having them just been implemented. I received aircraft Y from toga (1t) sector climbing to 050. Aircraft Y's exit route to me was radar vectors east of myshn at 050. Aircraft X crossed myshn at 060 as aircraft Y turned to a 340 heading to join V334 at 050 instead of being vectored east of myshn per the SOP toga (1t) to mulford (3m) exit routes. I issued traffic to aircraft X for aircraft Y who was crossing left to right in front of him at 050. As aircraft X passed myshn at 060 I believed I had stopped aircraft X's EMZOH1 descend via clearance at 060; I was wrong. As aircraft X descended thru 058 and aircraft Y passed beneath him I realized my mistake and notified my front line manager (flm) of my error.I recommend that the aircraft on the EMZOH1 arrival be given the myshn @ 060 descend via clearance restriction when necessary and stay on that clearance at 060 until clear of traffic turning northbound at 050 or vectored east of myshn at 050 to ensure separation.

Google
 

Original NASA ASRS Text

Title: Northern California TRACON (NCT) Controllers report of a loss of separation due to him not having an aircraft maintain an altitude until crossing/lower traffic had passed. The controller thought he told aircraft to maintain specific altitude but did not. The other controller failed to use the new procedure and vector the aircraft past a fix to avoid the inbound aircraft.

Narrative: I was working the Mulford/Grove (3g/3m) sectors combined. I received Aircraft X descending via the EMZOH1 arrival except maintaining 060 after MYSHN from the SUNOL (3s) sector. When Aircraft X came onto my frequency he checked in just descending via on the runway 30 transition. I responded with descend via the EMZOH1 arrival to reduce verbiage from having these new procedures and many pilots misunderstanding restrictions with the Optimization of Airspace and Procedures in the Metroplex (OAPM) descend via procedures having them just been implemented. I received Aircraft Y from TOGA (1t) sector climbing to 050. Aircraft Y's exit route to me was radar vectors east of MYSHN at 050. Aircraft X crossed MYSHN at 060 as Aircraft Y turned to a 340 heading to join V334 at 050 instead of being vectored east of MYSHN per the SOP TOGA (1t) to MULFORD (3m) exit routes. I issued traffic to Aircraft X for Aircraft Y who was crossing left to right in front of him at 050. As Aircraft X passed MYSHN at 060 I believed I had stopped Aircraft X's EMZOH1 descend via clearance at 060; I was wrong. As Aircraft X descended thru 058 and Aircraft Y passed beneath him I realized my mistake and notified my Front Line Manager (FLM) of my error.I recommend that the aircraft on the EMZOH1 arrival be given the MYSHN @ 060 descend via clearance restriction when necessary and stay on that clearance at 060 until clear of traffic turning northbound at 050 or vectored east of MYSHN at 050 to ensure separation.

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.