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

Date: 2007-06 · Aircraft: B737-800 · Phase: cruise

Anomalies: deviation-discrepancy-procedural-published-material-policy

Synopsis

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.

More incidents for this aircraft family →

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