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.

Date: 2010-10 · Aircraft: Regional Jet 200 ER/LR (CRJ200) · Phase: initial_climb

Anomalies: deviation-track-heading-all-types|deviation-discrepancy-procedural-published-material-policy|deviation-discrepancy-procedural-clearance

Synopsis

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..

Second reporter narrative

After take off from Runway 26L the FMS captured and the flight director indicated a turn to the right away from the runway heading. The first way point on the RMBLN Departure was SNUFY. I noticed; after the FMS captured; that the RNAV data had dropped out and was in the process of reloading the data. The aircraft was heading 330 and correcting to the left at the time the Tower made the initial call. The Tower asked the reason for the deviation. I explained the RNAV (RMBLN) and the first way point SNUFY had dropped out and that we were in the process of reloading and correcting course. Tower gave us heading of 300; maintain 8;000 and to contact ATL Departure. ATL Departure cleared us to 10;000 and direct to RMBLN. The rest of the flight was conducted without incident. Not sure why the runway dropped out. Everything was briefed and reviewed correctly. Closer observation of the MFD would help detection of way point failures during Take Off and notifying ATC. The detection of the failure in this instance happened during the highest work load point in the take off phase.

More incidents for this aircraft family →

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.