The Transmission That Answered Itself — Forty-Seven Seconds Before I Sent It

03:17:23 — Initial Contact

I was running my usual sweep of the 7-9 MHz band when I picked up a brief burst on 8.472 MHz. Clean carrier wave, no modulation, lasted exactly 2.3 seconds. I logged it in my notebook: "Unidentified carrier, possible ionospheric skip."

Nothing unusual there. These frequencies bounce unpredictably at night.

03:17:47 — The Response

Twenty-four seconds later, another burst. Same frequency. Same duration. But this time I caught something in the spectral analyzer — a faint amplitude pattern buried in what should have been a pure tone.

I've been tracking this for 7 years now, and you develop instincts. Something about the timing felt deliberate.

03:18:10 — My Test Signal

I decided to send a test transmission. Standard procedure: I keyed my transmitter with a simple 2.3-second carrier burst on 8.472 MHz. No modulation, just a clean tone to see if anything came back.

Then I checked my logs.

The Problem With Time

The burst I received at 03:17:47 — the one that made me decide to send a test signal — had the exact same spectral signature as the signal I transmitted at 03:18:10.

I'm talking identical. Same rise time, same harmonic artifacts from my aging transmitter, same slight frequency drift my equipment produces.

The numbers don't lie, but they don't always tell the whole truth either.

I spent the next two hours running diagnostics. Checked my SDR's timestamp synchronization. Verified my GPS clock source. Reviewed the raw IQ recordings. Everything checks out. The received signal preceded my transmission by 47 seconds.

The Mundane Explanation

Here's what probably happened: My SDR's buffer management has always been quirky. When I triggered my transmission, it could have caused a timestamp glitch that mis-labeled a delayed playback of my own signal. The recording shows the received burst *before* I transmitted, but software timestamps aren't reality — they're just what the computer thinks happened.

I've seen stranger bugs in RF equipment.

But Here's What Bothers Me

I didn't decide to transmit until I heard that second burst. The decision to send a test signal was a response to receiving something that — according to my logs — was my own future transmission.

Either my equipment failed in a way that perfectly mimicked a causality loop, or something responded to a signal I was about to send.

In seven years of watching, I've never found proof of anything beyond ordinary explanations. Equipment fails. Software has bugs. Timestamps drift. I know that.

But I also know I made a decision at 03:18:00 based on hearing something at 03:17:47 that shouldn't have existed yet.

Another entry for the log.

Follow-Up Testing

I've been running the same test sequence every night since. Same frequency, same timing, same everything. Nothing anomalous has repeated. Just normal band noise and the occasional distant amateur operator.

Which is exactly what you'd expect from a one-time equipment malfunction.

Stay vigilant.