Flight crew reported malfunctioning navigation and flight deck displays required a diversion to nearby airport.

Date: 2024-09 · Aircraft: B787 Dreamliner Undifferentiated or Other Model · Phase: cruise

Anomalies: aircraft-equipment-problem-critical

Synopsis

Flight crew reported malfunctioning navigation and flight deck displays required a diversion to nearby airport.

Narrative

Cruising at 350 towards ZZZZ. Both of the Captain's HDD (Head Down Display) screens PFD (Primary Flight Display) and ND (Navigation Display) failed to a blank display with a slight dim backlighting. They could not be controlled; swapped; or recovered. In addition; both FMCs entered a highly degraded mode. Both FMC keypads would not type entries into the scratchpads; both FMCs had very limited capability. Could not line select anything to the scratchpads; could not make entries to ACARS or CPDLC. We could cycle through FMC pages; but could not make any entries or modifications to the FMC. For the rest of the flight the FMC was locked into going to ZZZZ. Only could communicate via VHF or SATCOM. Loss of the FMCs led to loss of LNAV; only lateral modes we had available were HDG (Heading) or TRK (Track). No ECL (Electronic Checklist) checklists were generated and no status messages either. [Advised ATC] and proceeded to divert to ZZZ via alternate navigation and vectors from ATC; ZZZ was 2 hours away. We consulted with Dispatch; Maintenance Control; and a fleet specialist via SATCOM in an attempt to troubleshoot but to no avail. Everyone was briefed and I decided the FO would be PF as he had the only working screens. Both HUDS (Heads up Display System) were still working along with lower MFDs (Multi-function Flight Display). Vectored by ZZZ to join localizer for [Runway] XXC; we coupled up; but many new anomalies were noted. On the FOs PFD; no DME; no glideslope pointer. Only glideslope pointers were on the HUDS and the IFSD (Integrated Standby Flight Display). No autoland annunciation at low altitude along with various EICAS messages on short final. Landing was normal; but FMC still was trying to go to ZZZZ.

Second reporter narrative

I was pilot monitoring and on the second break during the event. I was called roughly 1/2 way through my break and told we had some loss of some displays and we were diverting to ZZZ and the functioning displays were on the First Officer side of the aircraft so I would be performing the landing in about 2 hours. I returned to the cockpit to discover the CA's PFD (Primary Flight Display) and MFD (Multi-function Flight Display) blank; and both keypads for data entry to the FMC's inoperative. The Captain was talking to Dispatch and Maintenance and as this was also a line check flight; the LCA (Line Check Airman) was in the First Officer seat flying and the Relief Pilot was in the jumpseat. I switched places with the LCA and became the pilot flying. We were diverting to ZZZ at FL340 in heading mode using vectors. Because there was no data entry available; we were unable to program a new destination; routes; use the divert page or use any ACARS functions rendering LNAV; VNAV the VSD (Vertical Situation Display) unusable.Alternate nav was still available to tune an ILS and program a LAT/LONG to get distance and bearing.We flew radar vectors to intercept the ILS [Runway] XXC in VFR conditions. Upon descending through FL180 we got a baro set disagree because the Captains was still set for previous setting and mine was set to ZZZ (his was uncontrollable). We were unable to obtain landing data or ref speeds via the FMCS and ACARS so Dispatch pushed that to us. Because we could not enter the speeds into the FMCS; the HUD (Heads Up Display) did not generate a 3 degree descent angle and when we selected flaps 30 the checklist would not complete saying the flaps were not set correctly however they did display correctly on the MFD. At glide slope intercept the standby attitude indicator did show LOC and GS however my PFD did not; the HUD displayed correctly however we were unable to get DME readings. We flew this to an uneventful landing in ZZZ and taxied to the gate. None of the moving maps worked because we could never tell the computer we were diverting to ZZZ.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.