Skip to main content

FAA Outage: System Downtime Puts an Entire Industry on Hold

Pete Goldin
APMdigest

"The US aviation sector was struggling to return to normal following a nationwide ground stop imposed by Federal Aviation Administration (FAA) early Wednesday over a computer issue that forced a 90-minute halt to all US departing flights," Reuters reported on January 11.


The breakdown showed how much American air travel depends on the computer system that generates alerts called NOTAMs — or Notice to Air Missions, Associated Press reported. The system broke down late Tuesday and was not fixed until midmorning Wednesday. The FAA took the rare step of preventing any planes from taking off for a time, and the cascading chaos led to more than 1,300 flight cancellations and 9,000 delays by early evening on the East Coast, according to flight-tracking website FlightAware.

The FAA said a corrupted file affected both the primary and backup systems.

Speaking of tech problems impacting the aviation industry, this happened only a couple weeks after Southwest Airlines experienced a meltdown during the holidays. National Public Radion reported: "By all accounts Southwest was using badly outdated computer systems to manage that complicated system."

But from the IT Ops perspective, the real take away from this news is not specifically about the FAA or the airline industry. Every organization faces this same concern every day — keeping systems updated and up and running. The alternative can be disastrous.

Many, if not most, companies in the US could not take a hit of this caliber and still maintain business as usual

"Today's FAA outage underscores the great need for modernized infrastructure, especially within organizations that operate on antiquated systems," said Fred Koopmans, BigPanda CPO. "The impact to travelers is obvious in this case, but it's imperative to also consider the internal mechanics the FAA will now have to address to recover from this."

Koopmans continued, "The average cost of a significant IT outage, according to 2022 research, is $6,912/minute or $414,720/hour – that's a $7.4M price tag for the FAA based on reports that issues arose at 3pm ET on Tuesday. Many, if not most, companies in the US could not take a hit of this caliber and still maintain business as usual."

"The outdated SaaS systems that many airlines rely upon are difficult to operate and run using older coding languages that few people still know how to use efficiently," explained Peter Pezaris, SVP of Strategy & User Experience at New Relic. "This means that when issues occur, they can be difficult to locate and fix — especially in a timely manner. Beyond that, they are also susceptible to cascading events, when a system fails and goes on to cause a ripple effect. As companies scale and the average tech stack becomes more complex, the risk of outages only rises. Not only is the IT team trying to get the system back up and running, but they are also fielding what can be a massive influx of requests ranging from internal stakeholders up to the Board level or customer complaints."

"Minimizing the time to understand the issue is critical," Pezaris added. "What makes this difficult is that most companies have observability data scattered everywhere. Observability unifies an organization's data and can provide airlines with a 360-degree view of their entire IT stacks, allowing engineers to detect and resolve issues before they impact flights."

Recently published data from New Relic's 2022 Observability Forecast shows that 45% of respondents experience an outage with a high business impact once per week or more — and 29% of those outages take an hour or more to resolve.

Pete Goldin is Editor and Publisher of APMdigest

Hot Topics

The Latest

Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...

In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ... 

Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...

Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...

Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...

The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...

The observability industry has an evolving relationship with AI. We're not skeptics, but it's clear that trust in AI must be earned ... In Grafana Labs' annual Observability Survey, 92% said they see real value in AI surfacing anomalies before they cause downtime. Another 91% endorsed AI for forecasting and root cause analysis. So while the demand is there, customers need it to be trustworthy, as the survey also found that the practitioners most enthusiastic about AI are also the most insistent on explainability ...

In the modern enterprise, the conversation around AI has moved past skepticism toward a stage of active adoption. According to our 2026 State of IT Trends Report: The Human Side of Autonomous AI, nearly 90% of IT professionals view AI as a net positive, and this optimism is well-founded. We are seeing agentic AI move beyond simple automation to actively streamlining complex data insights and eliminating the manual toil that has long hindered innovation. However, as we integrate these autonomous agents into our ecosystems, the fundamental DNA of the IT role is evolving ...

AI workloads require an enormous amount of computing power ... What's also becoming abundantly clear is just how quickly AI's computing needs are leading to enterprise systems failure. According to Cockroach Labs' State of AI Infrastructure 2026 report, enterprise systems are much closer to failure than their organizations realize. The report ... suggests AI scale could cause widespread failures in as little as one year — making it a clear risk for business performance and reliability.

The quietest week your engineering team has ever had might also be its best. No alarms going off. No escalations. No frantic Teams or Slack threads at 2 a.m. Everything humming along exactly as it should. And somewhere in a leadership meeting, someone looks at the metrics dashboard, sees a flat line of incidents and says: "Seems like things are pretty calm over there. Do we really need all those people?" ... I've spent many years in engineering, and this pattern keeps repeating ...

FAA Outage: System Downtime Puts an Entire Industry on Hold

Pete Goldin
APMdigest

"The US aviation sector was struggling to return to normal following a nationwide ground stop imposed by Federal Aviation Administration (FAA) early Wednesday over a computer issue that forced a 90-minute halt to all US departing flights," Reuters reported on January 11.


The breakdown showed how much American air travel depends on the computer system that generates alerts called NOTAMs — or Notice to Air Missions, Associated Press reported. The system broke down late Tuesday and was not fixed until midmorning Wednesday. The FAA took the rare step of preventing any planes from taking off for a time, and the cascading chaos led to more than 1,300 flight cancellations and 9,000 delays by early evening on the East Coast, according to flight-tracking website FlightAware.

The FAA said a corrupted file affected both the primary and backup systems.

Speaking of tech problems impacting the aviation industry, this happened only a couple weeks after Southwest Airlines experienced a meltdown during the holidays. National Public Radion reported: "By all accounts Southwest was using badly outdated computer systems to manage that complicated system."

But from the IT Ops perspective, the real take away from this news is not specifically about the FAA or the airline industry. Every organization faces this same concern every day — keeping systems updated and up and running. The alternative can be disastrous.

Many, if not most, companies in the US could not take a hit of this caliber and still maintain business as usual

"Today's FAA outage underscores the great need for modernized infrastructure, especially within organizations that operate on antiquated systems," said Fred Koopmans, BigPanda CPO. "The impact to travelers is obvious in this case, but it's imperative to also consider the internal mechanics the FAA will now have to address to recover from this."

Koopmans continued, "The average cost of a significant IT outage, according to 2022 research, is $6,912/minute or $414,720/hour – that's a $7.4M price tag for the FAA based on reports that issues arose at 3pm ET on Tuesday. Many, if not most, companies in the US could not take a hit of this caliber and still maintain business as usual."

"The outdated SaaS systems that many airlines rely upon are difficult to operate and run using older coding languages that few people still know how to use efficiently," explained Peter Pezaris, SVP of Strategy & User Experience at New Relic. "This means that when issues occur, they can be difficult to locate and fix — especially in a timely manner. Beyond that, they are also susceptible to cascading events, when a system fails and goes on to cause a ripple effect. As companies scale and the average tech stack becomes more complex, the risk of outages only rises. Not only is the IT team trying to get the system back up and running, but they are also fielding what can be a massive influx of requests ranging from internal stakeholders up to the Board level or customer complaints."

"Minimizing the time to understand the issue is critical," Pezaris added. "What makes this difficult is that most companies have observability data scattered everywhere. Observability unifies an organization's data and can provide airlines with a 360-degree view of their entire IT stacks, allowing engineers to detect and resolve issues before they impact flights."

Recently published data from New Relic's 2022 Observability Forecast shows that 45% of respondents experience an outage with a high business impact once per week or more — and 29% of those outages take an hour or more to resolve.

Pete Goldin is Editor and Publisher of APMdigest

Hot Topics

The Latest

Like most digital transformation shifts, organizations often prioritize productivity and leave security and observability to keep pace. This usually translates to both the mass implementation of new technology and fragmented monitoring and observability (M&O) tooling. In the era of AI and varied cloud architecture, a disparate observability function can be dangerous. IT teams will lack a complete picture of their IT environment, making it harder to diagnose issues while slowing down mean time to resolve (MTTR). In fact, according to recent data from the SolarWinds State of Monitoring & Observability Report, 77% of IT personnel said the lack of visibility across their on-prem and cloud architecture was an issue ...

In MEAN TIME TO INSIGHT Episode 23, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses the NetOps labor shortage ... 

Technology management is evolving, and in turn, so is the scope of FinOps. The FinOps Foundation recently updated their mission statement from "advancing the people who manage the value of cloud" to "advancing the people who manage the value of technology." This seemingly small change solidifies a larger evolution: FinOps practitioners have organically expanded to be focused on more than just cloud cost optimization. Today, FinOps teams are largely — and quickly — expanding their job descriptions, evolving into a critical function for managing the full value of technology ...

Enterprises are under pressure to scale AI quickly. Yet despite considerable investment, adoption continues to stall. One of the most overlooked reasons is vendor sprawl ... In reality, no organization deliberately sets out to create sprawling vendor ecosystems. More often, complexity accumulates over time through well-intentioned initiatives, such as enterprise-wide digital transformation efforts, point solutions, or decentralized sourcing strategies ...

Nearly every conversation about AI eventually circles back to compute. GPUs dominate the headlines while cloud platforms compete for workloads and model benchmarks drive investment decisions. But underneath that noise, a quieter infrastructure challenge is taking shape. The real bottleneck in enterprise AI is not processing power, it is the ability to store, manage and retrieve the relentless volumes of data that AI systems generate, consume and multiply ...

The 2026 Observability Survey from Grafana Labs paints a vivid picture of an industry maturing fast, where AI is welcomed with careful conditions, SaaS economics are reshaping spending decisions, complexity remains a defining challenge, and open standards continue to underpin it all ...

The observability industry has an evolving relationship with AI. We're not skeptics, but it's clear that trust in AI must be earned ... In Grafana Labs' annual Observability Survey, 92% said they see real value in AI surfacing anomalies before they cause downtime. Another 91% endorsed AI for forecasting and root cause analysis. So while the demand is there, customers need it to be trustworthy, as the survey also found that the practitioners most enthusiastic about AI are also the most insistent on explainability ...

In the modern enterprise, the conversation around AI has moved past skepticism toward a stage of active adoption. According to our 2026 State of IT Trends Report: The Human Side of Autonomous AI, nearly 90% of IT professionals view AI as a net positive, and this optimism is well-founded. We are seeing agentic AI move beyond simple automation to actively streamlining complex data insights and eliminating the manual toil that has long hindered innovation. However, as we integrate these autonomous agents into our ecosystems, the fundamental DNA of the IT role is evolving ...

AI workloads require an enormous amount of computing power ... What's also becoming abundantly clear is just how quickly AI's computing needs are leading to enterprise systems failure. According to Cockroach Labs' State of AI Infrastructure 2026 report, enterprise systems are much closer to failure than their organizations realize. The report ... suggests AI scale could cause widespread failures in as little as one year — making it a clear risk for business performance and reliability.

The quietest week your engineering team has ever had might also be its best. No alarms going off. No escalations. No frantic Teams or Slack threads at 2 a.m. Everything humming along exactly as it should. And somewhere in a leadership meeting, someone looks at the metrics dashboard, sees a flat line of incidents and says: "Seems like things are pretty calm over there. Do we really need all those people?" ... I've spent many years in engineering, and this pattern keeps repeating ...