A United Boeing 737-9 Max lands on wrong runway

A United Boeing 737-9 Max on Jun. 21, registration N37513, performing flight UA-2627 from Chicago O’Hare to Pittsburgh with 168 passengers and 6 crew, was cleared for a visual approach and was cleared to land on Pittsburgh’s runway 28C, however, lined up with runway 28L and continued for a landing on runway 28L. There were no injuries and no damage.

The NTSB opened an investigation into the occurrence. The NTSB wrote: Upon initial contact with PIT approach control, the flight crew was told to expect a visual approach to runway 32 into PIT. The flight crew briefed the new approach and proceeded to load the ILS 32 approach into the FMC to back up the visual approach.

While being radar vectored on the downwind and descending through about 4,000 feet Mean Sea level (msl), the flight crew indicated that they had a check landing altitude message displayed briefly on the FMC. After the message disappeared and with the autopilot engaged, the aircraft reverted to control wheel steering pitch mode. They selected level change and reselected the autopilot to command mode.

The airplane began its descent at about 0918 EDT, and as they were descending, approach control asked them if they could accept a visual approach to runway 28C. The weather was clear, and the winds were 250 degrees at 4 knots, so they accepted the runway change. The first officer then re-programmed the FMC for the RNAV GPS Y 28C to back up the visual approach.

The flight crew established communication with the local controller when the airplane was approximately 6. 5 miles east of the airport. They crew advised the controller they were on a visual approach to Runway 28C, to which the controller cleared them to land on Runway 28C. According to the captain, approximately 2 miles from SUPPR, on an intercept heading and while descending, “the screen was black, both FMC’s blanked” except for the aircraft communications, addressing and reporting system (ACARS) prompt and no FMC prompt. The captain used heading select and level change on the mode control panel (MCP). However, when the airplane joined an approximate 6-mile final, it was aligned with Runway 28L.

When the airplane was approximately on a 2-mile final and still aligned with Runway 28L, the flight crew requested verification of their clearance to land on Runway 28C. The controller advised the flight crew of mowing in progress in the grass area and cleared them to land on Runway 28C.

The flight crew read back their clearance to land on Runway 28C.

About 0944 EDT, the airplane landed on runway 28L, turned right off the runway, and exited runway 28L at taxiway F5. The controller noticed the airplane was lined up for runway 28L when it was on short final but decided that it was more appropriate to allow the airplane to land given their altitude. The facility reported that the traffic volume was light with routine complexity. The distance from the airport traffic control tower to the runway 28C threshold was approximately 7,500 feet. avherald.com