ZID controller experienced airspace incursion event when failing to note that the sector had been sp...

Attributes
ACN	876274
Time
Date	201003
Local Time Of Day	1201-1800
Place
Locale Reference	ZID.ARTCC
State Reference	IN
Aircraft 1
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Flight Phase	Descent Cruise
Flight Plan	IFR
Aircraft 2
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Flight Phase	Cruise
Flight Plan	IFR
Person 1
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Airspace Violation All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy

Narrative:

Issued aircraft X descent clearance from FL360 to FL280. The sector I was working 76 (FL320-FL360) and sector 66 (FL240-FL310) was de-combine approximately 20 minutes prior to this situation. Issued aircraft Y a descend clearance from FL360 to FL300 minutes later. When the aircraft was out of FL335 conflict alert activated with an aircraft in sector 66 air space at FL310; action was taken and aircraft Y was stopped at FL320 and turned to the right; no separation was lost. This is when I realized that I had violated sector 66 with aircraft X and coordinated with sector 66 about aircraft X and did proper coordination with aircraft Y. Recommendation; the next time that I split out any section I will put a visual aid on my radar screen that will identify the altitude stratum that I am currently working.

Original NASA ASRS Text

Title: ZID Controller experienced airspace incursion event when failing to note that the sector had been split and that normally utilized airspace had been divided.

Narrative: Issued Aircraft X descent clearance from FL360 to FL280. The sector I was working 76 (FL320-FL360) and Sector 66 (FL240-FL310) was de-combine approximately 20 minutes prior to this situation. Issued Aircraft Y a descend clearance from FL360 to FL300 minutes later. When the aircraft was out of FL335 conflict alert activated with an aircraft in Sector 66 air space at FL310; action was taken and Aircraft Y was stopped at FL320 and turned to the right; no separation was lost. This is when I realized that I had violated Sector 66 with Aircraft X and coordinated with Sector 66 about Aircraft X and did proper coordination with Aircraft Y. Recommendation; the next time that I split out any section I will put a visual aid on my RADAR screen that will identify the altitude stratum that I am currently working.

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.

ZID controller experienced airspace incursion event when failing to note that the sector had been split and that normally utilized airspace had been divided.