ENR 3.3.2 - Other Routes

ESTABLISHMENT OF USER PREFERRED ROUTE (UPR)

GEOGRAPHIC ZONE IN CHENNAI FIR AND MUMBAI FIR

1.

INTRODUCTION

1.1

To reduce the environmental impact of aviation the members of the Indian Ocean and Arabian Sea Strategic Partnership to Reduce Emissions (INSPIRE) are collaborating to allow airspace users access to User Preferred Routes across the Arabian Sea, Indian and Southern Oceans and adjoining airspaces..

2.

PROCEDURES

2.1

UPR Airspace

The Arabian Sea Indian Ocean UPR Geographic zone is that airspace formed from contiguous portions of adjoining Flight Information Regions (FIRs) across the Arabian Sea, Indian Ocean and adjoining airspaces. Each participating FIR defines in their own AIP the portion of their airspace where the UPR geographic zone is established and notifies specific constraints that apply in that airspace.

The UPR airspace for the Chennai FIR is the airspace within 11°35´N 072°00´E, 07°41´N 077°51´E, 07°00´N 077°00´E, 06°00´N 077°00´E, 06°00´N 074°00´E, 07°30´N 074°00´E, 07°30´N 072°00´E,. Vertical Limits: FL280 to FL460.

The UPR airspace for the Mumbai FIR is the airspace within 10°55´N 60°00´E, 15°10´N 66°50´E, 11°35´N 072°00´E, 07°30´N 072°00´E, 07°30´N 070°00´E,03°00´N 070°00´E, 00°00´N 068°00´E, 06°00´S 068°00´E, 06°00´S 060°00´E. Vertical Limits: FL280 to FL460.

Refer Appendix 1 - UPR Airspace Chennai and Mumbai FIRs.

This UPR airspace is contiguous with UPR airspace in adjoining FIRs

Refer Appendix 2 - UPR Airspace Arabian Sea Indian Ocean.

2.2

Access to UPR

Only those airspace users may flight plan a user preferred route in the UPR Geographic zone which meet the following minimum criteria:

- RNP10, and

- ADS-C and CPDLC equipped

The minimum criteria listed above must be notified in the flight plan. The flight shall log on to Chennai ADS-C/CPDLC VOMF or Mumbai ADS-C/CPDLC VABF as appropriate, prior to entering UPR zone.

UPR flights are subject to provisions applicable to IFR flights in Class E airspace.

2.3

Specific requirements within the Chennai and Mumbai FIRs

Within the Chennai and Mumbai FIRs the following flight planning requirements apply:

- Prior permission required at least seven days in advance for flight operators to fly UPR in Chennai/Mumbai FIR. Permission may be requested for whole or part of Summer/Winter schedule for particular flight/s.

Contact details:

Chennai:

i. General Manager (ATM)

Airports Authority of India

Chennai International Airport, Chennai

Telefax: +91 44 22561740

Email: gmaerochennai@aai.aero

ii. Watch Supervisory Officer (WSO), Chennai

Telephone: +91 44 22560894

Fax: +91 44 22561365

Email: wso_mm@aai.aero

Mumbai:

i. General Manager (ATM)

Airports Authority of India

Chhatrapati Shivaji International Airport, Mumbai

Telefax: +91 22 20888011

Email: gmatmmum@aai.aero

ii. Watch Supervisory Officer (WSO), Mumbai

Telephone: +91 22 20888088

Fax: +91 22 -20888088

Email: wsomum@aai.aero

The flight plan for a UPR flight shall be filed at least two hours before EOBT.

- The transition from a conventional ATS route to User Preferred Route or vice versa at the northern boundary of Chennai UPR zone shall take place at any of the waypoints on ATS routes P570. At the northern boundary of Mumbai UPR zone the transition from a conventional ATS route to User Preferred Route or vice versa shall take place at any of the waypoints south of METIP on ATS routes P570 or G450.

- In case the UPR is not entering or exiting Chennai/Mumbai FIR over a waypoint on the eastern/western or southern boundary of Chennai/Mumbai UPR zone the coordinates of the point at which the UPR is entering or exiting Chennai/Mumbai FIR shall be mentioned in the route field of the flight plan, except that entry/exit at Mumbai/Male and Chennai/Male FIR boundaries shall be via waypoints LATIK, ELKEL, MANAP, RULSA, OVPUK, IPNEB, OMLEV, ESLAV, BIBGO, POXOD, NODOL, NOKID OSERA and SEBLO.

(NOTE: Above mentioned entry/exit restrictions at Mumbai/Male and Chennai/Male FIR boundaries are imposed, due to restrictions mentioned in Male AIP supplement on the same subject)

- UPRs must be constructed via published waypoints, navigation aids, or positions designated by latitudes and longitudes.

- If the UPR is intersecting any ATS route within Mumbai/Chennai UPR zone the intersecting point shall be mentioned in the route column of flight plan as a position designated by latitude and longitude.

- Time interval between waypoints shall not exceed 30 minutes.

- UPRs may include ATS routes

2.4

Contincency Measures

In case of contingencies like failure of ATS automation system, failure of ADSC/CPDLC system etc., a NOTAM will be issued suspending permission for UPRs in Chennai/Mumbai FIRs. All flights intending to flight plan UPR in Chennai/Mumbai FIR and departing after the promulgation of NOTAM shall alter flight plan via a conventional ATS route. The flights already in air will be accommodated via flight planned UPR to the extent possible but may be re-cleared via nearest conventional ATS route if traffic situation demands so.

A flight unable to establish contact with Chennai/Mumbai CPDLC (VOMF/VABF) shall endeavour to establish contact on HF or SATCOM telephone as soon as possible. Such flights may also be re-cleared via nearest conventional ATS route if traffic situation demands so.

A flight unable to fly UPR due in-flight contingencies and requiring alternate clearance via conventional ATS route may request Chennai/Mumbai OCC for an alternate clearance. Such flights will be issued clearance as appropriate.