The Vigilance Trap – Why Federal Regulators Ignore Human Limits

The federal government accepts a hard limit on human attention. Baggage screeners are mandated to rotate every 30 minutes to prevent missed threats. Yet, across the nation’s radar consoles, that same government allows air traffic controllers to operate for hours without a mandated break. This investigation exposes the widening divide between established cognitive science and operational policy, and the systemic failures that emerge when human limits are treated as a suggestion rather than a rule.

The 1948 Vigilance Limit Foundations

In 1943, the Royal Air Force wanted to know why radar operators kept missing submarines during long patrols. Norman Mackworth built the Clock Test to find out.

By 1948, Mackworth had his answer. Detection accuracy dropped between 10 and 15 per cent inside the first 30 minutes of a monitoring task, and stayed depressed after that. The finding acquired a name in the literature: the vigilance decrement, meaning the well-documented drop in a person’s ability to spot rare signals after roughly half an hour of sustained watching, even when they are trying hard to stay focused.

That result did not go away. Decades of cognitive psychology have replicated the same curve, from ACT-R computational modelling of sustained attention through to broad reviews of fatigue in aviation.

Then the number moved earlier. A 2016 study in the journal ‘Human Factors‘ on airport baggage screeners found significant detection decrements emerging inside the first 10 minutes of busy shifts. The original 1948 Mackworth paper survives mostly through secondary citations in later human factors literature rather than as a freshly reproduced primary document. Every agency that now regulates continuous monitoring is working from the number without holding the original in front of it.

Federal Regulatory Inconsistencies

The TSA accepts the 30-minute number. Baggage screeners rotate away from X-ray monitoring every 20 to 30 minutes.

At the FAA, the rule differs. Under 14 CFR § 65.47, an air traffic controller may work up to 10 consecutive hours of duty, and no mandated 30-minute rotation for continuous monitoring appears in the text.

The Nuclear Regulatory Commission takes a third position. Generic Letter 82-12, dated 15 June 1982, together with Regulatory Guide 1.114 Revision 3, requires the operator at the controls of a nuclear reactor to maintain continuous visual surveillance and forbids leaving the station without a qualified relief. No prescribed cognitive rotational limit sits in either document.

One federal government reads the same underlying biology three different ways.

The NRC’s Generic Letter 82-12 lives inside a wider assessment file, ML010260345, titled ‘Assessment of the NRC’s Policy on Factors Causing Fatigue of Operating Personnel at Nuclear Reactors’. Internal page numbering inside that assessment jumps mid-document, and the two NRC document IDs sit next to each other in the archive without a clean index tying them together.

The Buried CAFMS Study Evidence

Between December 2011 and August 2015, a joint FAA and NASA team drafted the Controller Alertness and Fatigue Monitoring Study, known as CAFMS. Objective sleep, fatigue, and alertness measures were taken from serving air traffic controllers. The core finding was blunt: 70 per cent of midnight-shift controllers experienced severe fatigue.

Publication did not deliver the study to the public. An Associated Press Freedom of Information Act request did, in August 2015.

There is a further wrinkle in how the document circulates. NASA hosts one version under the Orasanu et al. evaluation title. The FAA hosts another with a separate filename and disclosure chain.

Nobody has published a document that explains why disclosure took roughly four years from drafting start, or who inside the agencies signed off on the decision to withhold.

Tempe 2018 and System Design Failure

An Uber Advanced Technologies Group test vehicle had been running in autonomous mode for 19 minutes on 18 March 2018 when it struck and killed a pedestrian in Tempe, Arizona.

Design decisions had ruled out automatic emergency braking on that vehicle. Collision mitigation depended entirely on the human safety operator sitting in the driver’s seat.

On 19 November 2019, the NTSB issued Highway Accident Report HAR-19/03. In the narrative sections, the Board explicitly acknowledged that drivers are ineffective at monitoring automation and that disengagement from a passive supervisory task is predictable.

Then the probable cause statement was published.

Probable cause, as recorded: the operator’s failure to monitor the environment due to visual distraction. Inadequate safety risk assessment procedures and the removal of the second vehicle operator were listed as contributing factors, one structural rung below the
probable cause line.

The draft memoranda that would show whether human factors investigators originally proposed system design as the primary probable cause, before internal review moved it down, are not public. NTSB releases the final report; the deliberation record behind it stays sealed.

The 2026 FAA Workforce Plan Arithmetic

Three numbers moved when the FAA’s Office of Financial and Labor Analysis released the Air Traffic Controller Workforce Plan 2026-2028 on 15 May 2025. That document is a staffing model, drafted inside the finance office rather than the medical office.

The Controller Availability Factor (CAF), an FAA staffing-model figure used to convert raw controller headcount into planned working hours, dropped from 2.14 to 1.87 in the published audit summary. Staffing target: cut from 14,633 to 12,563 controllers.

Modelled average time-on-position, meaning the hours a controller spends actively working a desk during a shift rather than the total shift length, climbed from roughly 4.01 hours to over 5.0 hours per 8-hour shift.

The 1.87 availability factor carries an archival wrinkle. Peer-reviewed work in a Transportation Research Board special report on air traffic controller staffing lists the AFN model’s availability factor as 1.82, not 1.87. The 1.87 figure appears in the r/atc2 audit of the plan and in downstream summaries, and the two numbers have not been reconciled from the open record.

Whatever the exact decimal, the direction of travel runs against an earlier scientific warning. In April 2024, the FAA’s Scientific Expert Panel had published ‘Assessing Fatigue Risk in FAA Air Traffic Operations’. The panel found that continuous surveillance combined with chronic sleep restriction produced cognitive impairment equivalent to up to two full nights of total sleep deprivation.

On 19 April 2024, the FAA Administrator issued a memorandum addressing time between shifts: 10 hours off between shifts, and 12 hours off before a midnight shift. Time-on-position inside a single shift went untouched by the directive.

CRWG model variables, which would show whether a 30 or 45-minute rotation was ever modelled by the Collaborative Resource Workgroup and rejected on cost grounds, are not in the public record. Staffing targets moved. What went into the model before they moved is sealed.

The published audit that carries these numbers into public view circulates in part through a Reddit thread on r/atc2 maintained by an anonymous account. Behind that summary sits the underlying FAA financial document, not in front of it.

The DCA Collision and Systemic Failure

PSA Airlines Flight 5342, a CRJ700, collided midair with a US Army UH-60L Black Hawk over the Potomac River near Ronald Reagan Washington National Airport on 29 January 2025. Sixty-seven people died. At DCA tower that night, the local control and assistant local control positions had been combined into a single desk handling high-volume mixed aeroplane and helicopter traffic.

Almost a year later, on 27 January 2026, the NTSB held a board meeting and published Aviation Investigation Report AIR-26-02.

The report is not shy about system-level failures. It cites an ‘unsustainable airport arrival rate’. Helicopter route placement close to civilian approach paths draws criticism, and airspace design flaws around DCA are flagged.

Probable cause and causal factors, as recorded: the tower team’s ‘loss of situation awareness’ and the helicopter crew’s ‘lack of effective pilot-applied visual separation’. Systemic findings sit in the narrative sections above; the names attached to the causal line sit at the sharp end. Inside the same report, the NTSB notes that the absence of mandatory relief periods for supervisory personnel is contrary to human factors research on prolonged time on task. That observation stays in the narrative. It does not move into the probable cause statement.

The precise continuous time-on-position for the controller working the combined desk at the moment of the collision is not in the public record. Duty logs for that shift remain sealed.

The report itself also carries a minor filing quirk. Board materials cite it as AIR-26-02, while the report PDF uses the filename AIR2602, and the NTSB press release page (NR20260127) carries a date stamp two days before the report PDF metadata in some indexed listings.

The HFACS Administrative Shield

The Human Factors Analysis and Classification System, known as HFACS, was built by Douglas Wiegmann and Scott Shappell for the US Navy between 1990 and 2003, drawing on James Reason’s Swiss-cheese model of accident causation. Its central move is a distinction between active failures (what the operator did or did not do in the moment) and latent conditions (pre-existing flaws in system design, staffing, or scheduling that made the active failure likely).

That taxonomy was designed to push analysis upstream, away from the sharp end.

Read the narrative sections of NTSB Highway Accident Report HAR-19/03 (Tempe) and NTSB Aviation Investigation Report AIR-26-02 (DCA). Both contain paragraphs describing latent conditions in HFACS-style language.

Now read the probable cause line at the end of each report. In both, the primary causal finding lands on the active failure by the operator.

A tool imported into US aviation and highway safety reporting to trace failures upstream ends up producing paperwork that names the upstream holes in the narrative and the downstream operator in the legal finding.

HFACS 8.0 was published in 2024 by the wider human factors community. NTSB reporting practice still tracks an earlier edition, and the two editions do not sit in a single mapped comparison document.

Source

Sources include: Norman Mackworth’s ‘The Breakdown of Vigilance During Prolonged Visual Search’ (1948) and contemporary cognitive research in the ‘Human Factors’ journal (2016); federal statutes including 14 CFR § 65.47; Nuclear Regulatory Commission guidance including Generic Letter 82-12 and Regulatory Guide 1.114 (Revision 3); the joint FAA and NASA ‘Controller Alertness and Fatigue Monitoring Study’ (CAFMS); the FAA Office of Financial and Labor Analysis ‘Air Traffic Controller Workforce Plan 2026-2028’; and National Transportation Safety Board findings including Highway Accident Report HAR-19/03 and Aviation Investigation Report AIR-26-02.