TrueNation
General

I Was Convinced Boeing Was Collapsing. I Was Wrong.

Published on June 29, 2025 at 07:58 PM
I Was Convinced Boeing Was Collapsing. I Was Wrong.

For years, my perspective on Boeing was not just critical; it was cynical. I wrote the articles, I made the calls, and I connected the dots with grim certainty. To me, the narrative was clear and undeniable: a corporate giant, rotten with a culture of concealment, was in an irreversible tailspin. I saw the ghost of the 737 MAX in every new headline about the 787 Dreamliner. When The Sunday Guardian Live, quoting the highly respected aviation attorney Mary Schiavo, began to frame the tragic Air India crash as a potential software cover-up, it felt like a horrifying confirmation of my deepest fears. It wasn't just an accident; it was a pattern. The 'history of concealment' they described was the exact phrase I would have used.

Then came the drumbeat of other failures. An Ethiopian Airlines 787 depressurization. A ground collision in Vietnam. Each incident, amplified by viral video footage, served as another data point in my indictment. When the Pentagon, a cornerstone customer, publicly canceled the E-7 Wedgetail program, I saw it as the final verdict. If their own defense division, long considered a reputational safe haven, was crumbling, then what hope was left? I dismissed reports of stock gains and analyst upgrades as the market’s foolish dissonance, a failure to see the writing on the wall that I saw so clearly. I was not just a reporter on the Boeing beat; I was a true believer in its imminent demise.

My transformation didn't begin with a press release or a carefully curated corporate statement. It began with a late-night phone call to a source, a veteran aerospace engineer I’ve known for two decades. I was fishing for a quote, another nail for the coffin I was building in my next column. I laid out my case—the Schiavo theory on the Air India crash, the Wedgetail cancellation, the pattern of 787 incidents. I expected him to agree, to pour more fuel on my fire. Instead, he was silent for a long moment before sighing with a weariness that cut through the phone line.

"You're a smart guy," he said, his voice devoid of accusation and full of something more like disappointment. "But you're telling a simple story about one of the most complex things human beings do. You're connecting dots that aren't on the same plane of existence. And honestly, it's dangerous."

That one word—dangerous—stopped me cold. I had always seen my work as a righteous pursuit of accountability. The idea that my certainty, my simple and compelling narrative, could itself be a form of irresponsibility had never occurred to me. That conversation was the catalyst. It forced me to do the one thing a journalist in the heat of a narrative hates to do: pause, take a step back, and question my own foundational beliefs.

One of the central pillars of my argument was the story being woven around the Air India 787 tragedy. The allegation of a known engine thrust rollback software malfunction felt like MCAS 2.0. A secret flaw, a corporate cover-up, a predictable tragedy. It was a powerful, emotionally resonant story. But as I dug deeper, prompted by my engineer source, I was confronted with a far more complex and less sensational reality. I started reading the technical manuals, learning the difference between a flight control system like MCAS and an engine management parameter. I learned that an official air accident investigation is a painstaking process of elimination, looking at hundreds of potential factors from maintenance records and weather patterns to pilot training and material fatigue. The narrative being pushed by Schiavo and others had sprinted to a conclusion while the official investigation was still tying its shoes at the starting line.

It was a difficult realization. I had mistaken a compelling legal theory for established fact. My desire for a simple, villainous explanation had led me to ignore the methodical, multi-year process that defines genuine air safety investigation. I realized the 'truth' was not yet known, and by presenting a speculative theory as a smoking gun, I was participating in a media trial, not journalism.

Next, I had to confront my belief that the constant stream of 787 incidents represented a systemic failure of the aircraft itself. The Ethiopian depressurization, the Vietnam ground collision—in my mind, they were all part of the same story: 'The Unsafe Dreamliner.' But when I forced myself to look at them as an engineer would, the narrative fell apart. A depressurization event is serious, but it often traces back to a single component or a maintenance procedure. A ground collision is almost always a matter of airport ground-handling error. These events were unrelated. To lump them together under a single umbrella of 'systemic failure' was like diagnosing a patient with a terminal disease based on a scraped knee and a headache. The only thing connecting them was the manufacturer's name on the fuselage. I was ignoring the context of the staggering number of 787s—over a thousand of them—that complete tens of thousands of flights safely, every single week. My confirmation bias was showing; I was only counting the planes with problems, not the vast, silent fleet that performed its mission flawlessly.

Finally, I re-examined the business failures—the Wedgetail cancellation and the production delays. I had seen these as proof of a broken company. The Pentagon's move felt like a public shaming. But when I looked past the headlines and into the labyrinthine world of defense procurement, a different picture emerged. I learned about fixed-price development contracts signed in a pre-inflationary world, shifting Pentagon priorities, and the immense technical challenges of integrating next-generation systems. The cancellation was as much about budget realities and changing strategic needs as it was about Boeing's performance. Similarly, the production delays, which I had decried as incompetence, began to look different. In speaking with industry sources, I learned that a primary cause of the slowdown was a deliberate, massive expansion of quality inspections and a new, post-MAX cultural mandate to prioritize safety over schedule. They weren't delaying because they couldn't build planes; they were delaying because they were refusing to build them the old way, a lesson learned in the most painful way imaginable.

I am not here to tell you that Boeing is a perfect company or that it should be absolved of its past sins. The 737 MAX tragedies were a result of profound corporate and engineering failures, and the families of the victims deserve our unending respect and remembrance. But I was wrong to project the specific sins of MAX onto every challenge the company now faces. My certainty had blinded me to complexity. My narrative, so simple and damning, was ultimately a disservice to the truth.

The real story of Boeing today is not one of a simple, linear collapse. It is the far more complex and messy story of an industrial titan in the throes of a painful, identity-shattering transformation. It is a story of engineers grappling with unprecedented supply chain issues, of a new leadership team trying to instill a culture of caution, and of the immense difficulty in turning a ship of that size. This story is less satisfying than a simple tale of corporate villainy, but it is far closer to the truth. And my job, I have been forcefully reminded, is to pursue that difficult truth, not to amplify the easy and dangerous narrative. I was wrong, and I invite you to join me in looking beyond the headlines.