28.06.2013 Views

9.Cochin International Airport - AERA

9.Cochin International Airport - AERA

9.Cochin International Airport - AERA

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

CIAL/FIN/<strong>AERA</strong>/2009-10<br />

23/03/2010<br />

Shri Sandeep Prakash<br />

Secretary<br />

<strong>Airport</strong> Economic Regulatory Authority<br />

Room No 58, B Block ,Rajiv Gandhi Bhavan<br />

New 111003<br />

Dear Sir,<br />

Subject : CIAL’s response to the Consultative paper –thereof<br />

On the outset itself, we welcome the continuing efforts of <strong>AERA</strong> to bring a consistent and<br />

predictable regulatory regime to the Indian <strong>Airport</strong> sector. As regards CIAL response to the<br />

consultative paper is concerned, we would first like to reiterates our stand taken by us vide this<br />

office letter no CIAL/<strong>AERA</strong>/2009-10 dated 05/10/2009 which was issued in response to the<br />

white paper issued by <strong>AERA</strong>.<br />

Having considered the consultative paper issued by <strong>AERA</strong>, we would also like to submit the<br />

following additional response to you, which may also be looked into by <strong>AERA</strong> before issuing the<br />

draft regulatory policies and guidelines for Indian Aviation sector.<br />

1. There exists an ambiguity as to whether the regulatory philosophies will be made<br />

applicable uniformly to all private sector airports in India. As pointed out by us in our<br />

earlier letter, the private sector airports in India are not a homogeneous group. Some of<br />

them are based on a concession /OMDA agreements which are basically leased airports<br />

from AAI /Government and some others are green field airports. Within the green field<br />

airport, CIAL is the only airport without any concession agreements and the ownership,<br />

management structure, size, nature of business etc varies greatly with that of other<br />

airports. Unlike other private sector airports, the entire airport land was purchased by<br />

CIAL and holds it as a freehold. The company has constructed the airport and<br />

maintaining it without any support from state or central government. All major capital<br />

investments were made years back and the airport is in a matured life cycle. However,


the consultative paper is silent as to whether all categories of airports will be treated at<br />

par in the new regulatory regime or not. We requests for separate regulatory frame<br />

work for Greenfield airports without any Concession agreements.<br />

2. Adoption of Single till: We would like to record our deep concern regarding the<br />

proposal for introduction of single till concept for Indian airport regulation. Under this<br />

scenario all airport assets are put under the scope of single till. In fact, para 2.2 to 2.42<br />

of consultative paper spells arguments in favour of adoption of a dual till in airport<br />

industry ,but, it concludes its assessment in the very next paragraph 2.43 by stating that<br />

in Indian scenario ,single till being the most appropriate basis in general for the<br />

regulatory regime for major airports in India. However, the arguments in favour of single<br />

till for Indian scenario do not seem to follow a detailed explanation or justification other<br />

than the following three factors.<br />

(a) Non aeronautical revenue is clearly a function of aeronautical activity at an airport.<br />

Therefore, there is a persuasive case for non aeronautical revenues to be taken into<br />

consideration for fixation of aeronautical charges.<br />

(b) A single till approach protects interest of users by ensuring service provision<br />

commensurate with the respective tariff /charges.<br />

(c) Avoids complications relating to the cost allocation.<br />

All the above three factors do not seems to be free of conceptual errors. For eg, CIAL is<br />

having unique non aeronautical revenues like golf course, hospitals, trade fair centres,<br />

convention centers, amusement parks etc, which are not necessarily a function of<br />

aeronautical activity at an airport.<br />

Similarly, empirical evidences show that user’s interests were protected well under the<br />

dual till basis on long term basis. Examples are Torronta airport &Paris <strong>Airport</strong> .Further,<br />

gradually all US airports are brought under dual till basis.<br />

Cost allocation does not seem to be complicated process in the Indian <strong>Airport</strong>, but the<br />

only problem in existence is of a clearly laid down parameters/basis for allocation which


can be easily brought out by regulatory body or can be entrusted to the professional<br />

statutory accounting bodies of India.<br />

3. Even if, <strong>AERA</strong> recognizes the need for a single till in Indian scenario and proceeds with it,<br />

the revenues earned out of activities on the land owned by the airport company ,which<br />

are not located in the operational area of the airport and/or generated not out of the<br />

functions of aeronautical activities in the airport warrants an exclusion from the<br />

definition of Regulatory Asset base and non aero nautical income. A company<br />

exclusively formed for airport operations may derive income out of its real estate and<br />

through its investment activities. This is especially applicable to those airport<br />

companies which own freehold land in their books of accounts and that land is used for<br />

various ambitious real estate activities of the airport company. Similarly capital<br />

investment cycle is different in various airports and gradually airport companies will<br />

have income from its investment activities. It is not clear from the consultative paper<br />

whether all these income like income from real estate, income from the capital assets<br />

created in the land owned by airport which is outside the operational area of airport,<br />

income from the investment activities of <strong>Airport</strong> Company etc will fall under the<br />

category of non aeronautical revenue. Any company earns income from other sources<br />

and investments which cannot be considered as the income from the operations of the<br />

company. Probably, in case of an airport company income from operations can be made<br />

out of aero revenues and non aero revenue but there can also be a category of income<br />

which is in the nature of non operating incomes of an airport company.<br />

4. Therefore, we requests to exclude all assets which are falling in the own land of an<br />

airport company other than located in the area earmarked for the operational area of<br />

the airport and it may be kept outside the ambit of Regulatory Asset base.Similiary, an<br />

airport company may earn non operating incomes like investment income and other<br />

miscellaneous income which are not a function of airport activities and which may not<br />

be the core income of the company. All these revenue shall be explicitly excluded<br />

from the non aeronautical revenues, if the tariffs are determined on a single till basis.


5. We also suggest for a legal examination at this stage itself whether considering the non<br />

aero assets for aeronautical tariff fixation is inconsistent with <strong>AERA</strong> Act as it has<br />

excluded the non aero nautical revenues from its jurisdiction.<br />

6. Price Cap Regulation: Under the proposed regime, airport operators would be required<br />

to propose specific tariffs which will be considered and approved by <strong>AERA</strong> based on<br />

considerations like cost relatedness etc and a price cap would prescribe a ceiling on the<br />

aeronautical charges so that it shall not exceed the prescribed price cap. However, the<br />

factors that will determine the first tariff cycles and the uniform methodology under<br />

which all airports are expected to approach the <strong>AERA</strong> for tariff fixation is not made<br />

clear.<br />

7. It is also stated that a Performance measurement plan will need to be developed and to<br />

be submitted by the airports as a part of the tariff proposals for approval of the<br />

authority as per the guidance provided in that respect. Adequate time may be given to<br />

the airports for implementation of these performance measurement mechanisms as the<br />

proposed one is very complex and extensive. We would request that during the first<br />

tariff cycle, submission of such an extensive performance measurements may be<br />

dispensed with as the installation of proposed comprehensive performance system is<br />

time consuming, requires additional investments on infrastructure and warrants<br />

modification of the existing agreements with various stakeholders.<br />

8. The tariff approval cycle due to CIAL is not presently aligned with the capex cycle. In our<br />

case, all major airport capital investments were made years back. The assets are in place<br />

and the debts were repaid, restructured or retired by infusion of additional equity<br />

capial.Therefore, next major expansion related capital projects are in its planning stage.<br />

Therefore, the approach to be followed for tariff fixation which is not aligned with any<br />

capex approval cycle is not known.<br />

9. Regulatory Asset base: The <strong>AERA</strong>’s position in regarding work in progress is that it<br />

would not be considered for inclusion in the Regulatory asset base, however, a<br />

capitalized financing approach will be adopted by including an allowance for the fair<br />

rate of return .But it is stated that fair rate of return for WIP assets will be its


assessment of cost of debt . This is highly objectionable. Either the WIP should be<br />

included in total for computing the regulatory asset base or the fair rate of return on<br />

WIP assets will be return on capital employed (ROCE) .<br />

10. Operating Expenditure: Authority’s assessment of operating cost shall invariably cover<br />

all matching costs of related aero or non aero revenues considered for opex calculation<br />

in the regulatory assets block. Say for eg, if the duty free sales are considered as non<br />

aero revenue income and taken into consideration in the RAB block, the Opex shall also<br />

include the cost of goods sold of the sale of duty free goods.<br />

11. Consultation protocol: Consultative process envisaged in the consultative paper<br />

suggests submissions of all detailed information to users including the business plans,<br />

project investment files, detailed plans etc. Consultation also encompasses the<br />

exchange of information and subsequent discussion between airport operators and<br />

users with the objective of achieving agreements, wherever possible within an<br />

appropriate time frame. CIAL has been doing the consultative process for all major<br />

investments decision. From our experience, the very detail consultative protocol<br />

brought out is counterproductive for the reason that ,in real situation there shall not be<br />

any exchange of information amongst users, but whatever, information airport operator<br />

furnishes to users shall be used in favour of them without any reciprocal basis and<br />

when there are multi user’s involvement, it is difficult to gain acceptance of proposals<br />

within a time limit and to reach to an agreement ,which will defeat the objective of the<br />

consultative process. The consultative protocol proposed is also silent as to how the<br />

decision is to be taken if there is no consensus for major capital project decisions. Taking<br />

into consideration, we suggest that, when ever, major capital investment decisions are<br />

mooted to <strong>AERA</strong>, consultation of various stake holders may be conducted in the<br />

presence of <strong>AERA</strong> as an intermediary and the airports may be permitted to exchange<br />

the project related plans only to the stake holders as information , not the entire<br />

business plans of an airport company .<br />

12. The consultation protocol also stipulates for incorporation of information on the asset<br />

disposals, including any of its land or building, where through sale, partial sale, long


term lease or Joint venture including disposals by the airport company to other entities<br />

.The information should also incorporate timing of such disposals and highlight the<br />

impact on airport operation. These clauses are highly unacceptable. As the multi users<br />

may include parties interested in the above affairs, it will impact airport company’s<br />

effort to have a proper price discovery of assets to be disposed or acquired.<br />

13. Quality of service parameters and benchmarks suggested in the consultative paper<br />

seems to unrealistic in the Indian context. Service parameters like security check within<br />

05 minutes for 95% of passengers, Checking time in queue within 10 minutes for 95%<br />

passengers ,Check in time suggested etc are unrealistic ,hence requires modification.<br />

Further, it may be noted that security check, CIQ, Check In , baggage delivery etc are not<br />

those activities directly undertaken by the airport operator, hence operator alone<br />

should not be penalized .Similiarly , time taken from aircraft arrival to kerbside in the<br />

<strong>International</strong> arrival involves customs and immigration agencies. Hence the prescribed<br />

time of 45 minutes for 95% passengers are possible only with cooperation of sovereign<br />

agencies. Hence the service parameters which are purely under the control of an airport<br />

operator may only be included with realistic benchmarks in the proposed quality of<br />

services.<br />

Trust you will consider the above facts also while framing the draft regulations.<br />

Thanking you in anticipation,<br />

Yours Faithfully,<br />

(A C K Nair)<br />

Executive Director (Operations)

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!