Chennai has taken its most formal step yet towards testing passenger transport along the Buckingham Canal.
On August 13, Chennai Metro Rail Limited issued a tender for a consultant to prepare a Detailed Feasibility Report-cum-Detailed Project Report for Water Metro transport between Ennore and Mahabalipuram. The assignment has a 240-day duration, while consultant bids close on September 18.
That makes the proposal substantially more serious than an abstract mobility idea.
But it still remains a study.
The next stage will determine whether the canal can become a transport corridor at all.
First, Chennai needs to establish what route it is actually studying
Current reporting does not agree on the proposed distance.
One DT Next report describes a 53-km Ennore–Mamallapuram route. A later report from the same publication gives nearly 78 km. Times of India reports around 70 km.
The official CMRL tender avoids the discrepancy by specifying only the two endpoints.
Earlier Comprehensive Mobility Plan reporting discussed a 35-km Central–Kovalam priority section, followed by roughly 20 km towards Mahabalipuram, while separately considering the northern stretch towards Ennore and Pulicat.
This suggests the latest consultancy may be testing a larger integrated corridor than the earlier priority scheme, but the official alignment should come from the tender study—not media arithmetic.
That distinction is important because every additional kilometre changes:
- dredging requirements;
- terminal numbers;
- bridges affected;
- environmental impacts;
- fleet requirement;
- travel time;
- cost;
- and operating economics.
Water quality is not an amenity requirement
A Water Metro cannot be planned as though polluted water is simply an unpleasant background condition.
Chennai already has a sanctioned Buckingham Canal restoration programme. CRRT records ₹1,281.88 crore for restoring the canal and connected drainage systems, with WRD and GCC among the implementing agencies.
The canal has also long faced severe problems involving sewage, silt, encroachments and invasive vegetation, all of which affect both hydraulic function and the possibility of navigation.
The correct sequence is therefore:
stop sewage → restore channel → establish hydraulic capacity → verify navigability → build terminals → operate passenger vessels
Not:
launch boats → clean canal later.
If Water Metro becomes the political reason that forces sewer interception and canal restoration to happen faster, that could be one of the project’s largest urban benefits.
But transport should not compromise ecological restoration.
Flood capacity has priority over ferry capacity
Buckingham Canal is part of Chennai’s drainage system as well as a historic navigational channel.
Any proposal for passenger vessels must therefore be evaluated against flood hydraulics.
Jetties, terminal structures, retaining walls, navigation channels and vessel berths cannot:
- reduce effective channel width;
- obstruct flood flows;
- worsen upstream water levels;
- interfere with stormwater outfalls;
- or create new bottlenecks.
The feasibility report should publish hydraulic modelling for both:
normal navigation conditions
and
extreme monsoon conditions.
A Water Metro that functions in January but weakens flood evacuation in November would be poor urban infrastructure.
The bridge problem could determine whether one continuous route is possible
DT Next reports that the earlier mobility assessment identified low-clearance bridges, MRTS infrastructure and encroachments among major constraints.
These are not secondary engineering details.
Bridge clearance determines:
- vessel height;
- passenger-deck design;
- propulsion equipment;
- operating water level;
- and whether a continuous through-service is possible.
If several bridges cannot economically be altered, Chennai may ultimately require separate navigable sections rather than one uninterrupted Ennore–Mahabalipuram service.
The feasibility study should resist forcing one headline route if shorter operating segments produce better mobility.
The MRTS is both obstacle and opportunity
Parts of Chennai’s MRTS infrastructure run alongside or through the Buckingham Canal corridor, physically constraining the waterway in places.
Yet those stations may also offer some of the strongest interchange opportunities.
A Water Metro terminal close to an MRTS or Metro station could allow journeys such as:
boat → rail → employment centre
But “close” must mean an actual transfer system:
- short walking distance;
- continuous accessible footpath;
- weather protection;
- safe crossings;
- integrated passenger information;
- coordinated service frequency;
- and ideally common ticketing.
A jetty 700 metres from a railway station across hostile roads is not multimodal integration.
Chennai should not copy Kochi literally
The Kochi Water Metro proves that scheduled electric passenger ferries can operate as part of an urban public-transport network.
It does not prove that Chennai’s canal has the same physical or demand conditions.
Kochi operates within a network of islands, backwaters and communities where waterways naturally connect origins and destinations.
Chennai’s Buckingham Canal is primarily a linear coastal corridor running parallel to major road and rail systems.
Its competitive question is therefore different:
Can a boat beat or complement Metro, MRTS, suburban rail and buses for enough journeys to justify the investment?
The DFR must model the Chennai problem independently.
Journey time is the decisive mobility test
Consider a passenger travelling from a neighbourhood near OMR towards central Chennai.
Their complete Water Metro journey could involve:
walk/feeder → terminal waiting → boarding → vessel journey → interchange → final walk
The relevant comparison is not boat speed against road congestion.
It is:
door-to-door Water Metro time versus bus, Metro, MRTS, suburban rail and two-wheeler time.
Each proposed terminal should therefore publish:
- catchment population;
- nearby employment;
- competing transport modes;
- expected boardings;
- interchange time;
- vessel travel time;
- waiting time;
- and complete door-to-door travel time.
Without that test, the project risks becoming attractive recreation rather than useful mass transit.
Mahabalipuram creates a tourism temptation
Extending the concept towards Mahabalipuram naturally gives it tourism appeal.
That may strengthen revenue.
But Urban Acres should resist evaluating the project primarily as a tourist service.
A public Water Metro should first answer:
- which daily commuters use it;
- what employment clusters it reaches;
- which neighbourhoods gain new access;
- whether fares are affordable;
- and how frequently services operate.
Tourism can support the business model.
It should not substitute for the transport case.
Ennore creates a different public-interest test
The northern end is even more important from an equity perspective.
A system reaching Ennore should examine whether it improves daily mobility for North Chennai residents and workers in industrial and employment areas—not merely whether it establishes a dramatic end-to-end leisure route.
The strongest corridor may ultimately consist of several high-demand sections connected into one operating network rather than most passengers travelling from Ennore all the way to Mahabalipuram.
The feasibility study should therefore publish station-to-station origin-destination demand rather than only total projected ridership.
Electric boats do not automatically make the system low-carbon
If electric vessels are eventually proposed, the environmental assessment should consider the complete system:
- vessel energy;
- battery production and replacement;
- charging infrastructure;
- terminal construction;
- dredging;
- canal maintenance;
- passenger access trips;
- and displaced road journeys.
The relevant metric is:
emissions per passenger-kilometre compared with the mode actually displaced.
A lightly occupied electric boat is not automatically more efficient than a heavily occupied electric train or bus.
CMRL is a sensible mobility planner—but cannot own the whole problem
CMRL’s involvement has one clear strength: it already operates mass transit and is positioned to think about passenger interchange rather than waterway beautification alone.
Its own tender formally moves the Water Metro into transport-planning territory.
But the canal itself involves other public authorities.
That means the DPR should have a formal inter-agency structure covering:
- canal ownership;
- dredging;
- pollution;
- sewer interception;
- terminal land;
- bridge modification;
- navigation regulation;
- emergency rescue;
- flood operations;
- vessel regulation;
- maintenance;
- and fare integration.
Without one lead delivery structure, Chennai could produce a transport DPR dependent on restoration projects controlled by agencies operating to different schedules.
There is already a restoration ledger to reconcile
The ₹1,281.88-crore CRRT restoration programme cannot simply sit beside the Water Metro study as unrelated expenditure.
The DFR should identify for every canal reach:
| Question | Required answer |
|---|---|
| Restoration already sanctioned? | Yes / No |
| Implementing agency | WRD / GCC / other |
| Sewage intercepted? | Status |
| Channel width | Existing / required |
| Dredging requirement | Quantity |
| Minimum navigation depth | Required |
| Bridge clearance | Existing / required |
| Encroachment | Status |
| Flood function | Hydraulic capacity |
| Terminal potential | Yes / No |
| Rail/bus interchange | Distance |
| Water quality | Baseline |
| Additional Water Metro cost | Separate amount |
That would prevent the Water Metro project from double-counting restoration already funded elsewhere.
The tender itself creates an accountability timeline
CMRL’s NIT was issued August 13. Tender documents become downloadable on August 19, the pre-bid meeting is scheduled for August 28, bid submission closes September 18, and the selected consultant will have a 240-day contract.
That provides several measurable next steps.
The newsroom should watch:
RFP release → consultant appointment → inception report → feasibility findings → preferred corridor → DPR → government decision
The most important publication will be the feasibility result—even if that result concludes that parts of the route are unsuitable.
A good feasibility study is allowed to say no.
The public-interest test
Chennai should explore water transport.
The Buckingham Canal is historically significant, geographically strategic and potentially valuable as part of a broader blue-green mobility system.
But the project should not begin with the assumption that boats are inevitable.
It should begin with the canal.
Can it be made:
- clean enough;
- deep enough;
- wide enough;
- hydraulically safe;
- continuously navigable;
- economically maintainable;
- accessible from neighbourhoods;
- and fast enough to compete for real journeys?
If those conditions can be met, Water Metro could become more than a transport project. It could give Chennai a powerful reason to finally coordinate canal restoration, sewage control, flood management and public mobility.
If they cannot, the city should still restore the canal.
The Water Metro is optional. A functioning Buckingham Canal is not.
