The Four-Hour Ground Stop: The Questions L3Harris Board Directors Should Be Asking

On Friday, November 13, 2026 America’s aviation system experienced the kind of event corporate directors are supposed to think about before it happens. A nationwide FAA ground stop lasted roughly four hours, disrupting thousands of flights across the country. NPR reported nearly 25,000 delays and more than 9,000 cancellations on Friday, citing FlightAware data.
The incident immediately became an operational story. But it also may become a corporate governance story.
L3Harris Technologies, a longtime FAA contractor, was performing work at an FAA location as part of a transition from aging copper telecommunications infrastructure to fiber when the problem occurred, according to Transportation Secretary Sean Duffy. Duffy said investigators were still trying to determine whether the problem involved contractor error or faulty equipment. FAA Administrator Bryan Bedford also said there was no evidence that the disruption was caused by anything nefarious or related to artificial intelligence.
That distinction matters because it would be premature to assign responsibility before the investigation is complete. But boards do not have to wait for an investigation to ask a different question: Did the governance and risk-management system surrounding this work function as it should have? That is a question worth considering not only at L3Harris, but in every boardroom responsible for mission-critical infrastructure.
The Event Changes the Governance Question
Before Friday, directors might reasonably have viewed FAA telecommunications modernization primarily as a major government program involving technology, execution, customer relationships, and contract performance. After Friday, the potential governance significance is much harder to miss.
According to Duffy, the disruption began while work was being performed at a remote FAA location transitioning telecommunications technology from copper to fiber. Investigators were examining an error that began flooding other routers in the air traffic control system. He also said the routers at the facilities dated to 2001.
That raises a fundamentally different board question. It isn’t simply whether the project is on schedule and within budget. It is:
What could happen if something goes wrong during the transition?
Good governance requires directors to distinguish between ordinary execution risk and risks that, even when arising from seemingly routine work, could have exceptionally broad consequences.
This Wasn’t an Exotic Technology Problem
One of the most striking aspects of the emerging account is how ordinary the underlying work sounds. Duffy characterized the transition from copper to fiber as straightforward work and noted that institutions across America have been making similar transitions for decades.
Yet that makes the governance question more interesting, not less. Boards naturally focus attention on novel technologies, cyberattacks, geopolitical threats, artificial intelligence, and other visibly emerging risks. But a significant operational event can also begin with something much more mundane: a routine change to an aging system that has unexpectedly large consequences.
For directors, there is an important lesson here: Technical complexity does not necessarily determine operational consequence. Something technically routine can still deserve significant oversight when it touches critical infrastructure.
The Board Should Not Be Engineering the Network
None of this means L3Harris directors should have been reviewing router configurations or approving individual network cutovers. That isn’t the board’s job. The board’s responsibility is oversight, which means making sure management understands the critical risks and has appropriate safeguards in place.
For a mission-critical modernization effort, directors should be asking management questions such as:
What are the most consequential failure scenarios?
Could a problem at one location propagate through a larger network?
How has management tested that assumption?
What safeguards prevent a routine change from becoming a systemic event?
What independent verification exists?
What is the rollback strategy if a transition fails?
How quickly could operations be restored?
Which risks have been elevated through the enterprise risk-management process?
What events would trigger escalation to a board committee or the full board?
These questions don’t require directors to become engineers. They require directors to understand consequence. Friday’s disruption illustrates why that distinction matters. According to NPR, the FAA experienced intermittent outages involving radar and communications before the nationwide ground stop. The aviation system was operating again Saturday morning, although cancellations and delays continued.
The Most Important Question: “What Happens If We’re Wrong?”
Boards receive enormous amounts of information. Dashboards show schedules, budgets, milestones, risks, customer satisfaction, compliance metrics, and operational performance. Those tools are useful, but sometimes one question is more powerful than an entire dashboard:
What happens if we’re wrong?
Suppose testing says a transition is safe. What happens if it isn’t? Suppose engineers believe a failure will remain isolated. What happens if it doesn’t? Suppose redundancy is expected to work. What happens if the assumptions underlying that redundancy prove incorrect?
The board does not need to determine the technical answer. It needs confidence that management has asked these questions, tested important assumptions, challenged the answers, and prepared for the consequences. That seems particularly relevant after Friday. Duffy said investigators were examining how an error associated with work at a remote location began affecting other routers in the air traffic control system. Whatever the investigation ultimately determines about responsibility, the scale of the resulting disruption makes propagation risk an important issue for directors to examine.
The ERM Question
There is an important distinction between whether a company has risk-management processes and whether those processes successfully elevate the right risks. The governance question for L3Harris therefore shouldn’t be framed simply as whether the company had Enterprise Risk Management.
The more useful question is: How did the risks associated with work on critical FAA infrastructure move through management’s risk processes and ultimately reach the board?
Was the possibility of a widespread telecommunications disruption considered? If so, how was its potential severity assessed? What mitigation measures were presented? Were underlying assumptions independently challenged? And at what point would the potential consequence become significant enough to warrant board-level attention?
Those questions cannot be answered simply by pointing to the existence of corporate policies or board committees. They require examining how risk information actually moved through the organization before the event. This distinction matters for every board. Having an ERM process is not necessarily the same as identifying every important risk. Identifying a risk is not necessarily the same as appreciating its consequences. And reporting a risk is not necessarily the same as ensuring directors understand its significance.
A Warning Against Hindsight Governance
There is a danger in evaluating boards after something goes wrong. Bad outcomes do not automatically mean bad governance. No board can eliminate every operational failure, and no risk-management system can anticipate every equipment malfunction or human mistake. Judging governance exclusively by outcomes would create an impossible standard.
The better question is whether the governance process was appropriate before the outcome was known. Did directors receive the information they needed? Were important assumptions challenged? Were high-consequence scenarios considered? Did management’s risk reporting communicate the potential magnitude of failure? Were escalation mechanisms appropriate?
Those are fair questions regardless of what the investigation ultimately concludes. That distinction is especially important here because responsibility had not been established as of Saturday morning. Duffy said investigators were still trying to determine whether the problem involved contractor error or faulty equipment. NPR also reported that L3Harris had not immediately responded to its request for comment.
A Bigger Lesson for Boards
The significance of the FAA incident extends beyond L3Harris. Companies today frequently operate systems and infrastructure upon which customers, governments, and other organizations depend. That changes the way boards should think about operational risk.
A project does not necessarily need to be one of a company’s largest sources of revenue to merit serious board attention. Directors should also consider the consequences that could follow if a system, service, or infrastructure project fails. Operational consequence can matter just as much as financial size.
Friday provided a vivid example. NPR described the event as only the second nationwide ground stop since September 11, 2001. The previous nationwide disruption of similar scale occurred in 2023, when an outage of the FAA’s NOTAM system grounded U.S. flights. The FAA later determined that contract personnel had inadvertently deleted critical files in that earlier incident.
There is a useful governance parallel. In both cases, an apparently operational or technical problem had consequences far larger than the immediate activity that preceded it. That is precisely the type of disconnect directors should be trained to recognize.
What L3Harris Directors Should Ask Now
The investigation will focus on technical responsibility. The board should be conducting a different review. The question shouldn’t simply be, “Who should we blame?” A more useful question is, “What did our governance system tell us before this happened?”
Directors should want to understand:
How this risk was identified and classified.
How it moved through the company’s risk-management process.
What assumptions management made about the possibility of broader network disruption.
Whether those assumptions were independently challenged.
What information reached the appropriate board committee or the full board.
Whether the board’s reporting thresholds appropriately captured high-consequence operational risks.
What other programs involve similar dependencies.
The seventh question may ultimately be the most important. Boards shouldn’t examine major failures simply to understand the event that already occurred. They should use them to identify vulnerabilities that could produce the next major event.
The Real Governance Test
The investigation may ultimately identify contractor error, faulty equipment, some combination of factors, or another cause. As of Saturday morning, federal officials had not reached that conclusion. Those findings will matter, but the corporate governance lesson doesn’t depend entirely on determining technical fault.
The deeper issue is whether directors overseeing companies responsible for critical infrastructure understand how apparently routine operational decisions can create extraordinarily large consequences.
Governance is often discussed in terms of board composition, independence, compensation, succession, and shareholder rights. Those things matter. But sometimes the clearest test of governance comes from a much simpler question: When management changes something the country depends upon, does the board understand what could happen if the change goes wrong?
For L3Harris, that is now more than a theoretical question.
Sources
NPR, November 14, 2026: Ava Berger and Joel Rose, “FAA blames Friday’s ground stop on ‘equipment issue’ during telecoms network upgrade.” Reporting includes comments from Transportation Secretary Sean Duffy and FAA Administrator Bryan Bedford concerning the copper-to-fiber work, the ongoing investigation, the router issue, and the nationwide flight disruption.
Federal Aviation Administration: FAA materials and statements concerning the U.S. air traffic control system and modernization of its infrastructure.
L3Harris Technologies: Public corporate governance materials, including the Audit Committee charter and board committee disclosures, for information concerning the company’s governance structure and risk oversight responsibilities.
See Major Corporate Event Preparedness and boardroom simulations Liquidity Crisis Pressure Test (TM) and Cyber Crisis Pressure Test (TM)





Comments