The cause of the FAA's nationwide ground stop on 13 November has not been confirmed in any source this article could verify. If you want to know why your flight was held, the official explanation still has to come from the FAA, the Department of Transportation, or the contractor involved.
Early explanations of outages often change. Until an official account is published, treat any single cause you see quoted as provisional.
Where the official explanation is likely to come from
L3Harris has published a page titled as a statement on the 13 November ground stop. The page's existence suggests the company is connected to the event in some way, but its contents could not be read and checked for this article. Read it directly rather than relying on summaries of it, including this one.
Questions an official account should answer
When a statement does appear, check whether it answers these plainly:
- What failed, and was it equipment, software, or a procedure?
- Was the failure planned work that went wrong, or something unexpected?
- Who was responsible for the system involved?
- What has been changed so it does not happen again?
If a statement skips one of these, that gap is worth noticing. Compare what the company says with what the FAA or DOT says, and treat the government account as the official one if they differ.
Are flights still delayed?
There is no confirmed information here on whether delays have cleared. Your airline's app or flight status page is the most reliable place to check a specific flight, since it reflects your booking rather than the national picture.
If your trip was disrupted, keep your booking confirmation and any messages from the airline. Whatever the final cause turns out to be, you will need those records when asking about rebooking or refunds.
What to watch next
The single thing to watch is a formal statement from the FAA or the Department of Transportation naming the cause. That account, alongside the L3Harris statement, is what will settle what actually happened.