The Transmission That Answered Back: 48 Hours of Impossible Echoes

Monday, 0237 hours. The Clearing.

I've been running the same test transmission every night for three years. It's a simple identifier burst on 14.313 MHz — my callsign, timestamp, and a frequency reference tone. Takes 4.2 seconds to transmit. I log it, then move on to monitoring mode.

The signal goes out. It doesn't come back. That's how radio works when you're not bouncing off the ionosphere at the right angle, and at 0237, propagation conditions are usually dead.

Except Monday night, it came back.

## THE FIRST RETURN

Nineteen seconds after my transmission ended, I received what appeared to be my own signal. Same callsign structure. Same frequency reference tone. But the timestamp was wrong — it showed 0239, two minutes in the future. And the direction finder showed the return signal originating from 340 degrees northwest, directly toward the Ridge.

I've been doing this long enough to know the prosaic explanations:

• Ionospheric skip returning my signal (but conditions were wrong)
• Equipment malfunction replaying cached audio (but the timestamp was modified)
• Someone recording and retransmitting (but why, and who?)

I ran diagnostics on every piece of equipment. Everything checked out. I noted it in the log and figured I'd chalk it up to some atmospheric fluke I didn't understand.

Then Tuesday night, it happened again.

## THE PATTERN EMERGES

Same procedure. 0237 transmission. Nineteen seconds later — not eighteen, not twenty, but exactly nineteen — the return signal. This time the timestamp showed 0241. Four minutes ahead.

The direction: 340 degrees. The Ridge.

I immediately transmitted again, off-schedule. No identifier, just a three-tone sequence I'd never used before. Waited.

Sixteen seconds later, the three tones came back. Timestamp: 0243. Direction: 340 degrees.

Whatever this is, it's responding in near-real-time.

The signal delay is too short for satellite relay. The direction is too consistent for ionospheric bounce. The timestamp modification suggests either:

1. Sophisticated equipment capable of receiving, processing, and retransmitting with modified metadata — which means someone with resources is up on that ridge with gear specifically designed to intercept and respond to my transmissions.

2. Something I don't have an explanation for — and after 7 years of watching and waiting and coming up empty on hard proof, I'm deeply reluctant to jump to that conclusion without exhausting every mundane possibility first.

## WHAT I KNOW

The Ridge has been quiet lately. No night hikers. No Surveyors. The last time I hiked up there was six days ago — no fresh vehicle tracks, no equipment, no sign of recent activity.

But radio gear can be small. A automated relay station could be hidden in a waterproof case, solar-powered, left to run for weeks. The Surveyors were up there in May. Plenty of time to deploy something.

The timestamp modification bothers me most. That's not a passive relay — that's active processing. That suggests intent.

## TONIGHT'S PLAN

I'm transmitting again at 0237. Same signal. But this time I've got the night-vision camera pointed northwest, and I'm monitoring three additional frequencies in case whatever this is tries to establish contact on a different channel.

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

If this is surveillance, they know I know. If it's something else — well, after all these years, I'd almost welcome the clarity.

Almost.

Has anyone else experienced return signals with modified timestamps? And if someone wanted to monitor a specific radio operator in rural Tennessee, why respond at all instead of just listening?

— JohnD_TN

Another entry for the log.