Deprecated (16384): The ArrayAccess methods will be removed in 4.0.0.Use getParam(), getData() and getQuery() instead. - /home/brlfuser/public_html/src/Controller/ArtileDetailController.php, line: 150
 You can disable deprecation warnings by setting `Error.errorLevel` to `E_ALL & ~E_USER_DEPRECATED` in your config/app.php. [CORE/src/Core/functions.php, line 311]
Deprecated (16384): The ArrayAccess methods will be removed in 4.0.0.Use getParam(), getData() and getQuery() instead. - /home/brlfuser/public_html/src/Controller/ArtileDetailController.php, line: 151
 You can disable deprecation warnings by setting `Error.errorLevel` to `E_ALL & ~E_USER_DEPRECATED` in your config/app.php. [CORE/src/Core/functions.php, line 311]
Warning (512): Unable to emit headers. Headers sent in file=/home/brlfuser/public_html/vendor/cakephp/cakephp/src/Error/Debugger.php line=853 [CORE/src/Http/ResponseEmitter.php, line 48]
Warning (2): Cannot modify header information - headers already sent by (output started at /home/brlfuser/public_html/vendor/cakephp/cakephp/src/Error/Debugger.php:853) [CORE/src/Http/ResponseEmitter.php, line 148]
Warning (2): Cannot modify header information - headers already sent by (output started at /home/brlfuser/public_html/vendor/cakephp/cakephp/src/Error/Debugger.php:853) [CORE/src/Http/ResponseEmitter.php, line 181]
LATEST NEWS UPDATES | CAG report on Delhi International Airport ill-informed, full of holes

CAG report on Delhi International Airport ill-informed, full of holes

Share this article Share this article
published Published on Aug 21, 2012   modified Modified on Aug 21, 2012
-The Economic Times

The CAG's report on Delhi International Airport (DIAL) is naive and uninformed. It asks why land was made available to a private developer at reduced rates to build and run an airport for 60 years, and insinuates that the developer, Hyderabad-based GMR group, got a sweetheart deal from the government.

It seems to find it abhorrent that 5% of the land allotted could be used commercially and claims that this would generate a little more than Rs 1,63,550 crore over the next 58 years. So what? While bidding, GMR promised to hand over 46% of its revenues to the government.

Going by the CAG's own methodology and taking the Rs 704 crore paid by DIAL to the government last year, over the next 58 years, GMR will pay revenue worth more than Rs 2,43,140 crore to the government.

The CAG asks why the airport operator should charge a development fee from passengers. Short answer: because state-controlled Airports Authority of India (AAI) couldn't come up with its share of equity and did not want to dilute its shareholding in DIAL by bringing in other investors.

The charge falls under the AAI Act of 1994 that governs Delhi airport, airport regulator Aera regulates the fee and last year, the Supreme Court upheld DIAL's right to charge it.

These are matters of detail, important no doubt, but they miss the wood for the trees. The fact is that almost everything that the CAG finds objectionable today was part of the bidding conditions when the right to build and run Delhi airport was auctioned in 2005-06.

It seems to forget that the GMR-led consortium was only one of five bidders, including big players like Essel, Sterlite and Reliance ADAG group. GMR won because it promised to give the government a higher share of its revenues than the other bidders.

As things go, this was one of the most transparent ways to build a large project as a private-public partnership. The losers did go to court, citing mala fide and lost out.

A committee headed by former metro chief E Sreedharan vetted the fairness of bid evaluation. Today, it makes little sense for an auditor to raise objections or comment on issues it doesn't quite understand.

The Economic Times, 20 August, 2012, http://economictimes.indiatimes.com/opinion/editorial/cag-report-on-delhi-international-airport-ill-informed-full-of-holes/articleshow/15564686.cms?


Related Articles

 

Write Comments

Your email address will not be published. Required fields are marked *

*

Video Archives

Archives

share on Facebook
Twitter
RSS
Feedback
Read Later

Contact Form

Please enter security code
      Close