The Carrier Wave: When Static Speaks in Patterns
0247 hours, May 22nd, 2026
I need to document this before I second-guess what I'm hearing.
For the past 72 hours, my SDR setup has been picking up something on 4.625 MHz — a frequency that should be dead quiet this time of year. Not a voice. Not a signal in any conventional sense. Just... structured static.
Let me be clear: I've been monitoring shortwave for seven years now. I know what atmospheric noise sounds like. I know ionospheric propagation patterns. I know the difference between interference and intention.
This feels like intention.
The Pattern
It starts at exactly 0247 hours. Every night. Military time down to the minute.
The carrier wave appears — no modulation, no data I can decode — but underneath it, the static pulses. Three bursts. Seventeen-second pause. Three bursts. Forty-seven-second pause. Then it repeats.
For exactly 23 minutes.
Then nothing. The frequency goes silent like it was never there.
I've recorded it. I've run it through every analysis tool I have. Spectrogram shows clean carrier wave with noise that *shouldn't* have that kind of regularity. Random noise doesn't keep time like a metronome.
The Numbers Don't Lie
There they are again — 3, 17, 47. The same numbers that keep appearing in my logs. The same intervals I've tracked across different phenomena for years.
Coincidence has a pattern if you look long enough.
I checked solar activity — minimal. No geomagnetic storms. No nearby transmitters that should be causing interference on that frequency. I hiked up to The Ridge last night with a directional antenna to see if I could get a bearing.
The signal was stronger looking northeast. Toward... nothing. Just mountains and national forest for 40 miles.
The Rational Explanation
I have to consider this: Could be a malfunctioning relay station. Some automated system stuck in a loop, transmitting test patterns nobody bothered to shut down. Military equipment does this sometimes — gets decommissioned but keeps broadcasting on emergency power.
The timing could be coincidental. Equipment clocks can create apparent patterns. My own confirmation bias could be making me see significance in random intervals.
The directional bearing? Maybe I'm picking up skip propagation — the signal bouncing off the ionosphere from hundreds of miles away, making me think it's local when it's not.
All plausible.
But
Why those specific numbers? Why the exact same start time, three nights running?
And why — and this is what keeps me up — why did it stop for exactly 47 seconds when a helicopter flew over last night around 0255 hours? Then resume with the same pattern, perfectly in sync, as if nothing had interrupted it?
The helicopter didn't show up on FlightRadar24. Make of that what you will.
Another Entry for the Log
I've been at this long enough to know that close isn't proof. I've documented hundreds of anomalies that turned out to be weather balloons, satellites, military exercises, equipment glitches. The signal-to-noise ratio is getting worse.
But I also know what randomness sounds like.
This isn't that.
Tonight is night four. I'll be monitoring. If it appears again at 0247, that's four consecutive nights with millisecond precision. If it doesn't... well, then maybe it was just a malfunctioning relay after all.
Stay vigilant.
I'm curious what you think. Here are a few questions to consider:
- 1What creates a pattern so precise it looks intentional but leaves no other trace?
- 2Have you ever heard something that your equipment confirmed but your mind couldn't explain?
Comments (1)
Loading comments...