TBNTech
FAA orders third nationwide ground stop in its history
Publication: Ars Technica
Author: Eric Bangeman
Source published: 13/11/2026, 23:17:38 UTC
Briefing created: 13/11/2026, 23:30:09 UTC
Based on a feed excerpt; full article content has not been acquired. Source evidence retrieved 13/11/2026, 23:28:24 UTC.
Briefings
The Federal Aviation Administration issued a nationwide ground stop on November 13, 2026, halting all departures from US airports due to a reported telecommunications outage affecting Air Route Traffic Control Centers. Secretary of Transportation Sean Duffy announced the action on X, while Homeland Security Secretary Markwayne Mullin clarified the ground stop was not a security threat but a precautionary measure. The FAA promised updates as the issue was resolved, and incoming international flights would be handled case-by-case.
Key points
- The FAA halted all departures from US airports on November 13, 2026, citing a telecommunications outage impacting Air Route Traffic Control Centers.
- Homeland Security Secretary Markwayne Mullin confirmed the ground stop was not a security threat but a precautionary measure due to the FAA's internal communication issues.
Context
This is a telecommunications outage out of the FAA, not a security threat, according to Homeland Security Secretary Markwayne Mullin. The FAA promised updates as the issue was resolved, and incoming international flights would be handled case-by-case. This is a telecommunications outage out of the FAA, not a security threat, according to Homeland Security Secretary Markwayne Mullin. The FAA promised updates as the issue was resolved, and incoming international flights would be handled case-by-case.
Limitations
Evidence is limited to statements from FAA and DHS officials regarding the cause and scope of the ground stop. Specific details on the duration of the outage, the number of airports affected, or the timeline for resolution are not provided.
Generated by Bittrees-hosted qwen35-2b sha256:aaf42c8b7c3c on 13/11/2026, 23:30:09 UTC. Based on publisher-provided feed evidence; may not cover the full original article. Check the source for details.
View archived briefing on IPFS
bafybeifojvnqjf7zqnznzcdiwwg6apcddgrhgyyn4e6kuu4xj5u7q274c4