Narrative:

The captain and I had brief the marica 1 departure from runway 10 with the botom transition departing sbgl. We also briefed the engine out procedure from runway 10 in great detail. The FMC was loaded and 3 fix pages were used to depict the engine out procedure for runway 10. Sbgl clearance informed us that a large amount of runway 10 was not available for ttakeoff and asked us for our intentions. We requested runway 15 and were given the obil departure botom trans from runway 15. We erased all the fix pages and built the eo (engine out) procedure for runway 15 consisting of 3 fix pages and again thoroughly briefed the new eo procedure. (Many lines and circles) the runway; departure; and transition were entered into the FMC. The legs page showed obil..dacir etc. I did not see any discontinuities. During taxi as I was accomplishing the before takeoff checklist. I selected the route page 1 and read 'runway 15'; upon selecting route page 2; it did not show the obil departure only showing obil as the first point. I brought this to the captain's attention; stating that I have never seen this before. We rechecked our entries and the captain stated it was good because all the fixes were on the legs page (he read them off a couple of times to me). I let myself get talked into this being just a glitch and that everything was ok. Shortly after takeoff; I realized that the LNAV did not engage. Looking down at the departure chart; I could not match it to anything that was on my navigation display. At this time I thought the sid required us to continue straight ahead; I asked for the 245 radial out of pcx be entered. Captain had trouble establishing communications with ATC (flight int selected); was unable to give me any assistance to get back on course or clear up the clutter from the eo procedure on the navigation display. We never flew to obil and as I was turning to set up an intercept heading for the pcx 245 radial; ATC cleared us direct to botom. No indication from ATC of any conflicts or problems other than the initial check in. The next day I tried to enter the runway 15 obil departure botom transition on a different aircraft. The SID does not load correctly and would require some other input to establish an intercept on the 113 bearing out of it to obil. Although this FMC issue may have contributed to the navigation deviation; I believe upon reflection that some distraction while loading this different runway; departure; eo procedure and our briefings; unintentionally prevented a thorough briefing of the SID to be accomplished. It was a very unsettling realization that I did not know where we were suppose to be on this departure. Multiple red flags were present; it's suppose to show the departure; here not catching the magenta line missing from the runway; by not briefing the SID (unintentionally) we missed that obil is actually 10 NM from the airport from the note (scale selected did not make obil jump out with all the clutter already on the navigation display? Also the arcing turn off obil on the chart was depicted as a straight line on the navigation display). From now on if something is different than what is expected; I will take whatever time is necessary to resolve the conflict. Also from now on if any change happens to the clearance; I will pull out my briefing card to ensure all items are covered thoroughly (runway data; SID; engine out procedure; etc). Additionally a text description of the sids would have been helpful. It could go without saying that I will not only have future sids briefed and planned as if there will be no LNAV available but also approaches; missed approaches; and eo procedure as well. Luckily there was no conflict with traffic or terrain that I am aware of.

Google
 

Original NASA ASRS Text

Title: B777 flight crew departing SBGL has track deviation attempting to fly the OBIL departure with the BOTOM transition. Distractions prior to departure prevented the crew from properly checking that the SID was loaded correctly.

Narrative: The Captain and I had brief the MARICA 1 DEP from Runway 10 with the BOTOM transition departing SBGL. We also briefed the engine out procedure from Runway 10 in great detail. The FMC was loaded and 3 fix pages were used to depict the engine out procedure for Runway 10. SBGL clearance informed us that a large amount of Runway 10 was not available for Ttakeoff and asked us for our intentions. We requested Runway 15 and were given the OBIL DEPARTURE BOTOM TRANS from Runway 15. We erased all the fix pages and built the EO (engine out) procedure for Runway 15 consisting of 3 fix pages and again thoroughly briefed the new EO procedure. (many lines and circles) The runway; departure; and transition were entered into the FMC. The LEGS page showed OBIL..DACIR etc. I did not see any discontinuities. During taxi as I was accomplishing the Before Takeoff checklist. I selected the route page 1 and read 'Runway 15'; upon selecting route page 2; it did not show the OBIL departure only showing OBIL as the first point. I brought this to the Captain's attention; stating that I have never seen this before. We rechecked our entries and the Captain stated it was good because all the fixes were on the legs page (He read them off a couple of times to me). I let myself get talked into this being just a glitch and that everything was ok. Shortly after takeoff; I realized that the LNAV did not engage. Looking down at the departure chart; I could not match it to anything that was on my NAV display. At this time I thought the sid required us to continue straight ahead; I asked for the 245 Radial out of PCX be entered. Captain had trouble establishing communications with ATC (FLT INT selected); was unable to give me any assistance to get back on course or clear up the clutter from the EO procedure on the NAV display. We never flew to OBIL and as I was turning to set up an intercept heading for the PCX 245 Radial; ATC cleared us direct to BOTOM. No indication from ATC of any conflicts or problems other than the initial check in. The next day I tried to enter the Runway 15 OBIL departure BOTOM transition on a different aircraft. The SID does not load correctly and would require some other input to establish an intercept on the 113 bearing out of IT to OBIL. Although this FMC issue may have contributed to the NAV DEV; I believe upon reflection that some distraction while loading this different runway; departure; EO procedure and our briefings; unintentionally prevented a thorough briefing of the SID to be accomplished. It was a very unsettling realization that I did not know where we were suppose to be on this departure. Multiple red flags were present; It's suppose to show the departure; here not catching the magenta line missing from the runway; by not briefing the SID (unintentionally) we missed that OBIL is actually 10 NM from the airport from the note (scale selected did not make OBIL jump out with all the clutter already on the NAV display? Also the arcing turn off OBIL on the chart was depicted as a straight line on the NAV display). From now on if something is different than what is expected; I will take whatever time is necessary to resolve the conflict. Also from now on if any change happens to the clearance; I will pull out my briefing card to ensure all items are covered thoroughly (Runway Data; SID; engine out procedure; etc). Additionally a text description of the SIDs would have been helpful. It could go without saying that I will not only have future SIDs briefed and planned as if there will be no LNAV available but also approaches; missed approaches; and EO procedure as well. Luckily there was no conflict with traffic or terrain that I am aware of.

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.