US controllers under investigation as they hope to rebuff Facebook
From Sleeping Controllers to Systemic Crisis: The FAA's Fatigue Problem (2019‑2026)
In 2011, a series of embarrassing incidents rocked the Federal Aviation Administration. Air traffic controllers were found asleep on the job—at Reagan National Airport, at a radar center near Miami, and at airports across the country. Transportation Secretary Ray LaHood declared he had never been "madder" and the FAA rushed to implement new scheduling rules: nine hours of rest between shifts, additional controllers on midnight shifts, and a ban on certain shift swaps.[reference:0][reference:1]
That was supposed to fix the problem. It didn't. In the 15 years since those sleeping‑controller incidents first made headlines, the issue of air traffic controller fatigue has metastasized from a series of embarrassing but non‑fatal events into a full‑blown systemic crisis. Controllers are working six‑day weeks, the FAA is short thousands of staff, and fatal accidents have been linked directly to overwhelmed, exhausted controllers. This post, originally published in 2019, has been completely updated with the full story of what happened next.
🛏️ The 2011‑2019 Era: Sleeping Controllers and Quick Fixes
The original wave of sleeping‑controller incidents in 2011 was a wake‑up call. At Reagan National Airport, a lone controller working overnight failed to assist two jetliners on approach. At Reno‑Tahoe International, a medical flight couldn't contact a controller who had fallen asleep. At a Miami radar center, a controller reported a co‑worker "asleep at the switches."[reference:2]
The FAA's response was swift but limited. New scheduling rules required a minimum of nine hours off between shifts, banned shift swaps that created unscheduled midnight shifts following days off, and added a second controller to midnight shifts at facilities that previously had only one.[reference:3][reference:4]
But these changes addressed symptoms, not root causes. The underlying problem—chronic understaffing that forced controllers to work mandatory overtime and six‑day weeks—remained untouched. A NASA study found that 70% of air traffic controllers had nearly dozed off while actively working, and more than half of those who made operational errors cited fatigue as a contributing factor.[reference:5][reference:6]
💡 Analyst Perspective: The Staffing Time Bomb
The FAA's controller workforce was already aging and understaffed in 2011. The agency knew that a wave of retirements was coming—controllers face mandatory retirement at age 56—but failed to build a hiring pipeline that could keep pace. The 2‑2‑1 scheduling model (working four shifts in five days, including a midnight shift) was popular with controllers because it created long weekends, but it likely resulted in "severely reduced cognitive performance" during overnight shifts due to cumulative fatigue.[reference:7][reference:8]
🛩️ The 2025 DCA Tragedy: A System Under Strain
On January 29, 2025, the accumulated strain on the air traffic control system resulted in catastrophe. American Airlines Flight 5342 collided with a U.S. Army Blackhawk helicopter near Reagan National Airport, killing all 67 people aboard both aircraft. The National Transportation Safety Board (NTSB) spent a year investigating, and in January 2026, it delivered a damning verdict: "systemic failures" within the FAA were to blame.[reference:9]
The details were chilling. In the 10 to 15 minutes before the collision, a single air traffic controller was simultaneously managing six airplanes and five helicopters on two different frequencies. Alerts were sounding throughout the control tower warning that the aircraft were in danger of colliding—but those warnings were never communicated to the pilots. "Were they set up for failure?" NTSB Chair Jennifer Homendy asked during the hearing. "They were not adequately prepared for the job they were assigned to do," came the response.[reference:10][reference:11]
The DCA tragedy was not an isolated failure. It was the predictable result of years of understaffing, inadequate training, and a culture that normalized near‑misses. "It should never have happened," said Matthew Collins, whose brother died in the crash. "Act on it. Do something. Save someone's life."[reference:13]
⚠️ The 2026 Near‑Miss Epidemic
Even after the DCA tragedy, the near‑misses have continued at an alarming rate. In March 2026 alone, several high‑profile incidents made headlines:
- Nashville (April 19, 2026): Two Southwest Airlines planes came within 500 feet of each other after an air traffic controller directed one pilot to turn into the path of the other plane. Both aircraft took evasive action. The controller "completely forgot about the other Southwest that he had just cleared for takeoff," according to a veteran controller with 20 years of experience.[reference:14][reference:15]
- John Wayne Airport, California (March 2026): A Black Hawk helicopter passed directly in front of a United Airlines passenger jet as the plane was landing. "Not good," the controller said after the incident.[reference:16]
- LaGuardia Airport, New York (March 2026): An Air Canada jet collided with a fire truck on the runway, killing two pilots. Only two controllers were on duty during the midnight shift, managing airspace, departure clearances, and ground traffic—tasks typically handled by separate staff.[reference:17][reference:18]
In Nashville, the numbers are particularly stark. The airport is one of the 30 busiest in the country but has only 28 controllers of the 52 it's allotted. Controllers at Nashville typically work schedules that require 10 controllers on the day shift and 12 on the night shift, but the facility is typically staffing anywhere between seven to nine on the day shift and five to seven on the night shift. "It's incredible that they're even getting by with these numbers," said one veteran controller.[reference:19]
👥 The Staffing Crisis: Thousands Short and Getting Worse
Behind every near‑miss and every exhausted controller is a simple, brutal reality: the FAA doesn't have enough people. The agency is short approximately 3,000 controllers nationwide, with critical facilities in New York and Chicago running at just 80‑85% of target staffing levels.[reference:20][reference:21]
The shortage has cascading effects. The National Air Traffic Controllers Association (NATCA) reports that over 40% of certified controllers are working 10‑hour days, six days a week. Many controllers have to request time off a year in advance, and when emergencies arise, they resort to using sick leave just to get days off.[reference:22][reference:23]
"The airport's busier than it has ever been, yet you're talking about a number of air traffic controllers that's as low as it's ever been," said Woody Hatchett, who worked as a controller for 12 years. "I think just about every controller that you talk to will tell you, 'Yeah, we're short staffed, we're working six days a week, we're tired.'"[reference:24]
The FAA is predicting it will lose 6,800 controllers before the end of 2028—a staggering number that will only worsen the crisis. Out of 8,000 applications from the most recent hiring push, only about 2% will end up as certified controllers. The training pipeline takes three to five years, meaning there is no quick fix.[reference:25]
💡 Analyst Perspective: The Morale Crisis
Staffing shortages aren't just a numbers problem—they're a morale problem. Controllers report feeling abandoned by leadership. One controller at a Midwest facility told NPR: "The morale just really plummets at that point. Honestly, it's more demoralizing than if they weren't talking about us at all." The FAA has focused on long‑term equipment upgrades and hiring goals, but controllers say nothing is being done to address their immediate quality‑of‑life concerns.[reference:26]
😴 The Rest Rule Flip‑Flop: 12 Hours, Then 10, Then Confusion
Perhaps nothing illustrates the FAA's muddled approach to fatigue better than its handling of rest requirements. In 2024, after years of pressure, the FAA and NATCA reached an agreement mandating 10 hours off between shifts and 12 hours off before and after a midnight shift. It was hailed as a major step forward.[reference:27]
Then, in July 2025, the FAA quietly changed course. Citing the need for "staffing flexibility," the agency reached a new agreement with NATCA to reduce the mandatory off‑duty period before a midnight shift from 12 hours to 10 hours. "The FAA and NATCA have agreed to change the requirement for a 12‑hour off‑duty period before a midnight shift to 10 hours, which aligns with industry rest standards," the FAA said in a statement.[reference:28][reference:29]
This reversal was driven by the staffing shortage. With thousands of positions unfilled, the FAA simply couldn't afford to give controllers the rest they needed. The agency has introduced incentives to shore up the workforce—increased pay for trainees, cash bonuses for controllers who accept positions in undesirable regions, and lump‑sum payments for older controllers who delay retirement. Transportation Secretary Sean Duffy has also used his authority to grant exemptions allowing "exceptional" controllers to work past the mandatory retirement age of 56, up to age 61.[reference:30]
🏛️ The 2025 Government Shutdown: Unpaid and Exhausted
In October 2025, the situation deteriorated further when a government shutdown forced air traffic controllers to work without pay. As essential workers, controllers were required to report for duty despite not receiving paychecks. Faced with mounting expenses, many took second jobs to cover their bills—cutting into the sleep they desperately needed. Others faced stress‑induced insomnia from unpaid bills and job uncertainty.[reference:33]
The effects were immediate and severe. Staffing shortages caused temporary ground stops at major airports, including a two‑and‑a‑half‑hour closure at Los Angeles International Airport. Some air traffic control towers saw a shocking 50% reduction in staffing as unpaid workers called out sick. Between October 30 and November 9, 2025, more than 4,100 flights were cancelled due to controller staffing issues.[reference:34][reference:35]
The FAA was forced to issue an emergency order targeting a 10% reduction in flights at 40 high‑traffic airports across the country. "Even under normal conditions, irregular schedules, undiagnosed sleep disorders, and lifestyle factors contribute to fatigue‑related errors. Shutdowns amplify these dangers," one analysis noted.[reference:36][reference:37]
🔬 The Systemic Nature of the Problem
The fatigue crisis is not simply a matter of individual controllers being irresponsible. It is a systemic issue rooted in how the FAA schedules, staffs, and supports its workforce. A 2025 report from the National Academies of Sciences, Engineering, and Medicine recommended that the FAA "continue to increase air traffic controller hiring, improve training success rates, incentivize transfers from overstaffed to understaffed airports, and implement robust fatigue management systems and efficient shift‑scheduling tools."[reference:38]
Researchers have also explored "micro‑mitigations"—small interventions like chewing gum, peppermint, exercise, and even video games—to help controllers stay alert during shifts. But these are stopgap measures, not solutions to the underlying problem of chronic sleep deprivation.[reference:39]
A 2025 study on fatigue dynamics in air traffic control found that the progression of fatigue across morning, evening, and night shifts remains "largely underexplored." The research confirmed what controllers have been saying for years: fatigue is not just about how long you sleep the night before a shift; it's about the cumulative toll of working irregular hours over weeks and months.[reference:40]
📋 The 2026 Response: Too Little, Too Late?
In 2026, the FAA and NATCA continue to tinker with scheduling rules while the underlying staffing crisis festers. The agreement to reduce the pre‑midnight‑shift rest period from 12 to 10 hours took effect in fiscal year 2026. All other provisions—including the 12‑hour rest period following the midnight shift and 10‑hour rest periods between all other shifts—remain in effect.[reference:41]
Congress has approved $12.5 billion for air traffic control modernization, but nearly all of that money is slated to replace aging equipment and infrastructure. Controllers say the problems run much deeper than hardware. "There was nothing there to actually help current controllers in the short or the mid‑term," one controller said of the funding package.[reference:42][reference:43]
The FAA has also changed policy to require air traffic controllers to actively use radar to direct helicopters and planes around airports nationwide, rather than relying on pilots to see and avoid each other. This change was a direct response to the DCA crash, where the "visual separation" approach was found to have contributed to the accident.[reference:44]
📊 Air Traffic Controller Fatigue: 2011 vs. 2026
| Issue | 2011 Status | 2026 Status |
|---|---|---|
| Rest Between Shifts | 8 hours minimum | 10 hours between shifts; 12 hours following midnight shift (but 10 hours before) |
| Staffing Shortage | Recognized but not quantified publicly | ~3,000 controllers short; 6,800 expected to leave by 2028 |
| Overtime Burden | Present but less severe | 40%+ of controllers working 10‑hour days, 6 days/week |
| Fatal Accidents | None directly linked to fatigue | 67 killed in DCA collision; 2 killed in LaGuardia runway crash |
| Near‑Miss Frequency | Isolated incidents | 15,214 close‑proximity events in DCA airspace alone |
| Fatigue Monitoring | Basic oversight | Budget cuts eliminated proactive monitoring capabilities |
| Government Shutdown Impact | Not a factor | 2025 shutdown caused 50% staffing reductions, 4,100+ cancellations |
📌 The Bottom Line: Key Takeaways for 2026
🛏️ The Sleeping Controller Problem Never Went Away: What began as embarrassing incidents in 2011 has evolved into a systemic crisis. A NASA study found 70% of controllers have nearly dozed off while working, and fatigue is a contributing factor in over half of operational errors.
💥 The DCA Tragedy Was Preventable: The January 2025 mid‑air collision that killed 67 people was the direct result of "systemic failures" at the FAA. A single overwhelmed controller was managing 11 aircraft on two frequencies, and alerts warning of the collision were never communicated to pilots.
⚠️ Near‑Misses Are Now Routine: In March‑April 2026 alone, major near‑misses occurred in Nashville, John Wayne Airport, and LaGuardia. Controllers are working with skeleton crews and making errors that could have been catastrophic.
👥 The Staffing Crisis Is Worsening: The FAA is short 3,000 controllers and expects to lose 6,800 more by 2028. Over 40% of controllers work six‑day weeks with 10‑hour shifts. Morale is at rock bottom.
😴 Rest Rules Are Moving Backward: In a desperate bid for "staffing flexibility," the FAA reduced mandatory rest before midnight shifts from 12 hours to 10 hours—exactly the opposite of what fatigue science recommends.
💰 The Shutdown Made Everything Worse: The October 2025 government shutdown forced controllers to work unpaid, leading to 50% staffing reductions at some facilities and over 4,100 flight cancellations in just 10 days.
🔮 The Path Forward Is Unclear: Congress has approved $12.5 billion for modernization, but nearly all of it is for equipment, not people. Controllers say nothing is being done to address their immediate quality‑of‑life concerns.
🔔 Enjoy evidence‑based aviation safety analysis? Subscribe for free weekly updates — no spam, just insight.