Narrative:

Bottom line short version was took off on correct runway (xxr) but had xxl in FMC. Now the long version. This leg falls in the middle of an 11 day trip and was suspected to be the hardest night since 2 legs at night after acclimating to [a far off timezone]. We come off [several days] in [a different timezone; country a] and we both discussed the plan to try and mitigate fatigue during this segment. The plan was to get up early the morning of and then rest the afternoon prior to show. I got up [early morning] local time and got to bed [in the late afternoon] planning on a [light night] alert. Got right to sleep but wind conditions outside started creating a banging noise that awoke me. I was up for at least an hour but then finally fell hard asleep and awoke to the alert call. We briefed with a discussion about fatigue being a threat along with [country B] ops and language challenges being top of the list. The first leg went uneventful to ZZZZ with arrival slightly early. One issue that started to become evident was that the a/C conditioning system was louder than normal although a very new plane. During the turn we ate our catering; had more coffee and prepared for the [next] leg. After my setup I started feeling a bit tired so I leaned my chair back and closed my eyes for a few minutes. I heard the ACARS bing with the weight and balance and sat back upright to finish briefing. This is where we failed to capture the error on the FMC having been loaded with xxl. We had briefed the departure for xxr and all the points were identical to the left except for 1 degree heading difference. During the performance brief when the runway challenge was made I failed to notice the error. We started to have some other errors that happened such as wrong a call sign (ZZZZ tower was working various frequencies making it hard to talk to him) during pushback request; failure to send off the final [weight and balance] report. We started both engines in an attempt to mitigate errors since we were noticing small errors increasing. During this phase of our taxi I became more aware of the air conditioning noise which I think was starting to affect communication. We made several runway crossings and arrived at the holding point for xxr and held short. I checked my efb enroute page and realized it was incomplete so that became a distraction prior to entering the runway and another uncaptured error although it was on my i-pad and was corrected later in the efb. We were cleared to line up and wait then shortly after to takeoff. We verbalized runway signage upon entering the runway and on the runway but missed the FMC verification and after completion of the before takeoff checklist started the takeoff roll. After standing up power I pressed to/GA (take-off go-around) then got the EICAS regarding FMC runway disagree and by the time I processed this we were past 80 knots so I elected to continue the takeoff rather than do a high speed reject. Trey re-verified the initial departure points and the flight continued without further incident. After top of climb and after landing we discussed this at length and both feel fatigue was a major contributor to this chain of events. Side note: all the times referenced in the form and in the narrative are local times. I was unable to get the form to take UTC (it may be due to fatigue)I believe fatigue caused the chain of events that allowed our accidental incomplete procedures to prevent this particular error.I know this particular error won't happen to me again but I will be more aware of the onset of fatigue.

Related reports:

Google
 

Original NASA ASRS Text

Title: Flight Crew flying cargo aircraft reported improperly programmed Flight Management Computer.

Narrative: Bottom line short version was took off on correct runway (XXR) but had XXL in FMC. Now the long version. This leg falls in the middle of an 11 day trip and was suspected to be the hardest night since 2 legs at night after acclimating to [a far off timezone]. We come off [several days] in [a different timezone; Country A] and we both discussed the plan to try and mitigate fatigue during this segment. The plan was to get up early the morning of and then rest the afternoon prior to show. I got up [early morning] local time and got to bed [in the late afternoon] planning on a [light night] alert. Got right to sleep but wind conditions outside started creating a banging noise that awoke me. I was up for at least an hour but then finally fell hard asleep and awoke to the alert call. We briefed with a discussion about fatigue being a threat along with [Country B] ops and language challenges being top of the list. The first leg went uneventful to ZZZZ with arrival slightly early. One issue that started to become evident was that the A/C conditioning system was louder than normal although a very new plane. During the turn we ate our catering; had more coffee and prepared for the [next] leg. After my setup I started feeling a bit tired so I leaned my chair back and closed my eyes for a few minutes. I heard the ACARS bing with the weight and balance and sat back upright to finish briefing. This is where we failed to capture the error on the FMC having been loaded with XXL. We had briefed the departure for XXR and all the points were identical to the left except for 1 degree heading difference. During the performance brief when the runway challenge was made I failed to notice the error. We started to have some other errors that happened such as wrong a call sign (ZZZZ tower was working various frequencies making it hard to talk to him) during pushback request; failure to send off the final [Weight and Balance] report. We started both engines in an attempt to mitigate errors since we were noticing small errors increasing. During this phase of our taxi I became more aware of the air conditioning noise which I think was starting to affect communication. We made several runway crossings and arrived at the holding point for XXR and held short. I checked my EFB enroute page and realized it was incomplete so that became a distraction prior to entering the runway and another uncaptured error although it was on my I-pad and was corrected later in the EFB. We were cleared to line up and wait then shortly after to takeoff. We verbalized runway signage upon entering the runway and on the runway but missed the FMC verification and after completion of the before takeoff checklist started the takeoff roll. After standing up power I pressed TO/GA (Take-Off Go-Around) then got the EICAS regarding FMC runway disagree and by the time I processed this we were past 80 knots so I elected to continue the takeoff rather than do a high speed reject. Trey re-verified the initial departure points and the flight continued without further incident. After top of climb and after landing we discussed this at length and both feel fatigue was a major contributor to this chain of events. Side note: all the times referenced in the form and in the narrative are local times. I was unable to get the form to take UTC (it may be due to fatigue)I believe fatigue caused the chain of events that allowed our accidental incomplete procedures to prevent this particular error.I know this particular error won't happen to me again but I will be more aware of the onset of fatigue.

Data retrieved from NASA's ASRS site 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.