B737 MAX flight crew reported experiencing a flight control issue while in cruise. The flight crew continue to destination airport and landed safely.

Date: 2024-11 · Aircraft: B737 MAX Series Undifferentiated · Phase: cruise

Anomalies: aircraft-equipment-problem-less-severe

Synopsis

B737 MAX flight crew reported experiencing a flight control issue while in cruise. The flight crew continue to destination airport and landed safely.

Narrative

At the top of climb (FL230) the master caution and spoilers lights illuminated. The F/O who was the pilot flying called out 'his aircraft'. I was the pilot monitoring and called 'my radios'. I then called for the QRC. After determining that the Spoilers procedure was not on the QRC I called for the QRH. Since we were in a B737 Max aircraft; I confirmed that the QRH checklist we were about to use was for our specific aircraft. I read and we preformed the QRH procedures. I advised ATC that we had a flight control issue and I requested a block altitude of FL220-FL240 since the first step in the QRH was to disconnect the auto pilot and auto throttle and check for any roll or any unordinary flight characteristics. Thankfully none were noted at this point. The checklist then states that the autopilot and auto throttles may be re engaged. We also discussed step 4 of the checklist that states that the roll rate and speed brake effectiveness may be reduced. We then [requested priority handling] with ATC and requested ARFF (Airport Rescue and Firefighting). I notified dispatch via ACARS of the event and that ZZZ airport was our destination and gave our ETA. I then completed the Non-Routine Landing Considerations checklist. I notified the flight attendants of our issue; that everything was under control and we would be doing a precautionary landing in about 10 minutes in ZZZ; the weather was fine and they may see some vehicles near the aircraft after landing. I also made a PA to the passengers with the same information. We requested runway XX at ZZZ since it was the longest runway in case we had any flight control issues. We then confirmed our landing distance requirement from the QRH and we were within acceptable tolerances to safely land on runway XX at ZZZ. We briefed the approach and any contingencies (go around; any flap or flight control issues; ARFF; stopping on the runway; flaps deployed after touchdown; PA requirements) and then completed the descent checklist and the landing checklist to the line. I advised ZZZ tower that we would stop on the runway straight ahead to allow the ARFF equipment to inspect the aircraft. We were cleared for ILS to XX and we completed the landing checklist below the line. After landing we stopped straight ahead on the runway and deployed the flaps to 40 degrees in case of any inadvertent passenger or flight attendant initiated evacuation occurred. I made an immediate PA for the passengers to remain seated while the safety equipment inspected the aircraft. I also called the Flight attendants to confirm everything was ok. ARFF met the aircraft and I spoke with the ARFF commander. ARFF equipment and personal inspected the aircraft and determined we were safe to continue. We called ATC and they gave us clearance to taxi to the gate. I put the flaps up and called for the after landing checklist. Once at the gate we performed the checklist shutdown procedures and then I notified the Chief Pilot and maintenance. Maintenance personnel met the aircraft at the gate. I then made a logbook entry. A report was subsequently filed.

Second reporter narrative

During cruise; Master Caution associated with SPOILERS light on overhead panel. QRH procedure completed with no change to ACFT. Due to 'Flight Control message' and out of extreme caution; we [notified ATC and they later gave us priority handling]. Uneventful landing on runway XX. After ARFF (Airport Rescue and Firefighting) assessment on the runway; ACFT was taxied to the gate.

More incidents for this aircraft family →

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