Narrative:

I am an fpl controller at mgm RAPCON/tower. I was in the process of training on our north radar sector. The sectors were combined because it was still early morning and the sectors stay combined until mid morning. The supervisor was busy with administrative duties (training our new facility manager) and had left an fpl as controller-in-charge. The fpl in charge has 15 yrs experience. I have 4 yrs only 2 yrs radar experience. I have been issued the duty of primary training. I was training a young man that has no previous radar experience. He has around 80 training hours on our radar sectors. The session was going normally and as scheduled. I anticipated no problems except that the controller-in-charge was having to work radar data and couldn't keep up with the duties of data and controller-in-charge (controller in charge). There were a couple of occasions when we didn't have flight plan information because of this. I, as trainer, wanted the trainee to work moderate traffic because he has reached the stage to where light traffic presents no challenge. And as it happened, the traffic built rapidly and I ended up asking for a split. The supervisor or controller in charge usually coordinates and watches as the sectors are split but couldn't in this case. The other fpl controller was setting up the south scope to split the sectors north and south. He was watching as we tried to split. At this time the trainee was still sitting at north radar, but I was working the position. The first transmission I made was to an air carrier to turn right heading 360 degrees climb and maintain 10000 ft. An MTR on a missed approach at mxf airport, took this clearance, also, and began a climb (rapid rate) to 10000 ft. Dannelly and maxwell airports are laid out such that conflicts become possible all the time. Anyway, I caught that MTR was climbing and immediately asked who issued the climb. I turned the MTR immediately to avoid conflict with the air carrier and they missed by 5 mi. As I was doing all of this, no one was watching the boundaries and an small transport entered ZTL's (mgm sector atlanta center) airspace without a handoff. After the conflict of air carrier and MTR was resolved I immediately went back to splitting the sector and noticed that small transport had not been handed off. I jumped on the line to ZTL and tried to coordinate. I also flashed the airplane to ZTL for an automated handoff. ZTL took the automated handoff but would not answer the shout line for coordination. The aircraft was not in conflict with any other aircraft and no other problem occurred. The aircraft was switched to ZTL and I informed the controller in charge what happened. He turned his head to the incident from radar data. I realize that it was my fault for not pulling the trainee out sooner and not asking for a split sooner but, also, feel that some of the blame belongs to the supervisor who wasn't around and the controller in charge who has much more experience and has held a temporary supervisor job and wasn't coordinating for me and watching the traffic.

Google
 

Original NASA ASRS Text

Title: APCH CTLR FAILED TO HDOF SMT TO ARTCC, UNAUTHORIZED PENETRATION OF AIRSPACE.

Narrative: I AM AN FPL CTLR AT MGM RAPCON/TWR. I WAS IN THE PROCESS OF TRAINING ON OUR N RADAR SECTOR. THE SECTORS WERE COMBINED BECAUSE IT WAS STILL EARLY MORNING AND THE SECTORS STAY COMBINED UNTIL MID MORNING. THE SUPVR WAS BUSY WITH ADMINISTRATIVE DUTIES (TRAINING OUR NEW FACILITY MGR) AND HAD LEFT AN FPL AS CTLR-IN-CHARGE. THE FPL IN CHARGE HAS 15 YRS EXPERIENCE. I HAVE 4 YRS ONLY 2 YRS RADAR EXPERIENCE. I HAVE BEEN ISSUED THE DUTY OF PRIMARY TRAINING. I WAS TRAINING A YOUNG MAN THAT HAS NO PREVIOUS RADAR EXPERIENCE. HE HAS AROUND 80 TRAINING HRS ON OUR RADAR SECTORS. THE SESSION WAS GOING NORMALLY AND AS SCHEDULED. I ANTICIPATED NO PROBLEMS EXCEPT THAT THE CTLR-IN-CHARGE WAS HAVING TO WORK RADAR DATA AND COULDN'T KEEP UP WITH THE DUTIES OF DATA AND CTLR-IN-CHARGE (CIC). THERE WERE A COUPLE OF OCCASIONS WHEN WE DIDN'T HAVE FLT PLAN INFO BECAUSE OF THIS. I, AS TRAINER, WANTED THE TRAINEE TO WORK MODERATE TFC BECAUSE HE HAS REACHED THE STAGE TO WHERE LIGHT TFC PRESENTS NO CHALLENGE. AND AS IT HAPPENED, THE TFC BUILT RAPIDLY AND I ENDED UP ASKING FOR A SPLIT. THE SUPVR OR CIC USUALLY COORDINATES AND WATCHES AS THE SECTORS ARE SPLIT BUT COULDN'T IN THIS CASE. THE OTHER FPL CTLR WAS SETTING UP THE S SCOPE TO SPLIT THE SECTORS N AND S. HE WAS WATCHING AS WE TRIED TO SPLIT. AT THIS TIME THE TRAINEE WAS STILL SITTING AT N RADAR, BUT I WAS WORKING THE POS. THE FIRST XMISSION I MADE WAS TO AN ACR TO TURN R HDG 360 DEGS CLB AND MAINTAIN 10000 FT. AN MTR ON A MISSED APCH AT MXF ARPT, TOOK THIS CLRNC, ALSO, AND BEGAN A CLB (RAPID RATE) TO 10000 FT. DANNELLY AND MAXWELL ARPTS ARE LAID OUT SUCH THAT CONFLICTS BECOME POSSIBLE ALL THE TIME. ANYWAY, I CAUGHT THAT MTR WAS CLBING AND IMMEDIATELY ASKED WHO ISSUED THE CLB. I TURNED THE MTR IMMEDIATELY TO AVOID CONFLICT WITH THE ACR AND THEY MISSED BY 5 MI. AS I WAS DOING ALL OF THIS, NO ONE WAS WATCHING THE BOUNDARIES AND AN SMT ENTERED ZTL'S (MGM SECTOR ATLANTA CENTER) AIRSPACE WITHOUT A HDOF. AFTER THE CONFLICT OF ACR AND MTR WAS RESOLVED I IMMEDIATELY WENT BACK TO SPLITTING THE SECTOR AND NOTICED THAT SMT HAD NOT BEEN HANDED OFF. I JUMPED ON THE LINE TO ZTL AND TRIED TO COORDINATE. I ALSO FLASHED THE AIRPLANE TO ZTL FOR AN AUTOMATED HDOF. ZTL TOOK THE AUTOMATED HDOF BUT WOULD NOT ANSWER THE SHOUT LINE FOR COORD. THE ACFT WAS NOT IN CONFLICT WITH ANY OTHER ACFT AND NO OTHER PROBLEM OCCURRED. THE ACFT WAS SWITCHED TO ZTL AND I INFORMED THE CIC WHAT HAPPENED. HE TURNED HIS HEAD TO THE INCIDENT FROM RADAR DATA. I REALIZE THAT IT WAS MY FAULT FOR NOT PULLING THE TRAINEE OUT SOONER AND NOT ASKING FOR A SPLIT SOONER BUT, ALSO, FEEL THAT SOME OF THE BLAME BELONGS TO THE SUPVR WHO WASN'T AROUND AND THE CIC WHO HAS MUCH MORE EXPERIENCE AND HAS HELD A TEMPORARY SUPVR JOB AND WASN'T COORDINATING FOR ME AND WATCHING THE TFC.

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.