Any Unknown or Unlisted Aircraft Manufacturer
Air Traffic Control Fully Certified
Air Traffic Control Time Certified In Pos 1 (yrs) 22
Communication Breakdown; Confusion; Troubleshooting
ATC Issue All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Air Traffic Control Provided Assistance
Airspace Structure; Procedure
The flight plan on Aircraft X had what appeared to be an erroneous route element that resulted in erroneous flight projection through airspace that the aircraft will never fly.  This same flight plan error has occurred before; and the confusion between intersections JAWSS/JAWWS is known to ZME/ZTL/ZJX.  However; this flight plan was allowed to progress through ZJX and ZTL without attention or correction before it was noticed by ZME and finally corrected.  I called the preceding ATC facility; Birmingham Approach; and inquired about the flight; she noted that she had a strip on the aircraft that estimated he should already be in her airspace but she did not know anything about it; I asked her to check with the preceding sector (ZTL BHM-L) and inquire about it and get them to correct it.  I informed my FLM; who informed the OSIC.  About 15 minutes late I got a land line call from ZTL saying that Aircraft Y (notice 'Y'; instead of X) was a bad flight plan and I should remove strips on him.  Came to learn that Aircraft Y had been noticed by a previous ZME Controller on the same bad flight plan and the same issue had been brought to ZTL attention.  I clarified with ZTL that I was still waiting for information on Aircraft X; and he said that if he had the same flight plan that it was a bad fix and I should just remove strips on him too. I explained that I didn't know if it was the same flight plan.  I verified that he wanted me to remove strips on both aircraft and he confirmed it; then said 'bye' (operating initials unknown). I removed strips on both aircraft and advised my FLM and; as I was then leaving on break; I saw the OSIC still holding a strip and advised him.  He seemed dissatisfied that ZTL still had not returned his call that spurred the investigative process and set the strip aside for future reference.A flight plan gives ATC knowledge of where an aircraft is going and when he will be at a given point.  When an aircraft does not appear at the expected location at the expected time; it should be cause for concern.  This is the trigger for initiating search and rescue.  If ATC does not monitor flight plan accuracy and progression then they cannot maintain any awareness of the aircraft's projected position and movement through the NAS.  All controllers should monitor their strips/URET/EDST for expected/arriving traffic and notice if they do not show up at the expected location at the expected time; this should be an entry level D-side function that all CPC's do well.  Once a bad flight plan element is discovered; it should not be ignored - controllers must manage flight plans effectively to communicate accurate information to adjacent facilities.  The erroneous route element should be amended to show the aircraft's correct route of flight; then any non-participant ATC facilities will simply get a 'remove strip' message and any involved ATC facilities will have valid effective information they can use to ensure positive separation.  When ZTL called me and asked me to remove strips; I had to use the /OK function because the flight plans had progressed so far.  ZTL could just have easily performed the same RS and used automated means of coordination in lieu of manual/verbal.
ZME controller reports of problems associated with similar sounding and written intersections.  Confusion of aircraft that may or may not be coming into their airspace.