July 7, 2026 · by David Gilbert · 3 min read · Radio & Broadcasting
Most of my "things going wrong live" stories are minor — a fluffed word, a wrong song cue, the usual small embarrassments of live broadcasting. This one isn't minor. This is the night the transmitter actually died, mid-sentence, while I was on air, and the half-hour afterwards that taught me more about staying calm under pressure than almost anything else in my career.
The Moment It Happened
I was partway through a segment, talking about something thoroughly unremarkable, when the studio monitor went quiet in that specific way that's different from a normal pause — the kind of silence that has a particular dead quality to it, somehow audibly different from "nobody's talking right now." Within a few seconds it was clear this wasn't a mic issue or a desk fault. The transmitter itself had gone down, taking the entire station off air, mid-broadcast, with zero warning.
The Part Nobody Tells You About Live Broadcasting Disasters
Here's what surprised me, even after years of being comfortable on air: the first reaction isn't technical problem-solving. It's a jolt of pure adrenaline, almost embarrassment, even though logically you know equipment failure isn't your fault and nobody's blaming you for a transmitter dying of old age. You sit there for a second feeling like you've personally let down everyone listening, before the more useful part of your brain kicks in and starts actually troubleshooting.
What Actually Happened Next
Community radio runs on a small, dedicated handful of volunteers, and that night was a genuine team effort — checking the obvious things first, working through the signal chain methodically rather than panicking and randomly flipping switches, and eventually tracing it to a component failure that needed a workaround rather than a same-night replacement. We were off air longer than anyone wanted, and when we finally got back on, there was no studio audience applause, no dramatic music sting — just the quiet, slightly anticlimactic satisfaction of hearing your own voice come back through the monitor and knowing the signal was live again.
What It Taught Me About Every Other Kind of Crisis
The transmitter failure itself isn't really the interesting part of this story. What's stuck with me is how directly it maps onto every other technical emergency I've handled since — a client's website going down during a product launch, a server failure at the worst possible moment, a critical file corrupting right before a deadline. The pattern is always the same: a horrible jolt of "oh no," a few seconds of useless panic if you let it in, and then the actual job, which is methodically working the problem instead of emotionally reacting to it.
Why I'm Glad It Happened
Not in the moment — in the moment it was stressful and a little humiliating. But I genuinely think every person who does technical work for a living needs at least one proper "everything's broken, right now, in public, with no warning" experience early on, because it's the only thing that actually teaches you what calm-under-pressure feels like from the inside. You can't learn it from a course. You learn it by sitting in dead air for what feels like an eternity and discovering you're still capable of thinking clearly.
These days, when something breaks badly during a client job, I think back to that dead, specific silence in the studio monitor, and it genuinely helps. Nothing since has felt quite that bad.