The Air Force ran on forms, acronyms, and the occasional act of faith.

Most problems came to us via work order: a few scrawled words, a tail number, a location on the flight line, and a set of boxes waiting for signatures. The paper didn’t have much personality, but the people who filled it out sure did. Sometimes the planes did too.

One afternoon at Webb Air Force Base in Big Spring, Texas, I got a work order that read: “Breaks lock.”

It included the aircraft tail number and the parking spot on the tarmac. It had the right routing, the right department stamp, and the right signatures—our lieutenant and our tech sergeant. Official enough to make it real. Real enough that it became my problem.

As a technician working in radar and fire control, I knew exactly what “breaks lock” meant.

It meant the radar couldn’t hold a stable track on a target. The system would see something, start tracking, and then—poof—lose it. That could be a nuisance or it could be deadly serious, depending on the day and the mission.

But on an F-102, “breaks lock” wasn’t an unusual complaint. Not out there in West Texas.

The F-102 fighter didn’t live a gentle life. It spent hours sitting in the hot sun on the flight line, baking like a forgotten casserole dish. Then it would launch, climb hard, and go screaming up to 35,000 feet or more, where the air turned thin and the temperature turned brutal. Mach 1 wasn’t unusual. Then back down it came to the same hot tarmac.

Heat. Cold. Vibration. G-forces. The kind of mechanical violence that didn’t care about how carefully some engineer in a lab had designed a delicate analog tube circuit. Electronics would fail just from trying to survive the day.

I slung my tool bag and grabbed a partner. Some jobs can be done solo, but this one was faster with two. One person in the cockpit, one person out at the exposed equipment in the nose. If you’ve ever tried to climb in and out of an aircraft cockpit, then walk back and forth to the nose section 10 times, you know what kind of “exercise program” that turns into. Boring.

It wasn’t a long walk from the shop, maybe half a mile, but it felt like a mile and a half in the late-afternoon Texas heat. The wind had come up too, which sounds nice until you realize West Texas wind isn’t a breeze. It’s sand with ambition. It dried your sweat instantly and replaced it with grit.

We got to work.

First came ground power—hooking up the external power unit to give us the voltages we needed without running the aircraft engines. Next, checking the air handling system—chilled air piped into the equipment bays to keep the radar components from cooking themselves into nonsense. Radar electronics don’t like heat. Radar electronics prefer being treated like expensive, temperamental houseplants.

Then I climbed into the cockpit.

The smell inside was familiar: hot metal, rubber, and something else—a mixture of jet fuel and sweat that had been there longer than any of us. I strapped in, powered up the radar, and brought the scope to life. The screen glowed and hummed with the quiet confidence of a system that believed it had done nothing wrong.

I found a target in the distance, a little blip moving along steadily. Probably a private pilot on a routine flight, completely unaware that a two-striped Airman was watching on a military interceptor’s radar scope.

I locked on. The system held.

I tracked that poor soul for several minutes, just to see if the lock would wander, stutter, or fall apart the way the work order implied.

Nothing.

Then I found another target—farther out, weaker return, not quite as clean. I locked onto that one too.

Solid.

Again and again, I repeated it with targets that were more distant, fainter, and less cooperative. Every time the radar locked like it meant it.

No breaks. No slipping. No mystery failure. The system looked perfect.

Which is when the job became annoying.

Because when the equipment behaves perfectly on the ground, but a pilot writes it up as failing in the air, there’s always an unspoken possibility floating in the background: pilot error.

And yes, “pilot error” was technically a valid maintenance entry. But it was the kind of entry that meant spending the rest of your day explaining your attitude to someone who outranked you. Captains and majors flew airplanes; two-striped Airmen signed logs. The hierarchy was not subtle.

I couldn’t just write pilot error, even if part of me wanted to.

Instead, my partner and I did what good technicians do when reality refuses to match the paperwork: We tested everything anyway.

We ran procedures that didn’t need to be run. We checked connectors, traced signals, verified settings, confirmed tolerances. We ran tests that were designed for problems we weren’t even having, because if we were going to sign off on the work order, we wanted to do it with a straight face and clean conscience.

The radar system continued to behave like it was auditioning for a training film.

At some point we ran out of ways to doubt it. Which left us with the final option: Doubt the work order.

We packed up, left the jet sitting there smugly in the late sun, and walked back toward operations.

My boots felt heavy; my tool bag felt heavier. My patience was approaching the kind of fatigue that doesn’t show up on medical records.

When we got to the operations office, we handed over the work order and explained the problem: Everything tested fine. We couldn’t reproduce the failure. The system held lock every time.

The chief master sergeant took the paper from us without a word. He looked at it like he already suspected this one was going to be a little special.

He read the line again: “Breaks lock.” Then he frowned, picked up a pen, scratched out one letter, and added another. The order now read: “Brakes lock.”

A very different problem.

Important to the safety of the pilot. Important to the survival of the aircraft. But not something radar technicians had any business fixing. It was the kind of thing routed to the crew chief—people with the skills and tools to deal with hydraulics, wheels, and everything else that kept a jet from becoming a very expensive uncontrolled slide.

The chief master sergeant handed the work order back like he’d just corrected the universe with a single stroke of ink.

I stared at the paper for a second, then looked at my partner. Neither of us said what we were thinking, but we both felt it: We had just spent the last four hours diagnosing a spelling mistake.

That’s the Air Force. Machines that fly at the edge of physics, supported by paperwork with third-grade spelling errors.

We walked out with our tool bags still full, our radar system still innocent, and our shift suddenly a lot lighter.

“Give me a break,” I muttered, half to myself.

And the Air Force did.

Just not the kind I expected.

This War Horse Reflection was edited by Kim Vo, fact-checked by Jess Rohan, and copy-edited by Mollie Turnbull. Kim Vo wrote the headlines.