Dispatcher describes confused flight plan event when ATC alleged incorrect departure airport informa...

Narrative:

The flight crew contacted dispatch prior to pushback and stated that there was no pre departure clearance available from the ACARS. I checked with ZDC flight data to get a cid number. I then sent an ACARS message to flight X with the cid number and to contact ground for clearance. The flight crew responded back with 'ATC strip shows us departing from ZZZ1 was problem. ATC says you need to refile so they can clear the wrong one from the system.' I checked the filing strip and nothing looked out of the ordinary. I then contacted ZDC flight data again and explained the problem with the strip. The controller working flight data told me that there was no active strip for flight X out of ZZZ. He also mentioned that there was a printout of the flight plan that was sent to ATC and that some of the ICAO codes were incorrect. He said we would re-enter the flight plan for our flight X. Shortly after contacting ZDC flight data; the command center contacted our ATC coordinator and explained that we had caused a call sign conflict by filing 2 flight plans for a flight X with different city pairs. After gathering some facts; I can state with confidence that dispatch did not send a filing for a flight X from ZZZZ1 to ZZZZ2. I could not figure out how ATC showed this as an active flight plan; because it was never filed by dispatch.

Original NASA ASRS Text

Title: 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.

Data retrieved from NASA's ASRS site as of May 2009 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.

Attributes
ACN	812396
Time
Date	200809
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : zzz.airport
State Reference	US
Altitude	agl single value : 0
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	A319
Operating Under FAR Part	Part 121
Flight Phase	ground : preflight
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	other personnel
ASRS Report	812396
Events
Anomaly	other anomaly other
Independent Detector	other other : 1
Resolutory Action	none taken : anomaly accepted
Supplementary
Problem Areas	FAA Company
Primary Problem	Ambiguous

Dispatcher describes confused flight plan event when ATC alleged incorrect departure airport information and ICAO coding data; all resulting in lack of clearance information.