Bookmarks

    Nothing saved yet. Use the bookmark on any article. Bookmarks are kept on this device only: they stay private and work without an account.

    Settings

    Appearance

    Reading mode

    Font size

    Content width

    Line spacing

    Keyboard shortcuts

    /
    Search
    j k
    Next / previous story
    ← →
    Previous / next section (columns)
    b
    Bookmarks
    s
    Settings
    r
    Columns / scroll
    t
    Light / dark

    Saved in this browser only.

    Ping2Prompt
    Subscribe to the Weekly Brief Sign in
    Ping2Prompt story card: FAA ground stop: White House forms tiger team to prevent a repeat. Medium, Trending in tech.

    FAA Telecommunications Infrastructure instability led to nationwide ground stop

    Automated source check

    Update (2026-11-18): This article now covers everything published about the FAA ground stop (22 sources), merged from separate reports.

    Nationwide FAA ground stop halted U.S. departures on Nov. 13

    The FAA ordered a nationwide ground stop on Friday, Nov. 13, grounding U.S. departures after router and networking instability disrupted its systems. CNBC puts the order before 4 p.m. ET, while CBS says it hit just after 3:30 p.m. and does not give a time zone.

    CNBC reports the stop was lifted after 8 p.m. ET, making it the longest halt to U.S. departures since 9/11. Wired says it lasted five hours, while CNBC and Skift say a little over four.

    The White House has formed a tiger team to prevent a repeat, and CBS reports its first meeting was held the Monday after the stop. Before the stop, Transportation Secretary Duffy asked Congress for $30.1 billion in funding, and on Friday he raised the request to $50 billion, according to Wired.

    Thousands of flights cancelled, with counts that differ by source

    Outlets report different totals, each tied to a different period or data provider:

    • Wired, citing FlightAware, says more than 6,300 flights were cancelled and 9,500 delayed by the time the stop was lifted.
    • CNBC, citing FlightAware, reports about 18,000 U.S. cancellations from Friday through Monday morning, with hundreds of thousands of travelers stranded.
    • NBC News says about 20,000 flights were affected, and 12,000 could not recover after the order ended.

    No single official total of cancellations is confirmed. Cirium data cited by CNBC shows American cancelled 5,367 flights, about 22% of its schedule, and Delta cancelled 3,434, or 17%. Southwest and United each lost more than 16%. CBS says around 3,500 flights were airborne when the stop hit.

    Airlines waived change fees and fare differences, and paid pilots and flight attendants extra to ease delays, CNBC reports. Raymond James estimates the four largest U.S. airlines could face a combined fourth-quarter hit of $370 million to $964 million. Its estimate for American runs from $136 million to $354 million, and for Delta from $94 million to $244 million.

    Bedford, L3Harris and Mullin address the ground stop

    FAA administrator Bedford said the agency would not accept any risk that the instability could cut a sensor's connection to aircraft, because it had not found the root cause. L3Harris said it is supporting the FAA investigation and, with partners, has finished more than 70% of the planned copper-to-fiber conversion of airspace communications.

    Mullin said there were no indications of a cyberattack, though he added that certainty is not complete. CBS reports intelligence agencies preliminarily ruled out nefarious activity after finding no concerning chatter or pings.

    Trump said he takes no responsibility for the stop and praised Duffy's handling of it. Former transportation secretary Pete Buttigieg said the administration has not explained why its repair work set off the worst FAA communications breakdown this century. Reps. Rick Larsen and Andre Carson said their committees will hold the administration accountable.

    Officials point to routers in Arkansas and Texas

    Bedford said the FAA could not identify a root cause and described instability it could not explain, with routers and networking equipment appearing involved. CBS reports a preliminary FAA investigation indicated that a router being replaced in Arkansas caused the problem.

    Duffy said the failure began during work to replace copper wire with fiber in El Dorado, Arkansas. He said a router in Amarillo, Texas, swapped in about three weeks earlier, began flooding the system when the Arkansas router was switched on. Duffy also blamed old switches, old routers and a data overload, and said a legacy system was involved.

    Mullin attributed the problem to patches added as new equipment went in, saying the new technology overwhelmed the older system. Trump said very old equipment had a "heart attack." Officials cited Cisco and L3Harris Technologies products and services, and Duffy said the Arkansas and Texas routers are at an L3Harris lab in Florida for examination.

    Root cause, tiger team findings and funding remain open

    Neither the FAA nor other officials have established a definitive root cause. No date has been given for the end of the investigation, and no official has said when the tiger team will report or what measures it will adopt. Whether Congress will approve the $50 billion request is not confirmed, and it is not stated whether the two routers in Florida have yielded findings.

    A copper-to-fiber upgrade of the FAA network

    The FAA Telecommunications Infrastructure network is the private backbone for air traffic control, and it is being moved from copper wire to fiber-optic cable. L3Harris operates the legacy system until the upgrades are in place. A September GAO report said the FAA could be putting speed ahead of cost and air traffic disruptions, and that it lacks a well-documented life-cycle cost estimate and an integrated master schedule.

    Sources


    This story was produced with AI assistance from the sources listed above and fact-checked against them before publication. Read our editorial methodology and the corrections log. Spotted an error? Email [email protected].

    Continue

    Share on Bluesky · Mastodon · Email ·

    Discussion