Narrative:

I was working the leonn sector and was at the tail end of an inbound rush to the charlotte airport. Greensboro approach control (gso) called with a manual handoff on a cga X off of NC14 going to dalton, GA. The pilot had misfiled his flight plan by putting in the wrong latitude/longitudes. In his defense this could have easily happened at the flight service station. The flight plan had processed to ZDC and they at first had the handoff. They canceled their track, but our computer did have the flight plan. After calling radar contact, I attempted several times to start a track on the aircraft. I was unable as the computer told me I did not have control of the data block. I was forced to input a whole new flight plan under a different call sign. I then started a track under the false call sign. By this time the aircraft was in another sector without a track (I had previously pointed the aircraft out using the transponder code). The entire time my attention was diverted from the sector and luckily I was not very busy. If this situation had occurred 5 mins prior, it would have been a real mess. A contributing factor was that my supervisor never offered any help.

Related reports:

Google
 

Original NASA ASRS Text

Title: WRONG LATITUDE AND LONGITUDES IN FLT PLAN CAUSE A MISDIRECTED HDOF TO ZDC INSTEAD OF ZTL. THE ZTL CTLR HAD TO START A NEW TRACK USING A FALSE CALL SIGN IN ORDER TO RECTIFY THE PROB. THE ACFT ENTERED ANOTHER SECTOR'S AIRSPACE, HOWEVER, THE RPTR HAD PREVIOUSLY POINTED THE ACFT OUT PRIOR TO ENTERING THE AIRSPACE.

Narrative: I WAS WORKING THE LEONN SECTOR AND WAS AT THE TAIL END OF AN INBOUND RUSH TO THE CHARLOTTE ARPT. GREENSBORO APCH CTL (GSO) CALLED WITH A MANUAL HDOF ON A CGA X OFF OF NC14 GOING TO DALTON, GA. THE PLT HAD MISFILED HIS FLT PLAN BY PUTTING IN THE WRONG LATITUDE/LONGITUDES. IN HIS DEFENSE THIS COULD HAVE EASILY HAPPENED AT THE FLT SVC STATION. THE FLT PLAN HAD PROCESSED TO ZDC AND THEY AT FIRST HAD THE HDOF. THEY CANCELED THEIR TRACK, BUT OUR COMPUTER DID HAVE THE FLT PLAN. AFTER CALLING RADAR CONTACT, I ATTEMPTED SEVERAL TIMES TO START A TRACK ON THE ACFT. I WAS UNABLE AS THE COMPUTER TOLD ME I DID NOT HAVE CTL OF THE DATA BLOCK. I WAS FORCED TO INPUT A WHOLE NEW FLT PLAN UNDER A DIFFERENT CALL SIGN. I THEN STARTED A TRACK UNDER THE FALSE CALL SIGN. BY THIS TIME THE ACFT WAS IN ANOTHER SECTOR WITHOUT A TRACK (I HAD PREVIOUSLY POINTED THE ACFT OUT USING THE XPONDER CODE). THE ENTIRE TIME MY ATTN WAS DIVERTED FROM THE SECTOR AND LUCKILY I WAS NOT VERY BUSY. IF THIS SIT HAD OCCURRED 5 MINS PRIOR, IT WOULD HAVE BEEN A REAL MESS. A CONTRIBUTING FACTOR WAS THAT MY SUPVR NEVER OFFERED ANY HELP.

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.