Friday, November 20, 2026

Summoning the Orbs: Ross Coulthart Joins a CE5 Night Watch Over Australia's Bass Strait

Can you meditate a UFO into showing up? NewsNation's Ross Coulthart went to find out, heading to Barwon Heads in southern Victoria, Australia, a reputed UFO hotspot on the edge of Bass Strait, to join the Whitehawk Psionics team for a night of CE5 "contact" meditation aimed at inviting mysterious golden orbs to appear over the water.

The setting is spooky on its own: it's near the spot where pilot Frederick Valentich vanished in 1978 after radioing that an object was hovering over his Cessna. Coulthart keeps one eyebrow raised the whole way, pressing the team on how they rule out planes, drones, satellites and Venus. Whether anything truly answered the call is unverified, so watch the episode (it runs a little over an hour, posted Nov. 17, 2026) and decide for yourself.

Video: "The UFO summoning experiment: What Ross Coulthart witnessed in Australia | Reality Check" by NewsNation on YouTube.

Cyber Chief Out: White House Swaps Its Cybersecurity Director After a Week of U.S. Tech Outages


After a week-plus of American tech meltdowns, the White House has changed who is in charge of the nation's cyber defenses. National Cyber Director Sean Cairncross is leaving his post, and Pentagon Chief Information Officer Kirsten Davies is stepping in as acting director, according to Axios, which broke the news Thursday, Nov. 19, 2026, and follow-up reports from NBC News, CNBC and Reuters via Military Times.

As of 11:05 a.m. MST (Arizona time), Friday, Nov. 20, 2026. Davies is serving in an acting role. A permanent director must be nominated by the president and confirmed by the Senate, and none of the reports we reviewed mention a formal nomination yet.

via @FoxNews on X

"Lacked the strong cyber credentials"

Axios said two sources described Cairncross' exit as amicable. But two White House officials told Axios that President Trump's new chief of staff, Stephen Miller, sought the change and pushed Cairncross out because, as one put it, he "lacked the strong cyber credentials to perform the job." Reuters, in a report published by Military Times, went further: a person close to the White House said Cairncross was "fired" and that "the president fully supported firing Sean Cairncross from his position." The White House declined to comment to CNBC, and the Office of the National Cyber Director did not immediately respond.

Cairncross sounded a gracious note on the way out. "It has been the honor of a lifetime to serve President Donald J. Trump," he said in a written statement quoted by Axios, adding that he was "incredibly proud of our work to strengthen America's cybersecurity, protect our critical infrastructure, confront foreign threats, and position America to lead the world in Super Intelligence."

NBC News said Cairncross had run the office, which oversees all government cybersecurity policy and strategy, since August 2025. Before that, he was the Republican National Committee's chief operating officer in the 2016 cycle. Reuters noted that previous cyber directors had technology and national security experience.

Who is Kirsten Davies?

Davies was sworn in as the Pentagon's CIO in December 2025, according to Reuters. Before that she was chief information security officer at Unilever and held technology and cyber roles at Estée Lauder, Barclays-Africa Group, Hewlett Packard and Siemens. Because the Senate already confirmed her for the Pentagon job, an administration official told Axios, "Kirsten has the credentials to excel in this position and has already been Senate-confirmed."

via @_KirstenDavies_ on X

In that post, quoted by NBC News, Davies said the country's opportunity "is to dominate the cyber landscape for generations to come …but only if we modernize and drive resilience into the foundations our great nation runs on." CNBC reported that Defense Secretary Pete Hegseth and Secretary of State Marco Rubio both congratulated her.

via @SecRubio on X

Outages, not attacks, officials say

The shake-up follows a brutal run that this blog has tracked day by day: the Microsoft Outlook outage, the FAA's nationwide ground stop, the Chase banking outage, the NSA's classified network going dark, United Airlines and the USDA's cybersecurity incident. But officials have been clear on one point. CNBC said the White House has insisted there are no indications of a coordinated cyberattack, state-sponsored activity or malign actor behind the recent outages, and Reuters reported that the top U.S. intelligence official said Wednesday they were separate outages tied to maintenance and technical changes. Cybersecurity experts told Reuters the disruptions are likely linked to companies rushing to patch newly discovered software vulnerabilities in the AI age.

What really grounded the planes

The FAA has also explained more about the Nov. 13 ground stop. In its official Q&A, the agency said legacy equipment became unstable when data flooded its FTI network at 1,000 connection attempts every 4 to 5 seconds. The initial investigation pointed to a radar site in Amarillo, Texas, and a radio site in El Dorado, Arkansas, where contractor L3Harris had been deploying a new router. The FAA said it has "no indication that this was a cyberattack," disabled the same function on more than 60 other Juniper routers and paused installing them. CNBC reported Nov. 18 that engineers had replicated the problem in a Florida lab but had not yet determined exactly why the routers failed. HPE told CRN its equipment "was working as configured."

Reuters noted that next week will test the nation's systems again, as millions fly for Thanksgiving and retailers brace for Black Friday. We'll update this story if Davies is formally nominated or investigators pin down a root cause.

Header photo: The White House at night, by Rob Young via Wikimedia Commons (CC BY 2.0), edited.

"Boom! Boom!": 74 Years Since a Man Said He Met a Visitor From Venus Outside Desert Center

Seventy-four years ago today, a group of seven saucer enthusiasts pulled their cars over on a lonely desert highway in Southern California, and one of them walked off into the rocks. When he came back an hour later, he had a story that would launch an entire movement: he said he had just met a man from Venus.

The man was George Adamski, and the date was Thursday, November 20, 1952. Whatever you make of what he claimed (and plenty of people, including most serious UFO researchers of his day, made very little of it), the "Desert Center contact" became one of the most influential UFO stories ever told. And, fun fact for those of us out here, a good chunk of the cast came from Arizona.

A road trip with hunches

Adamski lived at Palomar Gardens, a campground and café on the slopes of Palomar Mountain, where he kept a six-inch telescope. Visitors often assumed he worked at the famous Palomar Observatory up the hill. He didn't, and he had little formal schooling, but his admirers called him "Professor" anyway. By 1952 he had been lecturing about flying saucers for years and taking photos of what he said were spacecraft.

In his own account, published the following year in the book Flying Saucers Have Landed, he describes leaving Palomar Gardens around 1 a.m. that morning with Alice K. Wells, who ran the café, and his secretary Lucy McGinnis. Near Blythe they met two Arizona couples: Al and Betty Bailey of Winslow and George Hunt Williamson and his wife Betty of Prescott. After breakfast in Blythe, Adamski says he followed a "hunch" and led everyone back west to Desert Center, then about 11 miles up the highway toward Parker, Arizona.

They stopped among sharp volcanic rocks and silver-white desert holly. Then, according to the account, they saw a large cigar-shaped craft drifting high overhead. Adamski felt it was looking for him. He asked to be driven a short way off, told the others to stay put and watch, and walked out alone.

The visitor in the oxblood shoes

Here is the part of the story that made Adamski famous. He wrote that around 12:30 p.m. a smaller, bell-shaped "scout ship" settled among the hills, and a figure beckoned him from the mouth of a ravine. The figure looked like a young man: about 5 feet 6 inches tall, around 135 pounds, maybe 28 years old, with sandy hair to his shoulders. He wore a chocolate-brown, one-piece garment and oxblood-colored shoes. Adamski even noted, memorably, that "his trousers were not like mine."

Adamski said they communicated mostly through telepathy and hand signs. The visitor, he claimed, was from Venus, and he was worried about Earth's nuclear tests and the radiation they might spread. The only spoken words Adamski reported were a reply to his question about atomic bombs: "Boom! Boom!" In later books the visitor got a name, Orthon.

After about an hour, Adamski waved his hat to call the others over. The group reported footprints in the sand bearing strange symbols, and Williamson said he made plaster casts of them. Four days later, on November 24, 1952, the Phoenix Gazette ran the story, with photos of the four Arizonans, under the headline "Flying Saucer 'Passenger' Declares A-Bomb Blasts Reason For Visits."

Sworn statements, and second thoughts

In March 1953, all six companions signed notarized affidavits saying they had witnessed the contact, and those statements were printed in the book. That sounds impressive until you notice who they were: Adamski's café owner, his secretary, and four friends who had come specifically hoping to see a landing. By the accounts that survive, they watched from a considerable distance.

And at least one of them later wobbled. Years afterward, Al Bailey reportedly told UFO investigator James Moseley that he had not actually seen a UFO or an alien that day, which doesn't square with the affidavit he signed.

Then there's the photo. Adamski said the visitor returned on December 13, 1952, and that he snapped the scout ship through his telescope. Skeptics at the time said it looked suspiciously like the top of a chicken brooder. Writers have also pointed out how much "Orthon" resembles Klaatu, the calm, human-looking space visitor who warns Earth about its weapons in the 1951 movie The Day the Earth Stood Still. And of course, we now know that Venus's surface is a crushing, furnace-hot world no tanned young man in a brown jumpsuit is strolling around on.

Why it still matters

True or not (and the evidence leans hard toward "not"), the story mattered enormously. Flying Saucers Have Landed, co-written with Irish author Desmond Leslie, became a bestseller and reportedly sold more than 200,000 copies by 1960. It kicked off the 1950s "contactee" era of friendly, human-looking "Space Brothers" with messages of peace, and inspired a wave of copycat claims. It also infuriated researchers who wanted UFOs taken seriously and felt stories like this made them look ridiculous.

So next time you drive Highway 177 north out of Desert Center toward Parker, take a look at the rocky hills off to the side. Just a fun "what if" from us: if a guy in oxblood shoes waves you over, maybe bring a better camera than George did.

Sources: George Adamski & Desmond Leslie, Flying Saucers Have Landed (1953), chapter "The Memorable November Twentieth"; NHI Archives, "The Desert Center Contact"; UAP Codex, "Adamski case"; Wikipedia, "George Adamski"; Phoenix Gazette, Nov. 24, 1952.

New UFO Files Dropped: Pentagon's 8th Release Includes Unexplained Military Videos and a Skinwalker Ranch 'Exotic Tissue' Vault

The Trump administration opened the UFO vault again this morning. On Friday, Nov. 20, 2026, the Department of War published the eighth batch of declassified UFO files under PURSUE, the Presidential Unsealing and Reporting System for UAP Encounters. That's the government-wide declassification push President Trump ordered back in February. This drop includes three military sensor videos the government says it still can't explain, a 70-year-old saucer report from one of America's most famous aircraft designers, and the first official acknowledgment of a strange Pentagon-funded report about Utah's Skinwalker Ranch.

As of 7:15 a.m. Arizona time (MST), Friday, Nov. 20. The files went up early this morning, and reporters and researchers are still working through them.

"Release 08" is live

In a statement, chief Pentagon spokesman Sean Parnell said the department "is publishing the eighth release of declassified and historical Unidentified Anomalous Phenomena (UAP) files," and that it and its agency partners "are actively working on the next release." Everything is posted at WAR.GOV/UFO. That page says the files are "unresolved cases, meaning the government is unable to make a definitive determination on the nature of the observed phenomena." It also says the department "welcomes the application of private-sector analysis."

The Daily Mail, which got an early look at the material, reports the batch includes about 40 documents and three videos. It also says this release pushes the total number of records made public since May past 500. The paper's post about the files has been one of the most-viewed news posts on the release so far:

via @DailyMail on X

Three videos from the Middle East

All three new videos come from U.S. Central Command, which reported them to the Pentagon's All-domain Anomaly Resolution Office (AARO). They are labeled DOW-UAP-PR166 (2020), PR169 (2023) and PR168 (2026). The official descriptions are dry: each one tracks an "area of contrast" moving across the sensor's view.

  • PR166 (2020): 20 seconds of infrared video. An object enters from the right edge of the frame and crosses to the left while the sensor pans and zooms to keep it centered. According to the Daily Mail, this tiny white-hot object appears to fly across the bow of a warship.
  • PR169 (2023): 13 seconds of electro-optical and infrared video of the sensor tracking a single object.
  • PR168 (2026): 54 seconds of footage from this year. It tracks "multiple areas of contrast," then zooms in on two of them and loses contact with them from time to time.

Longtime FOIA researcher John Greenewald Jr. of The Black Vault posted all three clips, with the government's context, in the most-liked thread on the release so far:

via @theblackvault on X

Here's the 2020 infrared clip, shared by the UFO news account Interstellar:

via @InterstellarUAP on X

The Skunk Works legend who saw a saucer

According to the Daily Mail, the batch also includes the first complete copy of a 1953 report by Clarence "Kelly" Johnson, the Lockheed engineer who founded the Skunk Works and designed the U-2 and SR-71 spy planes. Johnson said a black, elliptical object hung motionless west of his ranch in Agoura, California, for at least three minutes on Dec. 16, 1953, then sped off and vanished within 90 seconds. A Lockheed test crew in the air at the time saw it too. "I am now more firmly convinced than ever that such devices exist," Johnson wrote. The Air Force filed it away as a "lenticular cloud."

Skinwalker Ranch and a vault for "exotic tissue"

The strangest item may be the government's first official acknowledgment of the "Ten Month Report." This is a 538-page dossier delivered to the Defense Intelligence Agency in July 2009 by Bigelow Aerospace Advanced Space Studies (BAASS), the contractor that studied Utah's Skinwalker Ranch for the Pentagon. The Daily Mail reports that it describes plans for a 5,000-square-foot underground vault with three-foot-thick walls to store "exotic material or tissue." It also recounts three military observers walking into a sudden "cold zone" at the ranch in 2009. The paper notes the government has found no record that the vault was ever built, and no physical material of the kind BAASS was after.

The batch also includes witness sketches that, according to the Daily Mail, were never made public before. One is a 1957 drawing of a spiked cylinder that five fishermen reported off Martha's Vineyard. Another is a Michigan teenager's drawing of a saucer with portholes.

What comes next

The Pentagon says more batches are coming, and that it's combing through tens of millions of records, many of them only on paper. None of today's files proves anything about aliens; they are, by the government's own label, unresolved. But for anyone who wants to judge the raw evidence for themselves, everything is now public at WAR.GOV/UFO. We'll keep watching for the ninth release.

Thursday, November 19, 2026

Farm Payments Frozen: USDA Takes Systems Offline After a Cybersecurity Incident


 

The week of American tech trouble just reached the farm. The U.S. Department of Agriculture has taken numerous applications offline over several days after its own security team found what it called a "security incident," Nextgov/FCW and Government Executive reported Thursday afternoon, Nov. 19, 2026. The outages have hit many of the financial tools USDA uses to move payments between the department and farmers.

As of 6:15 p.m. MST (Arizona time), Thursday, Nov. 19, 2026. USDA has not publicly confirmed a breach, no one has said who was behind it or whether any data was stolen, and no restoration timeline has been announced.

via @WatcherGuru on X

"Reset all database passwords"

According to Nextgov/FCW, the trouble traces back to an internal email sent Monday by Chris Rottler, acting assistant chief information officer for USDA's Farm Production and Conservation Business Center. The email said the department's Cybersecurity and Privacy Operations Center had "uncovered a security incident" that required its Information Services Division to "reset all database passwords in all environments, and this is requiring us to reset all applications causing outages."

Nextgov said a technical bulletin dated Thursday warned that maintenance was ongoing and that applications "may continue to experience intermittent outages throughout the week." By late Thursday afternoon, some staff were also having trouble with the department's virtual private network (VPN), according to one source and a separate notice the outlet viewed. Nextgov said it was not clear whether every employee received the Monday email, and that USDA and the Cybersecurity and Infrastructure Security Agency (CISA) had been asked for comment.

via @HormuzLetter on X

Why farmers should care

USDA gives farmers a financial safety net, including crop insurance and help covering losses when bad weather cuts harvests. Nextgov reported that the outages have affected many of the tools behind those payments, and that staff have been unable to reach key client-facing applications used to check notifications and the status of loans and other aid.

Farm trade outlet DTN/Progressive Farmer reported that software used by local Farm Service Agency (FSA) and Natural Resources Conservation Service offices has had intermittent outages since Monday, disrupting some work on producer loans and payments. Affected employees reported internal guidance to "proceed with caution and don't do any critical work," and users also reported problems with USDA's eAuthentication login system, DTN said. As of Thursday afternoon, a county loan officer told DTN the problem was still there.

The timing is awkward. DTN noted that producers have until Dec. 11 to enroll in the 2026 Agriculture Risk Coverage and Price Loss Coverage programs, and dairy producers have until Dec. 18 to enroll in the 2027 Dairy Margin Coverage program.

Officials play it down

USDA leaders did not call it a breach when DTN asked. FSA Administrator Bill Beam said, "I have heard that there's some outages. I talked to our leader in the IT department, and you know they're working on it." Richard Fordyce, USDA's undersecretary for farm production and conservation, said, "We will occasionally have outages sometimes because there's updates."

Inside the department, frustration is growing. Nextgov's sources said senior officials have not kept staff fully informed, and one said they had only been given vague information about a possible security breach.

via @InsiderWire on X

Another week, another outage

The USDA news lands on top of a string of disruptions this month, including the NSA's NSANet outage and Thursday's vendor breach tied to Chase, Visa and Mastercard. Nextgov said some USDA staff worried the department could be the next to suffer widespread IT problems, after recent incidents that were not cyberattacks hit aviation networks, financial systems, Microsoft tools and the NSA. DTN reported that on Wednesday, intelligence officials told Congress those recent outages were separate incidents tied to maintenance and technical changes, not a coordinated cyberattack.

DTN also pointed to a Government Accountability Office report released Thursday finding that USDA and the Food and Drug Administration have not fully put in place 16 federal requirements meant to improve cybersecurity across the food and agriculture sector, including emergency preparedness and sharing real-time threat information with CISA. USDA disagreed with GAO's recommendations, DTN said. Times Now also covered the incident.

We'll update this story if USDA confirms what happened, names a culprit or says when farmers' payment systems will be fully back.

Hacked Through the Side Door: Vendors for Chase, Visa and Mastercard Breached, Customer Emails Leaked


This week's run of tech trouble has a new chapter, and this time it's a hack. On Thursday, Nov. 19, 2026, JPMorgan Chase said outside companies that do work for the bank were hit by a cyberattack, and that the attackers may have gotten customer names and email addresses. Visa and Mastercard also said third-party providers they use were involved. A cyber extortion group calling itself "n0n" has claimed the attacks and posted data online, Reuters reported.

As of 11:15 a.m. MST (Arizona time), Thursday, Nov. 19, 2026. None of the three companies has named the vendors that were breached, and no one has said how many customers were affected.

What Chase said

Chase posted its statement on X at about 6:17 a.m. Arizona time. "Based on our investigation so far, we believe the attackers accessed certain marketing data held by those vendors, which may include some customer names and email addresses," the bank said. Chase also said "there is no disruption to our services" and that "where appropriate, we will contact affected customers directly and offer support, including complimentary credit monitoring," according to The Verge, which published the full statement.

via @Chase on X

The bank also said, "There is no connection to service disruption some customers experienced earlier this week." That refers to Monday's Chase outage, which the bank blamed on a software bug. ABC News noted that JPMorgan did not say when the cyberattack happened or name the third-party companies involved.

What the hackers claim

According to Reuters, n0n claimed on Nov. 16 that it had cardmember engagement records with "hundreds of thousands of campaign interactions for tens of thousands of distinct cardmember email addresses." Reuters cited a screenshot captured by the cybercrime research platform eCrime.ch. In its own review of the posted data, Reuters found what appear to be 124 bank employee email addresses and more than 16,000 customer email addresses, some with phone numbers and postal codes. Reuters said it could not independently verify that the data is authentic, and JPMorgan declined to comment on the data.

Cybernews, which has followed the gang's claims since Nov. 17, said n0n gave the companies a 48-hour countdown to negotiate before dumping the files. Its researchers said the JPMorgan leak covers roughly 16,000 customer email addresses, phone numbers in some cases and JPMorgan Chase account IDs. They said it appears linked to the bank's invitation-only Reserve card program.

via @Cybernews on X

Visa and Mastercard: no card numbers

A Visa spokesperson told Reuters the claims are "associated with an incident involving a third-party service provider in Asia Pacific. Visa's systems were not involved and were not impacted. No payments data such as card numbers were affected." Reuters said the Visa files focus mostly on Asia-Pacific markets such as Hong Kong, Taiwan, Korea, Japan and Australia. Cybernews counted more than 6,000 premium Visa customers in the leak, likely from a platform that tracks Visa's premium dining programs in the region.

A Mastercard spokesperson told Reuters the company was recently informed of an incident "at a third-party provider that resulted in the exposure of limited amount of email addresses — non-payments information — from a small subset of cardholders enrolled in a specific benefit program." It added, "There is no impact to the Mastercard payment network or the ability for people to use their cards." Cybernews said the Mastercard leak has about 2,000 customer entries, if authentic. A Cybernews researcher said all three datasets share similar formatting, which suggests they may have come from the same third party. That hasn't been confirmed.

via @WatcherGuru on X

Who is n0n?

Reuters, citing eCrime.ch, said the group has claimed roughly 200 incidents since it showed up in September 2026. Cybernews reported that the gang recently claimed travel giant Expedia too. The Washington Post and Quartz also covered the breach, with Quartz citing The Wall Street Journal.

What customers should do

If you're a Chase customer, watch out for scams. Dr. Pablo Molina, head of cybersecurity at Drexel University, told NBC10 Philadelphia that people should be careful with messages that look like they come from Chase but arrive from unfamiliar phone numbers or email addresses. He also suggested freezing your credit if you think your information was exposed. "Customers don't distinguish between a bank and a vendor when it comes to a cyberattack," consultant Carissa Robb of SolomonEdwards told Reuters.

Still unconfirmed

Several key questions are still open. The vendors haven't been named, and nobody has said how many customers were affected or when the break-in happened. Reuters and Cybernews both say they couldn't verify the leaked files. Nobody has confirmed that one vendor was behind all three leaks. We'll update this post as the companies share more.

It Flew on His Wing: 62 Years Since a Navy Destroyer and a Crusader Jet Chased a Dark Delta Off Puerto Rico

Sixty-two years ago tonight, somewhere over the moonlit Caribbean, a U.S. Navy pilot looked out his left canopy and saw something he could not explain sitting nine miles off his wing, matching his speed, his altitude and his heading as if it had been invited to fly formation.

It was the evening of November 19, 1964. What happened over the next 21 minutes ended up in Project Blue Book's files, set off a flurry of military message traffic, and was still being picked over by the CIA months later. It's one of the cases that UFO researchers keep coming back to, because it has nearly everything: a radar track, a trained pilot's eyewitness account, radarscope photographs, and even a brief spell of radar jamming nobody could pin on anyone.

A ship testing a new radar

The first detection didn't come from the jet. It came from the destroyer USS Gyatt (DD-712), which was at sea about 220 miles northwest of Puerto Rico running trials for the Navy's Operational Test and Evaluation Force. On board was a prototype AN/SPS-49 search radar, and the crew was recording its screen with a shipboard radarscope camera, a lucky detail, because it meant the night was being photographed.

Around 9 p.m. local time, the Gyatt's radar picked up a "bogey." The ship was working with an F-8 Crusader from Utility Squadron Eight (VU-8) out of Naval Station Roosevelt Roads, call sign "Salt Spray 26," which was cruising at about 30,000 feet over Puerto Rico. Communications were poor (the pilot later blamed working UHF radio at around 230 miles), but the Gyatt warned him something was out there, and around 9:01 p.m. he reported "a stranger closing very fast."

The delta that joined up

The pilot was the squadron's executive officer, a lieutenant commander with extensive jet experience, named in the records as K.H. Woodbury (some summaries spell it "Woodsbury"). The weather, by the Air Force's own message, was "clear, visibility good, with full moon."

In his written answers, he described a single object: a delta shape, "about size of operational fighter (F4)," dark black or gray, with no navigation lights and no contrail, just what looked like a single afterburner-style light glowing from its tail when it accelerated.

According to his report, it flew overhead at very high altitude and very high speed, swung around, came back past him on a parallel course, and then "circled to right around observer and joined up at about 8 or 9 miles in 9 o'clock position," holding about Mach .84 at 30,000 feet, the same as him. He lit his afterburner and tried to turn in and close the distance. His one-word verdict on that: "(Unsuccessful)." The object pulled away in a wide climbing turn, going up through 50,000 feet at a steep angle in excess of Mach 1.

And it wasn't done. On and off, the encounter lasted about 21 minutes, and on his way home to Roosevelt Roads, the object reportedly closed on him again from behind.

NICAP's case summary quotes his assessment: "Its speed, acceleration, ceiling and ability to de-cellerate exceed any aircraft I have ever seen or heard of. There is no reasonable explanation for this target." During the encounter, the Gyatt's SPS-49 was also briefly jammed, and the source was never identified.

How fast was it, really?

Here's where it gets messy, in a good way. A Caribbean Sea Frontier message reported the pilot's estimate as "in excess Mach 3" and said the Gyatt's radar had tracked the object at more than 3,800 knots, roughly 4,370 miles per hour.

When the Air Force's Foreign Technology Division analyzed the radarscope photos, it came up with a much tamer picture: the bogey cruised at subsonic speed for the first stretch, then accelerated, averaging about 1,200 knots and, per the photos, never topping about 1,515 knots. Blue Book's final call was simply "Aircraft." Even the squadron's own evaluation leaned that way: it judged the target a "very high performance aircraft" because it maneuvered like one, apart from that extreme acceleration, deceleration and steep high-speed climb.

Not everyone bought it. Researcher Antonio Rullan later re-worked the same scope data and argued that it supports the ship's original claim, that the bogey was supersonic for most of the track, hit around 1,500 mph, and then slowed to about 260 mph once it had shaken off its pursuer.

Not the only night

The Gyatt incident wasn't a one-off. An intelligence officer at Ramey Air Force Base reported that the same people had picked up unidentified radar contacts on November 16, 17 and 18, and again on the 24th. A 1965 CIA document on the episode concluded there were "apparently valid tracks and/or observations of unidentified aircraft" around the Atlantic Fleet Weapons Range on several of those dates. Researcher Joel Carpenter has also pointed to Blue Book teletypes suggesting the Air Force chief of staff ordered an investigation under pressure from the White House.

So whose was it? That's the fun "what if," and it's pure speculation: a secret U.S. test aircraft that nobody told the Navy about? A foreign intruder probing the range? Or something that didn't come from anyone's hangar at all? Officially, it was an unidentified aircraft. Unofficially, a veteran Navy pilot couldn't catch it, and couldn't explain it.

Sixty-two years later, the nineteen radarscope photos sent to Blue Book still haven't surfaced publicly. Somewhere, maybe, a dark delta is still flying on somebody's wing.

Sources: NICAP RADCAT case directory and Antonio Rullan's report; Project Blue Book case file; CIA document via The Black Vault; UAP Globe case file.

Wednesday, November 18, 2026

Streaking Past the Window: A Passenger's LaGuardia Video Leads NewsNation's Airport UFO Roundup

Look out your airplane window and you might catch more than the skyline. In this new NewsNation compilation, posted November 17, 2026, the standout clip is passenger Michelle Reyes's window video of a cylinder-shaped object streaking past her plane near LaGuardia Airport in New York. Investigator Ben Hansen estimates it was moving at more than 200 mph and says he found no evidence it was faked, while the rest of the segment revisits drones swarming over Long Island's Gabreski Airport and the airspace closures around El Paso.

Nothing here has been officially identified, so treat it as unexplained footage, not proof of anything otherworldly. UFO, drone, or something else entirely? Watch and decide for yourself.

Video: "Airport Sightings: UFOs or Drones Watching Our Skies? | Backscroll" by NewsNation on YouTube.

Cart Crash: Amazon App Outage Hits Thousands of Shoppers as Tech Breakdowns Keep Piling Up

First it was Microsoft, then the FAA, Chase, United, Apple and the NSA. On Tuesday, Nov. 17, 2026, it was Amazon's turn. Thousands of shoppers reported problems with Amazon, most of them with the Amazon mobile app, according to outage tracker Downdetector. Reuters reported that Downdetector showed more than 5,000 reports of issues with the shopping platform as of 6 p.m. Pacific time (7 p.m. Arizona time).

As of 11:30 a.m. MST (Arizona time), Wednesday, Nov. 18, 2026. Outage trackers show Amazon reports back near normal levels, but Amazon has not publicly explained what happened or confirmed a fix.

What went wrong

Downdetector's own account flagged the problem on X Tuesday evening, saying user reports indicated problems with Amazon "since 12:21 PM EST," which is 10:21 a.m. Arizona time. The big wave of complaints came later in the day. Downdetector's post went out at 6:21 p.m. Arizona time, and Reuters' 5,000-report count came about 40 minutes later.

via @downdetector on X

Another tracker, Instatus, recorded reports for Amazon jumping to a peak of 11,425 an hour, more than 60 times normal. By its count the spike lasted about 13 hours, starting in the 10 a.m. hour Arizona time on Tuesday and returning to normal around 11 p.m. Users who left comments there wrote "Not loading" and "Can't log in." Most reports were about the mobile app rather than the website.

Shoppers took to X as the evening went on. Financial news feed First Squawk posted that "Amazon experiences reported service issues as user complaints increase on Downdetector." A widely shared post from the account Anonymous TV described a "possible widespread Amazon outage" hitting the website, mobile app and checkout. That post has drawn more than 1,000 likes.

via @YourAnonTV on X

What Amazon has said

So far, nothing we could find. We didn't find any public statement from Amazon about the cause, how many customers were affected, or whether the problem has been fixed. Instatus lists Amazon's official incident note as "Nothing posted" and says it couldn't find an official status page for Amazon's shopping site. Reuters' report also didn't include any comment from the company. Until Amazon speaks, the cause is unknown. There's no confirmation either way about whether it was a software problem, a cloud issue or anything else.

via @FirstSquawk on X

Is it fixed?

The trackers suggest that things have mostly calmed down. On Wednesday morning, Instatus's live Amazon page said "No, it's up," with 55 reports in the past hour. Most of those were still about the mobile app. LiveOrDown, which only checks whether the website loads, found Amazon.com reachable from all three of its test regions at about 11:08 a.m. Arizona time. That's not the same as Amazon confirming a fix. India's Sunday Guardian Live cited Downdetector readings of 2,051 reports against a normal baseline of 14, later easing to 328. It said users described the app failing to load, "403" access-denied errors and trouble reaching orders and account pages.

What about Audible? We couldn't confirm a widespread Audible outage. LiveOrDown logged only three Audible app reports Tuesday evening, and another tracker showed no Audible reports during the same window.

Not Amazon's first stumble this year

Amazon has had a bad outage before. On March 5, 2026, Reuters reported that its website was hit by an outage that peaked at more than 22,700 Downdetector reports. Amazon later said that problem was related to "a software code deployment". There's no word yet on whether Tuesday's trouble had anything in common with that one.

A week of breakdowns

Tuesday's Amazon trouble came at the end of a remarkable run. CNBC counted Microsoft's Outlook problems on Thursday, the FAA ground stop on Friday, Monday's issues at JPMorgan Chase and United Airlines, and Tuesday's Apple outage and NSA network failure. Director of National Intelligence Jay Clayton told CNBC, "This is not cyberattack, and this is not a coordinated effort by a nation state. We've looked very closely." His comments came before Amazon's trouble peaked, and nobody has tied Amazon's outage to the others.

If your order history or checkout broke Tuesday night, you weren't alone. We'll update this post if Amazon explains what happened.

It Turned Inside His Plane: 78 Years Since a Glowing Oval Ran Rings Around a Pilot Over Andrews Air Force Base


Long before the famous 1952 "invasion" of Washington's skies, and more than half a century before Navy pilots chased the "Tic Tac" off California, a pair of Air Force reservists in a humble trainer plane spent about eighteen minutes trying to catch something over the capital's back yard. They never did. Seventy-eight years ago tonight, on November 18, 1948, a glowing, wingless oval toyed with them above Andrews Air Force Base in Camp Springs, Maryland, a few miles from the U.S. Capitol.

The case ended up in the Air Force's UFO files (Project Sign, later folded into Project Blue Book) as Incident 207, and the pilots' signed statements are still there to read. That's what makes it so fun: we don't have to guess what the witnesses said. We have their words.

A light that wouldn't behave

It was a Thursday night, and the base's 2238th Air Force Reserve Training Center had pilots up for night proficiency flying. The weather, according to the official report, was about as good as it gets: "CAVU, no smoke, haze or fog. Full moon."

At roughly 9:45 p.m., 2nd Lt. Kenwood W. Jackson spotted "a lighted object flying from northeast to southwest across Andrews Field." He and 2nd Lt. Henry G. Combs were flying a T-6 Texan, the classic two-seat trainer. Combs' first thought was the sensible one: probably just an airplane with burned-out navigation lights. So he went to take a look.

"As I came in," Combs wrote, "the object took evasive action."

The chase

What followed reads like a dogfight in which only one side knew the rules. Combs switched off his own wing and tail lights and tried to keep his exhaust flame hidden so he could sneak up on the thing. It kept "going quickly up and over my aircraft." He tried to line it up against the lights of Washington, D.C., and the moon to silhouette it, flying "very, very tight 360 degree turns with flaps down." And here's the line that gives today's post its title:

"The object could turn inside of my aircraft even under the preceding condition mentioned."

Combs also noted "the very quick variation of air speed from approximately 80 MPH up to 500 or 600 MPH." All he could make out was "an oblong ball, with one light, no wings and no exhaust flame."

Jackson's statement describes the same cat-and-mouse game. While they dove at it at about 240 mph, the object "would climb vertically then drop below us from behind and continue to circle."

Lights on

Finally, at about 7,500 feet, Combs pulled up sharply, came in underneath the object at an estimated 300 to 400 feet, and hit it with his landing light. It had, he said, "a very dull gray glow to it and was oblong in shape." Jackson saw the same thing: "It appeared to be oval, no wings, no tail surfaces."

Then it left. According to Jackson, it "headed to the Northeast climbing rapidly," and they lost sight of it around 8,000 feet at 10:03 p.m. Combs said it made "a very tight turn and headed for the east coast at about 500 to 600 MPH."

The witnesses on the ground (and in the pattern)

A second reserve pilot, flying in the local traffic pattern at 1,000 feet, signed a statement saying he saw "the same object" pass directly overhead across the northeast corner of the field. The Debrief identifies him as 2nd Lt. Glen L. Stalker.

On the ground, a staff sergeant named John Kushner (the typed transcript spells it "Kushmer") was standing by a parked plane when he heard a noise and saw "a shining object coming across the sky." It "sounded like a P-47 only twice as loud," he wrote, "but it couldn't have been a P-47 and I did not see any exhaust." When the pilots landed, some of them asked him if he'd seen anything. "This object did not look like an aircraft."

The base's report to Air Force intelligence, filed under the wonderfully blunt subject line "Flying Discs," summed it up: the object was "highly maneuverable, seemed aware of the presence of following aircraft, and capable of almost vertical flight," smaller than a T-6, oval or ovate. The witnesses were considered reliable.

So... a balloon?

This is where the file gets entertaining. According to The Debrief's review of the records, one analyst at Air Materiel Command at Wright-Patterson floated the idea of a weather balloon and suggested it would be "an interesting experiment" to have a plane chase a balloon and see whether it seemed to perform "evasive maneuvers." Another reviewer reportedly wrote a single sentence on the next page: "Definitely not a weather balloon."

There are some loose ends worth admitting. The investigators weren't even sure whether the pilots had been in one plane or two, and The Debrief's writer suggests the "twice as loud as a P-47" roar Kushner heard might have been a real P-47 in the air that night. That one is speculation, not something the file confirms. And nobody had radar, photos, or sketches; the report says plainly, "No photographs available."

Here's the fun "what if," clearly labeled as such: if a balloon really did all this, it was the most athletic balloon in Air Force history, one that outclimbed a diving trainer, slipped behind it, and then left at hundreds of miles an hour. If it wasn't a balloon, then something oval and wingless spent a quiet November evening in 1948 running laps around one of the most important airfields in America, and nobody ever found out what it was.

Seventy-eight years later, it's still listed in many case catalogs as unexplained. Look up tonight. Just in case.

Sources: Project Blue Book/Project Sign records for Incident 207 (Andrews AFB, Nov. 18, 1948), transcribed by NICAP (nicap.org); Jazz Shaw, "Incident 207: A Tic Tac over Washington, DC, in 1948?", The Debrief.

Tuesday, November 17, 2026

Spy Agency Goes Dark: NSA's Classified NSANet Network Hit by Outage After "Routine Maintenance"


 

The week of breakdowns has now reached America's most secretive spy agency. On Tuesday, Nov. 17, 2026, NSANet, the highly classified network the National Security Agency uses for its internal communications, went down. CNN broke the story, citing six people familiar with the matter. Workers at the agency's Fort Meade, Maryland, headquarters were told to stagger their arrivals while the problem was assessed.

As of 6:30 p.m. Arizona time (MST), Tuesday, Nov. 17. This is a developing story. Neither the NSA nor any outlet we checked has confirmed that NSANet is fully restored.

What went down

NSANet lets NSA employees send and receive classified information internally, including top-secret material. CNN posted the news on X just after 8:30 a.m. Arizona time. According to the Associated Press, a defense official who spoke on condition of anonymity confirmed that the problem disrupted NSANet operations.

via @CNN on X

The network wasn't completely dead. One source told The Record it was "only providing intermittent service." The staggered arrivals, the source said, were meant to avoid tens of thousands of employees all signing on to the network at the same time. CBS News reported that sources called this "Code Gray," a modified reporting schedule. CNN, citing a New York Times report, described an employee voicemail recording that called the situation a "code yellow" and told non-emergency staff to come in on a staggered schedule. CBS also reported that some activities were moved to other NSA facilities around the country.

The NSA's explanation: maintenance

On Tuesday afternoon the agency released a short statement: "The National Security Agency experienced temporary degradation during scheduled routine maintenance. While some internal systems were affected, mission-critical capabilities remain fully operational and our ability to defend national security continues." It added that NSA infrastructure "is designed with multiple layers of redundancy." As The Guardian noted, the statement did not name the network or say what caused the problem, how long it lasted or whether service had been fully restored.

Later in the afternoon, Director of National Intelligence Jay Clayton went further. CNN reported that he blamed the outage on software patches for major vulnerabilities discovered last month. "The patching that has gone on following that has caused some of these systems to not come back up when you patch them as expected," Clayton said on Fox Business. "That is that is what has happened at the NSA today." According to CNN, those vulnerabilities are in PHP, a widely used programming language for websites. Two sources also told CBS News that the outage came from routine system patching, though CBS said "the precise circumstances surrounding the disruption remain unclear."

via @BNONews on X

A hack? Officials say no

Every outlet we checked reported that there's no sign of a cyberattack. NBC News quoted Clayton: "This is not a cyber attack, and this is not a coordinated effort by a nation state. We've looked very closely." NBC also reported no sign that the outage affected the NSA's work. A former senior NSA official told CNN that NSANet is "more of a network of networks," and called the outage "alarming, but likely not crippling." CNN's sources said the Five Eyes intelligence-sharing system was not affected, and that the government has backup channels for reaching President Trump, who is traveling in Asia.

Not everyone is reassured. Former Defense Department analyst Mike Wiacek told The Guardian that "four major outages in under a week" look "suspiciously" like what he'd expect an attack to look like. He also said, "You can't compress months of forensic work into a few hours."

via @NBCNews on X

Is it fixed?

Not confirmed. A source told CNN that restoring the network was "ongoing but not yet complete." CNN reported that sometime Tuesday evening, the employee line switched to "code green" and told staff to report as scheduled. CNN added, though, that it "was not immediately clear whether the outage was resolved." An NBC News analysis said the network "stopped working for several hours." The NSA hasn't said when the trouble started or ended, and it hasn't said exactly which patch or system failed.

Six outages in six days

Politico counted "6 major outages in 6 days." The run has included last week's Microsoft Outlook outage, Friday's FAA ground stop that The Record said was traced to a single router in Arkansas, Monday's Chase banking outage and United Airlines tech outage, and Tuesday morning's Apple outage. The Record said there is "no evidence that they are linked." According to a separate Politico report, lawmakers are calling for an investigation into the string of outages.

The agency that listens to the world couldn't count on its own internal network for part of Tuesday. We'll update this post if the NSA confirms what happened.