Narrative:

I was training a new trainee on radar. A BE9 had departed right before a G150 and his flight plan had dropped out. We didn't know it until he was level at 5;000 and not tagged up. That's when local and ground called to let us know. We were trying to get that in the system; the G150 departed and after the trainee told him to climb and maintain 100 turn left direct lyh; which I had to step in because that would have taken him through the BE9 flight path; he asked for a destination change. Another controller that was in the room stepped in to help make the amendments. It took him awhile to get the flightplan in for the BE9 then he was doing the route change for the G150. I thought he said the change was in and he thought we had coordinated the route with ZDC so the trainee cleared him and switched him to ZDC. We realized the error about a minute later and he called ZDC to alert them to the mistake. The G150 was climbing out of 110 when he called.other things to note: training was being conducted by me and also on ground control; and a newly checked out controller on local. Recommendation; this is a definite example of how the chain needs to be broken! Ground and/or local control should have updated the time for the BE9 so it wouldn't have dropped out of the system. We got him late and with a problem. We only own up to 100 and he was a BE9 climbing at a good rate (we had to climb him because of the MVA's). The G150 came off asking for a destination change which he should have asked for on the ground not on initial contact. Hindsight for me; and what I learned; is if he is a fast climber to call ZDC and coordinate with them for headings. I don't want to cause another controller to have more workload that is why I tried to take care of it. But they can slew and enter and they have the new routing with the preferential routing. We have to turn our backs to the scope and enter the change in the fdio. He was too quick to get the flightplan in plus when they are climbing high we don't know exactly what routing the center wants them to have which ZDC has at their finger tips.. Also; it drove home how important communication is; I should have made sure the change was in before I let the trainee switch him.

Related reports:

Google
 

Original NASA ASRS Text

Title: TRACON Controller providing OJT described a confused hand off/coordination effort with the Center when trying to enter flightplan information on a fast climbing IFR aircraft; the reporter acknowledging coordination with the Center earlier would have proved more beneficial to all involved.

Narrative: I was training a new trainee on RADAR. A BE9 had departed right before a G150 and his flight plan had dropped out. We didn't know it until he was level at 5;000 and not tagged up. That's when Local and Ground called to let us know. We were trying to get that in the system; the G150 departed and after the trainee told him to climb and maintain 100 turn left direct LYH; which I had to step in because that would have taken him through the BE9 flight path; he asked for a destination change. Another controller that was in the room stepped in to help make the amendments. It took him awhile to get the flightplan in for the BE9 then he was doing the route change for the G150. I thought he said the change was in and he thought we had coordinated the route with ZDC so the trainee cleared him and switched him to ZDC. We realized the error about a minute later and he called ZDC to alert them to the mistake. The G150 was climbing out of 110 when he called.Other things to note: training was being conducted by me and also on Ground Control; and a newly checked out controller on Local. Recommendation; this is a definite example of how the chain needs to be broken! Ground and/or Local Control should have updated the time for the BE9 so it wouldn't have dropped out of the system. We got him late and with a problem. We only own up to 100 and he was a BE9 climbing at a good rate (we had to climb him because of the MVA's). The G150 came off asking for a destination change which he should have asked for on the Ground not on initial contact. Hindsight for me; and what I learned; is if he is a fast climber to call ZDC and coordinate with them for headings. I don't want to cause another controller to have more workload that is why I tried to take care of it. But they can slew and enter and they have the new routing with the preferential routing. We have to turn our backs to the scope and enter the change in the FDIO. He was too quick to get the flightplan in plus when they are climbing high we don't know exactly what routing the Center wants them to have which ZDC has at their finger tips.. Also; it drove home how important communication is; I should have made sure the change was in before I let the trainee switch him.

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.