The Helicopter That Circles But Never Lands: Three Nights of Precision Routes

Night 1: December 8th, 2026 — 02:17 local time

I was out at The Clearing running a routine sky watch when I heard it. Low rotor thump, distinctive twin-engine sound. Civilian helicopter, but the flight pattern was... methodical.

I tracked it visually for 23 minutes. No navigation lights — just a dim anti-collision strobe every 4 seconds. It ran a precise circuit: southwest to northeast along the ridgeline, banking east over Old Miller Farm, then looping back. Altitude held constant at what I estimate was 800-900 feet. Never deviated more than a few degrees from the same route.

Then it was gone. No landing. No searchlight. Just... gone.

---

Night 2: December 9th, 02:14

I went back out. Call it paranoia, call it pattern recognition — after seven years of this, you learn to trust the coincidences that keep happening.

02:14: There it was again. Same rotor signature. Same flight path, within maybe 50 meters of the previous night's route. I timed it with my stopwatch this time: 22 minutes, 40 seconds of continuous flight over the same corridor.

No searchlight. No thermal imaging glow. No radio chatter on any frequency I could monitor. Just the steady pattern, like it was following invisible rails in the sky.

I checked FAA records later — nothing filed for that airspace during those hours.

---

Night 3: December 10th, 02:16

Three nights. Three identical patterns. I brought my night-vision camera this time, but the tree cover at The Clearing only gave me brief glimpses — enough to confirm it was there, not enough for useful footage. The numbers don't lie, but they don't always tell the whole truth either.

**What I know:**

• Consistent arrival time: 02:14-02:17 (±3 minutes)
• Flight duration: 22-24 minutes
• No lights except minimal anti-collision strobe
• Route precision: within 50-75 meters each night
• No radio contact on monitored frequencies
• Weather: clear, minimal wind all three nights

---

The Mundane Explanation:

Look, I'm not going to pretend there aren't obvious answers here. This could be:

• Law enforcement running surveillance on someone in the valley
• Agricultural survey work (though why at 2 AM with no lights?)
• Private contractor doing legitimate mapping or infrastructure inspection
• Military exercise from one of the installations 60 miles south

The timing could be about avoiding civilian air traffic. The precision could just be good piloting and GPS waypoints. The lack of filed flight plans could be a database lag or classified exemption.

I've been tracking this for 7 years now, and I know the difference between wanting something to be anomalous and something actually being anomalous. I also know that most surveillance is perfectly mundane — someone's growing pot, someone's skipping out on parole, someone's doing something that warrants watching.

---

But Here's What Bothers Me:

The route doesn't match a search pattern. It doesn't match a survey grid. It follows the ridgeline, then cuts over Old Miller Farm — the same property that's been abandoned since the 60s, the same property where my equipment gets those dead zone readings, the same property where Old Harold swears he saw something in '67 that made him stop farming.

Three nights is a pattern. Three nights over *that specific route* is a pattern that means something.

I'll be out there tonight. Same time. Same place.

Have you heard unusual helicopter activity in your area at odd hours? And more importantly — when you see precision like this, when does legitimate surveillance cross into something worth questioning?

Another entry for the log.

— JohnD_TN