Ground Stop Action Guide

by Citizen Action Guide www.citizenactionguide.org

A citizen's guide, not a government website. Facts as of Nov. 16, 2026.

Text size

Call and write before

Wednesday, Nov. 18, 10 a.m. Eastern

That leaves today and tomorrow.

That morning a House committee questions the Homeland Security Secretary, one of the officials who spoke to the public during the ground stop. Calls that arrive before then can shape the questions members ask.

On Nov. 13, the government went silent for hours. Don't wait to be told. Speak up first.

On Friday, Nov. 13, 2026, the government stopped every departure in the country for more than four hours. Many travelers found out from their phones, their relatives and strangers. The officials had the facts. They had no reliable way to get them to the people sitting in airports and on planes.

The fix is simple and costs almost nothing. Congress can write it into the spending bill it must pass by Dec. 11. But members of Congress act on what they hear from the people they represent, and right now most of them are hearing about money and equipment, not about the people left in the dark.

Your first exercise: communicate the way the government did not

The failure on Nov. 13 was a failure to speak up clearly and on time. So start by doing what the officials did not. Call your two senators and your representative before Wednesday morning, then send the same message in writing. Be clear, be brief, and ask for an answer.

What you ask for: a simple rule for the Federal Aviation Administration (FAA). When flights are stopped nationwide, tell the public within 15 minutes, give an update every 30 minutes, and keep one official record with the time on every entry.

What you can do

This takes about 15 minutes. You do not need to be an expert. You only need to be a constituent, which means a person who lives in the member's state or district.

Do steps 2 to 4 before Wednesday, Nov. 18, at 10 a.m. Eastern. Offices are open today and tomorrow. If you read this later, call anyway: the next deadline is Dec. 11.

  1. Read the fix

    Two minutes. The seven-point fix is here. You will then know what you are asking for.

  2. Find your three members of Congress

    Everyone has two senators and one representative. Look yours up here, or call one number and ask to be connected.

  3. Call each office before Wednesday and read the script

    About two minutes a call. The script is here. A staff member or a voicemail will take your message. Both count. Calls before the Nov. 18 hearing count the most.

  4. Question

    Were you, or someone close to you, stuck in an airport or on a plane on Nov. 13?

    Yes

    Say so in one sentence when you call. Then file a complaint with the U.S. Department of Transportation. It goes on the official record.

    Open the official complaint form

    No

    Go on to step 4. Your call counts just the same.

  5. Email the same message, the same day

    Congress takes email through a message form on each office's website. Copy the written message and paste it in. A written message gets a written reply, and it leaves a record.

  6. Call the committees

    Before Wednesday, call the House Homeland Security Committee, which holds the Nov. 18 hearing. Then call the two committees that handle air travel for the whole country. Their numbers are here.

  7. Pass it on to three people

    Send this page to three people who fly, or who have family that flies. Offices count how many people call about the same thing.

  8. Call again next week

    Ask what the member has decided. Keep calling until Dec. 11, when Congress must pass its next spending bill. In January a new Congress begins. If the rule is not in place by then, start again.

The whole plan: learn the ask, reach your own three members by phone and in writing, add the two committees, bring in three more people, and follow up weekly.

Have you worked in aviation, at an airport, for an airline, or with computer networks? Say so when you call. Offices listen closely to people who know the work.

Find your members of Congress

Everyone has three: two senators and one representative. There are two easy ways to reach them.

The easiest way: one phone number

Call the U.S. Capitol switchboard. Tell the operator your state and ZIP code, and ask for your senator's office or your representative's office. The operator will connect you.

(202) 224-3121

Offices answer on weekdays during business hours, Eastern time. At other times, leave a voicemail. It counts.

Or look them up here

Not sure which House district you live in? The House has an official ZIP code lookup.

About email addresses

Congress does not publish a list of members' email addresses. Each office takes written messages through a form on its own website. The “Write to this office” links above take you to those websites. Look for the word “Contact” at the top of the page.

Names and phone numbers were copied from the official House and Senate directories on Nov. 16, 2026. A new Congress begins in early January 2027, and some names will change then.

What to say

A staff member or a voicemail will answer. That is normal. Their job is to write down your message and pass it on. Be polite and brief. Give your real name and where you live.

On the phone

Hello. My name is ______, and I live in ______ (your town and ZIP code). I am calling about the nationwide ground stop on November 13. Travelers in airports and on planes were left without clear information for hours. On Wednesday morning a House committee questions the Homeland Security Secretary, and I want my message on record before then. I am asking the Senator (or the Representative) to make sure any air traffic control funding bill requires the FAA to keep the public informed: a first notice within 15 minutes, an update every 30 minutes, and one official record with the time on every entry. It costs almost nothing, and it can be in place before the next outage. Will the Senator (or the Representative) support that? Please let me know. Thank you for taking my message.

If they ask which bill: “The Modern Skies Act. In the Senate it is S.5572. In the House it is H.R.10683.”

If your representative sits on the Homeland Security Committee (the directory above marks them), add one sentence: “On Wednesday, please ask the Secretary how the public will be told during the next outage, and when.”

If they ask something you cannot answer: “I don't know, but I can send you a page with the details.” That is a fine answer.

In writing (by email)

Send it the same day you call. Paste this into the message form on each member's website. Fill in the blanks. Offices need your name and address to confirm that you live in their state or district.

Subject: Require the FAA to keep the public informed during a ground stop Dear Senator (or Representative) ______, I live in ______ (your town and ZIP code). I am writing about the nationwide ground stop on November 13, 2026. Travelers in airports and on planes went hours without clear information. Many learned what was happening from their phones or from relatives. The FAA's official statement promised updates and then did not change. I am writing before the House Homeland Security Committee's hearing with the Homeland Security Secretary on Wednesday, November 18, so that my view is on record. The next outage could come during Thanksgiving travel. Please make sure that any air traffic control funding bill, including the Modern Skies Act (S.5572 and H.R.10683), requires the FAA to adopt a public-update standard within 90 days: 1. A first public notice within 15 minutes, in plain words. 2. An update every 30 minutes until flights resume. 3. One official record that shows every update with its time. 4. The same updates sent to airports, airlines and security checkpoints. Please also ask the Department of Transportation to restore status updates every 30 minutes for passengers held on aircraft. This costs almost nothing. It can be in place before the next outage. Will you support this? I would be grateful for a reply. Sincerely, (Your name, street address and phone number)

The people who decide

Start with your own three members. Offices give the most weight to people who live in their state or district. If you have more time, call these committee offices too.

Before Wednesday: the committee holding the hearing

House Homeland Security Committee

Questions the Homeland Security Secretary and the FBI's deputy director on Wed., Nov. 18, at 10 a.m. Eastern. Chaired by Rep. Andrew Garbarino (R-N.Y.). Its senior Democrat is Rep. Bennie Thompson (D-Miss.). It has two staffs.

Republican staff: (202) 226-8417

Democratic staff: (202) 226-2616

The hearing page · Watch it live

The hearing covers threats to the country in general, not the ground stop alone. Members choose their own questions. Ask the committee to include one about how the public will be told during the next outage.

Any time: the committees that write aviation law

House Transportation and Infrastructure Committee

Writes the House's aviation laws.

(202) 225-9446

Senate Commerce, Science, and Transportation Committee

Writes the Senate's aviation laws. It has two staffs.

Republican staff: (202) 224-1251

Democratic staff: (202) 224-0411

Members who lead on this issue

If one of these people represents you, your call matters twice.

What happened

At 3:36 p.m. Eastern time, radar and radio links at air traffic control centers across the country started to falter. At 3:54 the FAA stopped all departures. This is called a ground stop. About 3,500 planes were in the air. Controllers brought every one of them down safely. Flights were allowed to leave again at 8:15 p.m.

Officials say the trouble began when a contractor installed a new router at a remote site, and that router flooded an older network with data. They report no sign of a cyberattack. The exact cause is still being investigated.

About 12,500 flights were canceled that day, by the FAA's count. The FAA notes that not all of those were caused by the stop.

What the public was told, and when

  1. 3:54 p.m.The FAA stops all departures. Its notice gives the reason only as “extraordinary circumstances and for reasons of safety.”
    No cause given
  2. About 4:00The FAA posts three sentences online. The last one reads: “We will provide updates.”
  3. 4:16The Transportation Secretary posts on X: a communication problem at the air traffic centers.
  4. About 5:00The Homeland Security Secretary tells reporters there is no sign of an attack, and that nothing has been ruled out.
  5. About 5:00Newark's airport has still made no announcement. One worker there hears the news from a passenger.
    No announcement
  6. 7:35At JFK, a traveler learns of the stop from Instagram. The boards still list flights as on time.
  7. 8:15Flights are allowed to leave again.
  8. About 8:30The first full briefing begins, more than half an hour late and after the stop is over.
    Delayed
  9. Sat. 11 a.m.The head of the FAA briefs the public for the first time.

What went wrong

  1. The official statement never changed.

    The FAA's statement that afternoon was three sentences long, and the last was a promise of updates. Saved copies of that page from 8:38 p.m., from 9:00 p.m. and from 1:57 p.m. the next day all show the same three sentences. The FAA did post on X, and it published a question-and-answer page two days later. The statement itself stood still.

    The FAA has done better before. During the last nationwide stop, in January 2023, its page logged new statements at 7:15, 8:15 and 8:50 a.m., each marked with its time. In February 2025 it promised airlines and other aviation businesses a notice every 30 minutes during an outage.

  2. Nobody said when the next update would come.

    Word arrived at about 4:00, 4:16, 5:00 and 8:30. None of those messages said when to expect the next one. People waited without knowing how long to wait.

  3. Every airport was on its own.

    Boston's Logan Airport used its loudspeakers. Newark had made no announcement after about an hour. LaGuardia later announced it was closing, and the agency that runs it then said not to take that literally.

  4. The public is missing from the plan.

    The FAA has a written plan for outages. It calls for notices to airlines and other aviation businesses, to the military and to airport authorities. We searched that plan for any step about telling passengers or the public and found none. If the FAA has such a step written down somewhere else, it should publish it.

  5. On a stuck plane, the rule is one announcement.

    Until 2021, airlines had to tell passengers on a delayed plane what was happening every 30 minutes. The Department of Transportation changed that. Now the rule guarantees one notice, once the delay passes 30 minutes. After that it is up to the airline. In 2024, airlines reported 437 domestic flights that sat on the ground for more than three hours, by the Bureau of Transportation Statistics’ count.

The fix

A public-update standard for nationwide stops. Seven points, none of them expensive.

  1. Tell people within 15 minutes, in plain words.

    What is happening. What kind of problem it is. What is not yet known. What travelers should do. When the next update will come.

  2. Give an update every 30 minutes.

    Even if nothing has changed. “No change yet” is still news to someone waiting at a gate.

  3. Speak with one voice.

    The FAA gives the updates. Security agencies add one line: whether there is any sign of an attack.

  4. Keep to the facts.

    Requests for money and arguments about blame can wait until the planes are moving.

  5. Reach people where they are.

    Send every update to airports, airlines and security checkpoints at the same minute, so it goes out on loudspeakers and screens.

  6. Bring back 30-minute updates on stuck planes.

    With the reason for the delay, if it is known.

  7. Keep the record.

    Leave every update online with its time. Publish a full timeline within three days and the cause within 30 days.

Who can do this

  • The head of the FAA can order most of it today.
  • Congress can require it with one paragraph in the aviation funding bill now before it. That bill, the Modern Skies Act, would spend $30.1 billion, about a third of it on air traffic control systems. It says nothing about keeping the public informed.
  • The Department of Transportation can restore the 30-minute rule on planes.

Why now

The Transportation Secretary estimates that a new network, if Congress paid for it today, would be ready in late 2028 or early 2029. He has also said to expect more outages until then. The equipment will take years. The plan for telling people can be ready in weeks.

To be fair

The people in charge did several things right, and they have reasons for what they did.

  • Controllers landed about 3,500 planes without an injury. The safety procedures worked.
  • Officials isolated the problem in a little over four hours and explained it the next morning.
  • The Homeland Security Secretary went on camera within about an hour to say there was no sign of an attack.
  • The Transportation Secretary says he does not want to give out information before it is certain.
  • When the Department of Transportation dropped the 30-minute rule on planes in 2021, it reasoned that repeated announcements add little when there is nothing new.

Our answer to the last two points is the same. People can handle “we don't know yet.” What they cannot handle is silence. Say what is known, say what is not, and say when you will speak again.

This page does not blame any one person, and it takes no side on how much money Congress should spend.

Dates to watch

Wed., Nov. 18, 10 a.m. Eastern
Call before this. The House Homeland Security Committee questions the Homeland Security Secretary and the FBI's deputy director. The ground stop is expected to come up. Watch it live.
Thu., Nov. 26
Thanksgiving. The week around it brings some of the heaviest air travel of the year.
Fri., Dec. 11
Congress must pass a spending bill by this date. The Transportation Secretary has named it as a chance to add air traffic money.
Early January 2027
A new Congress begins.

Common questions

Is this about one political party?

No. The last two nationwide stops happened under two different administrations, in January 2023 and in November 2026. The fix is a procedure. It applies no matter who is in office.

Will my call matter?

One call rarely changes anything. Many calls about the same specific request do. Offices keep a count of what constituents call about, and a short, exact request is easy to count.

What if I reach a voicemail?

Leave the message. Say your name, your town and your ZIP code, then read the script.

I am not good with computers. Can I do this by phone alone?

Yes. Call (202) 224-3121, tell the operator your state and ZIP code, and ask for each of your three offices in turn.

Why not just fix the equipment?

That work is under way and it should continue. It will take years. This fix can be done now, and it will still be needed after the new equipment arrives.

Who made this page?

A private citizen, with research help from Claude, an AI assistant made by Anthropic. The page is not connected to the FAA, any airline, any political party or any campaign. Every fact here comes from a source listed below. Please check them.

Sources

Every fact on this page comes from one of the sources below. A date in parentheses shows when a federal record was last checked. For every finding and its limits, read the full research file.

Official statements and records

News reports

← Back to the action guide

This is the full research file behind the action guide. It is written for reporters, congressional staff and anyone who wants every finding, its limits and its source.

Case file 001 — The Nov 13, 2026 ground stop: fixing how the public gets told

Public edition · Nov 16, 2026 · Fix drafted (v0.1)

Starting point: CNN (Brian Stelter, Nov 14), “'No answer': Messaging failures worsened the air traffic freeze and sowed distrust in government”

Read this first. Everything here comes from public reporting, official releases and federal records gathered three days after the event. The root cause is still under investigation and details will move. Items resting on one person's account are marked.

Who wrote this. A private citizen, with research and drafting help from Claude, an AI assistant made by Anthropic. It is not connected to the FAA, any airline, any political party or any campaign. Every claim names its source so that it can be checked.


1. Why this problem and not the bigger one

Two things failed on Nov 13. The equipment failure, in a telecom network of 1980s design, is a multi-year job costing tens of billions, and it already has the attention of the White House and Congress. The communication failure is small, cheap and has no owner: officials had facts and no dependable way to get them to people in terminals and on aircraft.

By the Transportation Secretary's own estimate, a new network funded today would be ready in late 2028 or early 2029, and he has said to expect more outages until then. So the communication plan is the only piece that can be in place before the next one.

2. What happened

3. What the public was told, and when (Friday, Eastern time)

Time What reached the public Source
3:54 p.m. The FAA's advisory to aircraft operators: all airports stopped “due to extraordinary circumstances and for reasons of safety.” No cause, no real end time (listed expiry: 11:30 p.m.). This wording became the headline. ABC, USA Today
About 4:00 Three sentences on faa.gov: communication problems at several en route centers, technicians investigating, and a promise: “We will provide updates.” CNBC, archived FAA page
4:16 Transportation Secretary on X: a communication issue at all en route centers; immediate updates promised. CBS, Newsday
About 5:00 Homeland Security Secretary, to reporters at the White House: a telecom outage, no indication of an attack, nothing ruled out, a possible link to the new AI tool being looked at. FAA on X: a temporary telecom outage; every flight accounted for. ABC, USA Today
About 5:00, Newark Still no airport-wide announcement. One staff member heard about the stop from a passenger. USA Today
7:35, JFK A traveler learns of the stop from Instagram while departure boards still list flights as on time. Newsday
7:45 → about 8:30 The scheduled briefing starts more than 30 minutes late, after the stop has ended. Officials told CBS a fix was minutes away and they did not want to interrupt it. CBS, ABC
8:15 Stop lifted. The FAA's operations site notes the cancellation around 8:30. DOT, USA Today
Sat. 11:00 a.m. First briefing that includes the FAA administrator; the router explanation is given. It starts late because of technical problems. ABC, CNN
Sunday The FAA publishes a question-and-answer page. FAA

4. Findings

1. The official record never moved. The FAA's statement page carried three sentences and a promise of updates. Archived copies from Friday 8:38 p.m., Friday 9:00 p.m. and Saturday 1:57 p.m. ET all show the same three sentences. As of Nov 16 the FAA's general-statements page still lists that Nov 13 entry and nothing later on the subject, and the original address now forwards to Sunday's Q&A.

Two comparisons from the FAA's own record:

So a timestamped running log and a 30-minute cadence are both existing FAA practice. Neither was used for the public on Nov 13.

Fair caveats: the 2023 failure built slowly overnight and the stop was shorter; on Nov 13 controllers were landing 3,500 aircraft at once. The FAA did post on X around 5 p.m. and did note the cancellation on its operations site. This finding rests on three archived snapshots, not a continuous record.

2. No clock. Updates arrived at about 4:00, 4:16, 5:00 and 8:30. None named a time for the next one. Duration estimates depended on where you stood: the advisory listed 11:30 p.m.; an announcement at San Francisco reportedly said at least six hours (second-hand, Boston Globe).

3. Several voices, shifting answers. The FAA, DOT and DHS each spoke. On the two fears that mattered most to the public, an attack or the new AI tool, the answer moved from not-ruled-out at about 5 p.m. to no-evidence at 8:30.

4. No last mile. Logan announced the stop over its loudspeakers. Newark had not after about an hour. Travelers at JFK, Dallas-Fort Worth, Los Angeles, Miami and LaGuardia describe learning from phones, relatives or strangers while boards showed flights on time or merely delayed. LaGuardia later announced it was closing; the Port Authority then said not to take that literally. Each airport and airline improvised.

5. The public is not in the contingency plan. The FAA's 2024 order on operational readiness and contingency planning (JO 1900.47G) requires notices to industry, the military, other FAA facilities and airport authorities. A keyword search of its text found nothing addressed to passengers, the press or the public. A separate FAA communications procedure may exist; none turned up. (Keyword search of the order, not a full read.)

6. A thin rule on aircraft. Since a 2021 amendment, federal rules require a single status notice once a tarmac delay passes 30 minutes; anything further is the airline's choice (14 CFR 259.4(c)(6)). Before that, carriers owed passengers status and cause every 30 minutes. DOT's 2021 reasoning: repeated notices add little when nothing has changed, especially overnight. Most commenters agreed; the passenger group FlyersRights objected.

7. Status and advocacy shared a podium. By ABC's account, most of the Transportation Secretary's time at the Friday briefing went to the funding appeal. No FAA official spoke there (NPR).

5. Both sides, fairly

The administration's account

The critics' account

A third position — Speaker Mike Johnson: committees will engage, but no investigation is needed to know more investment is needed.

The fair objection to any fix: officials were busy fixing the thing and reluctant to speak before they were sure. The standard below answers that by having them say what is unknown, on a clock, instead of waiting for certainty.

6. Proposed fix — a public-update standard for nationwide air traffic stops (draft v0.1)

Applies whenever the FAA stops departures at all U.S. airports, or several en route centers lose reliable service.

  1. First notice within 15 minutes, in plain words. Posted at one fixed public address and sent at the same moment to airlines, airports and TSA. It always answers five questions: what is happening; what kind of problem it is (equipment, weather, security, or not yet known); what is not yet known; what travelers should do; and the clock time of the next update.
  2. An update every 30 minutes until the stop ends, even when nothing has changed.
  3. One operational voice. The FAA owns status updates, delivered by a named senior official from the operation. Security agencies contribute one line: whether there is any evidence of an attack. Cabinet briefings add to the clock; they never replace or delay it.
  4. Status only. Updates carry no budget requests and no blame. Those wait for the after-action report.
  5. Last mile. Airports put each update on loudspeakers and screens within 15 minutes. Departure boards stop showing affected flights as on time. TSA tells people in line before they are screened. Airline crews get the same text to read to passengers.
  6. On aircraft. DOT restores a status update at least every 30 minutes during a tarmac delay, with the cause if known.
  7. A permanent record. Every update stays online with its timestamp. A full public timeline within 72 hours, a root-cause report within 30 days, and an independent review that covers the communication as well as the equipment.
  8. Practice. One exercise a year with airlines and airports.

Illustrative first notice (model text for this proposal, not an FAA statement; it uses only what officials were already saying by about 4 p.m.)

4:05 p.m. ET. The FAA has paused all departures from U.S. airports. Radio and radar links at several air traffic centers are unstable. Aircraft now in the air are being guided to land normally. This began in our own telecommunications equipment. We do not yet know the cause or how long this will last. Security agencies are checking for any sign of an attack and we will report what they find. If you have not left for the airport, wait. If you are at the airport, stay near your gate. Next update: 4:35 p.m. ET, at this address.

7. Who can adopt it

8. Routes open to a private citizen

This is not legal advice. The filings below are simple, but procedure should be confirmed before anything is signed.

9. Calendar

Date Event
Mon Nov 16 DOT's detailed funding request due on the Hill; FAA and DOT staff brief House Transportation; Homeland Security Council meets (CBS, AP)
Wed Nov 18, 10:00 a.m. ET House Homeland Security hearing, “Worldwide Threats to the Homeland: 25 Years After 9/11,” Cannon 310. The DHS Secretary is the expected lead witness (Congress.gov, Newsday)
From about Nov 20 Thanksgiving travel builds; Thanksgiving is Nov 26
Fri Dec 11 Stopgap funding expires
About Dec 13 Airlines' tarmac-delay reports for Nov 13 due at DOT
Jan 3, 2027 New Congress convenes

10. Context from federal records

11. Draft questions on the network failure

For network engineers and for the committees doing oversight. These are questions, not findings.

  1. Blast radius. How could a device at one remote radio site reach and destabilize equipment serving 17 of 22 centers? What segmentation, filtering or rate limiting sits between remote sites and the core, and why did it not contain this?
  2. Load. The reported flood works out to roughly 200–250 connection attempts a second. What made that enough to disturb radar and voice feeds? What is the measured capacity of the 2001-era routers, and was it documented?
  3. The disabled function. What is the broadcast function that was switched off on about 60 routers, why was it on in newly installed devices, and what does turning it off cost?
  4. Change control. What testing was done on this router model and configuration against the legacy equipment? Was there a staged rollout, a rollback plan and a monitored window? Who at the FAA approved a Friday mid-afternoon cutover?
  5. The second site. Amarillo's router had been in place about three weeks and began flooding only when El Dorado was switched on. What interaction explains that, and how many similar pairs exist?
  6. Detection. The FAA administrator said the source was unclear for about 45 minutes. What monitoring would locate a flooding device in minutes?
  7. Ownership. The contractor owns and operates the network. What visibility and control does the FAA itself have over configuration and telemetry, and what does the contract require?
  8. Remaining exposure. Roughly 30 percent of circuits are still to convert. What changes before the next cutover, and what is the plan for Thanksgiving week?

12. Open questions

13. How this was researched, and its limits

14. Sources

Official statements

Federal records via the USAFacts connector (all accessed 2026-11-16)

Other federal sources

News

← Back to the action guide