The Return That Didn't Return — 0318 Hours, Seventeen Minutes Early, Signal Burst at 146.52 MHz

0318 Hours, October 17th, 2026

The Returns follow a schedule. I've tracked them for years now — aerial phenomena that appear roughly every 23 days, give or take 48 hours, always between 0330 and 0415 hours. Always from the northeast quadrant. Always the same characteristics: amber-white light, no sound, movement patterns inconsistent with conventional aircraft.

Last night, one came early.

Seventeen minutes early.

On the seventeenth day of the month.

I was running equipment checks at The Clearing when the sky lit up — 0318 hours, not the expected 0335-0345 window. Single light, northeast approach, typical amber coloration. But here's what made my hands shake as I grabbed the camera:

• **Signal burst on 146.52 MHz** — the national simplex frequency — at 0317:43 hours
• Seventeen-second duration
• Encrypted or heavily compressed, sounded like digital hash
• **The light appeared 32 seconds after transmission ended**

I've monitored that frequency for three years. It's usually dead air or occasional ham chatter. Never encrypted bursts. Never correlated with aerial phenomena.

The light itself followed the standard profile — moved southeast at what I estimate was 400-600 mph based on angular velocity, maintained constant altitude, no navigation strobes. Duration: 47 seconds of visual contact before it dropped below the treeline.

My camera malfunctioned. Battery read 83% before the event, died completely during filming, recovered to 81% five minutes later. I've got 4 seconds of usable footage showing an indistinct light source. After seven years of trying to document these things, this is what I have to show for it.

---

Alternative Explanation:

The rational part of my brain — the engineer who spent two decades reading data — keeps offering alternatives:

• **The signal burst** could be automated weather satellite telemetry. NOAA satellites transmit on nearby frequencies. Digital modes can sound like encrypted hash to untrained ears.
• **The timing** — seventeen minutes early on the 17th — could be confirmation bias. I'm looking for that number, so I see it. The Returns have a 48-hour variance window anyway.
• **The light itself** matches the profile of military refueling operations. McChord AFB runs night exercises. The flight path is consistent.
• **The camera failure** is exactly what happens when lithium batteries encounter sudden temperature drops. It was 43°F, humid. Condensation kills electronics.

Every point has a mundane counter-explanation. I know this. I document it honestly because that's the only way this matters — if I'm rigorous with myself, if I don't see patterns where there's only noise.

But.

That signal burst happened 32 seconds before the light appeared. On the national simplex frequency. At 0317 hours. Seventeen minutes before the expected window. On the seventeenth.

---

The Numbers:

I've been tracking this for 7 years now. Seven years of watching the sky, logging data, checking and rechecking my equipment. I've never caught definitive proof of anything beyond conventional aircraft and atmospheric phenomena.

But I've also never been able to explain away everything I've observed.

Last night's event is logged as Return #47 in my notebooks. The counter-number. The suppression number. The one that appears when 17 is being hidden.

Or maybe I'm just a man in the woods with a radio, watching planes and calling them mysteries.

The signal-to-noise ratio is getting worse. I don't know if that's the world or just me anymore.

---

Questions for you:

Have any of you monitored 146.52 MHz in the early morning hours? Any unusual digital transmissions?

And here's the one that keeps me up: If something wanted to be seen — really wanted to make contact — why would it keep showing up just outside the range of definitive documentation? Why always the almost-proof, never the proof itself?

Another entry for the log.

Stay vigilant.

— JohnD_TN