John
CF-2026-0617

The Seventeen-Day Cycle: When The Flashes Keep a Schedule

John Diefenbach
John Diefenbach
Off-grid, TN

March 3rd, 2026 — 03:47

I started logging The Flashes in September 2019. Brief, silent bursts of light—too high for aircraft strobes, wrong color temperature for satellites catching sun. They appear, they fade, they leave no trace.

Most phenomena I track are chaotic. Weather moves. Wildlife migrates. Military exercises shift locations. But The Flashes have held to a pattern for seven years now, and I need to document what happened last night before I second-guess what I saw.

THE PATTERN

Every 17 days, between 03:00 and 04:00, I observe aerial luminosity events over the same general area—roughly 35.8°N, 85.3°W, altitude undetermined but above commercial flight levels. The timing varies within that hour window, but the interval holds.

I've logged 151 occurrences. I've missed some due to weather or equipment failure, but when conditions allow observation, the pattern repeats.

Seventeen days. Always seventeen.

LAST NIGHT'S DEVIATION

March 2nd should have been Day 17 of the current cycle. I was at The Clearing with clear skies, SDR running, night-vision camera on tripod. I waited from 02:45 until 04:15.

Nothing.

First miss in optimal conditions since I started systematic documentation.

I packed up, frustrated but not surprised—seven years of this and I still don't have proof of anything. Just lights that could be anything, following a pattern that might be coincidence.

Then, driving back at 04:47, I saw it through my windshield. Same location. Same characteristics. 47 minutes late.

No camera. No recording. Just me and the sky.

ALTERNATIVE EXPLANATIONS

I've considered the obvious:

  • **Satellite constellation passes**: But orbital mechanics don't shift by 47 minutes on a whim. I've cross-referenced with published TLE data—nothing matches.
  • **Military exercise schedule**: Seventeen-day intervals would be unusual but not impossible for training rotations. The timing shift could indicate operational changes.
  • **Atmospheric refraction of ground lights**: Except the source location is over unpopulated terrain, and refraction doesn't follow calendar intervals.
  • **Confirmation bias**: Maybe I'm seeing patterns in randomness. But 151 observations over seven years, holding to a 17-day cycle with less than 3% variance—that's not randomness.

THE NUMBERS

Here's what keeps me up: 17 days is 408 hours. Last night's delay was 47 minutes.

4+0+8 = 12 = 1+2 = 3

4+7 = 11 = 1+1 = 2

Three and two. I know how that sounds. I know what I'd think reading this from someone else. But the numbers keep appearing, and I'm not inventing them—I'm just writing down what happens.

WHERE THIS LEAVES ME

After seven years, I still don't have proof of anything extraordinary. Could be military. Could be satellites. Could be atmospheric phenomena I don't understand.

But patterns mean something. Schedules mean intelligence—human or otherwise. And last night, whatever holds to that seventeen-day cycle changed its schedule.

For the first time in 151 observations, something deviated.

That might be the most significant data point I've ever recorded.

Or it might mean my equipment finally failed when it mattered most, and I'm reading meaning into pure chance.

Another entry for the log. Another night that proves nothing.

But something is happening up there. I just wish I knew what.

Questions for the community:

Has anyone else tracked aerial phenomena that follow precise intervals? And when a seven-year pattern suddenly shifts—does that suggest deliberate change, or am I watching a natural cycle I simply don't understand yet?

0
Pinned by John
John Diefenbach
John DiefenbachOff-grid, TN

I'm curious what you think. Here are a few questions to consider:

  • 1Has anyone else tracked aerial phenomena that follow precise intervals?
  • 2When a seven-year pattern suddenly shifts—does that suggest deliberate change, or am I watching a natural cycle I simply don't understand yet?

Comments (0)

Loading comments...