Approach controller observed 3 air carrier aircraft off sfo get near his airspace without a pointout and with less than required separation. Reporter notified his supervisor of the situation and was advised that management was aware of the airspace boundary problem and was working to change it. Supervisor says no deviations took place.

Home

Browse by month

Random

Latest

About

Contact

Attributes
ACN	360616
Time
Date	199702
Day	Sat
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : sfo
State Reference	CA
Altitude	msl bound lower : 1500 msl bound upper : 1500
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : oak
Operator	common carrier : air carrier
Make Model Name	MD-80 Super 80
Operating Under FAR Part	Part 121
Navigation In Use	Other
Flight Phase	climbout : intermediate altitude
Route In Use	departure other
Flight Plan	IFR
Aircraft 2
Operator	common carrier : air carrier
Make Model Name	B727 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Phase	climbout : intermediate altitude
Route In Use	departure other departure sid : sid
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : approach
Qualification	controller : radar pilot : instrument
Experience	controller radar : 16 flight time total : 300
ASRS Report	360616
Person 2
Affiliation	government : faa
Function	oversight : supervisor
Qualification	controller : radar
Events
Anomaly	non adherence : published procedure other anomaly other
Independent Detector	other controllera
Resolutory Action	none taken : anomaly accepted
Consequence	Other
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	other
Situations
ATC Facility	procedure or policy : unspecified

Narrative:

I advised the supervisor that I thought an airspace deviation was occurring with an aircraft being worked by an adjacent sector (richmond dr-2). Facility and sfo tower orders and LOA's require aircraft to depart on a heading of 030 degrees (routed north and east off sfo). The airspace boundary between my sector (ar-3/4 woodside/foster) and richmond is an sfo direct oak line. This is approximately a 030 degree heading off sfo. I observed 3 aircraft depart sfo (air carrier X, air carrier Y, air carrier Z) all on a 030 degree heading. They were not 1 1/2 mi from my airspace boundary as required by the 7110.65. Management of the facility is aware of the problem but has not yet implemented an airspace boundary change to remedy the problem. I have been told that since they are working on the problem these are not deviations.

Original NASA ASRS Text

Title: APCH CTLR OBSERVED 3 ACR ACFT OFF SFO GET NEAR HIS AIRSPACE WITHOUT A POINTOUT AND WITH LESS THAN REQUIRED SEPARATION. RPTR NOTIFIED HIS SUPVR OF THE SIT AND WAS ADVISED THAT MGMNT WAS AWARE OF THE AIRSPACE BOUNDARY PROB AND WAS WORKING TO CHANGE IT. SUPVR SAYS NO DEVS TOOK PLACE.

Narrative: I ADVISED THE SUPVR THAT I THOUGHT AN AIRSPACE DEV WAS OCCURRING WITH AN ACFT BEING WORKED BY AN ADJACENT SECTOR (RICHMOND DR-2). FACILITY AND SFO TWR ORDERS AND LOA'S REQUIRE ACFT TO DEPART ON A HDG OF 030 DEGS (ROUTED N AND E OFF SFO). THE AIRSPACE BOUNDARY BTWN MY SECTOR (AR-3/4 WOODSIDE/FOSTER) AND RICHMOND IS AN SFO DIRECT OAK LINE. THIS IS APPROX A 030 DEG HDG OFF SFO. I OBSERVED 3 ACFT DEPART SFO (ACR X, ACR Y, ACR Z) ALL ON A 030 DEG HDG. THEY WERE NOT 1 1/2 MI FROM MY AIRSPACE BOUNDARY AS REQUIRED BY THE 7110.65. MGMNT OF THE FACILITY IS AWARE OF THE PROB BUT HAS NOT YET IMPLEMENTED AN AIRSPACE BOUNDARY CHANGE TO REMEDY THE PROB. I HAVE BEEN TOLD THAT SINCE THEY ARE WORKING ON THE PROB THESE ARE NOT DEVS.

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