What happened: the timeline

Tuesday, 24 February 2026. A normal weekday morning at Cape Town International Airport — South Africa's second-busiest aviation hub and the primary gateway for Western Cape tourism and trade. The airport processed over 11 million passengers in 2025. The next day, Finance Minister Enoch Godongwana was scheduled to deliver the national budget speech in Cape Town, meaning the city was already busy with an influx of politicians, business leaders, and media.

Then, at approximately 11:15 on Tuesday morning, a fire broke out in the Northern Service Yard on the landside of the airport. Within minutes, the consequences cascaded far beyond the flames themselves.

The suspected cause: an electrical cable fire

The official investigation is still under way, but the evidence available within the first day points clearly in one direction: an electrical infrastructure failure.

Visual evidence posted on social media showed thick bundles of heavy cabling engulfed in flames inside an exterior structural column, with fire and smoke venting from the top of the conduit. The Daily Maverick described the scene as a suspected IT cable fire, with images pointing to a major electrical blaze within the airport's infrastructure.

An airport employee present during the initial moments told News24 they suspected an electrical fire based on the smoke and its location. ACSA confirmed that the fire was on the "landside" of the airport and that it had knocked out network and IT services, including Wi-Fi and essential operational systems. A later update pinpointed the location as the Northern Service Yard.

What makes this particularly concerning is the apparent single point of failure. Modern airports rely on layered redundancy — backup generators, distributed network infrastructure, and failover systems designed to keep critical operations running even when one component fails. At Cape Town International, a single cable fire appears to have brought almost everything down at once.

The cascade: what the fire took down

The fire itself was contained relatively quickly. But the systems failure it triggered was far more damaging than the flames. Here's what went offline:

This was, in the words of the eTurboNews analysis, less a fire event and more a technology failure event. The flames were contained quickly. The systems failure lasted for hours.

The communication vacuum

If the fire exposed an infrastructure vulnerability, the response exposed something arguably worse: a total failure of crisis communication.

Across multiple news sources and passenger accounts, a consistent picture emerges: for the first two or more hours of the crisis, passengers received essentially no official information from the airport itself.

BusinessDay reported that an eyewitness observed hundreds of passengers filling the airport floor as systems went offline, with no official communication transmitted to the stranded travellers. The electronic display boards were down — but there were also no PA announcements, no printed notices, and no staff visibly deployed with information.

News24 journalists who visited the airport during the crisis found confused passengers stopping anyone they thought might work at the airport, desperately seeking answers. There were no functioning notice boards and no visible announcements informing people that flights had been suspended.

FlySafair was the first airline to communicate directly with passengers via SMS, confirming delays and the baggage system outage — but this came at approximately 13:50, nearly three hours after the fire started. ACSA's formal media statement was competent and clear, but it was directed at journalists and social media, not at the thousands of people standing in a darkened terminal with no idea what was happening.

A passenger arriving at the airport saw none of this

One of the most concerning aspects: people continued arriving at the airport throughout the afternoon, completely unaware that flights had been suspended. As one traveller told News24, people were still streaming in hours after the fire, with no public notice outside the terminal explaining the situation. The question of how to manage incoming pedestrian traffic when the airport itself is non-functional was raised by multiple passengers — and apparently went unanswered.

Evacuation: partial, confusing, inconsistent

ACSA's official statement urged passengers to "follow security instructions and proceed to designated places of safety as directed by airport personnel." The reality on the ground appeared considerably less organised.

The evacuation was partial. Sections of the International Terminal affected by smoke were cleared, and patrons at a Spur restaurant inside the airport complex were evacuated due to an emergency. Passengers in the baggage reclaim area were redirected to the emergency escape route at immigration.

But in other parts of the terminal, the situation was different. EWN reporter Nokukhanya Mntambo, who landed at the airport during the height of the crisis, reported that passengers were kept on their aircraft for nearly an hour while fire trucks worked to contain the blaze outside.

The inconsistency is what made the experience so disorienting for passengers. In one part of the building, emergency protocols were activated. In another, people were queueing for flights that wouldn't depart. In another still, staff were simply absent.

The human cost: passenger accounts

No one was physically injured. But the disruption had real consequences for real people — and the stories that emerged paint a picture of frustration, helplessness, and in some cases genuine distress.

What stands out in every account is not anger at the fire itself — fires happen — but anger at being left in the dark, both literally and figuratively.

Not the first time: a pattern of power failures

The 24 February fire would have been alarming enough as an isolated incident. But it is not isolated. Cape Town International Airport has experienced multiple significant power failures in recent years, raising serious questions about the state of its electrical infrastructure.

The questions that need answers

ACSA has confirmed that a full investigation is under way. Based on the available reporting, here are the questions that investigation should address:

The timing: one day before the budget speech

The fire occurred the day before Finance Minister Enoch Godongwana's 2026 national budget speech in Cape Town — an event that annually draws hundreds of business leaders, politicians, and journalists to the city. The Mail & Guardian noted that the airport serves as an essential connector for both domestic and international travel, and that interruptions can cascade across airlines, logistics networks, and the tourism sector.

Whether the timing affected the political response remains to be seen. But the optics are stark: South Africa's second-busiest airport failed catastrophically on the eve of the country's most important economic policy announcement of the year.

If you're travelling: what to do

Power has been restored and operations have resumed, but ACSA has warned that delays may persist as IT systems stabilise. If you are travelling through Cape Town International in the coming days, build in extra time and stay in contact with your airline.

Bottom line

Nobody was hurt. The fire was put out within about 30 minutes. In that narrow sense, the emergency response worked. But the broader response — the communication, the passenger management, the infrastructure resilience — failed comprehensively.

Thousands of people were left in a darkened terminal with no information, no updates, and no visible plan. Staff appeared overwhelmed. Airlines were slow to communicate. New passengers kept arriving with no one to turn them around. People missed memorial services, connecting flights, and business engagements. And all of this happened not for the first time, but for at least the third time in 14 months at the same airport.

As eTurboNews put it, this incident may ultimately be remembered less as a fire and more as a technology failure event — one that exposed how fragile the digital systems underpinning a major international airport really are, and how poorly prepared the airport was to cope when those systems failed.

Cape Town International Airport is a critical piece of South Africa's economic and tourism infrastructure. It deserves backup systems that actually work, communication plans that don't depend on electricity, and a management culture that treats passengers as people who need information — not obstacles to be managed with silence.

The investigation will determine what caused the cables to catch fire. But the harder questions are about what happens next. Will the infrastructure be upgraded? Will communication protocols be rewritten? Will there be accountability? Or will we be writing this article again in six months?

Sources & references