A controller described an RNAV departure event where an aircraft assigned the RNAV to snufy failed t...

Narrative:

I working local control-2 and cleared CRJ2 for takeoff runway 26L with RNAV to snufy. After placing the subsequent aircraft in position my attention was diverted to local control-1 with a B757 rolling long and a minimum fuel aircraft on short final. After ensuring that a go around situation did not exist I cleared the second aircraft for takeoff runway 26L RNAV to impas. I then completed my scan and noticed that the CRJ2 was turning to a northbound heading. I observed the aircraft preceding the CRJ2 out of seven thousand feet and determined him to be no factor. I quickly turned the CRJ2 to a 250 heading for a vector for snufy; with the intention of stopping the trailing aircraft at 3;000 ft. I called north departure for coordination. Departure instructed me to assign a three hundred degree heading. I told the CRJ2 to fly heading three zero zero. After ensuring no conflicts with the trailing or leading aircraft I switched the CRJ2 to departure. To ensure this type of event does not happen in the future I recommend that all atl departures be assigned initial headings off the ground versus RNAV off the ground..

Original NASA ASRS Text

Title: A Controller described an RNAV departure event where an aircraft assigned the RNAV to SNUFY failed to initiate the required turn. Suggested that RNAV departures be assigned an initial vector to prevent future occurrences.

Narrative: I working LC-2 and cleared CRJ2 for takeoff Runway 26L with RNAV to SNUFY. After placing the subsequent aircraft in position my attention was diverted to LC-1 with a B757 rolling long and a minimum fuel aircraft on short final. After ensuring that a go around situation did not exist I cleared the second aircraft for takeoff Runway 26L RNAV to IMPAS. I then completed my scan and noticed that the CRJ2 was turning to a northbound heading. I observed the aircraft preceding the CRJ2 out of seven thousand feet and determined him to be no factor. I quickly turned the CRJ2 to a 250 heading for a vector for SNUFY; with the intention of stopping the trailing aircraft at 3;000 FT. I called North Departure for coordination. Departure instructed me to assign a three hundred degree heading. I told the CRJ2 to fly heading three zero zero. After ensuring no conflicts with the trailing or leading aircraft I switched the CRJ2 to departure. To ensure this type of event does not happen in the future I recommend that all ATL departures be assigned initial headings off the ground versus RNAV off the ground..

Data retrieved from NASA's ASRS site as of April 2012 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	913407
Time
Date	201010
Local Time Of Day	1201-1800
Place
Locale Reference	ATL.Tower
State Reference	GA
Aircraft 1
Make Model Name	Regional Jet 200 ER/LR (CRJ200)
Operating Under FAR Part	Part 121
Flight Phase	Initial Climb
Flight Plan	IFR
Person 1
Function	Local
Qualification	Air Traffic Control Fully Certified
Person 2
Function	Pilot Not Flying Check Pilot
Events
Anomaly	Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types

A controller described an RNAV departure event where an aircraft assigned the RNAV to snufy failed to initiate the required turn. Suggested that RNAV departures be assigned an initial vector to prevent future occurrences.