Date: 201505
Local time of day: 0001-0600
Location: NCT.TRACON, CA
Aircraft: B737 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Flight phase: Descent
Airspace: Class E ZOA
ATC / advisory: TRACON NCT
Second aircraft: Small Transport; Low Wing; 2 Turboprop Eng
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Situational Awareness; Distraction; Confusion; Communication Breakdown
Second reporter function: Approach
Anomaly: ATC Issue All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Automation Air Traffic Control; Person Air Traffic Control
When detected: In-flight
Contributing factors: Procedure; Human Factors
Primary problem: Procedure

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.


Second narrative: I was working Toga sector and had I was working toga sector and Aircraft Y departed SJC northbound on the SUNOL departure to 5000 feet going to grove sector.  Grove sector had Aircraft X descending northwest bound to on the EMZOH arrival to OAK to 4100 feet.  Aircraft Y crossed too close to Aircraft X and separation was lost.  Closest proximity was 1.2 miles and 800 feet.  I failed to use the new procedure of taking the aircraft off the departure and giving them a vector east of a fix called MYSHIN. I was notified by management of the loss; and told it would have made no difference because Aircraft X was not restricted from descending and there would not have been divergence.I'm not sure; possibly modify the EMZOH arrival to protect for SUNOL departure/v334 airway IFR traffic; or modify the SUNOL departure.


Synopsis: 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.