The Beginning

On October 6th, 1979, everything changed for aviation in the Maldives. That afternoon a DC-10 touched down at Malé International Airport, what we now call Velana International Airport. The airport had been built with the Boeing 707 and DC-8 in mind, but by then those aircraft were already fading away. Up until that day, the only jets we saw there were Boeing 737s flown by Maldives International Airlines and Air Lanka. So when the DC-10 came in, it was something else. That was the real start of wide-body operations in the Maldives. From then on, more tourists began to arrive, and longer routes became possible.

The runway back then was 2,840 metres long and 45 metres wide. It could just about take the large jets of the time, but right from the start the airport was not up to ICAO standards. The runway strip, which should have been kept clear, was not. Aircraft parked on the apron sat inside it. The fuel farm was sitting inside it too, a solid block that could not be moved. And at both ends the strip simply stopped at the seawall, with the sea right beyond, no safety area, no RESA.

As traffic grew, ground staff had to make do, parking aircraft wherever they could find a bit of space. It was not neat, and it was certainly not by the book, but somehow it worked. Day after day, the airport kept moving, handling more jets than it was ever designed for, stretching what little there was until the whole place became a story of improvisation. Over the years, the apron was pushed out in steps, and the runway itself was stretched from 2,840 to 3,200 metres to take on the heavier wide-bodies.

Hazards and Risk

For 43 years the hazards never went away. Aircraft and even the fuel farm sat inside the strip. Both runway ends simply fell into the sea. Frangible installations were missing where ICAO required them. By design, the airport was not safe. And yet, in all that time there were about 800,000 aircraft movements (not counting seaplanes). Out of those, only four runway excursions ever occurred. Three were minor taxi slip-ups with no damage and no injuries. The fourth was serious, a landing veer-off at speed, into the seawall, the aircraft somersaulting into the sea. The aircraft was a write-off, but everyone walked away without a scratch.

That works out to roughly one excursion in every 200,000 movements. By ICAO’s Event Risk Classification, the hazards put the airport at “Remote × Catastrophic”, Medium to High risk. Unacceptable by design terms, but tolerated in practice.

Compliance vs Performance

This is where the definition of safety gets tested. Through a compliance lens, Male’ was unsafe. The strip was obstructed, there were no RESAs, and the airport failed Annex 14 from day one. But through a performance lens, it was safe, because 800,000 movements in 43 years produced no fatalities and no injuries. The truth lies somewhere in between. By design it was not safe, but in practice it was kept safe enough for the country to survive, for tourism to grow, and for the economy to prosper until the day came when a proper fix was finally possible.

Between Accident and Bankruptcy

This balance is really the heart of the story. Had the Maldives insisted on full compliance in 1979, wide-bodies would not have landed, tourism would have stalled, and bankruptcy was a real possibility. Had the country ignored safety altogether, one major accident could have destroyed lives and crippled the young industry overnight. Instead, operations were run in that narrow space between accident and bankruptcy. Everyone, ATC, pilots, ground staff, operators, knew the airport was non-compliant. Safety was managed not by design, but by discipline, vigilance, awareness, and procedures. And yes, luck too played its part.

Safety vs. Production

This balance is really at the heart of the story. If the Maldives had insisted on full ICAO compliance in 1979, wide-bodies would never have landed here, and tourism, the lifeline of the economy, would have stalled before it began. Bankruptcy was not a distant threat, it was a real possibility. On the other hand, if the country had ignored safety altogether, it would only have taken one serious accident to destroy lives and cripple the young industry in an instant. What happened instead was something in between. Operations were run in that narrow space between accident and bankruptcy. Everyone knew the airport did not meet the book of rules, ATC, pilots, and operators all lived with that reality. Safety was not guaranteed by compliance, but by discipline, procedures, vigilance, and constant awareness. And, truth be told, luck too had its part to play.

The Turning Point

On October 6th, 2022, exactly 43 years after that first DC-10, a new runway was finally opened. Land reclamation had given space for proper safety areas and RESAs. The fuel farm was relocated outside the strip. For the first time, Velana International Airport looked like ICAO had always intended. It marked the end of four decades of improvisation and the beginning of operations on a runway that was both compliant and safe by design.

The Lesson

For 43 years, even an aircraft as large as the A380 operated safely from a runway that, on paper, was never really safe. The record shows that aviation safety is not only about compliance, but also about performance outcomes. By regulation, it was unsafe. By performance, it was remarkably safe. The truth was always in the middle. Not safe by design, but kept safe enough in practice to keep the nation alive until the fix came.

Final Word

This story is a reminder that in aviation, safety must always live in that narrow space between accident and bankruptcy. Too little safety, and disaster strikes. Too much safety without context, and growth dies before it begins. Velana International Airport’s runway strip is a case study in how a small nation walked that fine line, knowingly non-compliant, but pragmatically managed. The record looks good, but the risk was always there, waiting. And that is the lesson: safety by design can be delayed, but risk never disappears.