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.