Boeing

There has been a bunch of recent headlines involving Boeing. This blog looks at how this might relate to one of the Exodus plagues. This week we are also back to technical work. The 400, BIG and SR have been refreshed. Read on for details.

Plague of Gnats

The plagues on Egypt have passed 2 times along the modern timeline. The first was centered on August 1, 2000. The second was during the plagues series of 2008.

Both of these times saw the Plague of Gnats show up in related headlines. In the summer of 2000 it was the Concord crash outside of Paris. The second was the grounding of MD-80 aircraft by the US Government on April 8, 9, and 10, 2008, over concerns about wheel well wiring.

Gnats are small flying creatures. Airplanes are a modern technical expression of those. In terms of Pharaoh's Egypt, gnats also represent small details. It seems that a feature of Egyptian style governance is that leadership is never able to properly care about details.

If you don't care about details, you will never succeed in the high tech modern world, as so much of it depends on caring about details. The entire woke western world is now being overrun by little Pharaohs. Our high tech western world is slowly becoming unmanageable and deadly as a result. It is becoming what was once called a 3rd world nation, which also had the characteristic of being unable to handle modern technology.

Boeing, as a single company, crosses both ideas expressed in that ancient plague. They manufacture gnats, and they appear to have become unable to handle gnat like details when building those same airplanes.

It is a miracle that nobody has been killed by a Boeing airplane in the past few months. Give it time. That will likely change.

For readers here, perhaps too young to remember, I want to cover the key details of Boeing's history and then suggest why Boeing is the venue for a slow ongoing replay of the plague of gnats.

Boeing Merger (finance.yahoo.com)

The Boeing company of today is the result of a 1997 merger between Boeing and McDonnell Douglas. The link here reviews the history. The most important detail is how the culture of McDonnell Douglas took over Boeing in 1997. These are well known facts, even if not widely known.

At that point I was months away from starting work on Bible Time. I worked for IBM. I had a desk at Boeing for several years while on the IBM payroll. In 1997 I was still occasionally back on Boeing property on short term assignments.

My father had worked for Boeing from when I was young until he died in 1996. His very strange skill was auditing and setting up business processes. As a kid, trying to explain what my dad did at work was always hard to do in short sentences. In old Boeing's case, it was those same business processes that kept airplanes from falling out of the sky.

Those processes were my father's passion. He knew that was the secret that kept Boeing planes flying. Even in the 1970s he would not willingly fly on McDonnell Douglas aircraft because they were so dangerous.

An interesting memory peg on this is the fact that the IBM manager responsible for the team who designed the first IBM PC died in a crash of a McDonnell Douglas airplane in Texas. (As did his son, who was traveling with him.) IBM treated employee deaths while traveling as the same as a death while working in an IBM factory or office. The survivors benefits in both cases were the same. In the mid 1990s I was required to fill out time cards for all time traveling on business to Israel in order to be eligible for that same death benefit.

The public at large is now forming a similar fear of Boeing airplanes, and for the same reasons.

The article above correctly explains the problems with the 737 MAX as having been caused by the McDonnell Douglas merger. McDonnell Douglas, the MD in the MD-80 grounding of 2008, was always a defense contractor, generally without a passion for quality. That McDonnell Douglas culture took over Boeing beginning in 1997. Why?

What was well known, but mostly unspoken, in that 1997 merger was that this was a leveraged buyout of Boeing by McDonnell Douglas. Boeing had a cash reserve and fat order book. McDonnell Douglas was a failed defense contractor that was mostly out of money.

A leveraged buyout is a type of purchase where the assets of the acquired company pay for the purchase of that company. Because it was the McDonnell Douglas management team that was behind this merger, this is why their culture took over Boeing.

The thought among the engineers at Boeing in 1997 was that it was just a matter of time before Boeing aircraft would start dropping from the skies just like McDonnell Douglas aircraft had done years before. Though it took longer than anyone expected, the 737 MAX crashes were the eventual fulfillment of those dire predictions.

Concord Crash (Wikipedia)

The link here is to the Wikipedia article about the July 25, 2000, Concord crash outside Paris. If you read down through that article you will find a strange detail. That crash was caused by a McDonnell Douglas MD-10.

This was one of the planes that my father had refused to fly on. This was the same type that had killed the father of the IBM PC. Now, one of those cursed planes was causing the crash of a plane from an entirely different manufacturer.

As the article above explains, the Concord crashed because during takeoff it rolled over a loose part lying on the runway. That part had fallen off of an MD-10 that had departed on the same runway just ahead of the Concord.

That loose part bounced up and punctured the underside of the Concord causing a series of failures that caused it to crash soon after takeoff. The ultimate cause of over 100 deaths was a Paris based Continental maintenance crew who did not care about the details of their work. See the gnats pattern?

The Concord itself used 4 jet engines. But, they were housed in pairs under each wing. So they risked scenarios were a failure in 1 engine could take out a 2nd engine. The alternative design is seen on the 747, and Airbus 380, where the 4 jets are spread apart. Engine failures on the 747 do not easily cascade because of that spread out design. So the Concord had a fragile design, but it was not the root cause of the crash.

This crash was caused by a maintenance problem on the MD-10. It was not directly the cause of the MD-10's manufacturer. Several of the Boeing related headlines this past few weeks are also related to poor maintenance on Boeing airplanes. So the details of this plague are not constrained to the manufacturer's own actions, but to the community built up around these planes. This is still a plague of ignoring technical details in modern machines.

MD 80 Grounding (howstuffworks.com)

The link here is to an article on How Stuff Works that explains the details of the 2008 grounding of all American Airlines MD-80 aircraft. This was the plague of gnats in 2008.

This event caused the sudden cancellation of all American Airlines MD-80 flights. This was done by the order of the FAA. About 100,000 travelers were suddenly stranded at airports across the USA.

If you dig into the details you should note a few points. First, the MD-80s of the time were about 18 years old, so manufactured about 1990, so long before the Boeing merger. The article thus incorrectly states these were Boeing airplanes. Those planes were not manufactured under the Boeing culture of 1990. The MD in the series name gives this away.

The McDonnell Douglas that had built those planes in 1990 was ruling over Boeing's culture in 2008. Boeing in 2008 was now the responsible party for engineering support for those MD-80 airplanes.

But the other problem that article does correctly explain, is that the FAA had issued an airworthiness directive with an engineering change that was so incomprehensible that the airline staff could not figure out how to carry out that government directive.

In order to shift blame away from themselves, the FAA grounded American Airline's fleet of MD-80s. That plague of gnats was indeed at Pharaoh's own order.

This takes us back again to the plague of Gnats being related to governance. Remember President Reagan's famous quip, the 9 most dangerous words in the English language, I'm from the government and I'm here to help.

Current Boeing Troubles

So this brings us up to the current troubles with Boeing planes. For the record I am giving links below to mostly videos that explain Boeing's current set of problems.

The following Youtube links are to the same blancolirio channel. The host there, Juan Brown, is an experienced commercial airline pilot who flies the Boeing 777 for a living. He has been covering Boeing for a long time on his channel. Over the past 2 months his tone towards Boeing has changed.

Portland, OR, Door Plug (youtube.com)

The 737 was back in the news when a brand new 737 in a flight out of Portland, OR, lost a plug door. Fortunately, nobody was killed. But, planes don't usually fall apart in the sky. Something was very wrong.

Door Found (youtube.com)

The door was found on the ground. This was the start of trouble. The paint would indicate there had never been bolts in those doors. The FAA would wait a few weeks before saying this loudly.

Legal Fight (youtube.com)

Turns out Boeing once had a manufacturing plant in Wichita, KS. My father went there at times when I was young. Business processes that kept the planes safe started at that factory where the shells of the 737 were made. They were shipped by train to Renton, near Seattle, where they went through final assembly.

Once the financial engineers took over, that Wichita factory was spun out of Boeing. So now, instead of solving technical problems between 2 remote factories of the same company, the owners of those different factories were left with just going to law. How does that help the flying public? Or for that matter, either company?

The FAA Steps In, Inspect (youtube.com)

So the FAA steps in. Are they the adult in the room? Or is the FAA document pushing maniacs like in 2008? This time the FAA is maybe better than 2008. But, this is a problem that should never left the Boeing factory.

Quality Problems Explained (youtube.com)

Ouch. Nobody cared. Maybe we should say, Woke goes for broke? Interesting note, the quality manager for Boeing was a diversity hire. Pharaoh does not care about details.

No Expanded Production (youtube.com)

Boeing has a long order book for 737s. The FAA stepped in and prevented the company from making more faster. Interesting how the lack of business quality processes can cost a company many billions of dollars. Details matter.

Can't Certify New Models (youtube.com)

So Boeing had been planning a couple new models of the 737. Now, they could not certify those models for flight. Ouch.

757 Slats (youtube.com)

Here is where the trouble with Boeing leaves the 737 and starts to show up with the 757. At this point it starts to look like the company itself is under some sort of plague.

Maybe a dirty tricks campaign against the company? If so by whom? For what purpose?

Is someone trying to tear down the industrial base of the USA itself? Boeing, at least historically, was the largest US exporter measured by dollars. If you want to ruin the USD as a currency, then you want to ruin Boeing as a company. (As well as Hollywood, a close second.)

777 Wheel (youtube.com)

The pace of Boeing troubles is picking up. This time a wheel falls off of a United Airlines 777 as it departs San Francisco for Asia. Instead it safely diverts to Los Angeles where it can have an emergency landing on a very long runway. This was a maintenance problem, not a Boeing company problem. Or, perhaps, a dirty tricks campaign against Boeing?

From a prophetic perspective, United was spun out of Boeing back in the dawn of the airline industry. So these are not completely unrelated companies. Even as an independent company, United has been a launch partner for Boeing, being the first to fly new models of most Boeing airplanes.

In the Mud (youtube.com)

Only a few days later, a United Boeing 737 lands at high speed. Then, it tries to take the last corner off the runway at a speed faster than recommended. That plane ended up in the mud. Nobody hurt. But even legacy media was starting to see the pattern.

Hydraulics (youtube.com)

And again, a United Boeing 777, looses 1 of 3 main hydraulics systems and is forced to land with landing gear doors open and no normal control of the landing gear pitch. Apparently a blown out hydraulics hose in the landing gear itself. Easy for someone with a knife to damage. Nobody hurt, but more bad publicity.

Sudden Drop (youtube.com)

This one is a followup, so out of sequence, but in the same cluster of problems. A 787 heading out of Australia had a sudden in-air drop.

Passengers not strapped in crashed into the ceiling. Then when the drop ended, they crashed back down on each other. 50 were hurt. A passenger reported that the captain had come into the passenger cabin and said the screens in the cockpit had gone dark at the same time as the drop. The video explains how loss of computers cause drops like this if the mechanical trim is not set correctly. Why did the computers go out? A Computer glitch? EMP? UFO? Flipping a switch on the back of the pilot's seat? (Morbidly hilarious if so.) This video is adding a few more details.

Criminal Investigation (zerohedge.com)

That first case I linked above, the 737 plug door blowout in Portland, has now become a criminal investigation against Boeing. This is the followup link at Zero Hedge for details.

Inspector Suicide (redstate.com)

This was the first report I read about John Barnett, a Boeing whistle blower, who was found dead in his truck. He was a quality inspector at a Boeing plant in South Carolina. He was in a multiple day long series of legal depositions preparing documents for court. He was expected back in the lawyer's office the next day.

This report cites the coroner indicating that he committed suicide. No other later reports on this death would agree with that preposterous claim.

The coroner sounds like another little Pharaoh who does not care about details. Maybe someone in on the plot? Maybe someone who feels threatened by whomever did this? Maybe all of the above?

Not a Suicide (youtube.com)

This is a second link on Barnett. Seems he told a family friend that if he ended up dead that it would not be a suicide. He seems to have understood something about the modern Boeing culture.

All little Pharaoh's solve their problems the same way, think Gaza. This is even more condemning of Boeing.

Robert Kennedy Jr. on Barnett's Death (twitter.com)

John Barnett's death attracted Robert Kennedy's comment. He is asking for an investigation into this "suicide." Of course in our current world of Pharaoh's Egypt, there are no independent investigators who could be trusted with such a task. It would end up back in Pharaoh's court.

An Ongoing Prophetic Headline?

In earlier plague series we saw headlines strike on or very near predicted prophetic dates.

I have just given an example of something different. The plague of gnats is a pattern from the text. It has some historical examples. We know this. But perhaps we should think of the list of plagues as ongoing. So running at the same time, across some number of years before the final fall of prophetic Egypt.

Boeing is a good example. This plague appears to be spreading out across time. Their name shows up in both the 2000 and 2008 timed references to the plague. That we know.

Was the early 737 MAX crashes and grounding part of it? Was the Portland, OR, door plug part of it? Was failure to certify new models part of it? Was Barnett's death part of it?

Is there still more to come? Boeing airplanes appear to be in so much trouble that surely some will again be grounded or fall from the sky.

In some sense the same company was involved in all of the earlier modern examples of this same plague of gnats. Boeing has been in trouble by the Boeing name since 1997, but by the McDonnell Douglas name since my father's day in the 1970s.

What I have given here is evidence for the idea that there might be some sort of large ongoing plague of gnats that has been running for years.

The venue for that plague appears to be the defense contractor formerly known as McDonnell Douglas, now known as Boeing. They have a predatory nature as seen in the Boeing takeover, and apparently with Barnett's death too.

Boeing recently moved their corporate headquarters from Chicago to outside of Washington DC. In some sense that company is one of Pharaoh's officials where prophetic Egypt is the USA. Interaction with the federal government is obviously more important than interaction with the engineers and factory workers who are the people ultimately responsible for building safe airplanes.

If Boeing should loose the criminal case for the plug door problem, maybe the CEO will be sentenced to sleeping on Boeing factory floors? We could hope. I digress.

A Pattern?

How many other companies consider Washington DC to be more important than their factories, product, workers or customers?

Might Boeing be a pattern for what is going on in other cases?

Are there other companies that are close to the Deep State in Washington DC who might also be closely tied to Pharaoh and thus be venues for ongoing replays of the Plagues of Egypt?

Maybe.

Areas to explore include finance, media, medicine, education, agriculture and maybe even the southern border. If I can find enough supporting documentation, I will return to this idea in future blogs.

The plagues themselves do appear to be going on in some continuous way. They are spread across time.

New Build

Before breaking for Unleavened Bread, we had been reworking our apps to our new build and runtime environments. We returned to that task this week. Let me list off the apps that are now on the new build and run time system along with some notes on what else was changed.

Ezekiel's Bones (ezekielsbones.org)

This site has been up on the new build for a few weeks. This week I fixed a regression related to moving this to a website from a web app. It should now work OK for anyone who visited there in the past, or who may have bookmarked that site.

Sabbath Reads (sr.paleo.in)

The Sabbath Reads app has been updated to new build and new runtime code.

This is the first of our scripture apps to be converted over to the new system. Though there might be some unexpected regression, there are no intended changes in the user interface of that app.

Bible In Genome (big.paleo.in)

The Bible In Genome project was worked on in the summer of 2022. At that time I explored the genome to see if we might find a vaulted copy of the text at that location.

This week I did a refresh of that project. It is now a standalone website, rather than a web app. It uses tabs like our other websites. So it is easier to explore when someone visits the site for the first time.

I have rewritten the front page of that site to give a little introduction to the problem.

The value of this site is the various Bible studies that point at places in the text that hint about how the text may be found within the Genome.

I have removed some inactive tools pages, and moved some pages that are not really interesting into the footer.

I suspect we will return to that problem again, once we have confidently worked out some longer inspired sections of the text.

With a solid long sequence of letters, the interesting test case for the genome is to attempt a hunt where all possible letter encoding tables are tested. That code might take weeks to run, but it would still be very interesting to try.

Table of 400 (400.paleo.in)

Ryan has been working on this app for several weeks. Though the domain is still 400, the core tables were recently expanded to 500. That larger grid size is getting filled in. Much of the UNLB week discoveries are reflected into these tables too.

This week that app was shifted onto the new build and runtime. This is a fairly large app. It contains an entire copy of the TT along with many large tables. In the new build environment it is about 10 percent smaller and thus installs slightly quicker.

This app also gained a new table, currently at the bottom of the drop down menu. It lists off the heavenly kings against the kings of the northern and southern kingdoms. If you inspect that table you will see how the 2 parts of David's reign are needed to cause the columns in these tables to all line up. Also note, Joshua is the last king and closes out all of the columns.

There are a few notes for each row in that table, just enough to suggest the alignment is correct. Much more work to do on that discovery.

More Later,

Phil