Narrative:

I was working the r-side on sector 47; combined with sector 48. I was on position for about an hour and a half and received my 3rd d-side. It wasn't very busy at the time; working about 10 aircraft. I took a handoff on aircraft 1 climbing out of sector 9 in the vicinity of PDT and climbed the aircraft to FL370. Aircraft 1 flight path was going to cut the corner of sector 16 then proceed into ZLC. Their low sector 31 owns FL280 and below and the high sector 41 owns FL290 and above. My d-side turned to me and said; 16 has the point-out. I displayed the data block to sector 31. I then responded; ok; 31 has the data block looks like they'll need a point-out. The d-side turned back to the uret and I continued responding to the frequency; expecting the coordination would be completed. When my scan came back around I initiated the handoff on aircraft 1 to sector 41; and they took the handoff about 10 miles from the boundary climbing out of FL250. Approximately 3 to 4 minutes later I had another aircraft check on coming from sector 41 landing psc and requesting lower. My d-side leaned over to hit the shout line for control when we heard ZLC calling 16. My d-side hit the line and I waited for a response. When he got off the line he told me they called 16 and said point-out approved on aircraft 1; 16 responded that they were not working the aircraft. He jumped in and said we were working that aircraft; ZLC responded that it wasn't a problem and released control. I replied; you didn't point-out the aircraft 1. He shook his head and said; when you told me you sent them a data block I misunderstood you and thought you did it. At this point aircraft 1 was about 5 miles into ZLC airspace climbing out of FL275. The recommendation for me is that I need to eliminate the possibility of misunderstanding by following up with my d-side.

Related reports:

Google
 

Original NASA ASRS Text

Title: Two ZSE Controllers report a miscommunication that leads to a late point out of climbing traffic.

Narrative: I was working the R-side on sector 47; combined with sector 48. I was on position for about an hour and a half and received my 3rd D-side. It wasn't very busy at the time; working about 10 aircraft. I took a handoff on Aircraft 1 climbing out of sector 9 in the vicinity of PDT and climbed the aircraft to FL370. Aircraft 1 flight path was going to cut the corner of sector 16 then proceed into ZLC. Their low sector 31 owns FL280 and below and the High sector 41 owns FL290 and above. My D-side turned to me and said; 16 has the point-out. I displayed the data block to sector 31. I then responded; OK; 31 has the data block looks like they'll need a point-out. The D-side turned back to the URET and I continued responding to the frequency; expecting the coordination would be completed. When my scan came back around I initiated the handoff on Aircraft 1 to sector 41; and they took the handoff about 10 miles from the boundary climbing out of FL250. Approximately 3 to 4 minutes later I had another aircraft check on coming from sector 41 landing PSC and requesting lower. My D-side leaned over to hit the shout line for control when we heard ZLC calling 16. My D-side hit the line and I waited for a response. When he got off the line he told me they called 16 and said point-out approved on Aircraft 1; 16 responded that they were not working the aircraft. He jumped in and said we were working that aircraft; ZLC responded that it wasn't a problem and released control. I replied; you didn't point-out the Aircraft 1. He shook his head and said; when you told me you sent them a data block I misunderstood you and thought you did it. At this point Aircraft 1 was about 5 miles into ZLC airspace climbing out of FL275. The recommendation for me is that I need to eliminate the possibility of misunderstanding by following up with my D-side.

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.