An 'eastbound' mem departure controller took prompt action to redirect a 'westbound' air carrier dep...

Narrative:

I was training a developmental on east departures during a south flow late night shift. We observed a target depart runway 18R--a westbound departure runway--instead continue south then turn southeast. This put the aircraft in confliction with our departure off runway 18L. I immediately overkeyed my developmental trying to get hold of our departure so I could turn him away from the traffic cutting in front of him. Our flight was not on my frequency; however the 18R departure did check on with me; and I immediately turned that straying aircraft away from my traffic.memphis should terminate the use of the RNAV sids; and start using issued headings off the airport. Let the departure controller issue the clearance to join the cleared RNAV SID. Don't rely on the pilot to go to the right initial fix. If they programmed their FMS wrong they're in a critical phase of flight and in close proximity to other departures. By the time a controller notices the wrong heading; the aircraft may be switching frequencies and might go to the wrong frequency. Maybe distracted by the wrong heading and trying to correct; or getting a TCAS RA from the traffic they cut off.

Original NASA ASRS Text

Title: An 'eastbound' MEM Departure Controller took prompt action to redirect a 'westbound' air carrier departure off of Runway 18R who had apparently programmed the wrong RNAV SID and was conflicting with the reporter's legitimate eastbound departure aircraft off Runway 18L.

Narrative: I was training a Developmental on east departures during a south flow late night shift. We observed a target depart Runway 18R--a westbound departure runway--instead continue south then turn southeast. This put the aircraft in confliction with our departure off Runway 18L. I immediately overkeyed my Developmental trying to get hold of our departure so I could turn him away from the traffic cutting in front of him. Our flight was not on my frequency; however the 18R departure did check on with me; and I immediately turned that straying aircraft away from my traffic.Memphis should terminate the use of the RNAV SIDs; and start using issued headings off the airport. Let the Departure Controller issue the clearance to join the cleared RNAV SID. Don't rely on the pilot to go to the right initial fix. If they programmed their FMS wrong they're in a critical phase of flight and in close proximity to other departures. By the time a controller notices the wrong heading; the aircraft may be switching frequencies and might go to the wrong frequency. Maybe distracted by the wrong heading and trying to correct; or getting a TCAS RA from the traffic they cut off.

Data retrieved from NASA's ASRS site as of July 2013 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	1032944
Time
Date	201208
Local Time Of Day	0601-1200
Place
Locale Reference	MEM.Airport
State Reference	TN
Environment
Light	Night
Aircraft 1
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Flight Phase	Initial Climb
Flight Plan	IFR
Aircraft 2
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Flight Phase	Initial Climb
Flight Plan	IFR
Person 1
Function	Departure
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Track / Heading All Types

An 'eastbound' mem departure controller took prompt action to redirect a 'westbound' air carrier departure off of runway 18R who had apparently programmed the wrong RNAV SID and was conflicting with the reporter's legitimate eastbound departure aircraft off runway 18L.