Narrative:

Received digital pre departure clearance from vhhh delivery. We printed out and reviewed the frequencies and transponder code and verified our pre-briefed speed constraints on the departure (SID). The company filed SID for this leg was the ocean 2A; however the clearance we received was for the rasse 3A. Expecting the ocean 2A we missed the change in our clearance as this is not only the SID we 'always' receive on this leg but; also the one listed in our flight plan. After departure; with the autopilot engaged we mistakenly began following the ocean 2A. The controller asked us to verify that we following the rasse 3A and I responded that we were following the ocean 2A. He said; 'no problem; I can fix that;' and gave us a series of headings to fly. Shortly thereafter the controller cleared us direct to ocean intersection and explained that at this time of night they use the rasse 3A for noise abatement purposes. All 3 pilots were in the cockpit when we reviewed the clearance; and we all missed the change of departure procedure. Even though we had a 30 hour layover in vhhh; none of us were able to get good sleep prior to the flight which had a hotel departure time of shortly after midnight local.I believe this contributed to us making 2 major procedural errors. First; when the pre departure clearance was received; we did not thoroughly read aloud; word for word; the body of the clearance. Second; we neglected to write the clearance down on the mfp; as is standard procedure; in addition to creating a printed copy. Adherence to these procedures would have alerted us to the change in the SID and we would have modified the FMC loaded flight plan accordingly. After the incident; while enroute; we all reviewed the chart departure notes and found that the rasse departures are normal night time noise abatement procedures. Unfortunately; none of us usually fly this particular (late night) trip and the fatigue feed complacency sent us down a path of 'doing what we're used to.'in the future; I'm sure this experience will cause all of us to more closely adhere to the standard procedures. Another help would be if the dispatchers were also familiar with the operating procedure at the airport and filed the appropriate departure. Maybe he or she was in the same boat as the crew and was just used to always filing this plan the same way. I'm not trying to criticize or blame the dispatcher. The responsibility rest solely with the crew; specifically with me as the PIC; but had we noticed an 'unusual' SID on the flight plan maybe we would have caught it there.

Related reports:

Google
 

Original NASA ASRS Text

Title: A cargo flight left VHHH very early morning with a the pilot crew all of whom misread the PDC revised clearance and mis-programmed the FMS because of fatigue and circadian rhythm effects.

Narrative: Received digital PDC from VHHH delivery. We printed out and reviewed the frequencies and transponder code and verified our pre-briefed speed constraints on the departure (SID). The company filed SID for this leg was the OCEAN 2A; however the clearance we received was for the RASSE 3A. Expecting the OCEAN 2A we missed the change in our clearance as this is not only the SID we 'always' receive on this leg but; also the one listed in our flight plan. After departure; with the autopilot engaged we mistakenly began following the OCEAN 2A. The Controller asked us to verify that we following the RASSE 3A and I responded that we were following the OCEAN 2A. He said; 'No problem; I can fix that;' and gave us a series of headings to fly. Shortly thereafter the Controller cleared us direct to OCEAN Intersection and explained that at this time of night they use the RASSE 3A for noise abatement purposes. All 3 pilots were in the cockpit when we reviewed the clearance; and we all missed the change of departure procedure. Even though we had a 30 hour layover in VHHH; none of us were able to get good sleep prior to the flight which had a hotel departure time of shortly after midnight local.I believe this contributed to us making 2 major procedural errors. First; when the PDC was received; we did not thoroughly read aloud; word for word; the body of the clearance. Second; we neglected to write the clearance down on the MFP; as is standard procedure; in addition to creating a printed copy. Adherence to these procedures would have alerted us to the change in the SID and we would have modified the FMC loaded flight plan accordingly. After the incident; while enroute; we all reviewed the chart departure notes and found that the RASSE departures are normal night time noise abatement procedures. Unfortunately; none of us usually fly this particular (late night) trip and the fatigue feed complacency sent us down a path of 'doing what we're used to.'In the future; I'm sure this experience will cause all of us to more closely adhere to the standard procedures. Another help would be if the dispatchers were also familiar with the operating procedure at the airport and filed the appropriate departure. Maybe he or she was in the same boat as the crew and was just used to always filing this plan the same way. I'm not trying to criticize or blame the Dispatcher. The responsibility rest solely with the crew; specifically with me as the PIC; but had we noticed an 'unusual' SID on the flight plan maybe we would have caught it there.

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.