Narrative:

I am currently training in all radar sectors at day. We were working everything combined; and we started to get busy. There were 2-3 land line calls; I had 3-4 transmissions I needed to make; and I could feel myself starting to get behind. A GLF3 was apreq'd; with a previous controller; direct his destination instead of an arrival gate. I took the hand off on the GLF3; and when he checked on I told him who I was and told him what approach to expect. I also immediately descended him to 6;000 ft as he was about 2 miles from columbus' boundary. Columbus owns from the surface to 10;000 ft; and I took the GLF3 at 11;000 ft. I was distracted with other aircraft and land line coordinations; including a point out for parachute jumping from cincinnati. I was too early in anticipating separation regarding columbus' airspace. A minute or so later; my trainer asked me if I descended the GLF3; who is now at 10;700 and descending about 1 mile from the lateral columbus boundary. I told my trainer that I did and immediately called columbus for a point-out. By the time columbus approved the point out the GLF3 was at about 10;500 over the boundary and still descending. The severity of this incident is minimal because there were no aircraft within 15-20 miles of the GLF3; and I did not observe any traffic in columbus' airspace near the GLF3 as well. In the future; when I get busy; I need to slow down and make sure that my control actions are accurate and timely. I became distracted with land line coordinations and I believe that led to me not realizing the GLF3's proximity to cmh airspace. I need to have a little more patience in situations like this.

Google
 

Original NASA ASRS Text

Title: DAY Controllers described an uncoordinated airspace entry event during a training session when the instructor waited too long prior to insuring the required point out had been accomplished.

Narrative: I am currently training in all RADAR sectors at DAY. We were working everything combined; and we started to get busy. There were 2-3 land line calls; I had 3-4 transmissions I needed to make; and I could feel myself starting to get behind. A GLF3 was APREQ'd; with a previous controller; direct his destination instead of an arrival gate. I took the hand off on the GLF3; and when he checked on I told him who I was and told him what approach to expect. I also immediately descended him to 6;000 FT as he was about 2 miles from Columbus' boundary. Columbus owns from the surface to 10;000 FT; and I took the GLF3 at 11;000 FT. I was distracted with other aircraft and land line coordinations; including a point out for parachute jumping from Cincinnati. I was too early in anticipating separation regarding Columbus' airspace. A minute or so later; my Trainer asked me if I descended the GLF3; who is now at 10;700 and descending about 1 mile from the lateral Columbus boundary. I told my trainer that I did and immediately called Columbus for a point-out. By the time Columbus approved the point out the GLF3 was at about 10;500 over the boundary and still descending. The severity of this incident is minimal because there were no aircraft within 15-20 miles of the GLF3; and I did not observe any traffic in Columbus' airspace near the GLF3 as well. In the future; when I get busy; I need to slow down and make sure that my control actions are accurate and timely. I became distracted with land line coordinations and I believe that led to me not realizing the GLF3's proximity to CMH airspace. I need to have a little more patience in situations like this.

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.