Narrative:

Aircraft X was released for departure off of runway 30 sql; VFR downwind procedure. Aircraft Y was VFR inbound about 15 east of san carlos airport. Aircraft Z was IFR inbound on an instrument approach about 20 east of sql. Aircraft X departed sql and executed a climb to 2;100 heading 120 as prescribed but never checked onto departure frequency 135.65 (woodside sector). Subsequently; aircraft X climbed into and merged with aircraft Y at 2;100/2;200 feet. I contacted sql tower to try switching him again; they said they had. I broadcast on guard to aircraft X to contact nct on guard; at which point he keyed up finally on my frequency. By this point aircraft X had possibly lost lateral separation with aircraft Z who was inbound to sql over pao descending out of 3;100 feet.aircraft X was issued a climb and turn to heading 250. I then withheld the climb to 5;000 feet and restricted aircraft X to 2;100 in reference to aircraft Z. Once it appeared as though divergence had been established aircraft X was issued a climb to 5;000. By this point aircraft X was approaching an MVA of 3;000 and another shelf of 4;000. Aircraft X was vectored to the northwest in reference to the MVA thus again causing a loss of lateral separation with aircraft Z who was still descending inbound to sql.the 'VFR downwind' IFR departure route out of sql is a questionable procedure to begin with. It allows aircraft on an IFR flight plan to depart in VFR conditions and turn out to the southeast towards incoming traffic into sfo and sql; making it essentially an opposite direction departure.

Related reports:

Google
 

Original NASA ASRS Text

Title: An NCT Controller reported releasing a departure on a departure procedure which reverses course towards inbound traffic. The pilot of the departing aircraft did not contact the Controller in time for the Controller to vector the departure out of the way of two arrivals.

Narrative: Aircraft X was released for departure off of Runway 30 SQL; VFR downwind procedure. Aircraft Y was VFR inbound about 15 east of San Carlos Airport. Aircraft Z was IFR inbound on an instrument approach about 20 east of SQL. Aircraft X departed SQL and executed a climb to 2;100 heading 120 as prescribed but never checked onto departure frequency 135.65 (Woodside sector). Subsequently; Aircraft X climbed into and merged with Aircraft Y at 2;100/2;200 feet. I contacted SQL Tower to try switching him again; they said they had. I broadcast on guard to Aircraft X to contact NCT on guard; at which point he keyed up finally on my frequency. By this point Aircraft X had possibly lost lateral separation with Aircraft Z who was inbound to SQL over PAO descending out of 3;100 feet.Aircraft X was issued a climb and turn to heading 250. I then withheld the climb to 5;000 feet and restricted Aircraft X to 2;100 in reference to Aircraft Z. Once it appeared as though divergence had been established Aircraft X was issued a climb to 5;000. By this point Aircraft X was approaching an MVA of 3;000 and another shelf of 4;000. Aircraft X was vectored to the northwest in reference to the MVA thus again causing a loss of lateral separation with Aircraft Z who was still descending inbound to SQL.The 'VFR downwind' IFR departure route out of SQL is a questionable procedure to begin with. It allows aircraft on an IFR flight plan to depart in VFR conditions and turn out to the southeast towards incoming traffic into SFO and SQL; making it essentially an opposite direction 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.