Narrative:

The incident occurred on the midnight shift. I was in the control room at the time; but not officially on position; I was on break. I heard the r-side working the a-area say that seattle approach (S46) was not taking their handoff of aircraft X. I began trying to assist by calling seattle approach on shout and land lines and calling neighboring facilities to have them try as well; but to no luck; we were unable to reach seattle approach. During this time; the aircraft descended into seattle approach airspace without a handoff. Realizing that something was wrong at seattle approach; the controller turned the aircraft away from the airspace so as to cease violating their airspace as quickly as possible. After about 10 minutes of holding the aircraft out; the omic declared seattle approach ATC zero and seattle center assumed their airspace. At this time; the controller vectored the aircraft towards the boeing field ILS13 as requested and I assisted by calling an inbound to the tower. I later learned that this was an incorrect procedure as during seattle approach ATC zero. Seattle tower actually assumes 10 NM of seattle approach airspace up to 5000 MSL. This means that vectoring for the ILS and calling the inbound violated seattle tower's airspace because he went through their airspace without a point out or handoff. At the time this was not clear from our brief review of the contingency binder and communication with the omic and seattle tower.better briefings on seattle approach contingency plans and a much easier checklist for the transition to assuming their airspace. Also some changes at seattle approach to prevent controllers from getting locked out of the facility.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZSE Controller describes a situation where Seattle TRACON (S46) doesn't answer landlines and an aircraft is inbound to Boeing Field (BFI). ZLA assumes S46 is ATC - Zero and vectors the aircraft for the ILS Runway 13. Controller finds out late that Seattle Tower assumes the airspace that they had the aircraft in and ZSE violated the contingency plan and airspace.

Narrative: The incident occurred on the midnight shift. I was in the control room at the time; but not officially on position; I was on break. I heard the R-Side working the A-Area say that Seattle Approach (S46) was not taking their handoff of Aircraft X. I began trying to assist by calling Seattle Approach on shout and land lines and calling neighboring facilities to have them try as well; but to no luck; we were unable to reach Seattle Approach. During this time; the aircraft descended into Seattle Approach airspace without a handoff. Realizing that something was wrong at Seattle Approach; the controller turned the aircraft away from the airspace so as to cease violating their airspace as quickly as possible. After about 10 minutes of holding the aircraft out; the OMIC declared Seattle Approach ATC Zero and Seattle Center assumed their airspace. At this time; the controller vectored the aircraft towards the Boeing Field ILS13 as requested and I assisted by calling an inbound to the tower. I later learned that this was an incorrect procedure as during Seattle Approach ATC Zero. Seattle Tower actually assumes 10 NM of Seattle Approach airspace up to 5000 MSL. This means that vectoring for the ILS and calling the inbound violated Seattle Tower's airspace because he went through their airspace without a point out or handoff. At the time this was not clear from our brief review of the contingency binder and communication with the OMIC and Seattle Tower.Better briefings on Seattle Approach contingency plans and a much easier checklist for the transition to assuming their airspace. Also some changes at Seattle Approach to prevent controllers from getting locked out of the facility.

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.