2011-11 · NASA ASRS report 978740
Despite what appeared to be perfectly normal and accurate aircraft and software responses to flying the DAWGS RNAV SID from Runway 8R at ATL; ATC advised the flight crew of a Lear 45 that had flown nearly six miles off course before turning toward RONNI waypoint; their first fix following takeoff. ATC advised this was only one of a number of track deviation associated with newly instituted RNAV SIDs from ATL.
We were assigned Runway 8R and the DAWGS5 departure; SPA transition. My First Officer entered the departure runway and procedure in the FMS and I confirmed it. We were asked by Ground Control to confirm it to them and note 'RNAV to RONNI.' We did that; concurrently cross-checking the FMS again. Upon receiving our take off clearance we also confirmed the information with the Tower and cross-checked the FMS a third time. We took off and proceeded to follow the 092 heading toward the intercept of the 079 course to RONNI. We followed the FMS noting it gave us a turn toward RONNI and sequenced to go to RONNI. Both FMS needles were aligned on course. We also verified the turn toward RONNI occurred at the point where the FMS placed the intercept 'X' on the MFD as well. By all indications in the cockpit to me and my First Officer; everything was operating as it should. We were talking to Atlanta Departure at this point and; after the turn toward RONNI; were asked to confirm that we were direct RONNI. We replied affirmative; we were direct RONNI. Shortly after the Departure Controller asked us to call the Tower when able and gave us a number regarding a possible pilot deviation. At that point; we had no idea what he was talking about. After we landed we called Atlanta Tower. He said that the radar track of the aircraft showed us about 5 miles east of the airport and out of 6;000 FT before making the turn to RONNI. He said the turn should normally have been within about 1.5 miles (if I recall correctly). He said these are all new procedures and they are trying to determine if deviations they've noted thus far are due to GA equipment problems or due to some other reason. Without outlining specifics; he noted there were three deviations; including our alleged deviation that they were looking into. He noted the only way they could see to sort the problems out was to file deviations to start an investigation. Accordingly; he said he intended to file a pilot deviation.The cause of the alleged deviation is not readily apparent to us. The only thing I would say is that we be cautious about accepting these departures out of Atlanta until we are sure the FMS is navigating them properly. The departure procedures are apparently all new. We did verify the FMS was current before departure.
No additional information was provided in the second narrative.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.
Loading the flight search…
Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.
We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.
Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.
Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.