DISPATCHER DESCRIBES CONFUSED FLIGHT PLAN EVENT WHEN ATC ALLEGED INCORRECT DEPARTURE AIRPORT INFORMATION AND ICAO CODING DATA; ALL RESULTING IN LACK OF CLEARANCE INFORMATION.

Narrative

THE FLT CREW CONTACTED DISPATCH PRIOR TO PUSHBACK AND STATED THAT THERE WAS NO PDC AVAILABLE FROM THE ACARS. I CHKED WITH ZDC FLT DATA TO GET A CID NUMBER. I THEN SENT AN ACARS MESSAGE TO FLT X WITH THE CID NUMBER AND TO CONTACT GND FOR CLRNC. THE FLT CREW RESPONDED BACK WITH 'ATC STRIP SHOWS US DEPARTING FROM ZZZ1 WAS PROB. ATC SAYS YOU NEED TO REFILE SO THEY CAN CLEAR THE WRONG ONE FROM THE SYSTEM.' I CHKED THE FILING STRIP AND NOTHING LOOKED OUT OF THE ORDINARY. I THEN CONTACTED ZDC FLT DATA AGAIN AND EXPLAINED THE PROB WITH THE STRIP. THE CTLR WORKING FLT DATA TOLD ME THAT THERE WAS NO ACTIVE STRIP FOR FLT X OUT OF ZZZ. HE ALSO MENTIONED THAT THERE WAS A PRINTOUT OF THE FLT PLAN THAT WAS SENT TO ATC AND THAT SOME OF THE ICAO CODES WERE INCORRECT. HE SAID WE WOULD RE-ENTER THE FLT PLAN FOR OUR FLT X. SHORTLY AFTER CONTACTING ZDC FLT DATA; THE COMMAND CTR CONTACTED OUR ATC COORDINATOR AND EXPLAINED THAT WE HAD CAUSED A CALL SIGN CONFLICT BY FILING 2 FLT PLANS FOR A FLT X WITH DIFFERENT CITY PAIRS. AFTER GATHERING SOME FACTS; I CAN STATE WITH CONFIDENCE THAT DISPATCH DID NOT SEND A FILING FOR A FLT X FROM ZZZZ1 TO ZZZZ2. I COULD NOT FIGURE OUT HOW ATC SHOWED THIS AS AN ACTIVE FLT PLAN; BECAUSE IT WAS NEVER FILED BY DISPATCH.