Ecologists Watched A Silent Craft During Night Wildlife Survey

I have spent twenty-six years being paid to stand in fields at night and write down what is above me. I want to say that first, not because it makes me a better witness, but because it makes me a *specific* kind of witness, and I think the difference matters.

I'm an ecological consultant. The unglamorous end of it. When somebody wants to build a wind farm, a bypass, a housing estate on the edge of a village, a person like me is hired to go out for a season and count what lives there. Most of my career has been bats. Bat surveys happen at dusk and through the night, which means I have spent something in the region of two thousand nights looking upward in the dark, in the rain, with a flask of tea going cold on a fence post.

So when people say "you can't identify things in the night sky," I want to be careful and honest here: they're mostly right. Night sky observation is a catalogue of embarrassments. I have called in a Chinese lantern as a barn owl. I have watched Venus for four minutes convinced it was a helicopter that wasn't moving. Sirius, low down and scintillating through bad air, will flash red and green and blue and do a very good impression of something with navigation lights. Once, on a coastal site, I logged what I was certain was a low-flying goose and it turned out to be a plastic bag.

I tell you all this so you understand that I'm not the man in the pub who saw a light. I'm the man who has been wrong about lights professionally, hundreds of times, and who has written down being wrong in a notebook that somebody else then read.

This was late August, a wind farm scoping survey on upland moor in the north. I won't name it. The site was a long ridge of rough grazing and old peat hags, with a met mast already up — one of those slim lattice towers they put in for a year to measure wind speeds before they commit. Eighty metres. That mast matters later, because it gave us something to measure against, and having a known object of known height in the frame is the difference between a story and an observation.

There were three of us. Myself; a woman I'd worked with for about nine years, very steady, ex-RAF ground crew before she retrained, which I mention because she knew aircraft the way I know bats; and a lad in his second season, keen, good ears, not yet cynical.

The kit, because the kit is the point of this whole account: two bat detectors running continuously — the type that records full-spectrum audio and time-stamps everything to the second — a handheld thermal imager, GPS units, and paper notebooks, because you always keep paper. The thermal camera was there for a specific reason: on that site we were also being asked about barn owl and nightjar activity, and thermal is how you see a bird against a cold sky. It's a modest bit of equipment, nothing military, but it does one thing very reliably. It shows you heat.

The night was clear, which is unusual up there, and cool. No moon to speak of. There was an aircraft corridor to the west of us and we'd been seeing the usual traffic — lit, blinking, audible if the wind was right, moving in that steady, boring way aircraft move. I'd logged two of them out of habit.

At 23:47 the lad said "what's that," in the flat voice people use when they already know the answer isn't good.

There was an object coming up the valley from the south, below the ridgeline, which is to say it was below us. That is the first thing that was wrong. We were standing at about four hundred metres of elevation and looking *down* at it.

It was not lit. I want to be precise. It was not a light in the sky. It was a shape that was darker than the dark behind it, and I only picked it out at all because the valley floor had a scatter of farm lights and the shape moved across them and took them away one at a time, like a hand passing over a row of candles.

Nothing under power is silent at that distance. I've had a hang glider go over at three hundred feet and heard the fabric. I've heard microlights from a mile away. That night the wind was almost nothing, maybe two or three metres a second, and I could hear a stream at the bottom of the valley and sheep somewhere and one of us breathing.

I could not hear that.

It came up the valley and it rose — not climbing the way an aircraft climbs, on a slope, but rising, the way a lift rises — until it was level with us and then above us, and it passed the met mast at what my colleague and I independently wrote down, separately, before comparing, as "level with mast head or slightly above." So call it eighty to a hundred metres. Call it two and a half times the height of the church I grew up next to.

At that range, on a clear night, with three trained observers, an aircraft is an aircraft. This was not an aircraft.

It was long, and it was without any feature at all. I have read enough accounts since to know that everybody says triangle or disc, and I would love to give you something that clean. What I saw was a shape with no edges I could fix on. When I looked directly at it I lost the outline, and when I looked slightly away from it I got it back, which is how you see faint things in the dark — you use your peripheral vision, and any astronomer will tell you the same. So my honest description is: something that took up roughly the width of my hand at arm's length, moving north, without sound, without lights, without any surface I could describe, at about the height of the mast.

And then the lad, who had the thermal, said a word I won't repeat and handed it to me.

I need to explain what I was expecting. Anything that flies under its own power is hot. Engines are hot, exhaust is hot, even the leading edge of a wing gets warm from friction. Birds are hot — a barn owl on thermal is a small bright lamp. Everything on that moor was some shade of grey and the sheep were white blobs and the mast was a faint warm line because metal holds the day's heat.

The object was cold. Not neutral. Colder than the sky behind it.

I have thought about this for a very long time and I've had the obvious conversations with myself. A thermal imager measures emitted infrared, and something with a very low emissivity — a polished metal surface, say — reflects rather than emits, and will read cold because it's showing you the reflected temperature of the sky, which on a clear night is genuinely, physically freezing. That's a real effect. I've seen it on a shiny grain silo roof. So it is not, on its own, impossible.

But a polished object that size, at that height, on a clear night, with farm lights below it and stars above it, should have been throwing reflections everywhere. It threw nothing. It was a hole punched in the picture. It had a boundary and inside the boundary there was less energy than anywhere else in the frame, and it moved.

It went north along the ridge for what my notebook says was "approx 40 sec," then it stopped.

Not slowed. Stopped, and held, over the far end of the ridge where the peat cuttings are.

And then it went straight up, and I lost it in about a second and a half, and there was nothing.

Now the part that has actually cost me sleep, and it is not the object.

The bat detectors were running the entire time. That's their job — they sit there and they record everything in the ultrasonic band, continuously, with timestamps, and later you sit at a computer and go through the files and identify the calls. On a good August night on decent upland edge you get common pipistrelle constantly, soprano pipistrelle, the odd myotis, noctules up high early on. It is not quiet. That night had been ordinary — busy, even, along the plantation edge below us.

When I processed the files the following week, there was a gap.

Bat activity on both detectors, sited two hundred metres apart, dropped to zero at 23:44 and resumed at 23:55. Eleven minutes. Nothing at all — not a distant pass, not a single social call, not the background scatter of insect noise that bleeds into the low end of those recordings. Both units. Simultaneously.

The object was in view from roughly 23:47 to about 23:49 by my notes. The silence started three minutes before I saw it and ended six minutes after it left.

I have tried to break that finding. I checked the units for a fault and there wasn't one; they were recording, the files exist, they are eleven minutes of clean ambient with the noise floor exactly where it should be. It's not a dropout — a dropout looks different, it looks like nothing, and this looked like a room with everyone holding their breath. I checked temperature, because bats will shut down if it drops sharply, and it didn't; I had the logger data. I checked for rain. There was no rain.

Bats stopped hunting for eleven minutes across an area of at least two hundred metres, and started again, and I have never seen that in twenty-six years and I have never spoken to anybody who has.

Here is where I stop being a witness and start being something worse.

That data went into a report. The report went into a planning application. And a gap of eleven minutes in the activity data on a wind farm bat survey is not a curiosity, it is a *problem*, because the whole document is a numbers exercise about collision risk and everything has to be accounted for and defensible at a hearing.

I raised it with the project lead. I said, roughly: there's an eleven-minute null on both units, I can't explain it, I want to flag it in the methodology as an unexplained gap.

He asked what I thought caused it.

And I sat in that office and I heard myself say that I didn't know, and I did not say the rest of it, because I could see exactly how the rest of it would land, and I had a mortgage, and this was a client we'd worked with for six years.

We logged it as a probable equipment reset. That is what it says. I wrote that sentence. It's in a document with my name on the contributors page, in a council planning portal, and anybody can read it right now, and it is not true.

The lad went along with it because he was twenty-four and it was his second season and I was the one who should have been protecting him from exactly that. My other colleague, the ex-RAF one, said one thing to me in the car park afterwards, which was: "You know what it wasn't." Then she drove home.

The turbines went up three years later. I've driven past. They look like every other wind farm.

I kept the raw files. All of it — the audio, the thermal clip the lad managed to save, which is eleven seconds long and shows a dark oblong against a grey sky and would convince absolutely nobody who wasn't standing there. I've got it on an external drive in a drawer with about forty other projects, and every few years I think about doing something with it, and I don't, because I know precisely how it would go. I'd be the ecologist who saw a UFO. That's the whole rest of my career, in one sentence, and it is a sentence that ends it.

Last winter I got an email from the lad, who is not a lad any more; he runs his own consultancy now and is quite well thought of.

The whole email was: "Do you still have the raw files from the ridge?"

I have not answered him yet. I know that when I do, he is going to tell me something, and I am fairly sure I already know what it is, because there is only one reason a busy man asks that question after eleven years.

I don't have an explanation and I'm not going to insult you by inventing one. What I have is the following: two independent recorders that stopped hearing anything for eleven minutes, a thermal signature that was colder than empty sky, three people whose entire professional training is the identification of things that fly, and a document in a planning archive that says "probable equipment reset."

The object doesn't frighten me. It was there and then it wasn't and I've made a kind of peace with that.

What frightens me is how easy it turned out to be — how ordinary, how procedural, how much like a normal Tuesday — for three qualified people to look at a genuine anomaly in their own data and agree, without any real argument, to write down something else.