Parandur Is Off. Chennai's Second Airport Belongs on the Water.
In August 2026 the Tamil Nadu government dropped the Parandur greenfield airport. Four years after the site was chosen, after in-principle clearance from the Centre, after revenue teams had already begun acquiring land, the project ended where it started — with thirteen villages that would not move, and a state still without a second airport.
The reasons given were the right ones. Close to five thousand acres across thirteen revenue villages, most of it privately held and under cultivation, along with the twelve lakes, twenty-odd ponds and the drainage channels that make that land farmable in the first place. The protest at Ekanapuram held for four years. It outlasted the project.
We are an architecture and interiors practice, not an aviation consultancy. But siting is the architectural part of this, and siting is where it failed. So we will say plainly what we think should happen next: Chennai should stop looking inland and start looking at its coast.
Another inland site will fail the same way
It is tempting to read Parandur as a political misstep — the wrong consultation, the wrong compensation, the wrong moment. We do not think that is what happened. The project had ₹20,000 crore behind it at announcement and more than ₹27,000 crore by the end. It had clearance. It had a Centre and a State that both wanted it built.
What it did not have was five thousand contiguous acres within reach of Chennai that nobody was already living on and farming.
That is not a Parandur problem. Open a land-use map of the region and the pattern repeats in every direction: wet agricultural land threaded with tanks and eris, or land already built up, or land so far out that an airport there stops being Chennai's airport at all. The committee now looking for an alternative site is looking for the same five thousand acres in the same landscape, with the same people on it. If the next site is inland, the next protest is only a matter of scheduling.
This is the heart of it. On the coast, the binding constraint is engineering — and engineering can be surveyed, costed, tendered and built. Inland, the binding constraint is consent, and consent cannot be procured at any price. Parandur is four years of proof.
An airport seventy kilometres away does not relieve anything
Parandur sat roughly 70 km from Chennai Central and about 57 km from the existing terminal at Meenambakkam — close to a two-hour drive on an ordinary day, before the traffic that a hundred-million-passenger airport generates for itself.
That distance quietly changes what the project is. A second airport exists to take load off the first. At two hours out, most of the city only routes there when the fare gap is wide enough to justify the journey — which means it collects the price-sensitive traffic and leaves the original airport exactly as congested as before. It becomes the cheap airport rather than the second airport.
Meenambakkam handled 23 million passengers in 2025–26, and the expansion under way lifts declared capacity to around 35 million. That buys time. It does not buy a decade. And a relief airport that most of the city will not use has not bought anything at all.
A city should hold together
This is the part that matters most to us, and it gets the least attention in the debate.
An airport is not a facility that happens to need a large flat site. It is a piece of urban infrastructure, and where you put it decides where a city grows for the next fifty years. Put it seventy kilometres out and you have not simply inconvenienced travellers. You have declared a second centre of gravity in open farmland, and the city will follow it — hotels, warehousing, logistics parks, housing for the people who work there, arterial roads to carry them, and the speculative land conversion that arrives years before any of it is built.
Chennai then has to service two centres instead of strengthening one. Every kilometre of new road, drainage, water supply and power laid out there is a kilometre the existing city does not get. The result is a metropolitan region that is thinner everywhere rather than stronger anywhere — precisely the sprawl pattern Indian cities are already struggling to pay for.
Japan has run this experiment for us, and the parallel to Parandur is almost exact. Narita was pushed some sixty kilometres out of Tokyo, onto farmland at Sanrizuka, in the late 1960s. The farmers refused. The state expropriated. What followed was one of the longest and most bitter land struggles in modern Japanese history — decades of it, and to this day there are fields inside the airport boundary that were never surrendered. Narita opened years late, incomplete, and never became the single gateway it was meant to be.
What did Japan do in the end? It went back to the water. Haneda — the close-in airport in Tokyo Bay, extended onto reclaimed land — opened a new runway in 2010, and international traffic returned to it. The far airport built on expropriated farmland lost to the near airport built on the sea. Tokyo spent forty years and a great deal of conflict learning something Chennai can simply read.
A coastal airport keeps Chennai's centre of gravity where the city already is. It reinforces the ECR–OMR corridor instead of opening a rival one in the opposite direction. It uses infrastructure that exists rather than duplicating it in a field. That is what centralised urban development actually means in practice — not everything crammed into one place, but new capacity added where the city already reaches, so the fabric thickens instead of fraying.
It has been done, and the lessons are already written down
Building airports on water is not experimental. It is a mature discipline with thirty years of built precedent behind it, and Asia holds most of it.
Haneda, Tokyo is the one to start with, for the reason above: a major international gateway extended onto reclaimed land in the bay, minutes from the city it serves, operating at a scale no Indian airport has yet reached.
Chubu Centrair, Nagoya (2005) is the model for building one from scratch. An artificial island in shallow water on a firm seabed, delivered on budget, with settlement that has stayed within design tolerance. It is the version everyone should be studying, and it is barely famous — which tells you how well it works.
Kansai, Osaka (1994) is the older, harder case: deep soft clay, and an island that has settled substantially since construction. It is worth naming for what happened next. It has run for thirty years, through typhoons and a serious flood, and it remains one of Asia's major gateways. Even the difficult version works. Centrair is what happens when you take Kansai's geotechnical lesson seriously before you start rather than after.
Chek Lap Kok, Hong Kong (1998) shows the hybrid route: level an existing island, reclaim around it, and let the rock do the structural work. Relevant anywhere the seabed offers something to build from.
Changi Terminal 5, Singapore is the current state of the art — around US$10 billion on reclaimed land, deliberately raised about 5.5 metres above sea level. Singapore did not treat water as a problem solved once during construction. It designed the platform for the climate the asset will actually live in.
None of this has to be invented. It has to be specified.
Chennai is unusually well suited to it
Most Indian cities hunting for five thousand acres do not have this option. Chennai does, and the advantages stack up.
- The coast runs the length of the metropolitan area. A coastal site can be genuinely close to the city in a way no inland site can — measured in tens of minutes, not two hours.
- Approaches come in over water. No flight path over dense settlement, which means no noise-contour argument, no height restrictions imposed across built-up neighbourhoods, and far simpler night operations.
- No farmland to buy. No eris drained, no villages relocated, no multi-year acquisition process, no litigation running alongside construction.
- The construction industry already exists here. Chennai Port and Kamarajar Port mean dredgers, marine contractors and geotechnical capability are on the ground and working. This is not a capability the state would have to import.
- It sits on the growth axis. ECR and OMR are already where Chennai's IT, manufacturing and logistics traffic lives. A coastal airport serves that corridor directly instead of asking it to drive west past the city.
The land pays for the platform
There is a funding argument here that rarely gets made, and it is the strongest financial case for going offshore.
Reclaimed land is state land from the moment it exists. There is no acquisition cost, no compensation settlement, no decade of title disputes — and, just as importantly, no speculative land market forming around the site years before anything is built. At Parandur, the appreciation in land values around the announced site accrued largely to whoever bought early. On a reclaimed platform, that value accrues to the public authority that created the land.
That is what the airport city on a plan like this is actually for. Hotels, cargo and logistics, offices, maintenance facilities and the commercial estate around the terminal all sit on ground the state owns outright and can lease on its own terms. Hong Kong and Singapore both leaned on land they had created or controlled to help fund airport and rail infrastructure. The platform is expensive; the land it creates is an asset on the same balance sheet.
Inland, the state buys land and hands the upside to the market. Offshore, the state makes land and keeps it.
What gets built first
A project like this is not delivered in one go, and it should not be sold as though it were. The sequence that has worked elsewhere is straightforward:
- Phase one is a single runway and one terminal. One full-length runway around 3,800 m, one terminal sized to the traffic that exists rather than the traffic being forecast, and the platform reclaimed with the second runway's footprint already formed but left undeveloped.
- Connectivity opens with it, not after it. An expressway and a rail link committed at the same time as the platform. This is the single most common failure in Indian airport projects, and it is entirely a matter of sequencing, not engineering.
- The airport city follows demand. Cargo, maintenance and the commercial estate are built out as traffic justifies them, on land already reclaimed and already owned.
Phasing it this way keeps the first capital tranche defensible and lets the asset start earning before the full masterplan is finished. It is also the honest way to present it: an airport that opens with one runway and grows is a credible project, and a rendering of the 2045 build-out is a picture, not a plan.
What it takes to do it properly
The engineering is well understood, and the sequence matters. Any serious proposal starts here.
Survey the seabed first, along the whole metropolitan coast. The entire difference between Centrair and Kansai is what was found before anyone committed to a footprint. Shallow water on firm ground exists on this coast; the job is to locate it rather than assume it.
Design for the Bay of Bengal from day one. Vardah and Michaung set the brief. The platform is raised the way Changi's is, drainage is over-specified rather than adequate, and the design case is sea level in sixty years, not the tide table today.
Model sediment movement before drawing anything. Chennai's shoreline already responds strongly to what is built on it — the harbour and its groyne fields reshaped the coast north of the port. A footprint offshore has to be shaped so that littoral drift keeps working, and that is a modelling exercise with a defensible right answer, not a matter of opinion.
Talk to the fishing villages early. This is the one community a coastal airport genuinely affects, and it deserves saying honestly: construction and operations change fishing grounds, launch beaches and access routes, and that has to be planned around, compensated where it applies, and settled before a site is announced rather than after. But it is a different order of thing from Parandur. Nobody loses a house. Nobody loses a field. No village is asked to stop existing. It is a question of access and working arrangements — the kind of thing ports and coastal infrastructure across India negotiate as routine, and the kind of thing that gets solved when it is raised at the start instead of defended in court at the end.
Cost the connectivity into the plan, not after it. An airport is only as close as the road and rail that reach it.
Why a design practice has a view on this
Because it is the same judgement we make on every project, at a different scale. Where a building sits on its plot decides most of what follows — how it takes light and air, what it costs to run, whether it works on an ordinary weekday morning. Get siting wrong and nothing downstream recovers it. Get it right and half the problems never appear.
A city is the same thing with more zeros. An airport is not a standalone object dropped wherever the land is cheapest and the resistance weakest; it is a piece of the urban fabric, and it either strengthens the city's structure or pulls it apart. Chennai has one coastline, one growth corridor, and one chance to add capacity in a way that makes the city denser and better connected rather than wider and thinner.
Four years and a great deal of public patience have established that the region does not have five thousand spare inland acres. It does have a coastline, a port industry, thirty years of built precedent to draw on, and a growth corridor already pointing at the water.
Before the same search starts again with a different village's name attached to it, the sea deserves a proper look.

