Any Unknown or Unlisted Aircraft Manufacturer
Air Traffic Control Fully Certified
Communication Breakdown
ATC Issue All Types; Deviation / Discrepancy - Procedural Other / Unknown
General None Reported / Taken
Company Policy; Procedure
I would imagine this problem is system wide. Aircraft 'A' has more than one (1) or multiple Flight Plan/s pending off of 1 specific domicile/airport. Unknowingly to the pilot and company; this creates confusion within the Air Traffic Control System. Example A: A foreign air carrier who files multiple flight plans with routes that differ well into the 'Body' of the routing many miles away from it's point of departure/over the Atlantic Ocean. Because multiple routes filed by the user are different; to the same destination; the potential for a mishap is greatly increased due to the existence of more than one flight plan being in the system. Add the language barrier; and you're asking for trouble. Example B: N12345 files multiple flight plans to different destinations off of the same domicile/airport. His problem is that his 1st choice is on an EDCT Program etc. So; he decides to file for something else to another airport close to his 1st choice airport. The problem is; he's got 2 flight plans pending in the system; with one flight progress strip at one position (i.e.: Flight Data or Ground Control); and another totally different flight progress strip (with the same call sign/different airport destination and route) at another position in the Tower. Example C: Swap Event in effect the Hub. So; now the major players decide to file multiple routes/flight plans to their destinations simultaneously due to weather avoidance. Despite ATC discouraging this activity; it happens all of the time. The ability to track flight plans is strained and breaks down; causing confusion among pilots and controllers both inter and intra-facility. Here's your logical fix to this dangerous problem: Do Not Allow Any Aircraft and the people who file flight plans on their behalf; to file more than (1) one flight plan off of the same domicile/airport simultaneously. The host computer can; and should generate a message to effect of saying 'Reject: Flight Plan Pending off of this Domicile'. Then the person entering the flight plan on behalf of the user (Flight Service etc) would have to query the user of their intentions; to either remove their current flight plan; or leave the one alone that already exists in the system. This fix also reduces the amount of 'Squawk Codes' issued by the host computer; as you are allocated 'one code per customer/user'. Four digit Codes are at a premium; especially during Swap Events.
IAD Controller voiced concern regarding the on-going issue of multiple flight plans being filed by the company that frequently result in confused and uncertain routing information.