Narrative:

Leading up to the event: a controller [was] sick. Staffing was short; training was in progress on south low with all the radar scopes combined. The supervisor asked that I split out south high because [vip aircraft] was coming through the airspace. I went over 2 hours on position because 'there was no one to relieve me'; yet training was not terminated to free up a controller. Poor coordination was done regarding [vip] by the supervisor. Apparently he was not listening to my coordination. Chicago put me in the hold for mdw. [Vip] was landing mdw and I knew it was because of [vip]. The supervisor told the traffic management command center (den) we were holding [vip] when I had actually already coordinated via the landline to chicago approach [vip] at 10;000 and fast which was approved.there was a lot of tension in the TRACON because the supervisor was trying to control everything and increased coordination with everything unnecessarily due to the fact that he didn't understand the situation. Things slowed down; and the supervisor took over south low sector. I was working 2 hours and 30 minutes and asked for a break. Traffic was very slow; but it was denied. I was ready for a break and stress was high over the recent events. A controller came into the TRACON and asked me if I needed a break. I said yes but ask the supervisor. The supervisor said no. The airspace violation: the south low controller/supervisor made a point out to me on aircraft X; a business jet climbing southwest bound across my fissk arrivals. I had aircraft Y entering my airspace at 11;000 feet that I was about to descend. I asked the controller if he saw aircraft Y. There was no response; and he kept talking to his airplanes. I decided to just take radar on aircraft X to work out the conflict myself. Using automation I took the handoff. I went to descend aircraft Y to 10;000 but scanned aircraft X and saw he was climbing through 8;200 feet. I told aircraft Y to disregard descent and maintain 11;000 feet.I then asked the south low sector if he climbed aircraft X to 10;000 feet. My sector owned 9000 and 10000 feet in that part of the airspace. He said yes he did. I called the next center sector and made a point out on aircraft Y to stay at 11;000 feet for traffic which they approved. I told the supervisor I needed time to fill out an atsap form. He didn't respond. I asked again and he said 'don't worry I'll report this on cedar'. I never heard him climb aircraft X to 10;000 feet. I'm not sure if I was talking to an airplane at the time or if being on position for what ended up being 3 hours had anything to do with not hearing it. I did catch it in time though and there was not a loss of separation. Don't leave controllers on position for more than 2 hours at a time.

Related reports:

Google
 

Original NASA ASRS Text

Title: A TRACON Supervisor working a control sector climbed an aircraft into another Controller's airspace without making a point out.

Narrative: Leading up to the event: A controller [was] sick. Staffing was short; training was in progress on South Low with all the radar scopes combined. The supervisor asked that I split out South High because [VIP aircraft] was coming through the airspace. I went over 2 hours on position because 'there was no one to relieve me'; yet training was not terminated to free up a controller. Poor coordination was done regarding [VIP] by the supervisor. Apparently he was not listening to my coordination. Chicago put me in the hold for MDW. [VIP] was landing MDW and I knew it was because of [VIP]. The supervisor told the Traffic Management Command Center (DEN) we were holding [VIP] when I had actually already coordinated via the landline to Chicago Approach [VIP] at 10;000 and fast which was approved.There was a lot of tension in the TRACON because the supervisor was trying to control everything and increased coordination with everything unnecessarily due to the fact that he didn't understand the situation. Things slowed down; and the supervisor took over South Low sector. I was working 2 hours and 30 minutes and asked for a break. Traffic was very slow; but it was denied. I was ready for a break and stress was high over the recent events. A controller came into the TRACON and asked me if I needed a break. I said yes but ask the supervisor. The Supervisor said no. The Airspace violation: The South Low Controller/Supervisor made a point out to me on Aircraft X; a business jet climbing southwest bound across my FISSK arrivals. I had Aircraft Y entering my airspace at 11;000 feet that I was about to descend. I asked the controller if he saw Aircraft Y. There was no response; and he kept talking to his airplanes. I decided to just take radar on Aircraft X to work out the conflict myself. Using automation I took the handoff. I went to descend Aircraft Y to 10;000 but scanned Aircraft X and saw he was climbing through 8;200 feet. I told Aircraft Y to disregard descent and maintain 11;000 feet.I then asked the South Low Sector if he climbed Aircraft X to 10;000 feet. My sector owned 9000 and 10000 feet in that part of the airspace. He said yes he did. I called the next Center sector and made a point out on Aircraft Y to stay at 11;000 feet for traffic which they approved. I told the supervisor I needed time to fill out an ATSAP form. He didn't respond. I asked again and he said 'Don't worry I'll report this on CEDAR'. I never heard him climb Aircraft X to 10;000 feet. I'm not sure if I was talking to an airplane at the time or if being on position for what ended up being 3 hours had anything to do with not hearing it. I did catch it in time though and there was NOT a loss of separation. Don't leave controllers on position for more than 2 hours at a time.

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