On Friday, November 13, the FAA stopped every departure in the country for more than four hours. Thousands of flights were canceled.
The investigation is still underway, and the full story may change. But the early explanation from federal officials should sound familiar to anyone who runs a veterinary hospital.
Transportation Secretary Sean Duffy said aging switches and routers in the FAA's telecom network became overloaded with data. Instead of failing outright, they started sending inconsistent data to air traffic controllers. When controllers can't trust the data on their screens, the safe move is to stop.
Two other details stood out. Duffy said the newer network equipment did not go down; the older equipment did. And Homeland Security Secretary Markwayne Mullin said the overload may have been triggered by new equipment being added to the system.
New tools don't fail on their own. They fail when the equipment underneath them can't keep up.
Think of it like anesthesia. You wouldn't put a senior patient under for a dental without pre-anesthetic bloodwork. Adding cloud software or AI to an aging network without checking it first is the same risk: the procedure is sound, but the patient can't handle the load.
The FAA isn't alone in this. Hospitals are tempted to buy the exciting new system, like a new PIMS, digital X-ray or AI scribe, and put off the unglamorous gear it runs on. Switches, firewalls and cabling never get shown off on a hospital tour. But they decide whether everything else works.
The most important part: aging equipment rarely fails cleanly. It slows down, drops connections, and sends bad data. Those problems are harder to spot than an outage, and they wear on your front desk, technicians and doctors every day.
Your practice is adding more data to its network every year. Moving your practice management software (PIMS) to the cloud, AI scribes in exam rooms, digital radiology and dental imaging, online payments, and cloud phones all push more traffic through the same switches and firewall.
If that gear is near the end of its life, you'll feel it in ways that look like software problems:
The new software often gets blamed. Many times the real cause is an aging switch, an overloaded firewall, or an internet connection that was sized for a different decade.
When your network goes down, the IT repair bill is the smallest part of the cost. Most of it never shows up on an invoice.
The cost that matters most is patient care. Without the network, doctors lose instant access to medical histories, allergies, current medications, lab results and radiographs. Anesthesia monitoring and treatment sheets go to paper. In an emergency or specialty hospital, referral records and in-house imaging can be out of reach in the middle of a critical case, and a 24-hour hospital carries that risk at 2 a.m. with a skeleton crew.
Add up lost doctor production, support staff wages, and the catch-up time it takes to recover. Here's an example; replace the assumptions with your hospital's numbers.
| Cost item | Example assumption | Cost per hour |
|---|---|---|
| Lost doctor production | 4 DVMs x $400 per doctor-hour | $1,600 |
| Support staff wages | 14 team members x $22 per hour | $308 |
| Catch-up and re-entry | 2 hours of overtime per outage hour x $22 | $44 |
| Total | About $1,950 per hour |
The FAA's outage lasted just over four hours. In this example, a four-hour outage on a busy Saturday costs nearly $8,000, before counting lost clients, missed charges or a bad review. Compare that to the cost of replacing an aging switch or firewall on your own schedule.
The FAA is now asking Congress for emergency funding after a nationwide shutdown. That's the most expensive way to modernize: all at once, under pressure, after the damage is done.
You'd never tell a client to skip wellness exams and wait for the emergency visit. Your technology deserves the same preventive care. Every switch, firewall and workstation has a predictable lifespan, and when you know the age of each one, replacement becomes a line in your hospital budget instead of a crisis on a Saturday morning.
Here are the general guidelines we use with practices:
| Equipment | When to plan replacement |
|---|---|
| Workstations | Around 5 years old; replace rather than upgrade |
| Laptops | Around 3 years old |
| Firewalls | Every 3 to 5 years, or sooner if manufacturer support or warranty ends |
| Switches | Every 8 to 10 years, or sooner if manufacturer support or warranty ends |
| Access points | Every 5 years, or sooner if manufacturer support or warranty ends |
| Internet connection | When below 500 Mbps download / 10 Mbps upload |
Age is only half the picture. Once a device is past manufacturer support or warranty, it stops getting security updates and there's no fast replacement if it fails. In a hospital, that's a risk to patient care, not just to your network.
Spreading replacements over three to five years keeps costs steady. It also means you're never running your whole practice on gear that's all aging out at the same time.
The practices that move to the cloud or add AI smoothly are almost always the ones that took care of the foundation first.
If you're not sure of any of these answers, that's the place to start.
The FAA's investigation will take time, and the final cause may look different from the first explanation. But the lesson is already clear: new technology is only as reliable as the network it runs on.
Your practice doesn't need a crisis to modernize. A simple inventory and a three-year replacement plan turn surprise failures into predictable budget items, and they make your move to the cloud or AI a smooth one.
I.T. Guru helps practice managers understand where their technology stands against our IT Standards of Care and build a roadmap they can budget for.
Schedule a Consultation to review your network before your next big upgrade.