Back to U.S.

Inside the FAA's nationwide ground stop: the call came from a duty manager at a Virginia command center as radio links failed center by center, 'It snowballed quickly'

FACTS

The decision to ground every departing flight in the country last Friday was made not in Washington but at the FAA's Air Traffic Control System Command Center in Warrenton, Virginia, about 45 miles from FAA headquarters, the Washington Examiner reported Friday.

Transportation Secretary Sean Duffy, FAA Administrator Bryan Bedford and Homeland Security Secretary Markwayne Mullin have been the public faces of the Nov. 13 ground stop. But according to three FAA employees with firsthand knowledge, the call to halt all departures was made by the national operations manager on duty at the command center, the same facility that ordered the nationwide stop on Sept. 11, 2001. The manager's name was not disclosed.

Shortly before 3 p.m. that Friday, staff at the center learned that Chicago's approach control had lost radar and communications. Within minutes, the Boston, New York and Washington en-route centers reported lost communications, followed by Minneapolis, Cleveland and Indianapolis. One person recalled someone yelling "I lost my frequencies" just as the first ground-stop notice was going out.

"Facilities were losing their ability to speak to pilots in real time, and it snowballed quickly," one command center employee told the Examiner. "The nationwide ground stop was 100% necessary for the safety of the flying public." A traffic management specialist said ground stops for single facilities are routine, "but the phone kept ringing with a new facility that needs to be stopped."

FAA notices to controllers cited a "rolling frequency outage in multiple centers." Some controllers have argued the full stop went too far because parts of the country were unaffected.

SOURCES

UPDATES

  1. 6:07 AM ET

    Published.