Narrative:

Just took the combined sectors of ckb and ray. Within one minute there were many hand-offs to my sector and I was informed that ray sector was being split out. I was asked; as the split happened; if it was good to do so. At first I said no since I was still getting up to speed and getting the picture. I then relented as the de-combing had already been done. This was a mistake. I should have stayed with my initial decision of keeping the sectors combined. Aircraft X was given a crossing restriction of bucko; in my airspace; to cross at FL290 and it was read back. Then the ray sector airspace was given to the new controller along with the frequency. I gave aircraft X the frequency change to ZDC; but before getting a read back; got a call from another aircraft. The d-side noticed the limited in moorefield's airspace at FL310. I said the aircraft had been given a restriction. The d-side called moorefield to point out the aircraft. I tried calling the aircraft; but with no response. I asked rayland sector to try the aircraft and it was on his frequency. Rayland gave the aircraft FL290 and switched it to the proper frequency of blueridge sector. Recommend if you are not ready to either combine with another sector or give up a combined sector; don't be pressured into doing so until you and traffic really permits. When de-combining a sector make sure the frequency pairing is off prior to the de-combining or else it stays at the split off sector. Don't let another aircraft call distract from attaining a proper read back. Ensure the full data block reflects what the aircraft is doing prior to dropping off when appropriate.

Related reports:

Google
 

Original NASA ASRS Text

Title: A Controller described a confused sector de-combination Where the hurried actions to split the sector were ill advised.

Narrative: just took the combined sectors of CKB and RAY. Within one minute there were many hand-offs to my sector and I was informed that RAY sector was being split out. I was asked; as the split happened; if it was good to do so. At first I said no since I was still getting up to speed and getting the picture. I then relented as the de-combing had already been done. This was a mistake. I should have stayed with my initial decision of keeping the sectors combined. Aircraft X was given a crossing restriction of BUCKO; in my airspace; to cross at FL290 and it was read back. Then the RAY Sector airspace was given to the new Controller along with the frequency. I gave Aircraft X the frequency change to ZDC; but before getting a read back; got a call from another aircraft. The D-Side noticed the limited in Moorefield's airspace at FL310. I said the aircraft had been given a restriction. The D-Side called Moorefield to point out the aircraft. I tried calling the aircraft; but with no response. I asked Rayland Sector to try the aircraft and it was on his frequency. Rayland gave the aircraft FL290 and switched it to the proper frequency of Blueridge Sector. Recommend if you are not ready to either combine with another sector or give up a combined sector; don't be pressured into doing so until you and traffic really permits. When de-combining a sector make sure the frequency pairing is off prior to the de-combining or else it stays at the split off sector. Don't let another aircraft call distract from attaining a proper read back. Ensure the full data block reflects what the aircraft is doing prior to dropping off when appropriate.

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.