Narrative:

R30/10 were combined; with a high volume of VFR traffic with a few IFR aircraft mixed in. ZOA 45 pvd'd the data block of aircraft X at FL230 to my position; and then called on the shout line to point the aircraft out to me. On the initial call something to the effect of; 'point south of lavaa; aircraft X; and which sector is that west of you that I'll be handing him off to?' I informed him that we're stratified at 230 and below; so it would be my aircraft to work. He replied ok; and handed the aircraft off to me without apreqing the inappropriate altitude. I took the hand off; called back to get control from ZOA45; and control from ZOA42 which the aircraft was passing through to change his altitude. After making a verbal point out to ZSE sector 13; I handed the aircraft off to ZSE14 and climbed aircraft X to FL240. As I changed the aircraft to ZSE 14 frequency; the controller asked if I had called ZOA 31 and pointed the aircraft out to him. I replied no; realized my error tried to pvd the data block up to ZOA31 but got a fail message. At the same time the sector 14 controller pvd'd the data block to ZOA31 and made the point out. The aircraft was leaving FL236 when it was completed. Recommendation; 1) ZOA comply with .65 and the ZSE/ZOA LOA for correct altitudes direction of flight as a contributing factor. 2) stratification change along the ZOA/ZSE boundary. The ZOA controller was confused as to which sector the AC was supposed to be handed off. ZOA is stratified at FL290 and all other sectors are stratified at FL240 which can sometimes add to confusion. This area; where ZSE 14/13 & ZOA 45/43/31; all meet can cause and create many coordinate issues that other wise would not occur. 3) in host it was possible to pvd a data block to any sector regardless of which sector had ownership of that data block. In eram; only the controlling sector may pvd a data block to someone else. I would suggest in the next future build that this be added in.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZSE Controller described an airspace incursion allegedly caused by confusion regarding stratified adjacent airspace; adjacent ATC non-compliance with 7110.65; and ERAM limitation with regard to automated point outs.

Narrative: R30/10 were combined; with a high volume of VFR traffic with a few IFR aircraft mixed in. ZOA 45 PVD'd the Data Block of Aircraft X at FL230 to my position; and then called on the shout line to point the aircraft out to me. On the initial call something to the effect of; 'point South of Lavaa; Aircraft X; and which sector is that West of you that I'll be handing him off to?' I informed him that we're stratified at 230 and below; so it would be my aircraft to work. He replied OK; and handed the aircraft off to me without APREQing the inappropriate altitude. I took the hand off; called back to get control from ZOA45; and control from ZOA42 which the aircraft was passing through to change his altitude. After making a verbal point out to ZSE Sector 13; I handed the aircraft off to ZSE14 and climbed Aircraft X to FL240. As I changed the aircraft to ZSE 14 frequency; the controller asked if I had called ZOA 31 and pointed the aircraft out to him. I replied no; realized my error tried to PVD the Data Block up to ZOA31 but got a fail message. At the same time the Sector 14 controller PVD'd the Data Block to ZOA31 and made the point out. The aircraft was leaving FL236 when it was completed. Recommendation; 1) ZOA comply with .65 and the ZSE/ZOA LOA for correct altitudes direction of flight as a contributing factor. 2) Stratification change along the ZOA/ZSE boundary. The ZOA Controller was confused as to which sector the AC was supposed to be handed off. ZOA is stratified at FL290 and all other sectors are stratified at FL240 which can sometimes add to confusion. This area; where ZSE 14/13 & ZOA 45/43/31; all meet can cause and create many coordinate issues that other wise would not occur. 3) In HOST it was possible to PVD a Data Block to any sector regardless of which sector had ownership of that Data Block. In ERAM; only the controlling sector may PVD a Data Block to someone else. I would suggest in the next future build that this be added in.

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.