ZME Controller described a confused STAR transition routing event that caused an unexpected turn by the flight crew; noting the subject transition should be eliminated.

Narrative

This same event occurred earlier this year. Approximately sixty days ago; I thought that I had resolved the problem with ATC personnel at the subject airline. The problem is a result of a STAR transition that is no longer required for traffic destination STL. ZME Area 5 flight plan data indicates aircraft from ATL destination STL are flying on the following route: ATL..CARPT..BNA..CGI.QBALL6.STL. The BNA to CGI portion is a heading from BNA of 296. Many times the aircraft makes a turn at BNA and heads west 277 to the VISQUA Intersection on the BNA transition of the QBALL arrival. The Controller is certainly not expecting this event and due to the lag in the RADAR display; exacerbated in Area 5 by the location of the QOJ; Nashville RADAR system; the turn causes panic due to the close boundaries of Sectors 61; 62; 63; 33; and 26. Previously; airlines personnel indicated that the problem existed due to several factors; FMS; type of aircraft equipment; and flight crew knowledge of the route. The ZME Controllers rely on accurate flight plan data contained in the HOST computer system. If a flight plan indicates one route and the aircraft follows something different; we can only expect that soon our luck will run out and major risk will prevail. Recommendation; the BNA transition of the STAR should be eliminated. The routing should be BNA..CGI.QBALL6.STL.