Narrative:

The aircraft had no traffic; I started flashing the hand off to the next sector and ranged in to work the area where my traffic was. This particular aircraft soon was off the edge of my scope. When I gave a relief briefing; I discovered the aircraft had already progressed the small area of the next sector that it goes through. In my opinion; this situation was inevitable. It will more than likely happen again; unless we make a procedural change. I know that I will change how I work these aircraft in the future to avoid this repeating. I will now point the aircraft out and skip the next sector all together. The routing of this particular aircraft is not uncommon. However; I know this has happened in the past; and will probably happen again because of: the size of the sector B; the fact there is very little traffic off the coast there and in order to effectively work the rest of the sector you need to range in; leaving any aircraft off the coast off the edge of your scope. Then to create more of a problem; the next sector that will be receiving the aircraft is doing the same thing. Recommendation; I would recommend sector 3 completes the coordination with oakland and then just points the aircraft out to sector 42. The aircraft are in 42's airspace for a minimal amount of time. So minimal that when they check in with them; 42 terminates them; puts them on a XXXX code; and sends them over to enroute. They would agree I believe 100 percent with this procedure. I'm not sure if all in my area of specialty would; but this is the only way that I believe would greatly reduce the risk of this type of air space deviation reoccurring.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZSE Controller described an airspace incursion event listing RADAR range limitations and intra facility procedures as factors contributing to this occurrence.

Narrative: The aircraft had no traffic; I started flashing the hand off to the next sector and ranged in to work the area where my traffic was. This particular aircraft soon was off the edge of my scope. When I gave a relief briefing; I discovered the aircraft had already progressed the small area of the next sector that it goes through. In my opinion; this situation was inevitable. It will more than likely happen again; unless we make a procedural change. I know that I will change how I work these aircraft in the future to avoid this repeating. I will now point the aircraft out and skip the next sector all together. The routing of this particular aircraft is not uncommon. However; I know this has happened in the past; and will probably happen again because of: the size of the Sector B; the fact there is very little traffic off the coast there and in order to effectively work the rest of the sector you need to range in; leaving any aircraft off the coast off the edge of your scope. Then to create more of a problem; the next sector that will be receiving the aircraft is doing the same thing. Recommendation; I would recommend Sector 3 completes the coordination with Oakland and then just points the aircraft out to Sector 42. The aircraft are in 42's airspace for a minimal amount of time. So minimal that when they check in with them; 42 terminates them; puts them on a XXXX code; and sends them over to enroute. They would agree I believe 100 percent with this procedure. I'm not sure if all in my area of specialty would; but this is the only way that I believe would greatly reduce the risk of this type of air space deviation reoccurring.

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.