ZOA controller described airspace incursion event when failing to note the status of adjacent sectors; i.e. combined vs. de-combined.

Date: 2009-11 · Aircraft: B737 Undifferentiated or Other Model · Phase: climb

Anomalies: airspace-violation-all-types|deviation-discrepancy-procedural-published-material-policy

Synopsis

ZOA controller described airspace incursion event when failing to note the status of adjacent sectors; i.e. combined vs. de-combined.

Narrative

I was working R34; I had a 'D'/RA side; and the sector to the north; 32; was combined with sector 29. My 'D' side takes a break and I'm working R/D combined. I accepted a hand off from NCT on Air Carrier X; on the FROGO SID; climbing to FL230. I made a point out to the sector to the north for climb. I thought that sectors 29 and 32 were still combined; but they weren't and I was not aware of the fact that they had been decombined. When I thought I had 'pointed out' Air Carrier X to sector 32; I had actually only 'pointed out' to sector 29. I eventually climbed Air Carrier X to an altitude to an altitude above sector 29. To solve another confliction; I called sector 32 to issue a control instruction to another aircraft; Air Carrier Y; that was level at FL250. The sector 32 controller advised me that sector 29 was 'open'; and as I remember; I immediately realized that I had climbed Air Carrier X into sector 32's airspace with out a 'point out'; so I 'pointed out' Air Carrier X to sector 32 already climbing out of FL309. The base of sector 32 in that area is FL300. I looked at my status board and it did indicate that sector 29 and 32 had been decombined but I was not aware of this. It was obvious that my 'D' side earlier had done his job changing the status board and he may have verbally told me; but I didn't catch either. I learned that the sectors had been decombined just a couple/few minutes before the incident. Recommendation; hard to say what could prevent this. I have often found myself lacking the knowledge as to whether or not sectors 29 and 32 are combined or decombined. Not only am I sometimes not aware; I often forget. I do usually try to double check before I climb an aircraft into the altitude strata of sector 32; but I was figuring a remedy to solve another confliction.

Second reporter narrative

If sector 29 had been more vocal about their being de-combined; or if sector 34 had been more careful about how they pushed up their aircraft; checking accept messages; and and point out re-route messages they would have gotten; this could have been avoided. Also; had I (on the D-side) been more active looking for limited data block; I might have seen the data block before he got into my airspace.

More incidents for this aircraft family →

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.