An aircraft departed atl after receiving a revised pre departure clearance SID which included the nu...

Attributes
ACN	920543
Time
Date	201011
Local Time Of Day	1201-1800
Place
Locale Reference	ATL.Airport
State Reference	GA
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Light Transport Low Wing 2 Turbojet Eng
Operating Under FAR Part	Part 121
Flight Phase	Climb
Route In Use	SID NUGGT4
Flight Plan	IFR
Component
Aircraft Component	FMS/FMC
Person 1
Function	Pilot Not Flying First Officer
Qualification	Flight Crew Multiengine Flight Crew Air Transport Pilot (ATP)
Experience	Flight Crew Last 90 Days 130 Flight Crew Total 5000 Flight Crew Type 700
Events
Anomaly	Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types

Narrative:

After I loaded the flight plan into the FMS with the summit four RNAV departure approximately 1 hour prior to departure and I requested the pre departure clearance 30 minutes prior to departure via ACARS (pre departure clearance). Our departure (SID) was changed by ATC from a summt four to a NUGGT4; we should have caught it; but we did not. The change on the routing comes in between the dashes; (ex:-summt4.summt-); but since the first two way points in both departure (SID) departing runway 26L were identical. The captain and I overlooked it; we figured out the problem after the ATC told us to call ATC after passing summt waypoint approx at 15000 feet. We did not have any conflict with another aircraft. At that point we re-checked the paper work and figured out the problem. I do believe that [fatigue] from the prior 14 hour duty day followed by an early duty-in; and the same initial waypoint in those sids are contributing factors. If the first waypoint in every SID were different it could raise a flag on the take off clearance; since when you are replying back the clearance you are looking at that waypoint on the screen.

Original NASA ASRS Text

Title: An aircraft departed ATL after receiving a revised PDC SID which included the NUGGT FOUR. The crew failed to remove the SUMMT FOUR from the FMC and so had a track deviation on departure.

Narrative: After I loaded the flight plan into the FMS with the SUMMIT FOUR RNAV departure approximately 1 hour prior to departure and I requested the PDC 30 minutes prior to departure via ACARS (PDC). Our departure (SID) was changed by ATC from a SUMMT FOUR to a NUGGT4; we should have caught it; but we did not. The change on the routing comes in between the dashes; (EX:-summt4.summt-); but since the first two way points in both departure (SID) departing RUNWAY 26L were identical. The Captain and I overlooked it; we figured out the problem after the ATC told us to call ATC after passing SUMMT waypoint approx at 15000 feet. We did not have any conflict with another aircraft. At that point we re-checked the paper work and figured out the problem. I do believe that [fatigue] from the prior 14 hour duty day followed by an early duty-in; and the same initial waypoint in those SIDS are contributing factors. If the first waypoint in every SID were different it could raise a flag on the take off clearance; since when you are replying back the clearance you are looking at that waypoint on the screen.

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.

An aircraft departed atl after receiving a revised pre departure clearance SID which included the nuggt four. The crew failed to remove the summt four from the FMC and so had a track deviation on departure.