ZME Controller voiced concern regarding existing procedures that place ATL arrival and departure aircraft in opposite direction conflicts; offering a number of routing alternative solutions.

Narrative

This is a daily occurrence in Area 5 at ZME. To date nothing positive has occurred. The severe consequences of aircraft departing the ATL airport routed over BNA to points beyond is a threat to safety when all of the arrivals to the ATL airport are required to cross the ZME/ZTL boundary at FL330 or below; spaced in a single line over BNA head-on with the opposite direction ATL departing traffic. The departures from ATL are climbing in the face of the arrival traffic that is forced to descend in a single line with only forty-five miles to the common boundary. This scenario is repeated throughout the workday. The highly ardent controller reaches out with three phone calls; three coordination calls minimum; and routes the aircraft away from the arrival stream. This involves entirely too much coordination and is a true risk to the safety of the operation when such a simple solution exists. The solution to this risk is to assign aircraft departing ATL routes over the CARPT intersection (ATL departure corridor) near GQO. These routes would be as follows: All RNAV equipped aircraft on assigned routes from over the CARPT intersection direct the following fixes - FIX/DEST AIRPORT; HEADING FROM 'CARPT' BWG 'MULTIPLE' 331 (also use for /W equipped aircraft) BMI BMI 333 MLI MLI329 ALO 'MSP326 KM39O' DEN333. Sample routing to MSP-ATL..CARPT..ALO.KASPR4. MSP Sample routing to MLI-ATL..CARPT..MZV..MLI. In the example for an aircraft destination of DEN; the Area 5 controllers could turn the aircraft in the direction of FAM as soon as feasible before reaching the KM39O fix 40 miles northeast of BNA.