Date: 201706
Local time of day: 1801-2400
Location: EGLL.Airport, FO
Flight conditions: Marginal
Weather elements / visibility: Turbulence
Light: Dusk
Aircraft: B777 Undifferentiated or Other Model
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Approach
ATC / advisory: TRACON EGLL
Aircraft component: Navigational Equipment and Processing
Component problem: Improperly Operated
Reporter organization: Air Carrier
Reporter function: Captain; Pilot Not Flying
Reporter qualification: Flight Crew Air Transport Pilot (ATP)
Human factors: Situational Awareness; Fatigue; Confusion; Time Pressure; Workload
Anomaly: Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Flight Crew
When detected: In-flight
Result: Air Traffic Control Issued Advisory / Alert; Flight Crew FLC Overrode Automation; Flight Crew Became Reoriented; Flight Crew Took Evasive Action
Contributing factors: Aircraft; Procedure; Human Factors
Primary problem: Procedure

Narrative: London Final Approach has our aircraft on a vector; base leg for Runway 27R. Approach for 27R had been selected and briefed and instead of the usual holding pattern at Ockham; the controller put us on a heading and descent for the approach without delay. On base leg controller gave us a 300 degree heading to intercept the localizer and once on the LOC descend on the glideslope. Aircraft displayed LOC Capture and began turning to intercept the final course 27L. ILS ERROR came up on the FMC. We noted aloud the Aircraft was aligning on the wrong runway. Approach reminded us we were cleared for 27R. We acknowledged we had a NAV anomaly; we resumed 300 degrees using raw data while I manually typed in the proper ILS frequency for 27R. Localizer and glideslope were intercepted; approach continued and landing was successfully achieved without incident. At no time was a break out required nor was any evasive maneuver required during the anomaly. FMC NAV Error was recorded in Maintenance Logbook for follow-up investigation upon flight termination. The FMC locked into the frequency for the ILS to 27L when it was selected on the ground during the FMC preflight programming of the entire route. The ILS Identifier is in the upper left quadrant of the PFD. Our normal cadence for preparation was thrown off slightly when we transitioned from expecting a hold at OCK to being cleared right into Heathrow. This expeditious handling got us saturated into configuration (speed slow down; descent profile for the CDA profile) and the ILS Frequencies was omitted out of our cross check. It wasn't until the aircraft actually turned to the parallel runway did we notice the discrepancy along with the ILS ERROR message on the FMC.I suggest ALWAYS cross check that the ILS Frequency for your Selected Approach is in the upper left of your PFD. Don't assume the aircraft will ALWAYS automatically select the proper frequency despite that being on this aircraft [for a while] this anomaly has never happened to me. Just because the Map display is correct; doesn't mean the Navaids have followed.




Synopsis: A B777 Captain reported programming the FMC incorrectly during preflight and lined up for the parallel runway.