The cost of non quality

The cost of non quality

The Boeing 737 Max is a legacy plane, built on decades-old systems. Boeing strategy was to keep updating the plane rather than starting from scratch, as this offered cost and competitive advantages: pilots were comfortable flying it, airlines didn’t have to invest new training, design and certification was faster and cheaper.

But this strategy has killed people.

The Max stretched to the limit the old 737 design, creating a patchwork plane without some safety features that are common on other planes.

The Max still has roughly the original layout of the cockpit and the cables/pulleys to control the plane, instead of drive by wire.

The Max by design has an "appropriate enough" level of technology to ensure safety, close to a 90's home computer.

The Max still requires makeshift solutions to keep the plane flying, one of which, an anti-stall system designed to compensate for the larger engines, was central to one of the crash. Let's see why...

Each of the three redesigns of the 737 since the first model in the 60's came (among other minor changes) with a new engine. The plane’s low-slung frame was a benefit for airlines and airports, as workers could load bags by hand and engine maintainance did not require a lift. But this low frame repeatedly complicated efforts to fit, for each plane evolution, bigger (as more efficient) engines under the wing.

To avoid a full redesign, engineers did two things: add a very few inches to the front landing gear and shift the engines farther forward on the wing.

While this solved one problem, it created another: the larger size and new location of the engines gave the Max the tendency to tilt up during certain flight maneuvers. To compensate potentially dangerous angles, engineers created the automated anti-stall system (MCAS), that pushed the jet’s nose down if it was lifting too high.

The software was intended to operate in the background, having the Max flew just like its predecessor, and for this reason the company didn’t even mention the system in its training materials. In addition, the system was designed to rely on a single sensor, instead of two for redundancy.

In the recent crashes, the MCAS malfunctioned and moved a tail flap, tilting the plane toward the ground, but pilots, unaware of why this was happening, tried to combat the system by cutting power to the stabilizer’s motor: the plane crashed.

SOUMEN S.

Author, Technical Leader & Manager @ Tech Companies | Software Development Methodologies

4y

Giovanni Stoto: while I agree and applaud your effort to highlight Technical Debt with Boeing 737MAX problem, I need to disagree with you. Specifically corporate corruption / subversive culture does not come under technical debt -- it is at a whole different level! Volkswagen emissions scandal (with defeat device based cheating) was not a technical debt ... to cite another example. Which quadrant would you put Boeing 737MAX technical debt?

  • No alternative text description for this image
Like
Reply
kyri kousou

Computer Software Professional

5y

It was pure incompetence and dare I say, scam.  Adding an electronic patch to keep your non aerodynamic redesign from crashing without telling anybody (to avoid re-certification) and on top of that not using multiple sensors for your patch is third world level incompetence because everything breaks over time. Hubble had 6 gyroscopes, it only needed one. People should go to jail over this. I am curious who was in charge, from those who designed the software to those who authorized it. I am shocked on their incompetence.

To view or add a comment, sign in

More articles by Giovanni Stoto

  • Sicurezza psicologica

    Sicurezza psicologica

    Se lavori in un team di ingegneri con un obiettivo comune, non devi feticizzare il prodotto del tuo lavoro. Qualsiasi…

    3 Comments
  • Team building, leadership and group culture

    Team building, leadership and group culture

    We can define the culture of a group as the shared and stratified learning experience when the group solves its…

  • Team building, leadership e cultura di gruppo

    Team building, leadership e cultura di gruppo

    Possiamo definire la cultura di un gruppo come l’apprendimento condiviso e stratificato allorché il gruppo risolve i…

    9 Comments
  • Team e disuguaglianza

    Team e disuguaglianza

    C'è un legame tra il modello di formazione del team di Tuckman (forming, storming, norming, performing) e gli stili di…

    1 Comment
  • Fixed Price (Agile) Projects

    Fixed Price (Agile) Projects

    According to Agile, Fixed Price Projects are to be avoided, as agility can be delivered only when scope, schedule and…

    22 Comments
  • Architettura IT e manager di business

    Architettura IT e manager di business

    È noto che i sistemi IT sono più costosi da mantenere che da acquistare/costruire, specialmente quando il loro ciclo di…

    6 Comments
  • Il Fordismo è ancora valido oggi?

    Il Fordismo è ancora valido oggi?

    La catena di montaggio di Ford era basata sull'ottimizzazione della produzione di un solo modello uguale per tutti…

    4 Comments
  • Resource Constraints and Critical Path Method

    Resource Constraints and Critical Path Method

    By definition, the Critical Path includes the activities with zero Total Float and therefore a delay in any of these…

    26 Comments
  • Program Management in relation to Change Management, Project Management and Operations

    Program Management in relation to Change Management, Project Management and Operations

    Program Management (PgM) has gained its own place of honor only during the last three decades, when Project Management…

    18 Comments

Insights from the community

Others also viewed

Explore topics