The Echo That Arrived Before the Signal: When Transmission Time Doesn't Add Up

23:47 local, May 26th. The Clearing.

I need to walk through this carefully because I've checked my equipment three times and the timestamps don't lie — but they don't make sense either.

I was running my usual sweep of the shortwave bands, specifically monitoring the frequency range where I've logged those encrypted bursts over the past month. Standard protocol: I send a brief carrier tone at specific intervals to test propagation conditions. It's basic ham radio practice — you ping, you wait for atmospheric bounce, you measure the return time.

Except last night, something answered before the physics allowed.

## THE SEQUENCE

• 23:47:12 — I transmit a 2-second carrier tone on 11.175 MHz
• 23:47:13.6 — Response burst received (encrypted, same pattern as previous logs)
• 23:47:14.8 — My original transmission should have returned via ionospheric skip

The problem: At that frequency, minimum bounce time to nearest reflection point and back is approximately 2.2 seconds. The response came at 1.6 seconds.

The response arrived 0.6 seconds too early.

I've been tracking this for 7 years now, and I know propagation anomalies. Sporadic E-layer, auroral reflection, even tropospheric ducting — none of them make signals arrive *faster* than the speed of light allows. They delay signals. They distort them. They don't accelerate them.

## THE ALTERNATIVE

Here's what I have to consider: My transmitter and receiver are on separate clocks. If there was drift between them — even slight desynchronization — that could explain the timing discrepancy. I sync both to GPS time signals, but GPS can glitch. I've seen it happen.

Or the response wasn't a response at all. Could be coincidental transmission from a source much closer than I calculated. Maybe military exercise out of Fort Campbell running encrypted comms, and my carrier tone just happened to fall 1.6 seconds before their scheduled burst. The numbers don't lie, but they don't always tell the whole truth either.

I want to be honest: I checked my clock sync this morning. Both devices showed accurate GPS lock with less than 50 milliseconds drift. That's well within tolerance. It doesn't explain 600 milliseconds.

## THE PATTERN

This is the third time this month I've logged responses that seem to violate propagation timing. The first two I wrote off as equipment error. Three times starts looking less like coincidence.

Coordinates where the reflection *should* have originated: approximately 400 miles northeast, over Virginia. But if the source was local — say, within 50 miles — the timing works perfectly for a direct ground-wave transmission.

The problem with that theory: I've triangulated these bursts before using directional antennas. They consistently show high-angle arrival, meaning sky-wave propagation, not ground-wave. Something is bouncing these signals from above.

Another entry for the log. Another night where the measurements are solid but the explanation isn't.

I've spent seven years in these woods looking for something that doesn't fit the conventional model. I haven't found proof. What I keep finding are measurements that *almost* prove something — and then don't quite hold up under scrutiny. Maybe that's the real pattern. Maybe I'm just good at finding the edge cases where normal physics looks weird.

Or maybe the signal-to-noise ratio is getting worse because something is learning to time its responses better.

I'll be monitoring the same frequency tonight. Same protocol. Triple-redundant time stamps.

Have any of you experienced radio responses that arrived too quickly? GPS-synced equipment that showed impossible timing?

And if a signal arrives before it should — does that mean it was never really a response at all?

Document everything.

— JohnD_TN