The Camera Died at Exactly the Wrong Moment — Again

23:47 — The Clearing

I've been running the same setup for three years now. Modified Sony A7S III with infrared filter, mounted on a motorized pan-tilt head. Battery backup. Redundant storage. I learned my lessons the hard way after 2019.

Last night, everything was nominal. Clear skies, 43°F, minimal wind. I was monitoring from the house via WiFi link, watching the live feed on my laptop while logging shortwave activity. Nothing unusual on the bands. Quiet night.

Then at 23:47, the camera feed froze.

Not a connection drop — those look different on my end. The image just locked. Last frame showed the treeline, stars, nothing remarkable. I immediately checked the backup recorder. Also frozen. Same timestamp. Same frame.

I grabbed my handheld thermal and headed to The Clearing. Takes about eight minutes to hike there in the dark. When I arrived, the camera was still running — LED indicators showed normal operation, motor responded to manual controls. But the recording had a gap. 23:47 to 00:03. Sixteen minutes missing from both primary and backup.

Here's what bothers me: The battery voltage dropped 23% during that window. Normal drain rate is maybe 2% per hour. The camera body was warm to the touch — warmer than ambient temperature would explain.

And here's the part I can't ignore: While I was walking back to the house, I saw them. Three lights, reddish-orange, moving south to north at what I'd estimate was 15-20 degrees above the horizon. Silent. No navigation strobes. No sound at all. They moved in formation — not rigid, but coordinated. I watched for maybe forty seconds before they winked out, one by one.

No camera. No recording. Just my eyes and my notebook.

The Mundane Explanation

I've been doing this long enough to know the obvious answer: equipment failure. The A7S III is a workhorse, but it's not immune to thermal issues, firmware glitches, or power regulation problems. The battery drain could be explained by a short circuit or a failing voltage regulator. The warmth, the freeze, the gap — all consistent with a hardware fault.

And the lights? I'm 40 miles from McGhee Tyson Air National Guard Base. They run exercises. The 134th Air Refueling Wing flies KC-135s, and depending on atmospheric conditions, their navigation lights can appear unusual. Formation flying is standard procedure. The silence isn't unusual at distance.

I've seen military aircraft hundreds of times. I know what they look like. These... moved differently. But "moving differently" isn't data. It's a feeling.

00:17 — Back at the House

I pulled the SD cards and examined every frame before and after the gap. Nothing. The last clean frame shows normal starfield. The first frame after the gap shows the same view, but the stars have moved — sixteen minutes of rotation, exactly as you'd expect.

Whatever happened, happened during the blackout.

I've been tracking aerial phenomena for seven years now. I've never captured definitive proof of anything that couldn't be explained conventionally. Every time I get close, something fails. Equipment malfunctions. Weather rolls in. The timing is always wrong.

Part of me wonders if I'm looking for patterns that aren't there. The other part can't shake the feeling that I'm being *allowed* to see just enough to keep looking, but never enough to prove anything.

The camera is currently running diagnostics. If it's a hardware failure, I'll find it. If it's not... well, that's the question, isn't it?

Another entry for the log. Another almost.

Has anyone else experienced synchronized equipment failures during observations? And what are the odds that a camera malfunction would occur during the exact window when something appeared overhead?