B737 MAX Captain reported systems failures and communications problems led to a landing on the wrong runway instead of performing a Go-Around. A Tower Controller also reported on the wrong runway landing.
Synopsis
B737 MAX Captain reported systems failures and communications problems led to a landing on the wrong runway instead of performing a Go-Around. A Tower Controller also reported on the wrong runway landing.
Narrative
Dispatched in MAX; ZZZ1 to ZZZ with flight planned landing Runway of XXL. Before descending briefed ZZZZZ RNAV arrival; briefed and loaded RNAV/GPS Y XXC per ATIS. Initial contact with Approach we were told to expect visual Runway XX. We proceeded to load and brief the ILS XX as a backup. Shortly thereafter assigned RNAV/GPS Y XXC again. Reloaded the FMC for RNAV/GPS Y XXC. While vectored on downwind message displayed to check landing altitude then it extinguished. On base leg vector while descending was cleared visual for XXC. Approx 2 miles from ZZZZZ1 on intercept heading and descending A autopilot engaged both FMC screens displayed time out/reselect message. All lateral and vertical guidance was lost and map displays were blank. Aircraft reverted to Control Wheel Pitch Mode. I disconnected the autopilot and auto throttle and continued visually with the field in sight. Would estimate I was 200 ft. high at ZZZZZ1; flaps 15/gear down and slowing. No other aircraft traffic at the airport at that time. Configured for landing and was stabilized. Transitioned to only visible PAPI for additional vertical guidance. At approximately 500 ft.; new FMC message of no active way point was displayed; nav map displays still blank. Due to lack of nav data; FMC constant messages and only XXL PAPI visible; I mistakenly proceeded to and landed Runway XXL. Both runways are similar lengths and closely spaced. Landed in touchdown zone on speed. Realized my mistake after touchdown. Exited runway at [Taxiway] XX and proceeded to Gate XX. FMC and map displays returned to normal before arriving at the gate. After arrival next hours ATIS listed PAPI XXL out of service.
Second reporter narrative
Aircraft X was on arrival to ZZZ via the ZZZZZ2 arrival and I assigned him Runway XXC. On his base leg I cleared him for a visual approach Runway XXC and switched him to Tower frequency. After landing at ZZZ I believe the Supervisor in the TRACON noticed he landed on Runway XXL and the Tower had called about it.
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.