The Deep State Strikes Back

  • United States Marines Semper Fi USMC Embroidered 12" Extra-Large Patch

By Adina Kutnicki

AS is said, all is not as it seems. In reality, much of what appears within the so-called mainstream media, a/k/a the mockingbird media, is little more than deep state fed propaganda, with a touch of fairy dusk injected within for an appearance of realism. As if.

SO, when the news broke that an OV-22 Ospry went down last Wednesday in the vicinity near Glamis, California, well, that was that. After all, it is not as if the Ospry hasn’t fallen from the sky before.

NATURALLY, the (media and political) spin-doctors clucked, clucked over the “tragic” deaths, even though they detest anything military related as much as they despise President Trump. Whom do they think they are fooling??

IN any event, it behooves those of us who understand what is really going down to shout what’s what from the rooftops. Indeed, those who lost their lives deserve no less.

SEMPER FIDELIS … ONWARD AND UPWARD!

♦  ♦  ♦  ♦  ♦

REAL RAW NEWS | By Michael Baxter | June 15, 2022

Several U.S. Marines on a clandestine assignment to arrest a prominent Deep State lawmaker were tragically killed last Wednesday when their OV-22 Osprey, a military aircraft with a somewhat checkered history, plunged from the sky and erupted in a colossal fireball. The mainstream media and the criminal Biden regime labeled the crash “an accident still under investigation,” but the White Hat vanguard of the U.S. military believes the crash was an act of Deep State sabotage.

The official narrative is simple: the tilt-rotor aircraft, which lands vertically like a helicopter but flies more similarly to an airplane, went down near Glamis, California, about 115 miles east of San Diego and 50 miles from Yuma, Arizona, during a routine training mission. On the surface this seems plausible because the Osprey has had 13 hull loss accidents that have resulted in 51 fatalities. Pilots have called the V-22 “an uncooperative aircraft to fly,” and some have petitioned for its withdrawal from service. So, in theory, last Wednesday’s crash could’ve been another random mishap.

But White Hats say the crash and the true nature of the Osprey’s mission, combined with unassailable evidence, rule out a mere accident; to the contrary, they assert that both a Deep State double-agent and a saboteur learned of the operation and conspired to bring down the airplane and its occupants.

They also challenge the number of Marines killed in the crash. Sources told RRN the Osprey held eight Marines: the pilot, the copilot, two flight engineers, and the four Marines tasked with apprehending a Deep State villain.

On Sunday, June 5, White Hats decided to move against a liberal lawmaker who lives near Glamis and was deeply rooted in a child trafficking ring whereby abducted American children, some as young as 4 years old, were sold to the House of Saud, the ruling royal family of Saudi Arabia. The military is said to have transactional proof implicating the target of last Wednesday’s disastrous operation. Our source did not reveal the target’s name because a follow-up operation is already underway.

“Several targets of opportunity live within 100-mile radius of that area. Naming a target or specific place of residence might spook them all,” our source said.

The operation, he added, ought to have been straightforward and effortless. The Marines were stationed at Camp Pendleton, a White Hat stronghold, and assigned to Marine Medium Tiltrotor Squadron 364 of Marine Aircraft Group 39, part of the 3rd Marine Aircraft Wing headquartered at Marine Corps Air Station Miramar in San Diego. On Wednesday, April 8, at approximately noon, Gen. David H. Berger greenlit the mission, and the Marines set forth to capture their target. The pilots were instructed to touch down briefly while a 4-man reactionary force travelled on foot a short distance to the target’s location. If the assignment had gone as planned, the Marines would have stormed the target’s home, captured him, and flown him to Camp Pendleton for processing.

The Osprey, though, plummeted into the arid terrain minutes after takeoff, killing all aboard.

According to our sources, White Hats have taken possession of both the cockpit voice recorder and the flight data recorder, instruments which record cockpit chatter and preserve the recent history of the flight through the recording of dozens of parameters collected several times per second.

Distrustful of outsiders, White Hats used in-house aircraft investigation experts to forensically analyze the Osprey’s short but ill-fated flight.

“There was zero sign of trouble up until 45 seconds before the crash. The pilots were talking casually about 4th of July plans. Then the shit hit the fan. The voice recorder picked up a massive explosion at the same time the FDR recorded an immediate loss of all flight controls. An explosion in the left engine was so strong it blew the rotor right off the engine. The aircraft banked hard and corkscrewed into the ground,” our source said.

The pilot’s last words were: “We’re dead, someone f***** us over.”

Certitude of sabotage, our source explained, was established when White Hats examined the wreckage. Explosive residue—C4 and thermite—was found on shrapnel from the left engine mount.

“We don’t yet know how it got there, who planted it. It’s damn peculiar. The V-22 was fully inspected 48 hours before, and a thorough preflight was done before it took off. Somehow, someone entered a secure area undetected and, by the looks of it, hid explosives in the engine cowling—that’s my guess, not official. We still have no answers why the explosion crippled all flight controls,” our source said.

More disturbing is that only 13 White Hats, excluding the deceased, had foreknowledge of the mission. White Hat operational details are compartmentalized, classified, and shared on a need-to-know basis. The implication is an officer within the White Hat echelon fed information to his true masters, the Deep State, which surreptitiously found a way to sabotage the Osprey without getting caught.

Gen. Berger, our source said, is personally spearheading an investigation to learn the traitor’s identity.

“It’s hard to believe someone in our ranks could’ve done this. We’re examining all angles. When we catch the traitor, and we will get him, he will be executed,” our source said in closing.

♦  ♦  ♦  ♦  ♦

{ADDENDUM: Bear uppermost in mind — To stifle the truth-telling found at this site, FB’s censors have “zeroed-out” all of my articles via their “Boom and Ban” censors ala their ubiquitous “Community Standards” — as they hunt me up and down the internet like rabid dogs to their prey! No kidding. This is just some of FB’s modus operandi, what is now deemed their “love notes” to yours truly:This URL goes against our Community Standards on spam:adinakutnicki.files.wordpress.comACTIVITY

About your post Today at 4:34 PM: No one else can see your post. And so on and so forth. In fact, just recently, each article at my “parent site”, ADINA KUTNICKI: A ZIONIST & CONSERVATIVE BLOG, had its FB registered shares go from the hundreds, with some up to the many thousands, to a big, fat ZERO. In other words, all my shares have gone down the rabbit hole. Just like that. Poof. Gone. As such, take it to the bank that each and every conservative voice which reaches a wide readership will, sooner than later, be CENSORED. MUTED.} MESSAGE FAILED:This message contains content that has been blocked by our security systems.If you think you’re seeing this by mistake, please let us know. Yes, additional “proof-in-the pudding” as to why “BANNED: How Facebook Enables Militant Islamic Jihad” had to be written!}