ZOA controller described near operational deviation when adjacent facility failed to initiate a time...

Attributes
ACN	741561
Time
Date	200706
Local Time Of Day	1801 To 2400
Place
Locale Reference	navaid : fjs.vor
State Reference	CA
Altitude	msl single value : 41000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zoa.artcc
Operator	common carrier : air carrier
Make Model Name	B737-800
Operating Under FAR Part	Part 121
Flight Phase	cruise : level
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : radar controller : handoff position
Qualification	controller : radar
Experience	controller limited radar : 9 controller radar : 12 controller time certified in position1 : 8
ASRS Report	741561
Events
Anomaly	non adherence : published procedure
Independent Detector	other controllera
Resolutory Action	none taken : anomaly accepted
Supplementary
Problem Areas	ATC Human Performance
Primary Problem	ATC Human Performance

Narrative:

I observed a target approaching my boundary from ZSE at FL410 not yet in handoff status. I was busy with numerous aircraft and a radar associate was not yet available. When the intruder limited data block approached 5 mi from the boundary I initiated a call to seattle. After a more urgent second call the controller picked up.. I asked about the target nearing my boundary and the controller replied that it appeared that I already had the handoff. I accepted radar on the target as I looked up the call sign. The controller at seattle mentioned another sector and the full data block then began to flash. I accepted the automated handoff. I believe the controller I spoke with had accepted a pointout on the aircraft and the controling sector forgot to hand it off to me. The airspace deviation was avoided by my call. Insufficient staffing did not allow me to have help in a timely fashion to take care of this at an earlier time. I don't know the circumstances specifically related to ZSE. This incident reaffirms the importance of good scanning techniques for all concerned.

Original NASA ASRS Text

Title: ZOA CTLR DESCRIBED NEAR OPDEV WHEN ADJACENT FAC FAILED TO INITIATE A TIMELY HDOF; LIKELY DUE TO A CONTROLLING SECTOR/POINT OUT ISSUE.

Narrative: I OBSERVED A TARGET APCHING MY BOUNDARY FROM ZSE AT FL410 NOT YET IN HDOF STATUS. I WAS BUSY WITH NUMEROUS ACFT AND A RADAR ASSOCIATE WAS NOT YET AVAILABLE. WHEN THE INTRUDER LIMITED DATA BLOCK APCHED 5 MI FROM THE BOUNDARY I INITIATED A CALL TO SEATTLE. AFTER A MORE URGENT SECOND CALL THE CTLR PICKED UP.. I ASKED ABOUT THE TARGET NEARING MY BOUNDARY AND THE CTLR REPLIED THAT IT APPEARED THAT I ALREADY HAD THE HDOF. I ACCEPTED RADAR ON THE TARGET AS I LOOKED UP THE CALL SIGN. THE CTLR AT SEATTLE MENTIONED ANOTHER SECTOR AND THE FULL DATA BLOCK THEN BEGAN TO FLASH. I ACCEPTED THE AUTOMATED HDOF. I BELIEVE THE CTLR I SPOKE WITH HAD ACCEPTED A POINTOUT ON THE ACFT AND THE CTLING SECTOR FORGOT TO HAND IT OFF TO ME. THE AIRSPACE DEV WAS AVOIDED BY MY CALL. INSUFFICIENT STAFFING DID NOT ALLOW ME TO HAVE HELP IN A TIMELY FASHION TO TAKE CARE OF THIS AT AN EARLIER TIME. I DON'T KNOW THE CIRCUMSTANCES SPECIFICALLY RELATED TO ZSE. THIS INCIDENT REAFFIRMS THE IMPORTANCE OF GOOD SCANNING TECHNIQUES FOR ALL CONCERNED.

Data retrieved from NASA's ASRS site as of January 2009 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.

ZOA controller described near operational deviation when adjacent facility failed to initiate a timely handoff; likely due to a controlling sector/point out issue.