Overnight air traffic control is, by volume, the quietest shift in the tower, a fraction of the daytime movement count at most mid-sized airports. It is not, according to the controllers who work it, the easiest. Fatima Bello has worked overnight rotations in a regional tower for eight years, managing cargo flights, occasional diversions, and a scattering of early departures that begin stacking up as the shift winds toward morning. We spoke with her at the end of a shift, as the first scheduled passenger departures of the day were being sequenced onto the runway.

How different is the actual work at night compared to the day shift?

The traffic volume is completely different, we might handle a tenth of the movements a day controller handles in the same number of hours. But the job doesn’t get easier just because it’s quieter, in some ways it gets harder, because vigilance is difficult to sustain when very little is happening. A day shift keeps you occupied by sheer volume. A night shift asks you to stay at the same level of readiness for a plane that might not need you to do anything for forty minutes, and then suddenly needs a precise, fast decision.

What’s actually moving through the airspace at three in the morning?

Cargo, mostly, at a lot of airports this size. Overnight cargo networks are built specifically around these hours, packages moving between regional hubs on a schedule designed to have everything sorted and back on delivery trucks by morning. We also get occasional diverted flights, weather or mechanical issues elsewhere sending a plane to us that wouldn’t normally land here, and those are the moments the quiet shift gets busy fast, with a crew that’s often smaller than the day shift would have on hand for the same situation.

Does fatigue actually affect the work, in your experience?

Everyone in this job will tell you fatigue is the real hazard of the night shift, more than traffic volume ever is. There are strict rest requirements between rotations specifically because of this, mandated break periods within a shift, and a hard limit on how many consecutive night shifts a controller can work before a mandatory stretch of days off. I’ve felt the difference myself, controlling a straightforward situation at 2 a.m. takes more conscious effort to execute cleanly than the same situation would at 2 p.m., even though on paper it’s the easier traffic picture.

What’s the moment in a night shift that requires the most concentration?

The handoff, both ways, going into the shift and coming out of it. Coming on at midnight, you’re taking over live traffic from someone who’s been awake and focused for hours, and you have to absorb everything they’re tracking almost instantly, no room to ease in. Coming off at dawn, handing over to the day shift as traffic is actively building toward the morning rush, that’s arguably the highest-pressure ten minutes of my whole night, more than anything that happened during the quiet hours in between.

Is there anything about the overnight shift you’d choose again, given the option?

The quality of the quiet, honestly, on the nights it stays quiet. There’s a kind of clarity to controlling three aircraft instead of thirty, where you can actually think a full step ahead instead of reacting continuously. I don’t love what it’s done to my sleep over eight years, that part is real and I won’t pretend otherwise. But there’s something in me that finds the tower at two in the morning, dark below, a handful of lights moving slowly across my screen, more honest than the tower at rush hour ever feels. It’s the same job. It just breathes differently.