Date: 201702
Local time of day: 1801-2400
Location: ZOA.ARTCC, CA
Aircraft: F/A 18 Hornet/Super Hornet
Operator: Military
Flight plan: IFR
Mission: Tactical
Flight phase: Climb
Airspace: Class A ZOA
ATC / advisory: Center ZOA
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Training / Qualification; Time Pressure; Situational Awareness; Human-Machine Interface; Distraction; Confusion; Communication Breakdown; Workload
Anomaly: ATC Issue All Types; Airspace Violation All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Fuel Issue
Detector: Person Air Traffic Control
When detected: In-flight
Contributing factors: Procedure; Airspace Structure
Primary problem: Procedure

Narrative: Parties involved were ZOA Sector 14; Fleet Area Control and Surveillance Facility (FACSFAC) San Diego; and a Fighter Wing from California. Aircraft X showed up as a Mode C intruder in sector 14 airspace with no info or handoff. Aircraft X showed with minimum fuel in sector 14 airspace no info on this until he was already there and the D-SIDE questioned FACSFAC on this. Aircraft X was a late handoff already in sector 14 airspace. Communications and intentions were not figured out until all these aircraft were in sector 14's airspace.Fighter Wings routes of flight and altitudes were conflicting with multiple pieces of traffic landing SJC or overflying sector 14's airspace. Had no communications or intentions been established prior to the fighter wing crossing this very busy corridor of sector 14 there could have been a loss of separation. Sector 14 D-SIDE was doing everything in his power to keep these aircraft from entering our airspace. FACSFAC repeatedly does not understand what unable to take a point out or handoff. They questioned it several times during this session. If you're working this type of scenario and the sector next you cannot take a handoff what makes you think a point out will be accepted.FACSFAC San Diego continues to allow these fighter wings to operate right on the boundary of Sector 14 and 10 and W283/285A on daily basis. Point outs are generally late and handoffs are either late or not done at all because of improper recovery procedures.This is the 3rd report that has been filed on FACSFAC and these fighter wings who operate out of [area military bases] on the same exact issues. I have gotten responses as bad as the military doesn't want to talk about this. Others were to try to talk about a LOA meeting to address not only the LOA; but the SOP or lack of SOP we have with them. Either way nothing has changed in past 6 months or longer since my last report. My recommendation is to negotiate directly with FACSFAC San Diego on a new LOA and bring up and fix all these problems we continue to have on a day to day basis. The controllers all recognize this as a very high potential for something bad to happen if we cannot get together and fix this. The Navy Fighter Wings and FACSFAC need to understand you cannot just expect the Center sectors to fix the problems anymore. Enough is enough.




Synopsis: Oakland Center Controller reported unsafe airspace problems with a Navy Facility when military flights enter Oakland Airspace without approval.