Tech
United Airlines system outage disrupts departures just days after the big ground stop
Publication: The Verge
Author: Richard Lawler
Source published: 16/11/2026, 22:54:59 UTC
Briefing created: 16/11/2026, 23:27:07 UTC
Based on a feed excerpt; full article content has not been acquired. Source evidence retrieved 16/11/2026, 23:16:25 UTC.
Briefings
United Airlines experienced a system-wide IT outage on November 15, 2026, at Newark Liberty International Airport, disrupting departing flights just days after a nationwide air traffic control issue. The airline is working to restore operations but lacks specific details about the technical failure. This incident occurred following a global Microsoft Outlook shutdown and a previous FAA radar communication halt.
Key points
- United Airlines' departing flights were disrupted at Newark Liberty International Airport on November 15, 2026, due to a system-wide IT outage affecting the airline's operations.
- The outage coincided with a global Microsoft Outlook shutdown and a prior FAA air traffic control communication issue that halted takeoffs nationwide.
Context
United Airlines' system outage occurred on November 15, 2026, at Newark Liberty International Airport, disrupting departing flights just days after a nationwide air traffic control issue. The incident followed a global Microsoft Outlook shutdown and a previous FAA radar communication halt, indicating a broader technological disruption affecting multiple sectors.
Limitations
Specific technical details about the United Airlines outage are unavailable. The article does not provide the exact duration of the disruption, the number of affected flights, or the specific nature of the IT failure. The source is a news report citing social media posts and a third-party link, which may not contain complete operational data.
Generated by Bittrees-hosted qwen35-2b sha256:aaf42c8b7c3c on 16/11/2026, 23:27:07 UTC. Based on publisher-provided feed evidence; may not cover the full original article. Check the source for details.
View archived briefing on IPFS
bafybeigcpdhzr6nn2mhrxhdqmymcbusnqh6267pmjsjf2fbedychzhtira