In the layered architecture of aviation safety, it is sometimes the operator — not the maker — who first notices what the machine is quietly trying to say. WestJet Airlines identified a software anomaly in Boeing's 737 MAX during routine commercial operations, before Boeing had formally brought the matter to federal regulators. The FAA reviewed the issue and cleared it, finding no threat to flight safety. The episode is a quiet reminder that the vigilance keeping aircraft aloft is distributed across many hands, not concentrated in any single institution.
WestJet discovered 737 MAX software glitch before Boeing, FAA approval memo shows
Airlines operate thousands of flights where manufacturers test in labs
Mark
So WestJet found something Boeing didn't catch first. How does that actually happen?
Mimi
Airlines fly these planes constantly, in real conditions. WestJet's maintenance teams or pilots encountered the software behavior during actual operations—maybe under specific conditions, maybe during a particular flight phase. That's different from a test lab.
Mark
And then what? They just call Boeing and say, hey, we found a problem?
Mimi
Essentially, yes. WestJet reported it to Boeing, Boeing then had to report it to the FAA. That's the chain.
Luke
We should be clear about what "software glitch" means here. The memos don't specify whether this was a display issue, a calculation error, something that affected flight control, or something else entirely.
Mark
Does it matter?
Luke
It matters for understanding the actual risk. A glitch in a non-critical system is very different from one in flight control. The FAA cleared it, which is reassuring, but we don't know the specifics.
Mimi
Fair point. What we know is the FAA reviewed it and found no safety risk. That's the regulatory judgment.
Mark
Is this common? Airlines finding things first?
Mimi
It happens. Airlines operate thousands of flights. They see patterns and edge cases manufacturers might not encounter in testing.
Luke
Though we should note the memos don't tell us how widespread this glitch was, how many aircraft were affected, or how long it had been occurring before WestJet reported it.
Mark
So this is actually a sign the system is working?
Mimi
That's one way to read it. Multiple layers of oversight caught and cleared an issue without disrupting service.
Luke
Or it's a sign that something slipped through Boeing's own quality checks. Both things can be true.
Le Pouls
- A Canadian airline, not the aircraft's manufacturer, was first to catch a software glitch hiding inside one of aviation's most scrutinized jets.
- The discovery carries weight precisely because the 737 MAX has lived under a microscope since two crashes killed 346 people — any anomaly, however small, lands with consequence.
- WestJet surfaced the issue through its own operational channels, triggering a chain of escalation that moved from airline to manufacturer to federal regulator.
- The FAA conducted its own independent assessment and cleared the glitch, determining it posed no risk to continued flight operations.
- The sequence — airline flags, Boeing reports, FAA clears — held together without disruption, suggesting the multi-layered safety architecture is doing what it was designed to do.
In the layered architecture of aviation safety, it is sometimes the operator — not the maker — who first notices what the machine is quietly trying to say. WestJet Airlines identified a software anomaly in Boeing's 737 MAX during routine commercial operations, before Boeing had formally brought the matter to federal regulators. The FAA reviewed the issue and cleared it, finding no threat to flight safety. The episode is a quiet reminder that the vigilance keeping aircraft aloft is distributed across many hands, not concentrated in any single institution.
WestJet Airlines identified a software problem inside Boeing's 737 MAX before the manufacturer had formally reported it to federal regulators, according to internal memos reviewed by Reuters. The Canadian carrier encountered the glitch during routine commercial operations and brought it to Boeing's attention, setting off a chain of review that ultimately reached the FAA.
The episode illuminates something rarely visible in aviation safety: it is often the airline — flying thousands of routes through real weather, with real crews — that encounters what controlled testing never surfaces. WestJet's maintenance or engineering teams flagged the anomaly, Boeing escalated it through regulatory channels as required, and the FAA conducted its own assessment before clearing the issue and allowing the 737 MAX fleet to continue without restriction.
The stakes of any MAX software discovery are never trivial. Since two fatal crashes in 2018 and 2019 grounded the aircraft for nearly two years and killed 346 people, every technical finding in the jet's systems draws heightened scrutiny. In this case, the glitch was minor enough — or sufficiently contained by existing safeguards — that the FAA found no safety risk. The process held: airline discovery, manufacturer reporting, regulatory clearance, no disruption. It is the system working as intended, even if the system's first signal came not from Boeing, but from the airline flying its planes.
WestJet Airlines discovered a software problem in Boeing's 737 MAX before the aircraft manufacturer itself reported the issue to federal regulators, according to internal memos reviewed by Reuters. The Canadian carrier identified the glitch during routine operations and brought it to Boeing's attention, setting in motion a sequence that eventually led to FAA review and clearance.
The discovery underscores a less visible dimension of aviation safety: airlines operating aircraft often encounter technical anomalies in real-world conditions that manufacturers may not immediately catch in testing or controlled environments. WestJet's mechanics or engineers flagged the software issue, which then moved through Boeing's internal channels before reaching the Federal Aviation Administration. The exact nature of the glitch was not detailed in the available memos, but the sequence of events is clear.
Boeing, once informed by WestJet, escalated the matter to the FAA as required by regulatory protocol. The agency reviewed the software problem and determined it posed no safety risk to flight operations. The FAA subsequently cleared the issue, allowing the 737 MAX fleet to continue operating without modification or restriction related to this particular glitch. The approval suggests the problem was either minor in scope, easily mitigated by existing safeguards, or both.
This discovery process reveals how the modern aviation safety system actually functions in practice. Manufacturers design and test aircraft, but airlines operate them across thousands of flights, in varying weather, at different altitudes, with different crew experience levels and maintenance practices. A software issue that might not surface in a test environment can emerge when an aircraft is pushed through the rhythms of commercial service. WestJet's identification of the problem before Boeing formally reported it suggests the airline's operational data or maintenance protocols caught something the manufacturer's own monitoring had missed.
The FAA's role as the final arbiter of safety clearance remains central. Even after WestJet identified the issue and Boeing reported it, the agency conducted its own assessment before approving continued operations. This layered approach—airline discovery, manufacturer reporting, regulatory review—is intentional. It distributes the responsibility for safety across multiple organizations, each with different vantage points and incentives.
The 737 MAX has been under intense scrutiny since two fatal crashes in 2018 and 2019 killed 346 people, leading to a 20-month grounding and extensive redesign of flight control systems. The aircraft returned to service in late 2020 after the FAA and other regulators approved modifications and new pilot training requirements. Any software issue in the MAX, no matter how minor, now receives heightened attention from both manufacturers and regulators. In this case, the glitch was identified, reported, reviewed, and cleared without incident or operational disruption, suggesting the safety oversight mechanisms are functioning as intended.
Envie de l'histoire complète ?
Lire l'original sur Reuters ↗