Narrative:

A mental lapse caused the problem. I violated airspace at a sector that I had worked approximately 1 hour before. The conflict alert discovered the confliction. Callback conversation with reporter revealed the following: reporter advised that both aircraft were acrs. The aircraft he was working had been issued a descent into the next controller's airspace. He was then relieved from the sector for a break and forgot to brief the new controller that a handoff had not been made. He learned of the conflict when he returned from his break. He did not know why the next controller did not take action to separate the aircraft when conflict alert activated, but suspects that there was not much time to prevent a loss of separation. Reporter states that incident occurred at FL310 with aircraft at 1600' and 4.6 mi apart.

Related reports:

Google
 

Original NASA ASRS Text

Title: ACFT ENTERED ADJACENT AIRSPACE AND CONFLICTED WITH ANOTHER ACFT RESULTING IN LESS THAN STANDARD SEPARATION.

Narrative: A MENTAL LAPSE CAUSED THE PROBLEM. I VIOLATED AIRSPACE AT A SECTOR THAT I HAD WORKED APPROX 1 HR BEFORE. THE CONFLICT ALERT DISCOVERED THE CONFLICTION. CALLBACK CONVERSATION WITH REPORTER REVEALED THE FOLLOWING: REPORTER ADVISED THAT BOTH ACFT WERE ACRS. THE ACFT HE WAS WORKING HAD BEEN ISSUED A DSCNT INTO THE NEXT CTLR'S AIRSPACE. HE WAS THEN RELIEVED FROM THE SECTOR FOR A BREAK AND FORGOT TO BRIEF THE NEW CTLR THAT A HANDOFF HAD NOT BEEN MADE. HE LEARNED OF THE CONFLICT WHEN HE RETURNED FROM HIS BREAK. HE DID NOT KNOW WHY THE NEXT CTLR DID NOT TAKE ACTION TO SEPARATE THE ACFT WHEN CONFLICT ALERT ACTIVATED, BUT SUSPECTS THAT THERE WAS NOT MUCH TIME TO PREVENT A LOSS OF SEPARATION. REPORTER STATES THAT INCIDENT OCCURRED AT FL310 WITH ACFT AT 1600' AND 4.6 MI APART.

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