Nct controller has to resequence a san carlos arrival due to conflicting san francisco arrival traff...

Attributes
ACN	981609
Time
Date	201111
Local Time Of Day	1801-2400
Place
Locale Reference	SQL.Airport
State Reference	CA
Environment
Light	Daylight
Aircraft 1
Make Model Name	PA-46 Malibu Meridian
Operating Under FAR Part	Part 91
Flight Phase	Final Approach
Route In Use	Other RNAV Z
Flight Plan	IFR
Aircraft 2
Make Model Name	Light Transport Low Wing 2 Turboprop Eng
Operating Under FAR Part	Part 121
Flight Phase	Descent
Route In Use	Vectors
Flight Plan	IFR
Person 1
Function	Approach
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Airspace Violation All Types Deviation - Procedural Published Material / Policy

Narrative:

I was working licke/hooks [sectors] combined. A meridian was handed off to me from morgan sector; inbound to sql at 6;000 ft. The aircraft was requesting the RNAV Z approach via ameby waypoint. I pointed out the aircraft via automation to 1T (toga); 2W (woodside); 1N (moffett tower); and 1P (palo alto tower). I cleared the aircraft for the RNAV Z approach. When the meridian was just outside of ameby; I noticed a tracked target on a woodside tag. I clicked on it and it was a turboprop; turning what appeared to be base leg to sfo; descending out of 4;600 ft. It was to the northwest and was going to cross the meridian's flight path going left to right. I canceled the approach clearance to the meridian and turned him to a heading of 030 and told him to maintain 4;000 ft. I asked toga to stop any sjc departures and told them of my intentions to circle the aircraft back to ameby. I circled the meridian back to ameby and re-cleared the aircraft for the RNAV Z approach. I then switched the aircraft to sql tower. I recommend that the airspace used by toga over palo alto and moffett be increased from 'surface to 3;000 ft' to 'surface to 4;000 ft.' this would ensure protection for the sql RNAV approach over ameby at 3;900 ft.

Original NASA ASRS Text

Title: NCT Controller has to resequence a San Carlos arrival due to conflicting San Francisco arrival traffic. The SFO arrival Controller had previously received a pointout on the SQL arrival.

Narrative: I was working Licke/Hooks [sectors] combined. A Meridian was handed off to me from Morgan sector; inbound to SQL at 6;000 FT. The aircraft was requesting the RNAV Z approach via AMEBY waypoint. I pointed out the aircraft via automation to 1T (Toga); 2W (Woodside); 1N (Moffett Tower); and 1P (Palo Alto Tower). I cleared the aircraft for the RNAV Z approach. When the Meridian was just outside of AMEBY; I noticed a tracked target on a Woodside Tag. I clicked on it and it was a turboprop; turning what appeared to be base leg to SFO; descending out of 4;600 FT. It was to the northwest and was going to cross the Meridian's flight path going left to right. I canceled the approach clearance to the Meridian and turned him to a heading of 030 and told him to maintain 4;000 FT. I asked Toga to stop any SJC departures and told them of my intentions to circle the aircraft back to AMEBY. I circled the Meridian back to AMEBY and re-cleared the aircraft for the RNAV Z approach. I then switched the aircraft to SQL Tower. I recommend that the airspace used by Toga over Palo Alto and Moffett be increased from 'surface to 3;000 FT' to 'surface to 4;000 FT.' This would ensure protection for the SQL RNAV approach over AMEBY at 3;900 FT.

Data retrieved from NASA's ASRS site as of April 2012 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.

Nct controller has to resequence a san carlos arrival due to conflicting san francisco arrival traffic. The sfo arrival controller had previously received a pointout on the sql arrival.