Why Nuclear Power Plant Operators Aren't Allowed to Work Tired
A look at 10 CFR Part 26, Subpart I — the federal rule that caps hours and mandates fitness-for-duty declarations for U.S. nuclear control room operators — and why almost no other industry regulates ordinary tiredness this way.
In this article6 sections
Nuclear power plant control room operators in the United States work under a federal rule, 10 CFR Part 26, Subpart I, that caps how many hours they can be on shift, fixes a minimum rest period before the next one starts, and requires each operator to declare in writing, before every shift, that they’re fit to work. Few other jobs in the country regulate plain tiredness with that much legal force behind it.
In March 1987, inspectors from the Nuclear Regulatory Commission arrived unannounced at Peach Bottom Atomic Power Station, a two-unit plant on the Susquehanna River in southeastern Pennsylvania, and found control room operators asleep at their stations. The incident became one of the most frequently cited case studies in the agency’s own fatigue-policy history, not because it caused a radiological release — it didn’t — but because it demonstrated something regulators had suspected without being able to prove cleanly: that operators running a reactor could be, and sometimes were, too tired to actually be running it, with nothing in the rulebook at the time that treated that as an independent hazard worth managing on its own terms.
What Does the NRC’s Fatigue Rule Actually Require?
The NRC’s Fitness-for-Duty program, codified at 10 CFR Part 26, originated in the late 1980s mainly as a drug and alcohol testing requirement, a response to a different set of incidents involving substance use among plant staff. Fatigue wasn’t folded into it as its own subject until nearly two decades later. Subpart I, titled “Managing Fatigue,” went through public rulemaking starting around 2005 and reached final form in 2008, with a multi-year compliance window that gave licensees time to build the scheduling and reporting systems the rule required rather than switching over instantly.
What it covers, in general terms: numeric limits on how many hours a covered worker can be on duty within a 24-hour period, a required minimum rest period before returning to safety-related work, caps on cumulative hours across rolling weekly and biweekly windows, restrictions on how many consecutive night shifts can be scheduled in a row, and — the part that has no clean equivalent in most other regulated industries — a requirement that the individual worker personally attest, before each shift, that nothing about their physical or mental state would put them below the standard needed to perform safety-related duties. That declaration covers fatigue specifically, alongside illness, medication, and personal circumstances that might impair judgment. The precise figures behind each of those caps run several pages of federal regulatory text and shift slightly depending on the role and the circumstance, — worth stating outright rather than compressed into a single tidy number that would read as more precise than it is.
The rule applies to a defined population: licensed reactor operators, non-licensed staff whose duties directly support control room operations, security personnel, and certain maintenance workers whose fatigue-related errors could plausibly compromise safety. It doesn’t apply to every employee at a nuclear plant, which is itself informative — the line the NRC drew wasn’t “everyone who works here,” it was “everyone whose degraded judgment on a bad night could matter to reactor safety specifically.”
Why Did This Take So Long to Become a Rule?
Peach Bottom wasn’t an isolated data point, and it wasn’t even the industry’s most consequential early morning. The accident at Three Mile Island Unit 2, in March 1979, began just before 4 a.m., a detail that gets less attention in most retellings than the equipment failures and the control room’s confusing instrumentation, but that later safety analyses have noted as circumstantially relevant: 4 a.m. sits near the low point of the human circadian cycle, the window where alertness and judgment are measurably at their worst for almost everyone, regardless of how rested a person believes they are. Investigators at the time focused overwhelmingly on engineering flaws in the plant’s instrumentation and gaps in operator training, and that focus was largely correct — TMI wasn’t primarily a fatigue accident. But the coincidence of timing became one thread in a much longer argument, stretched across the following three decades, that the industry’s existing training and licensing standards, rigorous as they were, weren’t built to account for a variable that degrades exactly the judgment those standards depend on.
That argument moved slowly. Individual incident reports accumulated through the 1980s and 1990s — near-misses, inspector findings, self-reported close calls — without ever producing the kind of single, undeniable catastrophe that forces immediate legislative action the way some other industries have experienced. What accumulated instead was a body of evidence that looked less like one crisis and more like a pattern, and patterns are harder to legislate against quickly. The NRC opened formal fatigue rulemaking in the mid-2000s, took public comment, revised the proposal, and landed on the final Subpart I text in 2008 — a regulatory timeline that, in retrospect, tracked the slow accumulation of the evidence more than it tracked any single triggering event.
What Does the Underlying Science Actually Say?
Two researchers, working independently and from different starting points, produced much of the science that eventually justified rules like this one.
Torbjörn Åkerstedt, a longtime sleep researcher at Stockholm University’s Stress Research Institute, has spent decades analyzing when human error and accident risk cluster across the 24-hour clock. Working with large industrial and transportation accident datasets, his research consistently finds two elevated-risk windows: a large one in the early morning hours, roughly 2 to 6 a.m., and a smaller, shallower one in the mid-afternoon. Both track much more closely with the body’s circadian rhythm than with how many consecutive hours a person has been awake, which is the finding that matters most for shift scheduling specifically — it means the danger window is partly predictable in advance, tied to the clock rather than to any individual’s personal stamina, and a schedule can be built around it rather than merely hoped around.
Gregory Belenky reached a related conclusion from a different direction. After two decades studying sleep loss for the U.S. Army — much of it at the Walter Reed Army Institute of Research, before he went on to direct the Sleep and Performance Research Center at Washington State University — Belenky’s work helped establish what researchers sometimes call a dose-response relationship between partial, repeated sleep restriction and cognitive performance. Cut sleep by even two hours a night, night after night, and the resulting impairment doesn’t level off; it compounds, so that a person on day five of mild restriction performs measurably worse than the same person on day two, even though most subjects in these studies consistently rated their own alertness as roughly unchanged across the whole stretch. That mismatch — real, accumulating impairment paired with a stable or even improving self-rating of how impaired a person feels — is the specific problem a rule built entirely on individual self-assessment can’t solve on its own, which is part of why 10 CFR 26 Subpart I pairs a mandatory self-declaration with hard numeric caps rather than relying on the declaration alone. Belenky’s Army-era research reached a conclusion the U.S. military’s own sleep-deprivation program kept arriving at from multiple directions: there’s no substitute for sleep itself, and no reliable way to train a person to stop needing it.
How Does This Compare to Aviation and Rail?
Commercial aviation runs on the closest legal cousin to the nuclear industry’s approach. Federal duty-and-rest rules for airline pilots fix minimum rest before a duty day, cap how long a duty period can run, limit cumulative hours across rolling windows, and let a pilot report themselves too fatigued to fly without facing discipline for saying so — a structure that looks, in broad outline, remarkably close to what nuclear plants now do. The parallel isn’t a coincidence; both industries arrived at similar answers because both are managing a small, highly trained workforce where an individual’s degraded judgment during one specific window can produce a catastrophic, public, unrecoverable failure, and both faced sustained pressure, after visible incidents, to stop treating fatigue as a private matter between a worker and their own judgment.
Freight and passenger rail sit a step behind. Following the 2008 Rail Safety Improvement Act — passed in the aftermath of a fatal commuter rail collision in Chatsworth, California, that year — railroads became legally required to file fatigue management plans and operate under federal hours-of-service limits for train crews. But rail’s rules lean more heavily on cumulative hour caps and less on the individualized, per-shift self-declaration that anchors the nuclear rule; a train engineer’s schedule is bounded by law, but there isn’t a comparable formal moment, built into every shift, where the individual is asked to personally attest to their own fitness before touching the controls.
Outside those two industries and nuclear power, formal, government-enforced fatigue regulation gets thin fast. Long-haul trucking has hours-of-service rules, but the compliance burden sits mostly on logged hours rather than a fitness declaration. Hospital medicine has duty-hour limits for residents, set nationally by an accrediting body rather than a federal regulator, and those limits are frequently described by the physicians working under them as loosely enforced in practice. Nowhere else does an individual worker sign something, shift after shift, formally attesting to their own tiredness under a rule specifically written so that telling the truth carries no professional penalty. Passenger ferries took a different route to a related fix: after an assistant captain lost consciousness at the helm and a New York City ferry hit a pier in 2003, regulators didn’t add a fitness declaration at all — they required a second licensed officer in the wheelhouse during docking, so no single person’s private state, tired or otherwise, could sink the vessel alone.
There’s also a case worth naming from outside the regulatory world entirely, because it shows the same underlying problem solved through pure schedule engineering rather than self-declaration. For most of the nuclear submarine era, U.S. Navy crews stood watch on an 18-hour day instead of a 24-hour one — a schedule that, circadian research eventually showed, human physiology never actually adapted to, no matter how long a crew spent underway. The Navy’s fix wasn’t a self-declaration system; it was rebuilding the schedule itself around the clock the body already runs on. Nuclear power’s fix and the submarine fleet’s fix point at the same underlying fact from two different angles: neither training, selection, nor sheer professionalism reliably overrides a body that’s circadian-misaligned or sleep-restricted, so both institutions eventually stopped asking people to override it and started building rules around it instead.
Why Doesn’t Every High-Stakes Job Work This Way?
Part of the answer is simply workforce size. The NRC oversees roughly 90 operating commercial reactors at about 54 plants, with a licensed workforce numbering in the low thousands — small enough that a detailed, individually enforced rule is administratively tractable in a way it wouldn’t be for an industry employing millions. Part of it is the specific shape of the tail risk: a fatigued reactor operator’s worst-case error is catastrophic, public, and essentially unrecoverable once triggered, a different profile than a fatigued worker’s error in most other settings, where a bad night more often produces a smaller, contained, and recoverable mistake. And part of it is cultural memory — an industry that lived through Three Mile Island and watched Chernobyl unfold seven years later inherited a level of public and political scrutiny that most workplaces never have to answer to, which created the sustained institutional appetite needed to write and defend a rule this specific.
None of that means fatigue matters less in other high-stakes settings. It means the regulatory appetite to build an enforcement system this granular showed up here first, for reasons tied to how catastrophic a single failure could be and how much sustained public attention the industry draws, rather than to how common or how dangerous workplace fatigue actually is across other fields.
What Can an Ordinary Reader Take From This?
The part of 10 CFR 26 Subpart I worth carrying outside the nuclear industry isn’t the specific hour caps — most workplaces couldn’t adopt those directly even if they wanted to, and most jobs don’t carry stakes that would justify the administrative weight of trying. It’s the smaller idea buried inside the mandatory declaration: the rule doesn’t ask an operator to privately decide whether they feel fit enough. It requires them to say so, out loud, on a form, on a fixed schedule, regardless of how the question strikes them that particular morning. That turns a private, easily-avoided judgment call into a recurring, unavoidable moment of accounting — not because operators can’t be trusted to notice their own fatigue, but because fatigue itself dulls the exact faculty a person would need to notice it accurately, a problem no amount of individual discipline fully solves from the inside.
Most people will never work a job where the law requires that kind of formal, repeated accounting. But the underlying insight travels further than the reactor floor: tiredness that never has to be named out loud to anyone tends to get quietly renegotiated, one reasonable-sounding exception at a time, until the standard it was supposed to protect has eroded without a single dramatic moment marking when it happened. The nuclear industry’s rule exists because regulators concluded that leaving that renegotiation entirely to an individual’s private judgment, night after night, was a bet the country couldn’t afford to keep making.
One honest caveat belongs here: this piece describes 10 CFR 26 Subpart I in general terms drawn from public NRC materials and secondary reporting, not as a substitute for the regulatory text itself. Anyone relying on the specific hour caps, rest requirements, or compliance deadlines for professional or legal purposes should read the current version of the rule directly, since federal regulations get amended and this summary won’t track future revisions.