Réveil

Things start out as “just a conspiracy” until suddenly it's just reality. The truth was always kept out of view. Don’t close your mind, open it.

I moderate the Reddit community r/UFOs, one of the largest online UFO communities It produces a constant stream of sighting reports. That stream is the best and worst thing about the subreddit. On a good night someone uploads clear footage of something that resists explanation, three other people in the same county chime in, and you remember why you volunteered for this. On a normal night it is a blurry dot filmed through a window screen, titled “WHAT IS THIS ORB??”, posted by someone who has never heard of Starlink.

A few months ago we ran a thread asking the community how to improve the sub. One comment stuck with me:

A lot of the sighting posts here are easily explainable as balloons, clouds, out-of-focus drones and aircraft, or Venus/Jupiter. It does get old after a while. I don't know what the solution is, maybe require sighting posts to include why they're not those things somehow.

That comment became a spec. The result is ufosighting.report, a permanent, searchable, media-backed archive of the community's sightings, plus a submission pipeline designed to raise the floor on report quality. This post is the longer story behind it: what it does, what the data revealed once I could see it in aggregate, and some notes on how it is built.

The quiet problem: sightings rot

Before the quality problem, there is a preservation problem that most people never notice.

Reddit is a terrible archive. Users delete their accounts and take their posts with them. Posts get removed. And even threads that survive slowly decay, because Reddit re-encodes uploaded media aggressively and old media links eventually stop resolving. Some of the most interesting sighting reports from even two years ago are now text skeletons with dead video embeds. If any of this material ever turns out to matter, it will matter as a body of evidence, and bodies of evidence should not depend on whether a stranger keeps their Reddit account.

So the first job of the site is boring and important: every post flaired “Sighting” on r/UFOs is ingested automatically, media and all. The video files, the images, the top comments, the original text. Around 8,000 sightings going back to early 2024 are already in, and new ones arrive within minutes of being posted. If the author later deletes their post, the archive keeps it, clearly labeled with what happened to the original. Reports that our own mod team removed for breaking the rules stay stored but out of the public archive; spam does not become history just by getting old.

Turning prose into pins

A Reddit sighting post is unstructured prose. “Saw this over the lake near my house around 9 last night” is a location and a time to a human and neither to a database.

The pipeline runs every incoming post (title, body, and the author's follow-up comments, because the useful details are always in a comment) through an LLM extraction step that pulls out the date, time, timezone, and location when they are actually stated, then geocodes the location to coordinates. I deliberately do not let it guess object shape, size, or behavior; free text is too easy to over-read, and hallucinated structure is worse than none. Dates and places it cannot corroborate stay blank.

About four in five archived sightings ended up with usable coordinates. That is what makes the map possible: nearly seven thousand pins, filterable by date. Set the date range to mid-November through late December 2024 and watch the New Jersey drone flap bloom across the East Coast. It is one thing to remember that period as a news cycle and another to see it as a point cloud.

What the data says once you can actually query it

Here is where it got fun. Once thousands of reports are structured, you can ask questions that are impossible to ask of a subreddit.

The hotspot map you expect is a population map. Every raw heatmap of UFO sightings lights up over big cities, because that is where the people are. Texas ranks second in raw sighting counts. Adjust for population and Texas falls to 35th. California drops from first to 15th. The map has a per-capita mode that normalizes each area against its local population, and when you flip it on, the glow migrates away from the metros and settles over the desert Southwest: Arizona, Nevada, New Mexico, plus a hot stripe of coastal New Jersey from the drone flap. Phoenix Lights country, Area 51 country, Roswell country. I make no claims about why. Reporting culture, dark skies, military airspace, and folklore all plausibly feed it. But the pattern is real and it is not where the people are.

Military bases are nearby more often than chance suggests. In the highest-anomaly states, 56 percent of sightings fall within 50 kilometers of a military installation, against 43 percent elsewhere. Bases sit on exactly the kind of open land that produces good sky views, so treat that gap gently. It is still an interesting gap.

A lot of UFOs have prosaic flight plans. For every mapped sighting with a time and place, the site computes what was actually overhead using orbital data: ISS passes, Starlink trains, bright satellites, and rocket launches. Of the sightings checked so far, roughly one in five coincided with a Starlink train visible from that location at that time. Two hundred and eighteen lined up with an ISS pass. Sixty-two happened within hours and a few hundred kilometers of a rocket launch, and a twilight rocket plume is responsible for more panicked video than almost anything else in the sky. Each sighting page shows this context automatically, along with links to historical aircraft traffic for that day and a sky chart for that exact spot and hour. The point is not to debunk anyone. The point is that “what else was up there” should be one click, not one research project.

Raising the floor on new reports

The other half of the site is the submission wizard, which is my answer to that comment from the feedback thread.

Posting a sighting through it requires actually describing the event: where, when, shape, movement, duration, distance, the “five observables” questions, and, centrally, a mandatory field asking why this is not a common object. You have to write down what you ruled out before the community sees it. It is friction, on purpose. Low-effort reports are cheap to produce and expensive for everyone else to wade through, and a little typing rebalances that.

Then there is the media handling, which I think is the strongest technical argument for the site:

  • Originals are preserved untouched. Reddit re-encodes everything you upload. The site keeps the exact file, byte for byte. Upload from an iPhone and the original HEIC goes into storage, not a recompressed JPEG.
  • Metadata becomes evidence, with consent. On upload, the site reads the file's EXIF: camera model, lens, exposure, capture time, GPS, even the compass heading you were facing. For a sighting, that heading is gold; it lets anyone reconstruct your exact view of the sky and check it against satellite and aircraft positions. You see everything the file contains before publishing, with checkboxes to withhold device details, timestamp, or location.
  • Withheld means scrubbed, not hidden. If you choose not to share GPS, the coordinates are stripped from the published file itself. Privacy that depends on nobody checking is not privacy.

Finally, submissions are tied to Reddit identity. After you submit, a bot DMs you a verification link, and only after you confirm does the sighting go live and post to r/UFOs under your username, marked verified. Anonymous drive-by noise gets expensive; standing behind your report gets easy.

What is next

The shape and object data on new submissions will compound over time into something genuinely queryable, and I would like the community to help enrich the older records the same way a wiki fills in gaps. More viewing angles on the data are coming. And if you have ideas, the whole point of building this for a community is that the community gets a say.

Browse the archive at ufosighting.report, explore the map, and if you see something in the sky you cannot explain, put it on the record. Properly, this time. With the metadata.

On January 20, 1996, three young women (Liliane, Valquíria, and Kátia) claimed to have encountered a strange creature on a vacant lot in Jardim Andere, a neighbourhood in the small Brazilian city of Varginha, Minas Gerais. What followed became one of the most controversial UFO cases in history: allegations of military capture operations, hospital cover-ups, a soldier's mysterious death, and a formal military inquiry that generated thousands of pages of documentation.

I recently obtained and translated 13 declassified Brazilian military documents, totaling over a million characters of Portuguese text, that were released to Brazil's National Archives. These include the complete Military Police Inquiry (IPM No. 18/97), the Brazilian government's formal response to Congress about UFO documentation, Air Force sighting questionnaires, and a 1971 military intelligence report that places UFO activity over Varginha a full 25 years before the famous incident.

Here's what they contain.

Read more...

In January 1996, something happened in Varginha, Brazil, that has never been adequately explained. Depending on whom you ask, the events of that month represent either the most significant extraterrestrial contact event since Roswell, or a spectacular case of mass misidentification fueled by media frenzy and UFO enthusiasm.

What is not in dispute is that dozens of unconnected witnesses across a small Brazilian coffee city reported seeing things they could not explain, that the military mobilized in ways that went far beyond routine, and that a young police officer who was allegedly involved in the events died under circumstances that remain deeply suspicious nearly thirty years later.

The “alien being” seen by three girls, just days after the alleged crash

This post is an attempt to lay out every well known detail of the Varginha incident, chronologically and comprehensively, drawing from the original Brazilian investigations, international research, documentary work, and the most recent testimony that emerged in January 2026 at the National Press Club in Washington, D.C. Where accounts conflict, both versions are presented. Where evidence is lacking, that is noted plainly. The goal is not to convince anyone of anything. The goal is to put every piece of this puzzle in one place and let the reader decide what to make of it.

Read more...

Searchable Project Blue Book archive (BlueBookFiles.org)

“The UFO phenomenon exists. It has been with us throughout history.” — Dr. J. Allen Hynek

If you’ve ever tried to dig into Project Blue Book case files, you know the pain: thousands of scans, inconsistent filenames, and lots of “where do I even start?” energy.

So I built a thing to make it easier to explore:

https://bluebookfiles.org/

It’s still very much a work in progress (and yes, there are bugs), but it’s already the easiest way I’ve found to actually research Blue Book cases without getting lost in a maze of PDFs.

What was Project Blue Book?

Project Blue Book was the U.S. Air Force’s official UFO investigation program, active from 1952 to 1969.

In simple terms: reports would come in from the public, pilots, police, radar operators, military personnel, etc., and Blue Book investigators would try to determine what happened. A lot of cases ended up as mundane explanations (aircraft, balloons, Venus, temperature inversions… the usual suspects). Some were chalked up to “insufficient information.” And a small number remained “unidentified.”

Blue Book is often remembered as a debunking effort, and honestly, that’s not wrong. It was largely designed to reduce public anxiety and close out cases with conventional explanations whenever possible.

But one of the most interesting parts of the story is the investigator who became synonymous with the entire program: Dr. J. Allen Hynek.

Hynek started out as a skeptic—brought in as a scientific consultant in part to help explain sightings away. Over time, after years of reviewing cases (including ones that didn’t fit neatly into simple explanations), his position evolved. By the end of his involvement with the subject, he became one of the strongest voices arguing that the UFO phenomenon deserved serious, scientific attention.

Why this site exists

The Blue Book records are already public and available online via the National Archives (and mirrored on sites like Fold3, Archive.org, etc.). But the problem I kept running into is that browsing and searching those sites feels slow and clunky—especially if you’re trying to search across the whole collection, follow patterns, or jump between related reports.

I wanted one place where I could search across the documents like a normal person.

So I built an archive that includes most of the Project 10073 Record Cards (the one-page “summary sheets” investigators filled out for each report), plus some other related Blue Book / UFO documents.

If you’ve never seen the cards: they usually include the date, location, witness info, what was reported, and the official explanation or conclusion. The usual stuff shows up a lot: Venus, aircraft, balloons… and of course, swamp gas 😅

What you can do on BlueBookFiles.org

Full-text search across ~6,000 documents

I ran roughly 6,000 reports through OCR so you can search the actual content (locations, dates, descriptions, weird phrases, whatever). Some scans are rough, so OCR quality varies—and the worst ones will be imperfect.

“Forgiving” search (not strict keyword-only)

Search is designed to be flexible: typo tolerance, partial matching, relevance ranking. For example, searching disk will also pull disc, and a bunch of misspellings still get picked up.

You can also search exact phrases using quotes, like:

  • "swamp gas"

Selectable / copyable document text

Where OCR succeeds, the text is selectable so you can copy snippets, cite something quickly, or just download the full OCR’d PDF.

Interactive map view (my favorite part)

There’s a geocoded map view for each report here:

https://bluebookfiles.org/?view=map

Read more...

Introduction

In my previous post “Was Flight MH370 Teleported?”, I broke down two viral videos that appear to show MH370 being surrounded by glowing orbs before vanishing in a flash of light. Whether you believe those videos are real or fake, one thing is clear: they sparked renewed interest in alternative theories about what happened to Flight 370.

But here’s the thing: whether those videos are real or not, there should be physical evidence. An event violent enough to make a Boeing 777 disappear or crash would almost certainly generate acoustic signatures detectable by underwater sensors.

The Comprehensive Nuclear-Test-Ban Treaty Organization (CTBTO) operates a network of highly sensitive underwater hydrophones throughout the world's oceans. These hydrophones are designed to detect nuclear explosions, but they can also pick up aircraft impacts, underwater explosions, and other violent events.

So what did those hydrophones record on March 8, 2014?

The answer is complicated. They recorded something. But more importantly, they recorded nothing during a critical 25-minute window at the station closest to Diego Garcia.

The Players: CTBTO Hydrophone Stations

CTBTO Stations

The CTBTO operates hydroacoustic monitoring stations throughout the Indian Ocean. Three are particularly relevant to MH370:

Station Location Code
HA01 Cape Leeuwin, Western Australia H01W
HA08 Diego Garcia, British Indian Ocean Territory H08S/H08N
HA04 Crozet Islands, France H04S

Each station consists of three hydrophones arranged in a triangular configuration, allowing researchers to determine both the bearing and approximate distance of acoustic events.

Diego Garcia is the location of HA08. It is also a remote coral atoll hosting a major U.S. military installation, Naval Support Facility Diego Garcia, which is shrouded in secrecy. The island has a 12,000-foot runway capable of handling any aircraft in the world.

Remember from Part 1: the coordinates embedded in the “satellite” video are approximately -8.834301, 93.19492, which places the supposed event south of the Nicobar Islands. Diego Garcia sits at approximately 7.3°S, 72.4°E. The distance between these two points is roughly 2,300 km.

Anomaly #1: The 25-Minute Data Gap

What Happened

At 03:07 UTC on March 8, 2014, all three hydrophones at the Diego Garcia station (HA08s) simultaneously stopped recording. They remained offline for exactly 25 minutes.

Figure 5 from Kadri 2019

This is documented in a peer-reviewed paper by Dr. Usama Kadri of Cardiff University, published in Scientific Reports (Nature):

“A fifth signal appears at 3:07... This signal probably indicates restarting the system after it was shutdown for 25 minutes, i.e. there is missing data in these specific CTBTO recordings.”

Kadri, U. (2019). Effect of sea-bottom elasticity on the propagation of acoustic-gravity waves from impacting objects. Scientific Reports, 9, 912.

Why This Matters

Dr. Kadri explicitly addresses the suspicious nature of this gap:

“Due to the sensitivity of the recorded data, it is unlikely that the three hydrophones on HA08s had a simultaneous technical failure and the reason behind the shut down is to-date unknown.”

He then offers a possible explanation:

“A violent nearby activity (including impact, explosion) could have resulted in a shutdown of the system.”

Let that sink in. A scientist publishing in one of the world's most prestigious journals is stating on the record that:

  1. A simultaneous failure of all three hydrophones is “unlikely”
  2. The shutdown remains “unexplained” by the CTBTO
  3. A violent nearby event, such as an aircraft impact or explosion, could cause such a shutdown

The Timeline and the Videos

The official narrative states that MH370’s final satellite communication occurred at 00:19 UTC on March 8, 2014. According to the mainstream account, the aircraft is believed to have crashed when it ran out of fuel over the southern Indian Ocean after turning and flying south.

Here is where it gets interesting. If the mainstream narrative is wrong and, instead of turning south, MH370 continued from its final reported coordinates toward Diego Garcia, then plotting its trajectory using the coordinates from the video (-8.834301, 93.19492) places the aircraft in that area sometime between 00:30 and 01:30 UTC. At a distance of about 2,100 km, the primary acoustic signal would reach Diego Garcia after roughly 10–25 minutes, depending on the propagation path: faster along the sea floor at about 3,350 m/s and slower through the water column at about 1,500 m/s. This means any acoustic signature from the event would have been recorded by Diego Garcia’s hydrophones sometime between 01:10 and 01:55 UTC, well before the 03:07 data gap.

Time (UTC) Event
18:22, March 7 Last radar contact with MH370
00:19, March 8 Final satellite handshake (Final satellite handshake (crash estimated shortly after))
~00:30-01:30, March 8 Estimated time at video coordinates (if direct flight from last radar)
01:58, March 8 Signal HA_32 detected at Diego Garcia (military bearing)
03:07, March 8 All three Diego Garcia hydrophones go offline
03:32, March 8 System comes back online
03:47-03:55, March 8 Three signals detected at nearly identical bearings (~170°)

So what happened at 03:07? If the acoustic signal had already arrived and been recorded around 01:30-02:00 UTC, the data gap doesn't represent missing evidence – it represents evidence that may have been deleted. You don't preemptively shut down a recording system before incriminating data arrives. You shut it down after you realize what's been captured. The 25-minute window – just enough time to review and scrub recordings – looks less like a technical failure and more like a cleanup operation.

The data gap starts at 03:07 UTC. Right in the middle of that window.

Coincidence?

Read more...

In July 2023, an anonymous Reddit post quietly appeared on the /r/aliens subreddit. Although that user deleted the post, it’s been archived on archive.org here

It claims to be a confession from a former government–adjacent molecular biologist. The author said they had spent years dissecting and characterizing the bodies of “Exo-Biospheric-Organisms” (EBOs) in a secret lab buried under Fort Detrick, Maryland.

Within hours the post was removed and the account vanished, which only made the story spread faster.

Copies of the text were archived and reposted across the web, from mirrors to UFO blogs and forums.

The result is one of the most elaborate “alien biology” narratives to hit the internet in years: part lab notebook, part theology, part science-fiction.

This article breaks down what the EBO leaker actually claimed, how it fits with real-world biology and facilities, why it grabbed so many people, and how plausible any of it really is.

Where the Story Came From

The original post appeared on /r/aliens in early July 2023 and was titled:

“From the late 2000s to the mid-2010s, I worked as a molecular biologist for a national security contractor in a program to study Exo-Biospheric-Organisms (EBO).”

The account:

  • Claimed to be a PhD-level molecular biologist
  • Described working for a “national security contractor”
  • Said the work was done in a restricted lab space at Fort Detrick, Maryland
  • Identified the operator as Battelle National Biodefense Institute (BNBI)

BNBI is a real organization. It manages the National Biodefense Analysis and Countermeasures Center (NBACC) at Fort Detrick for the U.S. Department of Homeland Security. NBACC is a high-containment biodefense facility built in the mid-2000s to study biological threats and forensic analysis of biocrimes.

So at minimum, the leaker anchored their story to a real, high-security lab with a plausible mandate for weird biology.

The author framed the post as a one-way leak: they explicitly said they would not testify to the Senate or talk to AARO, and that they possessed no evidence beyond the text itself. They described this as a compromise between their moral urge to “tell humanity” and their desire not to get themselves or their family into danger.

Who the Leaker Claims to Be

The author’s self-portrait is deliberately fuzzy:

  • PhD in molecular biology
  • Recruited informally at a scientific conference after chatting with a senior scientist
  • Put through several increasingly “suspicious” interviews where scientific expertise became less relevant
  • Required to sign a very detailed NDA, explained in person by a lawyer-type

Once hired, they say their first weeks were spent in a basement archive room at Fort Detrick, reading internal reports, memos, SOPs and briefings on EBOs: their biology, diet, religion, culture, and so on.

The scientific structure they describe is familiar to anyone who’s seen a large biomedical program:

  • ~20 PhD-level scientists doing hands-on lab work
  • 4 senior scientists who design assays and supervise
  • 1 director who sets priorities and is rarely on site
  • Security guards from contractors
  • No janitors or support staff; scientists do their own cleaning and maintenance

Internet access is restricted to senior staff, with an internal intranet for bioinformatics.

So far, nothing exotic: the weird part is what they say they were studying.

Inside the Alleged EBO Program

The stated goal of the program is to characterize the genome and proteome of EBOs: to decode their DNA and catalog the proteins they make.

According to the post:

  • The lab runs at BSL-3 for anything involving EBO samples or cell culture, with a connected BSL-2 area for most assays and normal cell lines.
  • The BSL-3 section includes a freezer room and a dedicated EBO cell culture space.
  • Four incomplete EBO bodies are stored in horizontal freezers at –80 °C, vacuum-bagged in a humidity-controlled environment. All show major traumatic injuries.

The author says they never saw live EBOs, only carcasses and derived cell lines.

One of the key tools is an EBO epithelial cell line called EPI-G11, allegedly developed by another team. This line supposedly:

  • Can be transfected with EBO genes via a gene gun (other methods kill it or fail)
  • Enters exponential growth in response to fetal bovine serum, like many eukaryotic cell lines
  • Is used as a platform to overexpress and purify EBO proteins for analysis

So the story is framed much like a very niche, very classified biotech program: nothing magical, just everyday molecular biology applied to something extraordinary.

Read more...

This is a deep dive into the anonymous claims that captivated the UFO community in 2023'

In April 2023, an anonymous poster appeared on 4chan's /x/ board with a simple opening line:

“I have intimate knowledge of what the US currently knows about UFOs minus the last two years.”

He claimed to be a former insider with access to UFO crash recoveries and classified programs, now undergoing chemotherapy for liver cancer. Facing the possibility of not having much time left, he chose the most chaotic confession booth imaginable: a 4chan thread.

Over the course of two lengthy sessions spanning nearly two weeks, this individual answered hundreds of questions with an unusual level of consistency and detail that set their posts apart from the typical “LARP” (Live Action Role Play) that plagues anonymous forums.

Whether genuine insider or elaborate fiction, these threads offer one of the most comprehensive, internally consistent accounts of alleged government UFO knowledge ever posted online. They have already become a notable node in modern UFO lore.

This is their story.

The Start

The first post arrived on April 24, 2023, with five core claims that would frame everything that followed:

  1. UFOs are primarily unmanned drones

  2. UFOs are built to specification each time they are deployed

  3. UFOs are created by a mobile construction facility hiding in the ocean

  4. This construction facility destroys anything that approaches it

  5. The U.S. believes this facility has been active on Earth for at least 100 years, possibly much longer

These claims immediately distinguished the poster from typical UFO narratives. No talk of crashed saucers from Zeta Reticuli, no galactic federations, no channeled messages from Ashtar Command. Instead, the picture that emerged was almost industrial: a manufacturing operation, hidden beneath the waves, churning out specialized drones for specific missions before recycling them back into raw materials.

“Atlantis”: The Underwater UFO Factory

Perhaps the most striking element of the whistleblower's account is the construction facility itself, jokingly dubbed “Atlantis” by older team members. When asked what it looked like, the poster provided surprising detail.

Q: What does it look like?

A: Shaped like an extremely large UFO but more of a “burger” design. Almost never leaves the Atlantic Ocean, in fact it will sit through hurricanes. No visible weapons or “cockpit” from sat footage. It also does not use any lights. The main construction facility does not rust or deteriorate from what we can tell.

The method of tracking this facility raised eyebrows:

Q: How do you track it?

A: We rely mostly on detecting the gravity it produces. It normally doesn't produce heat outright. When it does we believe it's in the process of construction since a small heat buildup can be detected when a craft returns or exits.

But the most chilling detail concerned what happens when humans get too close to the underwater “UFO Factory”

Q: What happens when you approach it?

A: The last unit we saw approach the facility didn't even have time to communicate they were being attacked before it was over. At one point we deployed fighters and a sub with serious intent. Everything except the sub was lost. This weapon destroys the matter it hits entirely. It also shits on anything electronic in the vicinity.

When craft return to this facility, heat signatures suggest they're smelted back down into component parts. This recycling operation explains why so few intact craft are ever recovered:

Q: Do the UAPs return to the manufacturing unit?

A: Yes, some come in and leave the planet but very rarely. Based on heat signatures likely smelted back down into parts. It feels more like a carrier but with construction capability.

The poster also suspects this may not be the only facility. With increasing attention on polar regions, he believes other units might exist, including one in the Arctic.

The Craft Themselves

The whistleblower's description of the craft challenges some popular UFO imagery while confirming others.

On shapes:

Q: What shapes have you seen?

A: Things like triangles and hard-edged squares don't exist. Pill shapes are extremely sought after, some we think are “freighters.” Cigar shaped are very rare, we were told finding one would be career changing.

The materials presented unique challenges:

Q: What are they made of?

A: An alloy that we cannot reproduce but only repurpose. This alloy is kind of like a “film” that fits over the frame of the craft. One of the main problems when repurposing these alloys is getting them hot enough. They absorb heat very well.

On the power source, the poster confirmed a name familiar to anyone who has followed UFO lore:

Q: What powers them?

A: The power source is E115. It produces its own gravity field. Bob Lazar handled E115 which was already pulled out which is rare and weird. Protocol now is that only one person is allowed to handle E115. We still have trouble producing this shit too.

When someone pointed out that Element 115 decays in milliseconds under lab conditions, the response was blunt:

Q: Element 115 nuclei lasts for milliseconds before disintegrating under lab conditions.

A: Correct. Still a massive problem.

The interiors matched what you might expect from craft not designed for human proportions:

Q: What does the interior look like?

A: Always cramped and hard to stand fully upright in. For reference I'm 5'8. There is almost never a storage facility unless dedicated to something for the craft. Tools are not freely placed around and have dedicated placement.

On stealth capabilities:

Q: Do they have stealth capabilities?

A: Maybe 1 in 20 has stealth technology. These crafts are so rare we actually almost never see them crash because we can't track them.

Read more...

Many have seen the footage. Far fewer know its tangled backstory.

Is it an early‑2000s hoax or a genuine recording of an unknown craft? The video, also referred to as the Pordenone UFO, has a surprisingly intricate timeline and a long trail of debate behind it.

The video first attracted international attention in 2005, when Italian-American researcher Paola Harris presented a fourth-generation copy at the 36th Annual MUFON International Symposium in Denver, Colorado. Harris, who was then living in Italy, stated that the footage had been supplied by an anonymous source who associated it with the Aviano area. The identity of the original cameraman has never been established, and the severe degradation caused by repeated copying has made detailed analysis difficult.

The video:

How the Aviano UFO Video Emerged

The story begins with an anonymous VHS tape.

The footage was allegedly recorded in 2003 near the NATO air base in Aviano, Italy. In 2004, a VHS copy of the video was sent anonymously to the well‑known Italian ufologist Antonio Chiumiento, accompanied by a brief but ominous message:

“Ho paura” (“I am afraid,” in Italian).

The tape was subsequently sent to other Italian ufologists in the following months.

Despite receiving the material in 2004, Chiumiento chose to keep the video confidential at first, allowing time for further analysis. The footage only became public in 2005.

That year, Italian‑American journalist and ufologist Paola Harris presented the video at two major events:

  • The 36th MUFON Symposium, in July 2005, in Denver, Colorado
  • The International UFO Congress, in Laughlin, Nevada

The versions that later circulated on YouTube were largely derived from a DVD of her MUFON presentation.

Read more...

The first encounter was early on the morning of January 23, 1981, photographer Carlos Díaz was parked on a ridge in Ajusco, just outside Mexico City.

The air was cold and thin, and mist rolled slowly over the trees below. He was waiting to meet a journalist for a story he’d been hired to shoot, his camera gear laid out on the passenger seat.

Then suddenly, he sees a bright light spread across the valley.

At first he thought it was a fire. Then the light began to move, swelling and flickering like molten metal. That was the moment his life took a very strange turn.

Díaz quickly reached for his camera and began capturing the series of photos that would later make him famous.

The object seemed to rise out of the valley and drift closer, glowing in a deep amber color that lit up the trees around him. He said the car began to shake. When he stepped outside, the object hovered for a few seconds before shooting straight up and disappearing.

Read more...

In May 2008, a short, 20 second low-resolution video surfaced on YouTube showing what appeared to be a disc-shaped object flying beside what is speculated to be a jet.

One of the earliest mentions of the “Flyby” footage seems to come from the UFO Chronicles website, where it appeared under the title “Flying Saucer UFO filmed from jet window.” The uploader, a user named Danny Lampkin, added only a short note: “not too sure about this one… you decide.”

Although, the actual earliest YouTube upload I could locate (though there may be older ones) comes from a user named frossani, who captioned it: “It’s a Blue Panorama flight from Rome to Paris on April 29, 2006.”

Interestingly, the version uploaded by frossani appears to be slightly higher in quality, suggesting that it may have been the original source for Danny Lampkin’s later post about two months afterward.

Watch the video:

At first glance, it looks like something from the early YouTube hoax era. The quality is awful, the reflections are odd, and the footage feels almost too dramatic to be real. Yet the deeper people have looked into it, the harder it has been to dismiss.

Below is a breakdown of what makes this case so persistent after more than fifteen years.

Original videos:

Uploaded March 5, 2008: frossani channel Uploaded May 14, 2008: Danny Lampkin channel

What’s in the Clip

The Flyby video runs just under twenty seconds. It is extremely low resolution, typical for uploads in 2008, and filled with heavy compression artifacts. There are visible reflections across the frame, which has led many to believe this is not the original footage but a recording of a screen playing the original. That would explain the odd glare and crushed image quality, although that remains a theory rather than confirmed fact.

Read more...

Enter your email to subscribe to updates.