The Helicopter That Circles But Never Lands: 47 Days of the Same Flight Path

0347 hours. Always 0347 hours.

I first logged it on May 19th — a helicopter, low altitude, running dark except for standard nav lights. Came in from the northeast, followed the ridgeline west for exactly 3.2 miles (I've measured it), then banked south toward the old Miller property before disappearing over the tree line.

Strange, but not unprecedented. We get military training flights. Search and rescue. The occasional rich guy's joyride.

But then it happened again. Same route. Same altitude. Same time — 0347 hours. Three days later.

And again. And again.

47 days. 16 flights. Every third day without fail.

I've been documenting everything:

• **Sound signature**: Consistent rotor pattern, likely a medium utility helicopter (Blackhawk-class, maybe civilian equivalent)
• **Flight characteristics**: Deliberate, methodical. Not searching. Not training. *Surveying.*
• **Timing precision**: Never more than 90 seconds variance from 0347
• **No transponder signal**: I've checked ADS-B Exchange every time — nothing
• **Weather independence**: Flies in clear skies, overcast, even light rain

Here's what makes my engineering brain itch: that level of precision isn't casual. You don't accidentally fly the exact same route at the exact same time every 72 hours for nearly two months. That's systematic. That's *monitoring something.*

I drove out to the Miller property last week — the place where it always banks south. Nothing visible from the road. Posted signs, new fence line, but the property's been abandoned since 2019. Or supposedly abandoned.

The mundane explanation? Some kind of infrastructure monitoring. Power lines run through that area. Could be a private contractor checking transmission equipment, though why they'd need to do it at 3:47 AM on a precise 72-hour cycle, I couldn't tell you. Maybe environmental surveys — we've had the Surveyors around before, though usually they're more obvious about it.

The alternative? Something on or near that property requires regular aerial observation. Something that operates or appears every third night. Something that coincides with — and I checked my logs — *some* of the signal bursts I've been tracking.

Not all of them. Not even most. But enough to notice.

I've been doing this for seven years now, and I've learned to separate what I *want* to see from what's actually there. Most anomalies have explanations — boring ones, usually. But I've also learned that boring explanations don't always explain why something needs to be hidden.

If this is just routine infrastructure monitoring, why no transponder? Why the middle of the night? Why does the Sheriff get uncomfortable when I mention helicopters?

Next flight is scheduled for tonight. 0347 hours. I'll be watching.

I've set up the night-vision camera with a better angle this time. Maybe I'll finally get a clear enough image to identify the aircraft type. Maybe I'll see what they're actually looking at.

Or maybe I'll just add another entry to the log. Another almost. The numbers don't lie, but they don't always tell the whole truth either.

What kind of infrastructure requires monitoring every 72 hours at 3:47 AM? And if you were trying to monitor something without drawing attention, wouldn't you vary your pattern at least a little?