Signal 01
Canada's Systems Were Working. Why Was Canada Still Grounded?
A major disruption to American air traffic control operations on November 13 affected thousands of flights and created consequences for Canadian travellers and businesses, even though Canada's own air navigation systems remained operational. The U.S. Federal Aviation Administration ordered a nationwide ground stop following communications failures affecting air traffic control operations. American officials identified problems involving aging network infrastructure and possible interactions between older and newer technologies. They reported no evidence that artificial intelligence or a cyberattack caused the disruption. For Canada, the larger issue is not simply what failed in the United States. It is what the incident reveals about our dependence on critical infrastructure beyond our borders. Canadian systems can be secure, operational and functioning as intended while Canadian businesses remain vulnerable to failures in foreign networks, transportation systems and essential services. The incident raises an important question for Canada's economic security and national resilience: how effectively are we identifying and managing the infrastructure dependencies we do not own or control?
What happened
On November 13, 2026, the U.S. Federal Aviation Administration ordered a nationwide halt to departing flights after communications problems affected the reliability of air traffic control operations. U.S. Transportation Secretary Sean Duffy attributed the disruption to aging communications infrastructure, including network switches and routers that reportedly became overloaded with data. The equipment began producing inconsistent information, creating uncertainty for air traffic controllers. The FAA stopped departures while technicians worked to restore stability. The disruption affected thousands of flights and created delays and cancellations extending beyond American airports. Canadian flights travelling to, from or through U.S. airspace were affected. NAV CANADA indicated that Canada's own air navigation systems remained operational, but the interconnected nature of North American aviation meant Canadian airlines and airports could not avoid the consequences. The ground stop was subsequently lifted, although delays continued as airlines and air traffic systems worked to restore normal schedules. The incident occurred during an ongoing effort to modernize American air traffic control infrastructure. Officials indicated that interactions between newer equipment and aging network systems may have contributed to the failure. The precise technical sequence remains subject to investigation. Questions were initially raised about a recently introduced AI powered air traffic management tool. American officials subsequently indicated that the AI system was not responsible. Authorities also reported no evidence of a cyberattack. The important development is therefore not an AI failure or a cybersecurity breach. It is a major operational disruption involving essential infrastructure that affected organizations and countries beyond the system where the failure originated.
Why it matters for Canada
Canada's relationship with the United States is one of the most economically important and technologically interconnected relationships in the world. Our aviation, transportation, electricity, telecommunications, financial services, manufacturing supply chains and digital platforms depend on infrastructure operating on both sides of the border. That interdependence creates significant economic advantages, but it also creates vulnerabilities that cannot be addressed exclusively through domestic investment or cybersecurity controls. The November 13 aviation disruption illustrates the difference between protecting national infrastructure and ensuring national resilience. NAV CANADA can operate its systems safely and effectively, but it cannot independently guarantee the availability of American airspace. Canadian airlines can maintain reliable aircraft and operational systems while still experiencing disruptions originating in another country's infrastructure. The same principle applies beyond aviation. A disruption affecting American telecommunications, financial processing, cloud infrastructure, transportation networks or energy systems could affect Canadian organizations even when their own systems remain fully functional. For Canadian governments, this raises questions about whether infrastructure strategies adequately account for international dependencies and whether contingency planning extends beyond systems directly under Canadian jurisdiction. For businesses, the implications are immediate. Airlines, logistics companies, manufacturers, financial institutions and technology providers may have strong internal security, reliable systems and comprehensive continuity plans, yet still be unable to operate when an essential external service becomes unavailable. This does not mean Canada should attempt to duplicate every American system or isolate itself from international networks. Such an approach would be economically unrealistic and would undermine many of the advantages created by integration. Instead, Canada needs a clearer understanding of where critical dependencies exist, how failures can spread across borders and which alternatives can realistically be activated when external systems become unavailable. The incident also raises important questions about technology modernization. New infrastructure must interact with older systems that may remain essential for decades. Introducing advanced technology without understanding these interactions can create unexpected operational vulnerabilities. This becomes increasingly relevant as Canadian organizations adopt artificial intelligence, automation, cloud computing and interconnected digital platforms. A system can be secure, compliant and functioning exactly as intended, yet the business depending on it can still be unable to operate. That is a fundamentally different way of understanding operational risk.
What CCN sees
CCN sees the aviation disruption as an important warning about the growing distance between technological modernization and operational resilience. Governments and businesses are investing heavily in artificial intelligence, automation, cloud computing and interconnected infrastructure. These investments promise improvements in productivity, efficiency and service delivery. But new technology does not automatically eliminate the weaknesses of the systems on which it depends. Modernization can introduce additional complexity when new applications, equipment and platforms must interact with aging communications networks, databases and operational processes. The reported interaction between newer equipment and the FAA's legacy infrastructure deserves particular attention. The final investigation will determine the precise technical causes, but the broader lesson is relevant to Canadian organizations today. Technology investments cannot be evaluated solely on whether the new technology works. Organizations must also understand how it behaves within the larger environment, especially when older systems remain essential to operations. This is particularly important as organizations introduce AI agents capable of making recommendations, interacting with applications and executing tasks. The FAA incident should not be characterized as an AI failure. Nevertheless, it illustrates why integration testing, operational visibility, human accountability and resilience become more important as technology environments grow increasingly complex. For Canada, there is also a strategic dimension. National sovereignty is frequently discussed in terms of domestic ownership, data residency, industrial capacity and independent decision making. These considerations matter, but they do not fully describe the reality of modern infrastructure. A country may own and control an important system while remaining dependent on foreign networks, suppliers, communications infrastructure or operational services. Sovereignty without an understanding of dependency can create a false sense of resilience. CCN believes Canada needs a more comprehensive approach connecting cybersecurity, operational resilience, technology modernization and economic security. The objective should not be technological independence at any cost. It should be informed interdependence, supported by visibility into critical dependencies, credible alternatives and the ability to maintain essential operations when external systems fail. The measure of success should not simply be how much money is invested or how advanced the technology becomes. It should include whether essential services can continue when something goes wrong. Canada's systems may be working. The question is whether Canada can keep working when someone else's systems are not.
What leaders should consider
Canadian government and business leaders should examine how well they understand the infrastructure supporting their operations, particularly systems outside their direct control. Which essential services depend on infrastructure located outside Canada, and do organizations know who owns and operates those systems? If an external network, supplier or operational platform becomes unavailable for several hours or several days, which business functions would stop, what financial consequences would follow and which alternatives could realistically be activated? Leaders should also reconsider how modernization projects are evaluated. Testing whether new technology performs its intended function is not sufficient. Organizations must understand how that technology interacts with existing infrastructure, including systems that may be decades old but remain operationally essential. Boards and executive teams should determine whether business continuity exercises include simultaneous failures across suppliers, transportation networks, communications systems and digital platforms. Organizations should review whether supplier contracts and service agreements provide sufficient transparency into infrastructure dependencies, recovery expectations and operational contingency arrangements. For government institutions, an additional question deserves attention: are Canada's infrastructure and economic security strategies coordinated sufficiently to identify vulnerabilities that cross departmental, sectoral and international boundaries? Leaders should also distinguish cybersecurity from operational resilience. Strong cybersecurity controls are essential, but they cannot prevent every equipment failure, network outage or external infrastructure disruption. These are not simply technical questions. They concern business continuity, public confidence, economic competitiveness and national security.
People to Watch
Sean Duffy, U.S. Secretary of Transportation; senior FAA leadership; NAV CANADA executive leadership; Transport Canada officials; Canadian critical infrastructure executives; Canadian transportation and aviation industry leaders.
Organizations to Watch
Federal Aviation Administration; U.S. Department of Transportation; NAV CANADA; Transport Canada; Canadian Air Transport Security Authority; Air Canada; WestJet; Canadian Airports Council; Canadian Centre for Cyber Security. Watch for the FAA's final technical investigation into the communications failure, including the precise cause of the network overload and whether modernization activities contributed to the disruption. Monitor how the United States responds through infrastructure investment, replacement of aging equipment, network redundancy and improvements to air traffic control reliability. In Canada, watch whether NAV CANADA, Transport Canada and aviation operators identify opportunities to strengthen cross border coordination, operational contingency planning and communications resilience. More broadly, monitor whether Canadian governments and businesses begin measuring their dependence on foreign infrastructure more systematically, particularly in telecommunications, energy, cloud computing, financial services and transportation. An important emerging signal will be whether resilience becomes a measurable requirement in technology and infrastructure investment decisions rather than an assumption made after systems have been deployed.