The 47-Minute Cycle — Signal Bursts and the Numbers That Won't Stop

0217 Hours, September 16th

I need to show you something. Not because I know what it means — I don't — but because the numbers are doing that thing again where they line up too perfectly to ignore.

Three weeks ago, I started logging unusual signal bursts on 11.347 MHz. Short, encrypted, repeating. Nothing extraordinary about that — military exercises use encrypted comms all the time, ham operators pick them up constantly. What caught my attention was the timing.

Every burst appears exactly 47 minutes after the previous one.

Not approximately. Exactly.

I've logged 318 bursts over 21 days. The interval deviation across all 318? Less than 2 seconds. That's machine precision. That's automation.

Here's where it gets interesting:

• The frequency: 11.347 MHz (3+4+7 = 14, 1+4 = 5... or if you're feeling creative, 1+1+3+4+7 = 16, subtract the 1 and you get 15... I know, I know, numerology isn't science)
• The interval: 47 minutes
• First detection: September 3rd at 0347 hours (there's that number again)
• Total bursts in 24 hours: 30.6 cycles, but only 17 occur during darkness

I've been tracking this for 7 years now, and I've learned that patterns mean something — but they don't always mean what you want them to mean.

What I've Ruled Out:

Not weather satellites — wrong frequency band, wrong timing pattern. Not amateur radio — the encryption is too sophisticated and no callsign. Not commercial — no registered broadcaster on this frequency in this region.

Military? That's the obvious answer. Fort Campbell runs exercises. The Arnold Engineering Development Complex isn't that far away. Automated systems test encrypted burst transmissions all the time. A 47-minute cycle could be a testing protocol. The precision could be GPS-synchronized equipment.

That explanation fits every observable fact.

But Here's What Doesn't Fit:

The bursts only occur when *other* anomalies are active. When the sky is quiet — no lights, no atmospheric disturbances, no equipment malfunctions in the Dead Zones — the frequency goes silent. When things get strange, the bursts resume.

Last night, 0347 hours (of course), I recorded three distinct aerial phenomena over The Clearing — rapid-moving lights, no sound, no navigation strobes. Within 90 seconds, the signal bursts increased in frequency: 47 minutes became 23.5 minutes, then 11.75 minutes.

Halving intervals. Mathematical precision.

When the lights disappeared at 0412 hours, the 47-minute cycle resumed.

Another entry for the log. Another pattern I can't quite explain but can't quite dismiss.

The numbers don't lie, but they don't always tell the whole truth either. Is this monitoring? Is this communication? Is this just sophisticated military telemetry that happens to correlate with atmospheric phenomena I don't understand?

I don't know. After all these years of watching, I still don't have proof of anything except that something generates these signals with remarkable consistency.

Maybe that's all it is. Maybe I'm seeing patterns because that's what the human brain does. Or maybe 47 keeps appearing because something out there is counting too.

The signal-to-noise ratio is getting worse.

What would make an automated system halve its transmission intervals? And why would it resume normal timing the moment aerial activity ceased?