My 9/11. A Personal Story

My 9/11 A Personal Story

By Steve Douglass

I had slept late that morning—late for me, anyway. I’d been up much of the night before, as I often was, monitoring the airwaves.

There was a small television on the nightstand beside my bed. I stretched, reached over, and turned it on, still trying to clear the cobwebs from my brain.

The news was already on. At first I wasn’t really paying attention, but gradually I became aware they were talking about a small plane hitting one of the World Trade Center towers.

I glanced over at the screen.

One of the towers was burning, a huge black wound cut into the side of the building.

I remember thinking, "That’s a pretty big hole for a small plane."

Then, as I watched, the second airplane slammed into the other tower.

For a moment, I was confused. Was this a replay? Then it dawned on me. It was a second plane.

In that instant, I knew. This wasn’t an accident. This was terrorism.

Almost immediately, my phone rang.

I picked it up. The voice on the other end belonged to someone I never expected to hear from that morning—my friend “Mark.”

There was no small talk.

He only said:

“Turn everything on. America is under attack.”

I knew exactly what he meant. Despite the shock, we were on the same page. I fired up my monitoring room, scanners. HF radios. recorders. Everything I had capable of monitoring aviation and military communications.

It was going to be a long and terrible day, and through radio monitoring I was going to have access to information few others would.

Within minutes, my monitoring room was alive.

At first, I concentrated on the civilian aviation bands. The FAA was ordering aircraft down, clearing the skies over the United States in a way that had never happened before. Commercial flights and private aircraft were being told to land as quickly as possible.

The message was unmistakable:

The sky itself had become part of the battlefield.

For the first few hours, the frequencies were chaotic, then something un unprecedented happened. They began to go quiet.

One aircraft after another disappeared from the airways until the normally crowded civilian aviation bands became almost eerily silent.

So I changed tactics.

I moved away from the civilian frequencies and began searching the UHF military bands.

That was where I hit the gold mine.

The military airwaves were very much alive.

I began hearing fighters talking to one another, tankers being requested, aircraft being repositioned, and Combat Air Patrols—CAPs—being established over parts of the country.

One of the first things I found was a fighter CAP being redirected to protect Air Force One.

That immediately caught my attention because, at the time, one of the big questions being asked on national television was:

*Where is the President?*

The public knew President George W. Bush had been moved from Florida to Barksdale Air Force Base in Louisiana. He had made a statement there and then departed again.

For a period of time, his next destination was not publicly clear.

I knew where he was going before most people watching television did.

Not because anyone had told me.

Because I could hear the pieces coming together over the military frequencies.

I followed the fighters and the plane-to-plane chatter. I heard air traffic controllers alerting them to noncompliant aircraft—most of them civilian pilots who had not gotten the word, or medevac flights that still had to fly.

I heard Combat Air Patrols being positioned over sensitive areas, including strategic and nuclear sites, one of them near my home.

Then I began hearing traffic associated with Air Force One being routed toward Offutt Air Force Base in Nebraska. I also noticed the telltale encrypted wideband channels used for communications with Air Force One and other high-priority aircraft began stopping my scanner.

I couldn’t decrypt what was being transmitted, but I didn’t need to.

Their mere presence spoke volumes.

That was the beauty—and sometimes the danger—of monitoring radio communications.

Nobody had to come on the air and announce:

“The President is going to Nebraska.”

You listened. You collected little pieces.

A tanker here. A fighter being redirected there. A CAP moving east.
Call signs changing frequencies.

Eventually, the picture formed. Air Force One was headed for Offutt.

Meanwhile, my own phone was ringing, assignment editors from CNN. ABC. CBS.

I had spent years building relationships with news directors who had my number on speed dial. I had broken many national and international stories simply by monitoring the right frequencies and knowing the right people.

They wanted to know what I was hearing.

I passed along what I could determine from the radio traffic, including that the President appeared to be headed toward Offutt.

By the time Air Force One made its approach into Nebraska, the media knew where to look.

For years, I had monitored military and aviation communications because I was fascinated by what you could learn simply by listening. Most nights it meant catching an unusual military flight, tracking an exercise, or occasionally hearing something nobody was supposed to notice.

Eventually, my obsession became my profession. I became a professional news-gatherer.

On that day, during the lulls—between the phone calls and bursts of radio traffic—I would look back at the television.

That was when the enormity of what was happening really began to sink in.

All I wanted at that moment was to know that my family and friends were safe.

My granddaughter had been born only a month earlier. She had barely entered the world, and suddenly I found myself wondering what kind of world she had been born into.

I started making calls. I tried my uncle in New York.

No answer. Then I called my friend and editor Stuart Brown at Popular Science magazine.

What happened next was almost surreal.

Stuart had no idea what was going on.

“My TV gets nothing but snow,” he told me, and asked if I knew anything.

I could hardly believe what I was hearing.

I told him what had happened—that airplanes had struck the World Trade Center and that the country was under attack.

He went outside.

From where he was on Long Island, he looked toward Manhattan.

He could see smoke billowing into the sky.

Then the reason for his dead television signal became obvious.

Much of the over-the-air television broadcasting in the New York area came from the enormous antenna complex atop the World Trade Center. The building carrying his television signal was burning.

I told Stuart everything I knew.

Then I told him to be safe.

At some point, I turned my attention back to the television and watched the towers come down.

That was when I lost it.

Until then, I had been functioning almost mechanically—listening, recording, answering phones, passing along information, trying to put together the constantly changing pieces.

But watching those buildings collapse broke through all of that.

I just bawled.

There was nothing professional about it.

Nothing analytical.

Nothing detached.

I cried for the people inside those buildings.

For the firefighters and police officers running toward something everyone else was trying to escape.

For the people on the airplanes.

For their families and maybe for all of us, because somewhere in those terrible minutes, I understood that the country I had awakened in that morning no longer existed.

It took me a few minutes to pull myself together.

Then the phone rang again.

I wiped my face, took a breath, and answered it.

There was still work to do.

Years later, I finally learned why I had been unable to reach my uncle that morning.

He owned a limousine service whose garage was located in one of the Twin Towers.

That morning, by sheer chance, he had gotten out early. He was on his way to Teterboro Airport to pick up members of the Catholic Archdiocese of New York.

As he was coming back toward the city, he saw the first airplane hit the World Trade Center.

He immediately got on the limo phone and started calling every one of his employees.

Stay home.

Don’t come in.

Then he called his office to make sure nobody had decided to show up early.

No one had.

All of his limousines were lost.

His business was gone.

But every one of his employees survived.

He would later tell me that he lost quite a few friends that day, but he didn’t lose a single employee.

The business could be rebuilt. People couldn’t.

That story stayed with me because, on a day remembered for such enormous loss, there were also thousands of smaller decisions being made in real time by people who had no idea what was coming next.

My uncle made one of those decisions and it saved lives.

There was another strange element to that morning.

At the time, I was being watched—or at least I was pretty certain I was.

I believed the men keeping an eye on me were federal agents, or perhaps contractors working for a federal agency. Nobody ever walked up, flashed a badge, and confirmed it.

It happened periodically, mostly because my column in *Monitoring Times*, a radio hobbyist magazine, was called “The Fed File” and centered on intercepting government communications.

The column had developed a following, and one of my biggest contributors was “Mark,” who obviously had extraordinary access.

I never published anything anyone could reasonably consider classified or a leak, but by all accounts the column irritated people in several three-letter agencies—many of whom, ironically, were also subscribers.

By then, I was used to being shadowed, and the arrangement had become almost strangely routine.

I knew they were there. They were easy to spot.

Usually two or three men, sometimes accompanied by a woman, staying in a house across the street and only leaving when I did, shadowing me in a Suburban that stuck out like a sore thumb.

Then there was the observation through partially drawn drapes with binoculars. Subtle, they weren’t.

I hadn’t broken any laws, so I tolerated their presence, although my wife at the time didn’t like it.

I rather saw it as a feather in my cap—confirmation that my reporting was apparently hitting close enough to something to get their attention.

What made me interesting was what I knew, what I listened to and, more importantly, who I knew.

Over the years, I had developed sources connected to parts of the military and government most people never encountered. Those sources sometimes pointed me toward things that were not supposed to attract attention.

One source in particular was undoubtedly of interest to whoever was watching me. "Mark."

The same Mark who had called that morning and told me:

“Turn everything on.”

So on the morning of September 11, while I was sitting in my house listening to a nation under attack, there were men across the street whose job—whatever agency they actually worked for—apparently involved keeping an eye on me.

The absurdity of it finally struck me.

The United States was under attack, and these guys were still watching the guy with the scanners.

So I walked across the street, still wearing my pajamas.

I knocked on the door and essentially told them:

“You guys have bigger fish to fry. Turn on the television.”

For a few moments, whatever relationship existed between watcher and watched didn’t matter.

We stood there looking at the television as smoke poured from Manhattan.

The next morning, they were gone.

The Suburban was gone.

The surveillance was gone.

September 11 had rearranged the priorities of an entire country overnight.

It also marked a dividing line in my own life.

There was the world before 9/11, and the world after.

I happened to hear a lot of that transition through a pair of headphones, connected to an almost hidden world through radio circuits and antenna wires,

Postscript:

Nearly ten years later, on the late afternoon of May 1, 2011, my phone rang again.

It was Mark.

The call was brief.

“They got him.”

Then he hung up. He never said who. He didn’t have to.

I knew instantly. It was Osama bin Laden.

I knew it hours before the rest of the world would.

I sat there for a moment, thinking about what to do with that information.

There were no details. No confirmation I could point to.
Nothing I could quote publicly.

Just Mark.

So I took a gamble.

I posted a photograph of bin Laden on my Deep Black Horizon blog with one word stamped across his face:

"DEAD"

What if I was wrong?

That thought certainly crossed my mind, but I trusted Mark, and I trusted my gut.

I offered no explanation. I didn’t pretend to know the details.
Those would come later.

Hours later, President Obama addressed the nation and confirmed that U.S. forces had killed Osama bin Laden in Pakistan.

Almost ten years after Mark had called me on September 11 and said, “Turn everything on,” he called again to tell me, in three words, that one chapter of that terrible day had finally come to an end.

Those words hit me like a sledgehammer. “They got him.” I wept again, but out of joy.

Tomorrow marks the 25th anniversary of September 11, 2001. For most people, the memories will come back through television images, photographs, and stories from that terrible day.

For me, there will always be another soundtrack—the voices in my headphones, the sudden silence of the civilian airwaves, the military traffic filling the bands, and the encrypted signals that told their own story even when I couldn’t hear the words. So tomorrow, as I have done for so many years, I’ll remember where I was, what I heard, and how quickly the world changed.

And I’ll be listening.

Task Force–Southern Border takes down 100 drones.

 

A senior War Department official says Joint Task Force–Southern Border took down approximately 100 suspected cartel drones during August.

That figure is significant because only days earlier, the military publicly disclosed that three cartel-linked drones had been defeated using the Army’s Multipurpose High Energy Laser system.

The two announcements should not be confused. There is no indication that all 100 drones were destroyed by lasers. Counter-UAS operations can involve electronic jamming, signal disruption, kinetic interception and directed-energy systems.

Still, the number suggests cartel drone activity along the southern border is far more extensive than previously disclosed.

Joint Task Force–Southern Border operates under U.S. Northern Command and supports the Department of Homeland Security in border-security operations and efforts to disrupt transnational criminal organizations.

Drones give cartels inexpensive capabilities for surveillance, reconnaissance, route monitoring and potentially payload delivery. Their low cost also creates a difficult economic problem for defenders: using expensive missiles to destroy relatively cheap commercial drones is not sustainable.

That is why directed-energy systems are attracting increasing attention. Once deployed, lasers can potentially engage repeated drone threats at a much lower cost per shot than conventional interceptors.

The reported August activity also raises several unanswered questions.

How many cartel drones were detected but not engaged? How many crossed into U.S. airspace? What missions were they conducting? What systems were used against them? And is 100 drones in a single month an unusual spike — or simply the first time the public has been given a realistic number?

If this level of activity is routine, the southern border is becoming an important real-world environment for U.S. counter-drone operations.

The three drones destroyed by laser attracted the headlines.  The other roughly 97 may be the more important story.

A Drone Over White Sands — And a Very Uncomfortable Chinese Intelligence Question

A Drone Over White Sands — And a Very Uncomfortable Chinese Intelligence Question

By Steve Douglass 

 

Sometimes the most interesting national-security stories don't become public until long after they happen.

CNN has revealed an extraordinary incident that reportedly took place in the spring of 2025 at White Sands Missile Range in New Mexico, one of the most sensitive military test facilities in the United States.

According to CNN's reporting, personnel at White Sands detected a small quadcopter-type drone repeatedly flying over the range in a manner that officials believed looked less like somebody accidentally wandering into restricted airspace and more like reconnaissance, and apparently, this wasn't a one-night event.

For roughly five days, authorities watched the drone come and go while trying to figure out who was operating it and what they were interested in.

Eventually, a multi-agency task force was assembled that reportedly included the Army, FBI, Department of Homeland Security, intelligence officials — and, interestingly enough, AARO, the Pentagon office responsible for investigating unidentified anomalous phenomena.

Then they set a trap.

Using electronic-warfare equipment, authorities reportedly took control of or disrupted the drone and forced it to land in a parking lot on White Sands Missile Range.

But finding the drone was only half the story. Authorities had also been watching a rented Mercedes RV parked near the installation. Inside were three Chinese nationals.

According to CNN, two had arrived in New York, rented the RV, and driven across the country to Las Vegas, where they picked up a third person. From there, they headed south toward White Sands.

Investigators reportedly determined that they were operating the drone.

The three were detained near the range by military personnel and turned over to federal authorities.

Then the story gets even stranger.

A second group consisted of a Chinese woman who reportedly arrived in Texas aboard a cruise ship, rented a vehicle, and drove to nearby White Sands National Park, where she remained after the park had closed. She was eventually cited and released.

According to CNN's sources, investigators apparently found identifying information connected to the woman inside the RV, convincing authorities that the two groups were connected.

Then comes the part that turns an illegal drone flight into something potentially much more serious.

CNN reports that the FBI later told military and Homeland Security officials that the individuals were believed to have connections to Chinese intelligence.

That's a substantial allegation.

It is also important to say what we don't know.

CNN was unable to determine what ultimately happened to the three people detained near White Sands, whether criminal charges were filed, or precisely what evidence led the FBI to conclude that they may have been connected to Chinese intelligence.

China's government has denied allegations that it conducts these kinds of espionage operations and has characterized such claims as unsupported speculation.

Still, put the pieces together, and this is certainly worthy of attention.

A drone isn't particularly sophisticated technology anymore. You can buy an extraordinarily capable one off the shelf. That's precisely what makes them such an effective intelligence tool. You don't necessarily need a satellite costing hundreds of millions of dollars to collect useful information about a military installation.

A relatively inexpensive drone can photograph antennas, vehicles, test equipment, security procedures, radar installations, construction projects, and aircraft. Fly repeatedly, and you can begin establishing patterns: What moves. When it moves. Where it goes. What equipment appears before a test. What disappears afterward.

That can be valuable intelligence.

Another reason White Sands would be enormously interesting to anyone collecting intelligence on American weapons technology.

RATSCAT.

Or, more precisely today, RAMS — the RATSCAT Advanced Measurement System, part of the Air Force's National Radar Cross Section Test Facility.

This is where the United States tests how visible — or invisible — aircraft, missiles and other weapons are to radar.

RATSCAT has been involved in radar-signature work associated with some of America's most important combat aircraft, including the F-117, B-2 and F-22. Today RAMS continues that mission, measuring the radar cross sections of models, full-size vehicles, and developmental low-observable systems.

RAMS includes an enormous outdoor radar-measurement range where test articles can be mounted on a retractable pylon, rotated and illuminated with radar from different angles to determine exactly how much energy they reflect back.

For a foreign intelligence service trying to understand the next generation of American stealth aircraft, missiles, or drones, information about what is being tested there — even photographs showing the shape of a test article — could potentially be extremely valuable.

Then there is Holloman Air Force Base, sitting directly alongside the White Sands complex.

Holloman is not just another fighter base.

It has a long history as a flight-test center and today supports training, test, and evaluation missions tied to some of the most advanced aerospace systems in the inventory. Its proximity to White Sands gives military planners access to enormous blocks of restricted airspace where aircraft, drones, missiles, sensors and other systems can be tested away from civilian traffic.

The Holloman-White Sands complex is also home to some unusually specialized test infrastructure.

There is the High Speed Test Track at Holloman, where rocket-powered sleds can be accelerated to hypersonic velocities to test weapons components, guidance systems, sensors, materials and other aerospace technology.

Now that I think about it, let's not forget that farther north on the range are the Oscura facilities, including North Oscura Peak, long associated with Air Force directed-energy research.

This is not science-fiction stuff.

White Sands openly lists directed energy among its major testing missions, including high-energy lasers and high-power microwave systems. Its High Energy Laser Systems Test Facility supports laser propagation, lethality, survivability, and weapons-development testing, while North Oscura Peak has supported Air Force Research Laboratory optical and directed-energy programs.

Historically, White Sands facilities have supported everything from the Airborne Laser program to high-powered microwave testing and other experimental directed-energy systems. The range's own planning documents identify North Oscura Peak with directed-energy weapons testing.

So within this one enormous military reservation you have:

Stealth-signature testing. Hypersonic testing. High-energy lasers. High-power microwave and other directed-energy systems. Missile and air-defense testing. Unmanned systems. Advanced radar and sensor development, and enormous blocks of restricted land and airspace in which all of it can be exercised.

Taken together, White Sands, Holloman, RAMS, the High Speed Test Track and the Oscura facilities make this one of the most technologically important military test environments in the United States.

For a foreign intelligence service, that's not simply a military base.

That's a shopping list.

Which makes the alleged repeated drone flights considerably more interesting.

Maybe the question isn't simply:

Why were they flying a drone over White Sands?

The better question may be:

What, exactly, were they trying to see?

But wait - there's more!

And Then There’s Nevada

There is another detail in this story that deserves a little more attention.

According to reporting on the incident, two of the Chinese nationals flew into New York, rented a Mercedes RV, and drove it across the country to Las Vegas, Nevada, where they picked up a third Chinese national.

Then they headed south toward White Sands Missile Range.

Why Las Vegas?

There are obviously a thousand perfectly innocent reasons to visit Las Vegas. But in the context of a group the FBI reportedly believed had ties to Chinese intelligence — and which was subsequently caught operating a drone over one of America's most sensitive weapons-testing ranges — Nevada becomes a little more interesting.

Because sitting roughly 80 miles northwest of Las Vegas is the Nevada Test and Training Range and, inside it, Area 51 — Groom Lake.

Was the third man simply meeting them in Las Vegas because it was a convenient transportation hub?

Maybe.

But another question practically asks itself:

Had he been doing anything else in Nevada before they picked him up?

Area 51 is exceptionally difficult to approach without attracting attention, and flying a drone anywhere near Groom Lake would be spectacularly foolish. But you don't have to penetrate the restricted airspace to conduct surveillance. Public roads, observation points, commercial satellite imagery, and even simple visual reconnaissance can provide useful information about activity around a military installation.

Area 51 isn't the only target in southern Nevada. The broader Nevada Test and Training Range supports some of America's most sensitive aircraft, weapons, electronic warfare, and tactics development.

So I'm not suggesting these men visited Area 51. There is currently no public evidence that they did, but considering what apparently happened next at White Sands, I'd certainly like investigators to answer a few questions:

Where was the third individual before the RV arrived in Las Vegas?

How long had he been in Nevada?

What places had he visited?

What photographs, videos, GPS records or drone telemetry were on his devices and was White Sands really their first military sightseeing trip?

Maybe the answers are completely mundane.

But when your road trip ends with a drone being electronically forced down inside White Sands Missile Range, Las Vegas suddenly becomes more than just a convenient place to pick up a passenger.

THE CIA DIRECTOR, A C-17, AND A VERY PUBLIC “SECRET” FLIGHT TO MOSCOW

 

THE CIA DIRECTOR, A C-17, AND A VERY PUBLIC “SECRET” FLIGHT TO MOSCOW

This is one of those stories where the airplane told us something important was happening before the government did.

On the morning of August 25, a U.S. Air Force C-17A Globemaster III did something you don't see every day: it flew into Moscow.

Not near Moscow. Not somewhere in Eastern Europe.

Moscow.

The aircraft, tail number 07-7181, was flying as RCH4555 — REACH 4555, an Air Mobility Command callsign. Publicly available flight-tracking data showed it departing Riga, Latvia, and landing at Moscow's Vnukovo International Airport shortly after 10 a.m. local time. The aircraft had arrived in Riga two days earlier after flying from Joint Base Andrews, Maryland.

For those of us who have spent years watching military aviation, that immediately raises an eyebrow.

C-17s go everywhere. That's what they're built to do. They haul troops, helicopters, vehicles, pallets and just about anything else the Pentagon needs moved.

But a USAF C-17 flying into Moscow in the middle of the current geopolitical climate?

That's different.

And this particular aircraft was interesting for another reason. 07-7181 carries almost no obvious unit identification, just subdued U.S. markings — something seen on a number of Air Mobility Command aircraft used for sensitive missions.

Then came the answer.

CIA Director John Ratcliffe was in Moscow.

The Kremlin has now confirmed that Ratcliffe met with Russian intelligence officials, including Russian foreign intelligence chief Sergei Naryshkin. Ratcliffe apparently did not meet Vladimir Putin, although Putin was briefed on the discussions.

President Trump has characterized the visit as essentially routine — or, in his words, “semi-routine.”

Maybe.

But there isn't much that's routine about putting the Director of the Central Intelligence Agency aboard a military aircraft and sending him into Moscow while Russia is at war with Ukraine and relations between Washington and Moscow remain extraordinarily tense.

The Wall Street Journal reports that Ratcliffe carried a much more serious message: a warning that Russia should not attempt an attack on a NATO member, reportedly prompted by U.S. intelligence suggesting Moscow might be considering some kind of limited action designed to test NATO's resolve. Neither the CIA nor the Kremlin has publicly confirmed that account.

There's another interesting wrinkle.

A USAF C-40B — essentially a military Boeing 737 configured to transport senior officials — also flew from Joint Base Andrews to Riga. Public tracking did not show the C-40 continuing to Moscow. One possibility reported by aviation sources is that Ratcliffe's party traveled aboard the C-40 to Latvia and then transferred to the C-17 for the Russian leg.

And that makes the C-17 itself even more interesting.

Why use a huge cargo aircraft to transport a relatively small delegation?

Because the passengers may be only part of the payload.

For sensitive overseas visits, a C-17 can carry the entire support package with them — secure communications equipment, vehicles, protective personnel and whatever specialized gear officials don't particularly want to borrow once they arrive. That's one reason these airplanes sometimes show up in places where you'd expect to see a VIP jet instead.

But my favorite part of this story is how the “secret” visit became public.

Nobody needed a spy satellite.

Nobody needed a mole inside the Kremlin.

They watched the airplane.

Flight trackers noticed an unusual C-17 leaving Riga. Aviation watchers identified the aircraft. People on the ground photographed and videotaped it approaching Moscow. Then a U.S. diplomatic motorcade was spotted moving through the city.

Only afterward did the pieces come together: the Director of the CIA was there.

That's modern open-source intelligence in a nutshell.

Governments can keep the purpose of a mission classified.

They can refuse to comment.

They can keep the passenger manifest secret.

But moving people and equipment around the planet leaves fingerprints — transponders, radio callsigns, aircraft movements, support flights, motorcades and thousands of people with cameras and internet connections watching all of it.

Sometimes the most interesting intelligence isn't hidden behind a Top Secret stamp.

Sometimes it's squawking Mode-S at 35,000 feet.

And if you know what you're looking at, the airplane can tell the story before anyone else does.

The $10 Million Snap: How a Design Flaw and Human Error Broke a KC-46 Refueling Boom

The $10 Million Snap: How a Design Flaw and Human Error Broke a KC-46 Refueling Boom

The world of military aviation is a high-stakes environment where even a minor mechanical hiccup can lead to a multi-million-dollar headline. That reality hit home recently when the U.S. Air Force dropped a massive accident investigation report detailing how a routine midair refueling mission went completely sideways over the Atlantic Ocean. 

The incident involved a KC-46A Pegasus tanker and an F-22 Raptor, and by the time the dust—or rather, the ocean spray—settled, the Air Force was looking at a hefty ten-million-dollar price tag for a single broken refueling boom.

To understand how this happened, you have to look at a perfect storm of human error and hardware limitations. During the refueling process, a highly experienced instructor boom operator made some incorrect control inputs that put the boom out of trim. At the same time, a student pilot flying the F-22 didn't properly account for how heavily the tanker handles, which messed up their closing speed. This combination caused the refueling nozzle to become completely jammed inside the fighter jet's receptacle. 

When the aircraft tried to force a quick disconnect, the extreme tension caused the boom to whip upward violently, smash into the tanker's own tail, and snap right in half before plunging into the sea.

While it is easy to point fingers at the crew, the investigation made it clear that the technology itself shares a huge part of the blame. The KC-46 has been plagued by a notorious design flaw known as the "stiff boom" deficiency, which means the boom doesn't compress or telescope smoothly when aircraft make minor movements. 

On top of that, operators on the KC-46 don't actually look out a real window like they did on older tankers. Instead, they sit in the main cabin using a Remote Vision System with 3D screens and cameras. This current system lacks sharp contrast and fails to give operators effective high-load warnings, making it incredibly difficult to judge depth and tension in real-time.

Unfortunately, this ocean mishap isn't an isolated incident. The Air Force has seen a frustrating pattern of these nozzle-binding events over the last few years, including a massive fourteen-million-dollar crash in 2024 where a broken boom rained debris down on a national forest. 

Boeing is currently working on a complete redesign of the boom actuator and a massive overhaul called Remote Vision System 2.0 to finally fix these blind spots. However, with fleet-wide upgrades delayed until at least the summer of 2027, tanker crews and fighter pilots will have to keep navigating these tense, stiff-boom handshakes in the sky with extreme caution.