Widebody Transport
Confusion; Situational Awareness; Communication Breakdown
Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter CFTT / CFIT
Air Traffic Control Issued Advisory / Alert; Flight Crew Returned To Clearance; Flight Crew Took Evasive Action; Flight Crew Became Reoriented
Human Factors
Normal operations preceded this event and standard briefings were completed. The Captain called for a Preflight checklist prior to receiving the clearance so I mention that we should get one prior to running the checklist. There was a delay in getting the clearance because the automated PDC was unusable. The departure clearance was given and copied by me. It had a minor change to it as we were originally filed for the RASE3C departure. The change was to the RASE1E departure. Immediately after receiving the clearance; the Captain and other non-flying First Officer; in the observer's seat discussed the new departure; but I was preoccupied trying to get the checklist to display on my MFDU panel. Nor did I see the departure being loaded into the FMC. There was a brief discussion about the differences on the departure; and specifically the PORPA waypoint. I believe the discussion resulted in the PORPA waypoint actually being deleted from the departure; but I did not see that happen. There was also a very short briefing about the new departure procedure that followed; and although I was not part of the discussion; I concurred with the other two pilots as to the accuracy of the departure. I did so having only given a quick glance at the departure chart. There was no fix-by-fix briefing of the new departure; or any mention of flyover waypoints. Had I taken the time to review the departure completely this may never had happened.The takeoff was normal; and the left autopilot was armed shortly after liftoff. Almost immediately after takeoff; the Hong Kong Tower and departure controllers began to query about our flight path because I believe the deleted waypoint resulted in the aircraft making a turn to the right toward the PORSH waypoint. The Captain seemed aware of the course deviation and had already begun to correct our path when ATC questioned us. The Captain said to me we are returning to course; and I respond to ATC with this information.Only moments later; the Ground Proximity Warning system activated with a terrain warning. The Captain responded as required and continued a turn to the left away from terrain and to regain the proper ground track. After clearing the terrain conflict; the left autopilot was re-engaged; and the departure continued without further incidence.Several factors led to this event. One was poor and non-standard communication in the flight deck. Although I read about the waypoints as being flyover points; I had forgotten about that as I was very focused on making sure I had completed all of my other duties as First Officer. This should have been a very important time on the preflight briefing; and it was omitted by ALL pilots. Another was the late clearance delivery with a change to what we were expecting. There were similar sounding and looking waypoints right next to each other (PORPA; PORSH) that may have led to some confusion; but I don't understand how a waypoint; with bold red lettering about required speed and altitude could have deliberately been deleted from a departure that was loaded from the FMC.
Widebody First Officer reported receiving a GPWS terrain warning when they flew an incorrect track departing VHHH.