AIP
URUGUAY
GEN 1.1-1
01 DEC 2010
GEN 1. NATIONAL REGULATIONS AND REQUIREMENTS
GEN 1.1 DESIGNATED AUTHORITIES
The addresses of the designated authorities concerned with facilitations of international air navigation are as follows:
1. Dirección Nacional de Aviación Civil
e Infraestructura Aeronáutica (DINACIA)
Av. de las Industrias Wilson Ferreira Aldunate
(ex Camino Carrasco) 5519
14002 Canelones - URUGUAY
!Tel.: 2604 0408 ext. 4002
!Fax: 2604 0408 ext. 4053
e-mail: [email protected]
5. Health
Ministerio de Salud Pública
División Epidemiología
18 de Julio 1892 piso 4
11200 Montevideo - URUGUAY
!Tel.: 2400 0101 (in A.I.C. 2604 0341 or
!2604 0329 extension 1270)
2. Meteorology
6.
Oficina Meteorológica
Aeropuerto Intl de Carrasco "Gral. Cesáreo
L. Berisso"
14000 Canelones - URUGUAY
!Tel.: 2604 1134 and 2604 0329 extension 1234 and
!1235;
!principal: 2604 0154 and 2604 0329 extension 1299;
!predictor: 2604 0299 y 2604 0329 extension 1230;
!administrative and technical secretary: 2604 9004 and
!2604 0329 extension 1231
!Fax: 2604 0242
Telex: DINAMET UY 22052
AFS: SUMUYMYX, SUZZMAMX
e-mail: [email protected] ;
[email protected]
Airport Rules
Dirección Gral. de Infraestructura Aeronáutica
Av. de las Industrias Wilson Ferreira Aldunate
(ex Camino Carrasco) 5519
14002 Canelones - URUGUAY
Telegraph: COM DGIA Montevideo
!Tel.: 2604 0310 – 2604 0074 – 2604 0352
!Fax: 2604 0064
3. Custom
Dirección Nacional de Aduanas
25 de Agosto 1825 s/n y Yacaré
11000 Montevideo - URUGUAY
!Tel: 2915 0007 (en AIC 2604 0263,
!2604 0221 ext. 1267)
7. Airport Services
Candysur - SATA
Aeropuerto Intl. de Carrasco
14000 Canelones - URUGUAY
!Tel.: 2604 0375
!Fax: 2604 0374
4. Immigration
Dirección General de Migración
Misiones 1513
11000 Montevideo - URUGUAY
!Tel: 2916 1419 – 2916 0471 – 2916 1094
! (in AIC 26040322 or 26040329 ext. 1365
!and 2604 0161)
8. Animal Health Service
Colonia 892 piso 3
11100 Montevideo - URUGUAY
!Tel.: 2908 0028 (in A.I.C. 2604 0320)
AIS URUGUAY
AMDT NR 37
GEN 1.1-2
28 MAY 2015
AIP
URUGUAY
9. Dirección General de Infraestructura Aeronáutica (DGIA)
Av. de las Industrias Wilson Ferreira Aldunate (ex Camino Carrasco) 5519
14002 Canelones – URUGUAY
Telegraph : COM DGIA Montevideo
Tel.: 2604 0025; 2604 0408 Ext. 4400/4401
Fax: 2604 0064
e-mail: [email protected]
10. Phytosanitary Service – Vegetal Health Service
Millán 4703
12900 Montevideo - URUGUAY
Tel.: 2309 7924 – 2309 4442 (in A.I.C. 2604 0329 extension 1347) 2604 0069
11. Aircraft accident investigation
!
Comisión Investigadora de Accidentes de Aviación
Av. de las Industrias Wilson Ferreira Aldunate (ex Camino Carrasco) 5519
14002 Canelones – URUGUAY
!Tel. Fax: (598) 2601 4851
!Tel.: (598) 2604 0408 extensions: 5172 and 5146 (MON - FRI 11:00 to 19:00 UTC)
!Tel. MDN: (598) 2487 2828 (H24)
!Tel. SUMU: (598) 2604 0329 extension 1364
!Tel. DINACIA: (598) 2604 0408, 2601 0932 (H24)
!e-mail: [email protected]
12. Servicio de Inspectores de Transporte Aéreo Comercial
Dirección General de Aviación Civil
Dirección Transporte Aéreo Comercial
Jefatura de Inspectores
14002 Canelones - URUGUAY
Tel.: 2604 0408 extensions 4042/4043
Tel./Fax: 2604 0424
Hours: MON - FRI 11:00 to 19:00 UTC
Tel. SUMU: Fax 2604 0290 (H24) and 2604 0329 extension 1-1364
Tel. SULS: Fax 4255 9007 (H24); and 4255 9777 extension 157
Tel. SUAA: Operations 2322 8035 (Hours from 11:00 to 23:00 UTC)
13. Dirección General de Aviación Civil (DGAC)
Av. de las Industrias Wilson Ferreira Aldunate (ex Camino Carrasco) 5519
14002 Canelones – URUGUAY
Tel.: 2604 0408 ext. 4035
Fax: 2604 0427
e-mail: [email protected]
AIRAC AMDT NR 01
AIS URUGUAY
AIP
URUGUAY
GEN 1.1-3
01 DEC 2010
14. Air Force Uruguay
Comando Aéreo de Operaciones
Centro de Operaciones Aéreas (COA)
Mendoza 5553
12300 Montevideo - URUGUAY
!Tel.: 2222 4203; 2222 4400 (extension 1408, 1409)
!Fax: 2227 3625
Cell phone: 099602653
AFS: SUBLYWYX, SUBLYXYX
e-mail: [email protected]
[email protected]
15. AVSEC National Direction
Av. de las Industrias Wilson Ferreira Aldunate (ex Camino Carrasco) 5519
14002 Canelones – Uruguay
AVSEC National Direction (Aviation security against unlawful interference acts)
!Tel.: 2604 0408 Principal: extension 4475
Secretary: extension 4476
Fax: extension 4477
e-mail: [email protected]
!AVSEC Sub-Principal and Inspector Offices
!Tel.: 2604 0408 Sub-Principal: extension 4003
Inspector Office: extension 4058
Fax: extension 4058
e-mail: [email protected]
AIS URUGUAY
AMDT NR 37
INTENTIONALLY
LEFT BLANK
AIP
URUGUAY
GEN 1.2-1
28 MAY 2015
GEN 1.2 ENTRY, TRANSIT AND DEPARTURE OF AIRCRAFT
1. General
1.1 International flights into, from or over Uruguayan territory shall be subject to the current Uruguayan regulations
relating to civil aviation. These regulations correspond in all essentials with the following regulations:
1) Código Aeronáutico (Aeronautical Code) - Act 14,305 dated November 29th, 1974
2) Digesto Aeronáutico de la República Oriental del Uruguay - Collection of Acts and Decrees
approved by the Executive, from the years 1942 to 1980 inclusive.
!3) Decree: 160/013 dated May 24th, 2013 and AIG RAU Regulations for Research Accidentes and
!Incidents of Civil Aviation, approved by DINACIA resolution 657-2010 with the attributes
!delegated by the Executive Branch.
4) Decree: 114/77 dated 01 MAR 1977
78/78 dated 08 FEB 1978
7/80 dated 23 FEB 1980
22/81 dated 20 JAN 1981
454/82 dated 01 JAN 1982
(all modify the maximum amount of the Fine under Title XVI, Article 193 of Act 14,305,
dated 29 NOV 1974 - Aeronautical Code-)
5) Decree NR 611/78, dated 03 NOV 1978: Documentation system is established for international
airlines
6) Decree NR 420/003 as modified by Decree NR 317/003
7) Decree NR 636/81, dated 22 DEC 1981: Title XIII Article 181 of the Aeronautical Code (airline
liability amounts) is updated.
8) Decree NR 261/994, dated 07 JUN 1994: Compulsory Sworn Statement from arriving passengers.
9) Decree NR 363/94, dated 16 AUG 1994: Safety Regulations - Code offenses and penalties for the
International Airports of the República Oriental del Uruguay.
1.2 Aircraft flying into or leaving the territory of Uruguay shall make their first landing or final departure at an
International aerodrome/heliport (see AIP URUGUAY, sections AD 1.3, AD 2 and AD 3).
1.3 Provisions applicable to landing, parking or shelter aircraft at aerodromes depending from the
Dirección Nacional de Aviación Civil e Infraestructura Aeronáutica.
1.3.1 The parking area of aerodromes is under the jurisdiction of the Dirección Nacional de Aviación Civil e
Infraestructura Aeronáutica which is carried out through the Dirección de aeropuertos (Operations office) or through
the administration of the aerodrome.
1.3.2 The fares and landing rights as well as parking and shelter of aircraft are published in the GEN 4 section of AIP
URUGUAY. The payment will be made in accordance with the regulations of such section.
1.3.3 The problems related to maintenance and refuelling must be agreed by the owners of aircraft with refuelling
companies, workshops aeronautical companies, flying clubs and private companies, as appropriate.
1.3.4 Under no circumstances the Dirección Nacional de Aviación Civil e Infraestructura Aeronáutica will be
responsible for deterioration, theft, damage of any kind during the stay of the aircraft in an aerodrome whether during
landing, take off, parking area, hangars or it is being towed. The owners will have to safeguard and watch over their
aircraft at all times.
AIS URUGUAY
AIRAC AMDT NR 01
GEN 1.2-2
01 DEC 2006
AIP
URUGUAY
1.4 Landing at non-international airports (with custom office) either as a destination or as an
alternate airport
1.4.1 If in case of an emergency, an aircraft leaving or coming to Uruguay, either national or from abroad, and has to
land at a non-international airport or anywhere else, the pilot in command will have to comply with the following:
a) the pilot will have to report his/her landing immediately to the nearest Police Station;
b) the pilot or any other person aboard must not move away from the aircraft until authorization to do so is
given, except in case of extreme necessity or until after the authority has checked the documentation of
the people and aircraft;
c) the pilot will be able to proceed with his/her flight when authorization to do so is given.
d) goods, baggage or mail from the aircraft must be removed except in case of extreme necessity.
1.5 Traffic of people and vehicles at aerodromes
1.5.1 Zone limits
1.5.1.1 An aerodrome building is divided into two areas:
a) a public area open to the general public
b) a restricted area which comprises the rest of the building.
1.5.2 Movement of people
1.5.2.1 Access to the restricted area will be authorized only according to the special regulations of the aerodrome
1.5.2.2 Customs inspection, Police, Operations, Health unit and other offices assigned to traffic in transit, are normally
only accessible to passengers, staff of public authorities and airlines and staff carrying out their duties in such areas.
1.5.2.3 The movement of people who have access to the restricted areas of the aerodrome is subject to the
conditions and regulations of air traffic and special requirements established by the administration of the aerodrome.
1.5.3 Movement of vehicles
1.5.3.1 The movement of vehicles in the restricted areas is limited to the vehicles driven or used by people who hold a
special permit or have an official card of access.
1.5.3.2 The drivers of the vehicles, whatever type of vehicle it is, and which get around within the limits of the
aerodrome, must respect the direction of the traffic and speed limits stated, and comply with the requirements of the
authority of the aerodrome.
1.5.3.3 !Drivers must know the system of signals used by the control tower and will limit all their movements to what
such authority indicates. The instructions are given via VHF/FM, for vehicles equipped with a radio.
AMDT NR 26
AIS URUGUAY
AIP
URUGUAY
GEN 1.2-3
01 AUG 2000
The Control Tower has a gun flares. The code employed is as follows:
a) Steady GREEN light "Authorized to circulate"
b) Steady red light: "Shut off"
c) A series of RED flashes: "Circulate separated of the aircraft transit zones," which is to say that upon
receipt of this signal must immediately leave the transit area of aircraft (runways, taxiways and
access to the apron), and
d) A series of WHITE flashes, "Return to the starting point of the vehicle."
Subject to strict compliance of the above, it shall be denial of access to runways and taxiway, the switch on of the
demarcation lights of any of the runways.
2. Scheduled flights
2.1 For regular international scheduled flights operated by foreign airlines into or in transit across Uruguay, must be
met to the established in Article 115 of the Aeronautical Code República Oriental del Uruguay (International Air
Services, by Foreign Companies), that reads as follows:
1) Foreign companies may perform international air transportation services in accordance with international
conventions signed by the Republic and prior grant of permission to the Executive. To this end the
Executive will require:
a) to establish an agent in the Republic
b) that constitutes home to all legal purposes in the Republic,
c) expressly submit to the national jurisdiction.
2) when dealing with international public transport services, the grant or authorization is granted to include
at least the same obligations as those imposed on domestic companies providing similar services.
2.2 Documentary requirements for clearance of aircraft
!Decree 611/978 - Establishing a system of documentation for international airlines:
!Art. 1) The international air transport companies, on arrival or departure airport, any of its aircraft, must
submit the following documents:
a) General declaration,
b) Cargo Manifest, and
c) Boarding-landing card for each passenger arriving or leaving the country.
Art. 2) The documents referred to in the preceding article shall be made according to the formats and records of
the forms attached to Annex 9 of the International Civil Aviation Convention on Facilitation of International Air
Transport and its amendments.
Art. 3) The documents referred to in Article 1, shall be delivered to:
- The Dirección General de Aviación Civil:
a) A copy of the General Declaration, and
b) a Cargo Manifest.
- The Dirección General de Infraestructura Aeronáutica:
a) A copy of the General Declaration, and
b) A Cargo Manifest.
AIS URUGUAY
AMDT NR 08
GEN 1.2-4
01 AUG 2016
AIP
URUGUAY
- The National Customs:
a) Two copies of the General Declaration, and
b) Three Cargo Manifest.
- The Department of Migration:
a) A copy of the General Declaration, specifying the number of passengers embarking or disembarking,
b) The Boarding-landing cards.
- Health Service:
a) A copy of the General Declaration, and
b) A Cargo Manifest.
Art. 4°) REPEALED BY DECREE NR 376/980 DATED JULY 8, 1980.
Art. 5°) In connection with the use of the documents required for entry or departure of aircraft, visas are not
required, nor taken any class rights.
Art. 6°) The National Directorate of Migration shall deliver the Police Authority outstanding on-site copy of the
embarkation and disembarkation cards, also making available to the authorities referred to in this Decree, which
require it, the list or lists that are made as resulting from the embarkation or disembarkation cards.
2.3 Public health measures applied to aircrafts
!2.3.1 It applies health checks on aircraft in order to verify the absence of clinical signs or symptoms or sources of
pollution that pose a risk to public health.
!2.3.2 Sanidad Aérea shall check aircraft to maintain disinsectisation measures, requesting the declaration of the
method used, and the validity.
!2.3.3 Additional measures may be applied when the aircraft comes from affected areas according to WHO.
3. Non-scheduled flights
3.1 Procedures
3.1.1 If an aircraft operator intends to carry out a flight or series of flights within the territory and territorial waters of
Uruguay, in order to land or take on passengers, cargo or mail, must obtain permission, at the Dirección General de
Aviación Civil.
3.1.2 The regular service is not considered "accidental" when flights are made a matter involving imminent,
temporary and sporadic. In this capacity the companies concerned may carry out, previously authorized by the
Dirección General de Aviación Civil del Uruguay (who shall take into account the national interest) those flights
without limitation does not require that the company is authorized to operate in the Republic.
3.1.3 Applications for performing non-scheduled "accidental" shall be forwarded to the Dirección General de Aviación
Civil of Uruguay by correspondence or telegraph, in the latter case, response and at least pay in advance at least 24
hours Uruguayan air space entry, may be less in cases of urgency duly substantiated. This should include the
following data:
- type, registration number and nationality of the aircraft,
- name and surname of the owner and crews,
- postal and telegraph, telex and telephone number of owner or operator,
- licensing of flight personnel,
- flying object,
- number of passengers,
- point of departure and destination,
AMDT NR 50
AIS URUGUAY
AIP
URUGUAY
GEN 1.2-5
01 APR 2005
- date and approximate time of entry to the Uruguayan airspace and landing,
- route to follow,
- aerodrome of scale,
- frequency and communication features of your radio station,
- in case of load carried, shall specify the nature and characteristics of it.
Note: The authorization granted will expire 15 days granted in cases that had not been used.
3.1.4 When the company concerned wishes to be authorized to operate in the Republic as non regular airline charter,
must meet the requirements of the Dirección General de Aviación Civil, then go to study of the Comisión Nacional de
Política Aeronáutica, constitutes by Decree 343/75 dated April 22nd, 1975, and then get approval from the Executive.
In the case of foreign companies, applications must be accompanied by the official record that the country of origin of
the aircraft or the registration, has authorized the transaction for which the permit is processed.
Note: Air Taxi services are not covered by previous rules. According to Article 116 of the Aviation Code, the
Executive will regulate the air taxi companies’ conditions of service and set their rates (Dec. 269/78 of May
16th, 1978).
3.2 Overflights - Technical Scales
3.2.1 If an operator wishes to perform an overflight of the Uruguayan territory or have need for a technical scale in a
custom airport, must obtain a permit, by the Dirección General de Aviación Civil. This authorization can be handled by
correspondence or Telegraph, the latter with paid reply, providing the information required in paragraph 3.1.3. The
application must be filed in time for the flight, and should be addressed to the following address:
Postal address:
Dirección General de Aviación Civil del Uruguay
!Av. de las Industrias Wilson Ferreira Aldunate (ex Camino Carrasco) 5519
!14002 Canelones – URUGUAY
Telegraphic address: AEROCIVIL - MONTEVIDEO
In case you have to make an emergency landing without authorization, the pilot in command must notify the fact of
arrival to the aerodrome Chief and justify in writing to the Dirección General de Aviación Civil of the same reason.
3.3 Requirements for documentation for the clearance of aircraft
3.3.1 The documents must be identical to that required for regular flights.
3.4 Measures of Public Health applied to aircrafts
3.4.1 The public health measures will be identical to those required for regular flights.
4. Private flights
4.1 Advance notification of arrival
4.1.1 All foreign private aircraft whose state registration is a member of the International Civil Aviation Organization
(ICAO) and is not engaged in conduct commercial air transport or aerial work in general, can land on or
overflight the territory of the Republic of Uruguay prior to send to the initiation of the flight a notice of arrival
flight or overflight with the data specified in 4.1.2 or otherwise been included in the transmitted portion of the
flight plan, the data included in 4.1 2 b).
AIS URUGUAY
AMDT NR 21
GEN 1.2-6
01 AUG 2016
AIP
URUGUAY
4.1.2 The aircraft belonging to foreign states with license that are not members of the International Civil Aviation
Organization (ICAO) and not engaged to perform services for commercial air transport or aerial work in general shall
send a notice to the entrance in good time to ensure that the Dirección General de Aviación Civil receives it. The
notice shall contain the following requirements:
a) registration and nationality of the aircraft,
b) Name, postal and telegraph address, telex and telephone number of owner or operator,
c) name of the crew and passengers,
d) object of the flight,
e) origin aerodrome, route and point of entry to the proposed FIR, aerodrome of income if arrival or destination if
overflight,
f) date and approximate time of entry into the FIR and arrival.
4.1.3 In accordance with the provisions of ICAO Doc 7030, any aircraft wishing to enter Uruguayan territory shall
submit a flight plan to the relevant air traffic control, which shall forward the flight plan to the MONTEVIDEO Area
Control Centre.
4.1.4 Foreign aircrafts of tourism and sports will be considered in transit if they do not stay more than 4 (four) months
in the country in total and in the calendar year.
4.2 Documentary requirements for clearance of aircraft
4.2.1
a) the aircraft: Registration certificate, airworthiness certificate and operating limitations,
book of aircraft and engines, daily log.
b) the crew: License for the role on board of the holder.
c) passengers: Passport with appropriate visa, except in cases where there are special agreements or
arrangements for the admission of passengers with other documents.
d) With respect to the boarding/disembarking Cards, General Declaration, etc., the requirements are
identical to regular flights.
4.3 Public health measures applied to aircrafts
4.3.1 The public health measures will be identical to those required for regular flights.
!4.3.2 The Health Declaration should be presented.
!4.3.3 Aerodrome Sanidad Aérea office has Health Declarations forms and recommendations about disinsectisation
methodologies.
5. Military flights and/or foreign State
The overflight permission and / or landing (PSA) is the authorization issued by the State for public aircraft of another
State overflying or landing in Uruguay. Applications must be submitted to the Estado Mayor of the Uruguayan Air
Force (Liaison Officer - Tel: (598) 2222 8113 from 08:00 to 17:00 local time) with 48 hours in advance using Form FA
NR 116.
The Air Operations Centre (COA) is the agency responsible for granting authorizations for PSA to foreign state aircraft
for conducting flights within the Uruguayan airspace.
The number of PSA must be inserted in box 18 of the Flight Plan form and can be requested by the ATS.
AMDT NR 50
AIS URUGUAY
AIP
URUGUAY
GEN 1.3-1
01 AUG 2016
GEN 1.3 ENTRY, TRANSIT AND DEPARTURE OF PASSENGERS AND CREW
1. Customs requirements
1.1 We inspect all the baggage, except those who come through diplomatic channels.
1.2 During the stay of any aircraft in Carrasco "General Cesareo L. Berisso"Intl Airport, it must be guarded by
officials of the Department of Airports of the National Directorate of Customs.
2. Immigration requirements
2.1 After landing, passengers must be submitted to the authorities for the purpose of complying with the
formalities for entering the country, with the exception of transit passengers, provided that their stay in the relevant
!airport does not exceed 24 hours.
2.2 A person who enters Uruguay, for immigration purposes must have: a valid passport and immigration visa,
issuing the latter in Uruguay consulates abroad. Temporary visitors must have a valid passport, with the exception of
nationals of Argentina, Brazil, Chile and Paraguay, which can enter the country with Identity Card. Not require entry
visas for temporary visitors from the following countries: Albania (only PDipOfSer), Germany, Argentina, Austria,
Bahamas, Barbados, Belgium, Belize, Bolivia, Brazil, Bulgaria (only PDipOfSer), Canada (PCOM only) Chile, China
(only PDipOfSer), Colombia, South Korea (only PDipOfSer), Costa Rica, Croatia, Denmark, Ecuador, El Salvador,
Egypt (only PDipOfSer), Slovenia, Spain, United States (only PCOM), Finland, France , Greece, Guatemala, Guyana
(only PDipOfSer), Holland, Honduras, Hungary, India (PDipOfSer only), Ireland (only PCOM), Iceland, Israel, Italy,
Jamaica, Japan, Liechtenstein (PCOM only), Lithuania, Luxembourg, Malaysia , Malta (PCOM only), Morocco (only
PdipOfSer), Mexico, Nicaragua, Norway, New Zealand, Panama, Paraguay, Peru, Poland, Portugal, United Kingdom,
Czech Republic, Dominican Republic (PCOM only), Romania (only PDipOfSer) Russia (only PDipOfSer), Seychelles
(PCOM only), South Africa (only PCOM), Sweden, Switzerland, Trinidad and Tobago, Turkey, Venezuela.
PDipOfSer = Diplomatic, Official and Service Passports.
PCOM = Common Passport.
In the text detailed above when the country's name appears alone, it means you do not need visa to both PCOM and
PDipOfSer.
Citizens of countries not included in this list are subject to the requirement of consular visa to both PDipOfSer and
PCOM.
Laissez Passer European Community, OEA Presidents and UN Laissez Passer, do not need visa.
The ICAO E/D standard card is required to all countries.
2.3As regards the members of the flight crew for regular services to retain their licenses when embarking and
disembarking, remain at the airport where the aircraft has a scale or within the city limits adjacent to it, and leaving the
same aircraft or on the next scheduled flight from Uruguay, accepted his crew license or certificate in lieu of a
passport or visa for temporary admission to the Republica O. del Uruguay. This provision does not apply if the crew
had entered the country by other means, then having to meet the same requirements as a common passenger. If the
crew leaves as a passenger, the company must make the relevant application in advance and in writing, to the
Immigration authorities.
2. For leaving it is required to the embarking passengers, the same formalities that are required to entry the
country.
AIS URUGUAY
AMDT NR 50
GEN 1.3-2
01 DEC 2001
AIP
URUGUAY
3. Public health requirements
It does not require passengers to disembark the presentation of vaccination certificate, except when coming directly
from an area infected with cholera, yellow fever or smallpox.
AMDT NR 12
AIS URUGUAY
AIP
URUGUAY
GEN 1.4-1
01 JUN 1997
GEN 1.4 ENTRY, TRANSIT AND DEPARTURE OF CARGO
1. Customs requirements concerning cargo and other articles
1.1 All goods to be imported must be accompanied by a cargo manifest, and have an Air Waybill and the Import
Permit. Upon payment of royalties and presentation of permits issued, goods will be delivered to the recipient.
1.2 The export of goods is authorized by the authorities if there is documentation handled by a customs broker.
1.3 Upon receipt of goods for air transport, the carrier shall require the consignor the "air waybill". If the
document is issued by the carrier, at the request of the consignor, shall, unless the contrary that the carrier has acted
on behalf of the consignor.
1.5 Upon request, brought before the National Customs Directorate (Central Building) may be exported without
the presentation of shipping permission: commodities such as samples, film developing, family gifts and products to
analyze.
2. Requirements relating to animal and plant quarantine
2.1 All animals and animal products entering the country must be accompanied by a certificate issued by the
origin Official Ministry or the appropriate office and approved by the Uruguayan Consul accredited there. This
certificate must be submitted at the time of landing and when requested.
2.2. In the case of the importation of dogs, when accompanied by the "pedigree", this too shall come stamped
by the Consul of Uruguay.
2.3 All animals or animal products when exported must be inspected by the Health Directorate who granted the
authorization. The permit for the export of cats and dogs must be handled within 10 days prior to shipment, presenting
an official certificate or private.
2.4 For dogs and cats require rabies vaccine whose duration shall not exceed 1 year or less than 15 days after
application.
2.5 Any plant or part thereof that is imported into the country, or it is exported, in whatever form, shall:
a) be submitted to his office for inspection by the Plant Health,
b) must be accompanied by phytosanitary certificate obtained at the place of origin and legalized by the
Uruguayan Consul accredited there. (For Argentina consular visa is deleted).
2.6 For vacuum-packed vegetables do not apply these requirements and must pass the same only by Customs.
2.7 It is forbidden the entry of all types of birds to our country, if this happens should re-embark to the place of
origin, otherwise these services are authorized to proceed to slaughter them.
2.8 The animal products and subproducts (sausages, etc..), who enter with the passengers' baggage will be
confiscated by the Service, styling the relevant Act and proceeding to denaturation in the presence of the person
concerned.
2.9 The passenger must submit to their arrival, the Affidavit required, according to Decree 261/94 from 07 JUN
1994.
AIS URUGUAY
3RD EDITION
INTENTIONALLY
LEFT BLANK
AIP
URUGUAY
GEN 1.5-1
02 JAN 2017
GEN 1.5 AIRCRAFT INSTRUMENTS, EQUIPMENT AND FLIGHT DOCUMENTS
1. General
Aircraft flying in Uruguay must comply with the provisions of the Rules of Civil Aviation of the República Oriental del
Uruguay, and the standards and recommended practices of ICAO.
To certified operators will be required copy of the AOC (Air Operators Certificate) on board the aircraft, according to
the RAU (Reglamento Aeronáutico Uruguayo - Uruguayan Federal Regulations) 121 and 135.
2. Special equipment to be carried
It will require the mandatory use of SSR transponder in Modes A and C throughout the airspace of the Montevideo
FIR, except operating in "G" airspace below FL 045.
!3. Optional equipment
!Aircrafts that fly throughout Montevideo FIR and were equipped with Mode S transponder must set the aircraft
!identification and activate it.
!This setting shall correspond exactly to the Aircraft Identification specified in Item 7 of the ICAO Flight Plan, or, if no
!flight plan has been filed, to the aircraft registration.
AIS URUGUAY
AMDT NR 51
INTENTIONALLY
LEFT BLANK
AIP
URUGUAY
GEN 1.6-1
02 JAN 2017
GEN 1.6 SUMMARY OF NATIONAL REGULATIONS AND
INTERNATIONAL AGREEMENTS/CONVENTIONS
Following is a list of civil aviation legislation, air navigation regulations, etc., in force in Uruguay. It is essential
that anyone engaged in air operations be acquainted with the relevant regulations. Copies of these documents may
be obtained from the Aeronautical Information Service. (Their address can be found on page GEN 3.1-1.)
The domestic and international flights to, from or over Uruguayan territory comply with the following regulations
!in Uruguay: RAU's, LAR, Aviation Code, Aviation Digest, Decrees, ICAO Annexes and Documents.
1. Controlled IFR Air Traffic routing between aerodromes "Jorge Newbery" or others and "Colonia" by
SURBO.
1.1 IFR flights will take place between 600 m (2000 ft) and FL 40 shall fly at altitudes or flight levels established in the
table of cruising levels inserted in the AIP of each State, except ATC clearance.
1.1.2 Air Traffic with destination Colonia Aerodrome (SUCA):
The aircraft shall receive the traffic permission from AEROPARQUE APPROACH up to the position SURBO.
From Aeroparque Jorge Newbery to SURBO the aircraft will be in communication with AEROPARQUE
APPROACH and from SURBO position, the aircraft will contact with Colonia TOWER. If the aircraft reaches the
position SURBO and has not established communication with Colonia TOWER or MONTEVIDEO ACC, must:
1°) In visual meteorological conditions (VMC)
a) Diurnal: Cancel IFR Flight Plan, continuing under the Visual Flight Rules.
b) Nocturne: Contact AEROPARQUE APPROACH who would be instructed to return to the departure or
routing to the alternate aerodrome, after coordination between AEROPARQUE APPROACH and BAIRES
CONTROL. BAIRES CONTROL will coordinate with MONTEVIDEO ACC the procedure to be adopted.
2°) In instrument meteorological conditions (IMC)
a) Diurnal or nocturne: contact with AEROPARQUE APPROACH who instruct their return to the departure
or routing to the alternate aerodrome, after coordination between AEROPARQUE APPROACH and
BAIRES CONTROL, BAIRES CONTROL will coordinate with MONTEVIDEO ACC the procedure to be
adopted.
1.1.3 Air Traffic destined to Aeroparque Jorge Newbery Airfield
COLONIA TOWER shall coordinate the transit permit with AEROPARQUE APPROACH through oral direct
link established.
1.1.4 In case of unavailability of the oral direct link it will be coordinated via ACC MONTEVIDEO/EZEIZA ACC.
1.1.5 Such permission shall extend from the position SURBO and shall include the following information:
a) Expected approach time
b) SSR Code assigned
c) Altitude or flight level (FL)
d) ATS Unit and how often you must communicate in SURBO.
AIS URUGUAY
AMDT NR 51
GEN 1.6-2
01 APR 2002
AIP
URUGUAY
1.2 SALTO INTERNATIONAL AIRPORT
Operational Agreement for the coordination of IFR procedures between CONCORDIA (ARGENTINA) and
SALTO (URUGUAY) airports.
1.2.1 Objective
1.2.1.1 The objective of this Operational Agreement is to establish procedures for air traffic coordination necessary to
ensure the safety of air operations taking place in the aerodromes of CONCORDIA and SALTO.
1.2.2 Extension
1.2.2.1 The procedures contained herein, supplement or detail when so required, the procedures described by ICAO
in the relevant documents and shall be applied to all air traffic to take place between the controlled airspace for both
aerodromes.
1.2.3 Routing of air traffic
1.2.3.1 IFR air traffic approaching or departuring from SALTO aerodrome entering CONCORDIA TMA/CTR shall be
previously coordinated between CONCORDIA/SALTO approach control units.
1.2.3.2 IFR air traffic approaching or departuring from CONCORDIA aerodrome entering SALTO CTR shall be
previously coordinated between CONCORDIA/SALTO approach control units.
1.2.3.3 Every air operation performed in accordance with instrument flight rules (IFR) shall be made in accordance
with the procedures published in the AIP MAP and En-route Charts of the respective States involved.
1.2.3.4 It may authorize procedures other than those announced in paragraph 1.2.3.3, after coordination and
approval from EZEIZA ACC and MONTEVIDEO ACC.
1.2.3.5 Given the need to overfly the airspace jurisdiction of SALTO CTR during approach operations or instrument
departures to CONCORDIA aerodrome, the Dirección Nacional de Aviación Civil e Infraestructura Aeronáutica of
Uruguay provides for the implementation of the above procedures by the Autoridad Aeronáutica Argentina (as
expressed in paragraph 1.2.3.3).
1.2.3.6 Given the need to overfly the airspace jurisdiction of CONCORDIA CTR during approach operations or
instrument departures to SALTO aerodrome, the Autoridad Aeronáutica Argentina provides for the implementation of
the above procedures by the Dirección Nacional de Aviación Civil e Infraestructura Aeronáutica of Uruguay (as
expressed in paragraph 1.2.3.3).
1.2.3.7 In the event that both airports have simultaneous instrumental traffic shall be allowed only an instrument
procedure at a time (approach or departure) according to the purposes of the Air Traffic Control Services.
1.2.3.8 In case of failure of radio aids of CONCORDIA or SALTO, it is agreed the use of an alternate instrument
approach procedure that has the holding pattern over the other state radio aid.
AMDT NR 13
AIS URUGUAY
AIP
URUGUAY
GEN 1.6-3
01 APR 2002
1.2.3.9 To this end both administrations will exchange their respective aeronautical approach charts and the
application is subject to coordination of both controls for the use of flight levels and shift to start the approach
procedure.
1.2.4 Flight Information Service and/or Advice
1.2.4.1 Both Control Units will be provided each other about all known traffic information to allow other aircraft are
using the airspace under its jurisdiction, do not interfere with the aircraft that is conducting instrument approach
procedure or instrument departure.
1.2.5 Approach Control Services
1.2.5.1 Transfer of Responsibilities
1.2.5.1.1 Unless otherwise coordinated, the responsibility for the provision of approach control services to aircraft to
be carried out instrument approach to CONCORDIA aerodrome, are the responsibility of CONCORDIA Control
Approach unit until the aircraft has completed the instrument approach procedure (including the missed approach).
1.2.5.1.2 Unless otherwise coordinated, the responsibility for the provision of approach control services to aircraft to
be carried instrument departures from CONCORDIA aerodrome, are the responsibility of CONCORDIA Control
Approach unit until the aircraft has established on the route.
1.2.5.1.3 Unless otherwise coordinated, the responsibility for the provision of approach control services to SALTO
aerodrome, are the responsibility of SALTO Control Approach unit until the aircraft has completed the instrument
approach procedure (including the missed approach).
1.2.5.1.4 Unless otherwise coordinated, the responsibility for the provision of approach control services to aircraft to
be carried out instrument approach to SALTO aerodrome, are the responsibility of SALTO Control Approach unit until
the aircraft has established on the route.
1.2.5.2 Transfer of Air-Ground Communications
1.2.5.2.1 Approach Control Dependencies of CONCORDIA and SALTO, maintain communications with aircraft
arriving or departing according to Instrument Flight Rules, unless otherwise coordinated.
1.2.5.3 Vertical separation
1.2.5.3.1 Within the respective CTR establishes the transition altitude for aerodromes of CONCORDIA and SALTO in
900 M/3.000 FT (QNH). The transition level shall be provided by the respective approach control units applying for
this a transition layer at least 300 M/1.000 FT.
AIS URUGUAY
AMDT NR 13
GEN 1.6-4
01 APR 2014
AIP
URUGUAY
1.2.5.3.2 During the holdings, both aerodromes shall use the same QNH value for the vertical separation of aircraft.
Always use the lowest QNH value of both as a unique reference. Initiated approach, the aircraft will adjust the
altimeter according to the QNH value for your destination aerodrome.
1.2.5.3.3 In order to determine the separation in holding patterns established on the radioaids of both aerodromes,
airspace is considered as only one, having used vertical separation of at least 300 FT M/1.000 between aircrafts.
2. Substantial parts of the Operational Agreement between EZEIZA ACC and MONTEVIDEO ACC for
routing traffic between both control centres signed in Lima, Peru on August 12, 2010 (effective date
!March 10, 2011).
2.1 IFR Air Traffic Routing
2.1.1 IFR air traffic that cross the common boundary of the indicated FIR will be routed by the ATS routes published
in the AIP and navigation charts of the States affected by this Agreement.
2.1.2 Route paths may be used which differ from those mentioned in 2.1.1 prior coordination and agreement between
the two Control Centres, where circumstances that affect flight safety.
2.1.3 IFR air traffic using RVSM airspace between FL 290 and FL 410 inclusive will be routed according to 2.1.1. In
addition, you must use the cruising levels published in Appendix 1 paragraph 3.2 of the Agreement signed by both
states, both for traffic entering or leaving MONTEVIDEO FIR and/or EZEIZA FIR, as appropriate.
2.2 VFR Air Traffic Routing
2.2.1 MONTEVIDEO ACC and Ezeiza ACC will not accept any traffic which has not received the flight plan.
2.2.2 VFR traffic that crosses the common boundary of the Ezeiza FIR and MONTEVIDEO FIR will be routed by ATS
routes and corridors published in the AIP, navigation charts and VFR Charts of the States affected by this Agreement.
2.2.3 Route paths may be used which differ from those mentioned in 2.2.2 prior coordination and agreement between
the ACC, when they are affected by any of the following:
a) adverse weather conditions or
b) establishing non-permanent restricted, prohibited or dangerous areas;
c) contingencies previously agreed between the two Administrations.
2.2.4 All VFR traffic from Ezeiza FIR originating at Jorge Newbery, San Fernando or other aerodromes and whose
destination is an airport located in Republica Oriental del Uruguay, except Colonia (SUCA) will be directed by Martin
Garcia island (Visual Corridor NR 2 Argentina) with a minimum altitude of 2500 FT and maximum of FL 045 will be
instructed to communicate/listen to Montevideo ACC. If your destination is Carrasco (SUMU), Adami (SUAA) and
Laguna del Sauce (SULS) aerodromes will be instructed to proceed to VFR 1 corridor (Uruguay). Traffic coming from
Carmelo (SUCM) to the Ezeiza FIR must use the Corridor NR 1 (Argentina).
AMDT NR 45
AIS URUGUAY
AIP
URUGUAY
GEN 1.6-5
01 DEC 2010
2.2.5 !All VFR traffic from Montevideo FIR, except Colonia (SUCA) and whose destination is Jorge Newbery
Airport, San Fernando or others will be routed to Martin Garcia Island with an altitude of 2000 FT.
2.2.6 !All VFR traffic from the Ezeiza FIR that originates from Jorge Newbery Airport, San Fernando or others and
whose destination is the airport of Colonia (SUCA) will be routed through the point SURBO and instructed to contact
with Colonia Tower.
2.2.7 !All VFR traffic from the airport of Colonia (SUCA) and whose destination aerodromes are Jorge Newbery
Airport, San Fernando or other will be routed through the point SURBO.
2.2.8 All VFR flights which have crossed the FIR boundary or the agreed point of transfer between ATS units shall
comply with the procedures established in the AIP of the FIR to which they are entering.
2.2.9 All aircraft shall maintain communication/listening on the frequency set according to the airspace to fly.
Transponder (Mode A and C) shall have operating and fly to altitudes or flight levels established in the table of
cruising levels inserted in the AIP of each State, as appropriate.
2.3 Flight Information Services
2.3.1 It will provide Flight Information Service to VFR/IFR crossing the common boundary of the FIR, only when they
cannot use the established routes for the reasons mentioned in paragraphs 2.1.3 and 2.2.3 respectively, except VFR
flights in Visual Corridor No. 2 Martin Garcia
(Argentina), there will be appropriate coordination. This coordination will include the transmission of the following
information about the flights concerned:
a) appropriate parts of the current flight plan, and
b) the estimated time on the agreed transfer point.
2.3.2 The information given will be transmitted at least five (5) minutes before the aircraft leaves the Flight
Information Region in charge of the ACC that has dictated.
2.3.3 The transferring Centre, shall assign an appropriate flight level prior coordination with the receiver Centre.
2.4 Area Control Services
2.4.1 Transfer of responsibilities and air-ground communications.
2.4.2 Responsibility for the provision of Air Traffic Services will be transferred from the Transferring Centre to the
Accepting Centre, when the latter obtains indication that the aircraft is flying near the transfer point specified in
Appendix 2 to this Operational Agreement, or other agreed transfer point, in accordance with paragraph 2.1.2.
2.4.3 The Accepting Centre may not alter the traffic permit until the aircraft has not flown the point of transfer, except
that previously coordinated. The transfer of communication will be carried out simultaneously with the transfer of
responsibility.
2.4.4 The Accepting Centre shall not need to notify the Transferring Centres when assumes responsibility indicated in
paragraphs 2.4.2 and 2.4.3, unless that need to make a correction to the permission granted.
AIS URUGUAY
AMDT NR 37
GEN 1.6-6
01 DEC 2010
AIP
URUGUAY
2.4.5 At the time chosen for the transfer of communication, the Transferring Centre shall authorize the aircrafts to
establish communication with the appropriate ATS unit.
2.4.6 The SSR code assigned to the flight concerned may be maintained.
2.4.7 The Transferring Centre shall notify the Accepting Centre the instructions that have been passed or are about
to be transmitted to the aircraft prior to that they establish communication with the appropriate ATS unit.
2.4.8 The Accepting Centre shall follow the procedures prescribed by ICAO in case that fails to communicate with the
aircraft to be transferred.
2.4.9 When not effected the transfer of Radar control, the aircraft shall not be vectored guided so as to get within five
nautical miles (5 NM) from the boundary of airspace that is responsible for the Radar Controller (FIR boundary)
except previously coordination.
2.4.10 Minima separation applicable during transfer
2.4.10.1 No radar longitudinal separation
2.4.10.1.1 The minimum longitudinal separation applicable between flights that will be transferred to the same
cruising level in the same ATS route or routes or paths converged, shall not be less than that specified for each case
in Appendix 2, columns 5 and 6 to this Operational Agreement.
2.4.10.2 Radar longitudinal separation
2.4.10.2.1 The minimum Radar longitudinal separation applicable between flights that will be transferred to the same
cruising level in the same ATS route or routes or paths converged, shall not be less than that specified for each case
in Appendix 2, columns 6 to this Operational Agreement.
2.5 Radar system failure or cut in ATS oral circuits
2.5.1 In case of failure, in any of the Radar Systems (MONTEVIDEO or Ezeiza) and ATS oral circuits, it will control
with No Radar separations (see Appendix 2 column 5).
2.5.2 Vertical separation
2.5.2.1 Normally the aircraft will be authorized to fly the transfer point maintaining a specified cruise level, which will
be selected from those listed for each case in Appendices 1, 2 and 6 of this Operational Agreement. But as well as
coordinated expressly with the Accepting Centre the Transferring Centre may authorize aircraft to cross the transfer
point ascending or descending from the cruising level previously agreed between ACC's.
AMDT NR 37
AIS URUGUAY
AIP
URUGUAY
GEN 1.6-7
01 APR 2014
2.6 Alert Service
2.6.1 Coordination for the provision of Search and Rescue Service lies with the Centre that has questions regarding
the status of the aircraft.
TELE/FAX RCC Ezeiza (Direct) (005411) 44802222
!2.7 Allocation and usage of SSR codes for IFR/VFR flights
!2.7.1 Procedures
!2.7.1.1 The following procedures are established for the usage of SSR codes by the IFR / VFR flights, developed
between EZEIZA and MONTEVIDEO ACC's.
!2.7.1.2 Ezeiza Area Control Centre shall use the following SSR code families assigned by ICAO:
Internationals: 0300-0400-0500
Nationals: 1500-1600-1700
!2.7.1.3 Montevideo Area Control Centre shall use the following SSR code families assigned by ICAO:
Internationals: 6000-6100-7300
Nationals: 1100-1200
!2.7.1.4 Aircraft may maintain the SSR code of origin assigned by the corresponding air traffic control unit within the
area of jurisdiction of both control centres.
!2.7.1.5 The transit permits shall be received by the accepting centre with SSR code assigned by the transferor
centre. This code shall be transmitted together with the Flight Plan Update (CPL).
!2.7.1.6 Unless otherwise coordinate an assigned code shall be kept by the transferor centre for a minimum of two
(2) hours from the point of transfer, before the Centre can assign it to another aircraft again.
!2.7.2 Contingency Plan
!2.7.2.1 If necessary, the Contingency Plan described in Appendix 5 of this Operational Agreement shall be applied.
!2.7.3 RNAV5 routes
!2.7.3.1 Those aircrafts that do not have the RNAV5 approval should be guided by existing conventional ATS
routes.
2.8 Appendix 1 to the Operational Agreement between Ezeiza ACC and Montevideo ACC
RVSM PROCEDURES
2.8.1 Flight levels
AIS URUGUAY
AMDT NR 45
GEN 1.6-8
01 APR 2014
AIP
URUGUAY
2.8.1.1 The assignment of flight levels for the transfer of responsibilities shall be as indicated in the Reference Table
for Transfer of Responsibilities of the Operational Agreement in force corresponding the "1" for tracks between 000º
and 179º and "2 "for tracks between 180° and 359°
2.8.1.2 RVSM Flight Levels to consider between FL 290 and FL 410 are listed below in accordance with Appendix 3)
of Annex 2 of ICAO:
1
000º to 179º
2
180º to 359º
FL 290
FL 310
FL 330
FL 350
FL 370
FL 390
FL 410
FL 300
FL 320
FL 340
FL 360
FL 380
FL 400
2.8.2 Transfer of responsibilities and communications in RVSM airspace
2.8.2.1 No transfers will be accepted between area control centres of aircraft that are not RVSM approved, except for
flights performed by State aircraft, maintenance/delivery or humanitarian reasons.
2.8.2.2 Non-RVSM approved aircrafts shall be transferred with available flight levels below FL 290 or above FL 410.
2.8.3 Vertical Separation
MINIMUM VERTICAL SEPARATION
FL 290 – FL 410
1000 FT
RVSM approved
1000 FT
2000 FT !
Non-RVSM approved
! Only for state aircraft, maintenance, first delivery, humanitarian or contingency.
AIRCRAFT
BELOW FL 290
ABOVE FL 410
2000 FT
2.8.4 Coordination for RVSM Operations
2.8.4.1 The messages of estimation (EST) of all non-RVSM approved aircraft (State aircraft, maintenance/first
delivery or humanitarian reasons) intending to operate within the RVSM airspace and crossing the common boundary
of two FIR's, shall be transmitted, at least 30 minutes before the estimated time of the aircraft on the transfer point in
order to plan the integration of the traffic with a minimum vertical separation of 2000 feet.
2.8.4.2 It must include a clear indication about the approval status of a non-RVSM approved aircraft and its
application for special treatment as an integral part of the estimated message:
a)
b)
c)
as confirmation of the data stored in the flight plan;
to provide for the degradation of system performance flight planning, and
to provide if for any reason the accepting unit has not received the flight plan.
AMDT NR 45
AIS URUGUAY
AIP
URUGUAY
GEN 1.6-9
01 APR 2014
2.8.4.3 Oral coordination of estimate (EST) messages
2.8.4.4 When using an oral coordination process, the ACC that transmits a message of estimation it must include at
the end of it, the information included in box 18 of the flight plan of ICAO for RVSM operations.
2.8.4.5 If applicable, it must include at the end of the message of estimation the term "NEGATIVE RVSM" or
"NEGATIVE RVSM State aircraft" or "NEGATIVE RVSM Flight Humanitarian" or "NEGATIVE RVSM Flight
Maintenance/Delivery".
2.8.4.6 For the case of a single aircraft that experiences a flight contingency, associated coordination messages, will
be provided orally by a description of the cause of the contingency. The associated coordination messages shall
incorporate either the word:
a)
b)
RVSM impossible due to equipment or
RVSM impossible due to turbulence, as appropriate.
2.8.5 Suspension of RVSM operations
2.8.5.1 The respective ACC coordinate the procedures for suspension of RVSM within the affected areas in the FIR
of jurisdiction, when there are pilot reports of turbulence greater than moderate. Within areas where RVSM
procedures are suspended, the minimum vertical separation between all aircraft will be 2000 feet, according to RVSM
levels specified in 2.8.1.2
2.8.5.2 The ACC that begin the suspension of RVSM operations shall coordinate any restriction/procedure with
adjacent ATS units.
AIS URUGUAY
AMDT NR 45
GEN 1.6-10
02 JAN 2017
AIP
URUGUAY
2.9 Appendix 2 to the Operational Agreement between Ezeiza ACC and Montevideo ACC
2.9.1 Reference table for the transfer of responsibilities
ATS
ROUTE
1
SURBO
Corridor
Table of flight levels and SSR
codes to be assigned by:
Montevideo
Ezeiza ACC
ACC
2
3
FL
SSR
FL
SSR
1
2
-
A314
1
-
2
-
A305
1
-
-
-
A306
-
-
2
-
UB555
1
-
2
-
UN741
-
-
2
-
UN857
1
-
-
-
A310
1
-
2
-
G680
1
-
2
-
B555
1
-
2
-
!UM424
1
-
-
-
UA306
-
-
2
-
UA310
1
-
2
-
UL324
1
-
2
-
UM654
1
-
-
-
UM534
1
-
2
-
UM418
1
-
2
-
AMDT NR 51
Transfer points agreed
for each route
Minimums applicable to longitudinal separation
Minute
Remarks
4
5
6
SURBO
34º26’58”S/057º57’38”W
10
PAPIX (b)
34º24’58”S/058º00’02”W
DORVO (b) (d)
34º42’58”S/057º31’02”W
SARGO (b) (d)
34º58’58”S/056º53’02”W
VOR/DME GUA (b) (c)
33º00’35”S/058º36’51”W
PAPIX (b)
34º24’58”S/058º00’02”W
DORVO (b)
34º42’58”S/057º31’02”W
DARKA
35º17’58”S/056º15’02”W
VOR/DME GUA (c)
33º00’35”S/058º36’51”W
VOR/DME GUA (c)
33º00’35”S/058º36’51”W
DORVO (b)
34º42’58”S/057º31’02”W
SARGO (b)
34º58’58”S/056º53’02”W
DARKA (b)
35º17’58”S/056º15’02”W
KUKEN (b)
34º10’58”S/058º13’02”W
KUKEN (b)
34º10’58”S/058º13’02”W
SUGRA (b)
32º12’34”S/058º11’24”W
RODOV (b) (f)
30º50’04”S/057º48’17”W
10 (a)
10 (a)
10 (a)
(e)
(e)
(e)
10 (a)
(e)
10 (a)
10 (a)
10 (a)
(e)
(e)
(e)
(e)
(e)
(a) The separation will be increased
by five (5) minutes when the ATS
Oral links fail
(b) Minimum longitudinal separation,
when Radar separation apply:
-20 NM between aircraft of the same
speed
-10 NM if the speed of the preceding
aircraft is 20 KT higher (true
airspeed)
(c) For routes that use GUA
VOR/DME the transfers shall be
made prior to 20 NM DME of GUA
VOR/DME for aircraft entering the
Ezeiza FIR. And on the GUA VOR
for aircraft entering MONTEVIDEO
FIR
(d) It will not accept VFR flights in
routes:
A305 by position DORVO and A306
by position SARGO
(e) 10 MIN/80 NM using Mach
number technique (MNT). The
separation will increase by 5 MIN/40
NM (MNT), when the ATS Oral links
fail
(f) The traffic transferences in route
UM418 shall be perform 15 minutes
before entering Montevideo FIR.
AIS URUGUAY
AIP
URUGUAY
GEN 1.6-11
01 APR 2014
Note: "1" and "2" indicate the series of IFR Flight Levels listed in Appendix 3) of ICAO Annex 2 and Appendix 1
(RVSM) to this Operational Agreement for the tracks of 000 degrees to 179 degrees and 180 degrees to 359 degrees,
respectively.
2.10 Appendix 3 to the Operational Agreement between Ezeiza ACC and Montevideo ACC
2.10.1 Reference table for the exchange of ATS messages
Type of
message
Circumstances in
which applicable
FPL
All flights
Immediately after being introduced
AFTN / Fax / Exceptionally
ATS Oral Circuit
CPL
All flights
Immediately after the occurrence of the
circumstance
Oral Circuit / AFTN / Fax
DLA
As required
Immediately after being introduced
AFTN / Fax / Exceptionally
ATS Oral Circuit
EST
All flights
CHG
As required
CDN
As required
ALR
As required
CNL
As required
RPL
As required
Limit time for transmission
Media to be used
15 MIN prior to EST transfer point
(weather permitting)
As soon as possible after occurrence of
the circumstance
As soon as possible after occurrence of
the circumstance
Immediately after the occurrence of the
circumstance
Immediately after the occurrence of the
circumstance
Oral Circuit
As soon as possible
AFTN / Fax
Oral Circuit / AFTN
AFTN / Fax
Oral Circuit / AFTN / Fax
AFTN / Fax / Oral Circuit
Note: Montevideo FAX….:(598) 2604 2298 (Communication station)
Ezeiza FAX………..:(5411) 4480-2222 (Ezeiza ACC)
(5411) 4480-2220 (Communication station)
2.11 Appendix 4 to the Operational Agreement between Ezeiza ACC and Montevideo ACC
!2.11.1 Messages for Control Flow between Argentina and Uruguay
!2.11.2 The objective is to establish standardized procedures for transferring Flow Control Messages.
!2.11.3 The scope: Dependencies of Air Traffic Control.
!2.11.4 When required to implement, modify or cancel a flow control, messages via AFTN or FAX (alternative) will
be sent according to the following rules:
!a) Addressed as appropriate:
SAEZZRZX – SAEZZTZX – SABEZTZX – SAEZZPZX – SABEZPZX – SADFZTZX –
SULSZPZX – SAREZRZX – SUMUYIYX – SBCWZQZX - SULSZTZX
AIS URUGUAY
AMDT NR 45
GEN 1.6-12
01 APR 2014
AIP
URUGUAY
!b) Originators as appropriate:
SUEOZQZX – SUMUZAZX – SUMUZTZX – SAEZZRZX – SAEZZTZR – SABEZTZX
!c) Implementation message format:
FROM .... UTC DAY .... UNTIL .... UTC DAY ...., IS IMPLEMENTED FLOW CONTROL IN POSITION ....
FOR ROUTE/S .... AND DESTINATION/S (DISCERNING BETWEEN) .... (REACTORS, CONVENTIONAL,
OVERFLIGHTS) WITH INTERVAL OF .... MINUTES DUE TO REASONS OF ....
!d) Modified message format:
REGARDING MY TXT NR .... GHO .... SHALL INCREASE/REDUCE CLEARANCE TO .... MINUTES ....
DUE TO ....
!e) Cancellation message format:
REGARDING MY TXT NR .... GHO .... FLOW CONTROL IS CANCELED AFTER .... UTC
2.12
Appendix 5 to the Operational Agreement between Ezeiza ACC and Montevideo ACC
2.12.1
Contingency measures agreed between URUGUAY and ARGENTINA
2.12.2
FIR AFFECTED: EZEIZA - MONTEVIDEO
2.12.3 GENERAL
2.12.3.1 Without coordination between the Control units of jurisdiction will apply the method of self-transference.
2.12.4 SELF-TRANSFERENCE
2.12.4.1 The following self-transference procedures must be applied as follows:
a) The ATS unit must:
1) Inform the pilot about the impossibility of communication with the accepting ATC unit, and
2) Provide instruction to make contact with the accepting unit.
b) The pilot must:
1) Make contact with the accepting unit;
2) Report to the accepting unit that is conducting a self-transference;
3) Transmit their origin, destination, route, flight level, transponder code, RVSM approval status and
estimated to the FIR boundary;
4) Report to the transferring unit when the accepting unit accepted the transfer and reporting the
existence of a change.
2.12.5 SUSPENSION OF RPL
2.12.5.1 During the contingency, it shall suspend the implementation of RPL listings, users must submit, in all cases,
the corresponding FPL.
AMDT NR 45
AIS URUGUAY
AIP
URUGUAY
GEN 1.6-13
01 APR 2014
2.12.6 PERMIT LIMIT
2.12.6.1 When en-route IFR flights have communications coverage for the aeronautical mobile service, but the ATS
units have not fixed communications between them, the traffic permit shall be valid up to the transfer of control point,
with the self-transference condition performed by the pilot.
2.13 SSR Code Assignment
2.13.1 Although RADAR systems were out of service, will continue assigning SSR codes to all aircraft.
2.14 Not transmitted Flight Plan
2.14.1 In the contingency period, the ATS units will accept flights whose FPL have not been transmitted. However,
the presentation of the FPL by the user is also required.
2.15 Vertical separation
2.15.1 Minimum Vertical separation shall be provided in accordance with the provisions of ICAO Annex 2, Appendix 3
Table a) Cruising Levels (although routes have been modified in only one way of flight, aircraft shall adopt flight levels
for as if they were two-way route of flight).
2.16 ATS Routes
2.16.1 While the contingency plans were activated it shall be used only those routes that are detailed below in Annex
Alfa.
Annex Alpha: Simplified Route Network Airspace Superior / Inferior
Routes
Segment
FIR
UL 324
EZEIZA /
KUKEN /
DAYMA /
CUARA /
ELAMO /
LUCIA /
ALDOS /
IGU / FOZ
EZEIZA
MONTEVIDEO
CURITIBA
RESISTENCIA
AIS URUGUAY
Restrictions
- With coordination between the FIR's (with or without radar) the
Agreements shall be apply.
- Without coordination between the FIR's: EZEIZA ACC shall deliver
the aircraft in KUKEN with FL 150 or HIGHER.
- Traffic capacity on the route: one (1) aircraft every 15 minutes in
KUKEN.
- Without coordination, use the method of self-transference, 5'
minutes before KUKEN.
- Unique direction of flight: from EZEIZA to CURITIBA.
- Aircrafts shall apply information procedure air/air 5' minutes before
and after KUKEN.
AMDT NR 45
GEN 1.6-14
02 JAN 2017
AIP
URUGUAY
Routes
UM 654
Segment
EZEIZA /
KUKEN
/ GAMOT/
FORTALEZA
(FLZ)
BAGE /
ISALA /
DURAZNO /
PAPIX /
EZEIZA
UN 741
EZEIZA /
LA PLATA /
DORVO /
LOMID /
MELO
UN 857
!UM424
A 305
EZEIZA /
DORVO /
CARRASCO
!
EZEIZA /
DORVO /
CARRASCO
/ L. DEL
SAUCE /
UGELO /
PELOTAS
AMDT NR 51
FIR
EZEIZA
MONTEVIDEO
CURITIBA
CURITIBA
MONTEVIDEO
EZEIZA
EZEIZA
MONTEVIDEO
EZEIZA
MONTEVIDEO
CURITIBA
Restrictions
- With coordination between the FIR's (with or without radar) the
Agreements shall be apply.
- Without coordination between the FIR's: EZEIZA ACC shall deliver
the aircraft in KUKEN with FL 150 or HIGHER.
- Traffic capacity on the route: one (1) aircraft every 15 minutes in
KUKEN.
- Without coordination, use the method of self-transference, 5'
minutes before KUKEN.
- Unique direction of flight: from EZEIZA to CURITIBA.
- Aircrafts shall apply information procedure air/air 5' minutes before
and after KUKEN.
- With coordination between the FIR's (with or without radar) the
Agreements shall be apply.
- Without coordination between the FIR's: MONTEVIDEO ACC shall
deliver the aircraft in PAPIX levelled with FL 100.
- Traffic capacity on the route: one (1) aircraft every 15 minutes in
PAPIX.
- Unique direction of flight: from CURITIBA to EZEIZA.
- Without coordination, use the method of self-transference, with no
less than 30 NM from PAPIX or 5' minutes before PAPIX.
- Aircrafts shall apply information procedure air/air 50 NM or 5'
minutes before and after KUKEN.
- With coordination between the FIR's (with or without radar) the
Agreements shall be apply.
- Without coordination between the FIR's: EZEIZA ACC shall deliver
the aircraft levelled with FL 170 or HIGHER climbing up to FL 250.
- Traffic capacity on the route: one (1) aircraft every 15’ minutes in
DORVO.
- Single direction of flight: from EZEIZA to CURITIBA.
- Without coordination, use the method of self-transference, with no
less than 5' minutes before DORVO.
- Aircrafts shall apply information procedure air/air 5' minutes before
and after DORVO.
- With coordination between the FIR's (with or without radar) the
Agreements shall be apply.
- Without coordination between the FIR's: EZEIZA ACC shall deliver
the traffic to MONTEVIDEO ACC levelled with FL 150 or LOWER in
DORVO.
- Traffic capacity on the route: one (1) aircraft each 15’ minutes in
DORVO.
- Single direction of flight: from EZEIZA to MONTEVIDEO or
CURITIBA.
- Without coordination, use the method of self-transference, with no
less than 5' minutes before DORVO.
- Aircrafts shall apply information procedure air/air 5' minutes before
and after DORVO.
AIS URUGUAY
AIP
URUGUAY
Routes
UA 306
A 306
GEN 1.6-15
01 APR 2014
Segment
FIR
LAGUNA
DEL SAUCE
/
CARRASCO
/ SARGO /
LA PLATA /
EZEIZA
MONTEVIDEO
EZEIZA
Restrictions
- With coordination between the FIR's (with or without radar) the
Agreements shall be apply.
- Without coordination between the FIR's: MONTEVIDEO ACC shall
deliver the traffic levelled with FL 140 or LOWER in SARGO.
- Traffic capacity on the route: one (1) aircraft each 15’ minutes in
SARGO.
- Single direction of flight: from CURITIBA or MONTEVIDEO to
EZEIZA.
- Without coordination, use the method of self-transference, with no
less than 30 NM from SARGO, or 5' minutes before SARGO.
- Aircrafts shall apply information procedure air/air 50 NM or 5'
minutes before and after SARGO.
NOTE 1: The traffic between EZEIZA FIR and MONTEVIDEO FIR, will be one (1) aircraft each (15’) minutes, which
forms a maximum flow of four (4) aircraft per hour between the two FIR's, by transfer point, regardless of the flight
level used by aircraft.
NOTE 2: Depending on the level of degradation of Services, respective ATC Supervisors may, by agreement,
coordinate the accommodation of a greater number of aircraft for each transfer points.
3. Operational Agreement between Montevideo ACC and Resistencia ACC for Air Traffic routing between
!both Control Centres, signed in Montevideo, March 18th, 2005 (in force 10 March 2011).
3.1 Air Traffic Routing
3.1.1 The IFR/VFR air traffic crossing the common boundary of the indicated FIR shall be routed by the ATS routes
published in the AIP and Navigation charts of the States affected by this Agreement.
3.1.2 Pathways that differ from those mentioned in 3.1.1 may be used prior coordination and agreement between the
two control centres when circumstances affect flight safety. IFR traffic using RVSM airspace between FL 290 and FL
410 inclusive levels, will be routed according to 3.1.1. In addition, it must use the cruising levels published in Appendix
1 paragraph 3.2 of this Operational Agreement, both for traffic entering or leaving RESISTENCIA FIR and/or
MONTEVIDEO FIR as appropriate. The procedures for air traffic control and RVSM contingency, shall result in
Appendix 1 of this Operational Agreement.
3.1.3 VFR air traffic will be coordinated in advance as the flight plan filed and shall enter the adjacent area when it
receives the approval of the Area Control Centre concerned, which may contain information, additional instructions
and/or amendments to the proposed route. RESISTENCIA ACC and MONTEVIDEO ACC not accept any traffic which
has not received the flight plan.
AIS URUGUAY
AMDT NR 45
GEN 1.6-16
01 APR 2014
AIP
URUGUAY
3.2 Flight Information Service
3.2.1 It shall provide Flight Information Service to IFR/VFR flights crossing the common FIR boundary, only when
they can not use the established routes for the reasons mentioned in paragraph 3.1.1, and shall be make the
appropriate coordination to include transmitting the following information about the flights in question:
a) appropriate portions of the flight plan updated,
b) the time estimated over the agreed transfer point.
c) the time it was the last contact with the aircraft.
3.2.2 In case of VFR flights that must be transferred to RESISTENCIA Control with current Flight Plan (CPL) at
takeoff, the pilot will be required to undertake the re-estimated for these flights because they are not controlled in
MONTEVIDEO FIR.
3.2.3 The information for IFR flights shall be transmitted at least twenty (20) minutes before the aircraft leaves the
Flight Information Region by the ACC that originates it.
3.2.4 The transferring Centre shall assign a flight level appropriate, prior coordination with the Receptor Centre,
which must be achieved before reaching the FIR boundary.
3.3 Area Control Service
3.3.1 Transfer of responsibilities and ground communications
3.3.1.1 Unless otherwise coordinated, the responsibility for the provision of Air Traffic Services shall be transferred
from the transferring Centre to the accepting Centre, when the this last one receive indication that the aircraft has
flown over the transfer point specified in Appendix 2 to this Operational Agreement, or other agreed point.
3.3.1.2 Normally, air-ground communications shall be transferred Five (5) minutes before the hour when the aircraft is
estimated to reach the agreed transfer point. However, when traffic conditions require it, the transferring centre may
delay the transfer of communications until the aircraft reports having flown the agreed transfer point.
3.3.1.3 SSR code shall be included with the transfer of control. If a code is not assigned to the aircraft, the accepting
Centre shall assign it, and the transferring Centre must promptly notify the pilot. The code changes will be made when
strictly necessary.
3.3.2 Minimum separation applicable during transfer
3.3.2.1 Longitudinal separation
3.3.2.1.1 The minimum longitudinal separation applicable between the flights that shall be transferred to the same
cruising level in the same ATS route, other routes or converging paths shall not be less than that specified for each
case in Appendix 2 of this Operational Agreement.
AMDT NR 45
AIS URUGUAY
AIP
URUGUAY
GEN 1.6-17
01 APR 2014
3.3.2.2 Vertical separation
3.3.2.2.1 Normally the aircraft shall be authorized to overflight the transfer point maintaining a specified cruising level
that will be selected from those listed for each case in Appendix 1 and 2 of this Operational Agreement. Nevertheless,
when this is explicitly coordinated with the accepting centre, the transferring Centre may allow the aircrafts to cross
the point of transfer in ascending or descending with respect to the previously agreed cruising level between ACC.
3.4 Coordination
3.4.1 Coordination prior to the transfer is effected by the exchange of ATS messages for these purposes prescribed in
ICAO Doc 4444-ATM/501.
3.4.1.1 It shall be used as the primary means of communication for coordination among the ACC's:
a) the ATS oral circuit
In case of the ATS oral circuit failure, it shall use as alternative means the following systems:
a) Resistencia ACC Telefax
(00543722) – 440939
!Resistencia-Operations Telefax
(00543722) – 436286
!Air Nav. Service – Dept. Chief Cel.
(00543722) – 15244202
b) CXK Fax
Montevideo ACC Telephone
(00598) 2604 0298
(00598) 2604 0295
!c) AFTN (MONTEVIDEO ACC)
!d) AFTN (RESISTENCIA ACC)
SUEOZQZX
SAREZRZX - SAREZQZX
3.4.2 ATS message exchange
!3.4.2.1 Except as regards the transmission of repetitive flight plans, which are subject to the provisions of
!"Operational Agreement for the Usage of Repetitive Flight Plans between Argentina and Uruguay" in force,
!information exchange is typically performed as indicated in Appendix 2 of the Operational Agreement.
Note: important changes include among others:
a) notifications received from the aircraft indicating a variation in the average speed of 5% more or less with
respect to the definition given in the FPL, and/or
b) a variation of more than three (3) minutes with respect to time calculated on the transfer point.
!3.5 Contingency Plan
!3.5.1 No Contingency Plan between Resistencia FIR and the Montevideo FIR shall be applied because the route
UA556 is unaffected
AIS URUGUAY
AMDT NR 45
GEN 1.6-18
01 APR 2014
AIP
URUGUAY
!3.6 Appendix 1 to the Operational Agreement between Montevideo ACC and Resistencia ACC
!3.6.1 Flight levels
!3.6.1.1 The assignment of flight levels for the transfer of responsibilities shall be as described in the Table of
Reference for the Tansfer of Responsibilities in force for this Operational Agreement corresponding the "1" for tracks
from 000º to 179º and the "2 "for tracks between 180º to 359º.
!3.6.1.2 RVSM Flight Levels to consider between FL 290 and FL 410 are listed below in accordance with Appendix
3) of Annex 2 of ICAO:
1
000º to 179º
2
180º to 359º
FL 290
FL 310
FL 330
FL 350
FL 370
FL 390
FL 410
FL 300
FL 320
FL 340
FL 360
FL 380
FL 400
!3.6.2 Transfer of responsibilities and communications in RVSM airspace
!3.6.2.1 No transfers shall be accepted between both area control centres, from aircrafts that are not RVSM
approved, except for flights by State aircraft, maintenance/delivery or humanitarian reasons.
!3.6.2.2 Non-RVSM approved aircraft shall be transferred with available flight levels below FL 290 or above FL 410.
!3.6.3 Vertical separation
MINIMUM VERTICAL SEPARATION
FL 290 – FL 410
1000 FT
RVSM approved
1000 FT
2000 FT !
Non-RVSM approved
! Only for state aircraft, maintenance, first delivery, humanitarian or contingency.
AIRCRAFT
BELOW FL 290
ABOVE FL 410
2000 FT
3.6.4 Coordination for RVSM Operations
!3.6.4.1 The messages of esteem (EST) of all non-RVSM aircraft (State aircraft, maintenance/first delivery or
humanitarian reasons) intending to operate within the RVSM airspace and crossing the common boundary of both
FIR's, shall be transmitted, at least 30 minutes before the estimated time of the aircraft on the transfer point in order to
plan the integration of the traffic with a minimum vertical separation of 2000 feet.
AMDT NR 45
AIS URUGUAY
AIP
URUGUAY
GEN 1.6-19
01 APR 2014
!3.6.4.2 Include a clear indication about the approval status of a non-RVSM aircraft and its application for special
treatment as an integral part of the estimated message:
a)
b)
c)
as confirmation of the data stored in the flight plan;
to provide for the degradation of flight planning system performance, and
to provide if for any reason the accepting unit has not received the flight plan.
!3.6.4.3 Oral coordination of estimate messages (EST)
!3.6.4.4 When someone is using an oral coordination process, the ACC transmitting an esteem message shall
include at the end of it, the information included in box 18 of the flight plan of ICAO for RVSM operations.
!3.6.4.5 If applicable, it must be included at the end of the message of esteem the term "NEGATIVE RVSM" or
"NEGATIVE RVSM State aircraft" or "NEGATIVE RVSM Flight Humanitarian" or "NEGATIVE RVSM Flight
Maintenance/Delivery".
!3.6.4.6 For the case of a single aircraft that experiences a flight contingency, the associated coordination
messages, shall be provided orally by a description of the cause of the contingency. The associated coordination
messages incorporated either the word:
a)
b)
RVSM impossible due to equipment or
RVSM impossible due to turbulence, as appropriate.
!3.6.5 Suspension of RVSM operations
!3.6.5.1 The respective ACC coordinate the procedures for suspension of RVSM within the affected areas in the
jurisdiction FIR, when there are pilot reports of turbulence greater than moderate. Within areas where RVSM
procedures are suspended, the minimum vertical separation between all aircraft shall be 2000 feet, according to
RVSM levels specified in 3.6.1.2
!3.6.5.2 The ACC that initiate the suspension of RVSM operations shall coordinate any restriction/ procedure with
adjacent ATS units.
AIS URUGUAY
AMDT NR 45
GEN 1.6-20
01 APR 2014
AIP
URUGUAY
!3.7 Appendix 2 to the Operational Agreement between Montevideo ACC and Resistencia ACC
ATS
ROUTE
A556
Table of flight levels and SSR
codes to be assigned by:
Montevideo
Ezeiza ACC
ACC
2
3
FL
SSR
FL
SSR
!1
!2
-
UA556
!1
-
!2
-
!UM402
!1
-
!2
-
1
Transfer points agreed
for each route
Minimum applicable for longitudinal separation
Minute
Remarks
4
5
6
MONTE CASEROS
VOR/DME (b)
30º16’00”S/057º38’18”W
10
(a) The separation shall be increased
by five (5) minutes when the ATS
Oral links fail
MONTE CASEROS
VOR/DME (b)
30º16’00”S/057º38’18”W
10
(b) Transfers shall be made prior to
20 NM MONTE CASEROS
VOR/DME for aircraft entering
RESISTENCIA FIR and over
MONTE CASEROS VOR/DME for
aircraft entering MONTEVIDEO FIR
!SEKLO (c) (d)
!10
!30º06’29”S/056º47’58”W
! (c) Traffic in UM402 route,
segment SEKLO/KIMIK apart from
the provisions of the Operational
Agreement with Curitiba ACC,
Montevideo ACC shall inform about
the traffic to Resistencia ACC. ACC
Resistencia shall inform about the
traffic to Montevideo ACC.
! (d) The transfer of traffic in
UA556 and UM402 routes shall be
performed 15 minutes prior to the
FIR Montevideo
Note: "1" and "2" indicate the series of IFR cruising levels listed in Appendix 3) of ICAO Annex 2 and Appendix 1
(RVSM) to this Operational Agreement for the tracks from 000 degrees to 179 degrees and from 180 degrees to 359
degrees, respectively.
4 Operational Agreement for the establishment of traffic coordination procedures developed in routes
B688 and W25 (effective August 12, 1999)
4.1 Procedures
4.1.1 MONTEVIDEO ACC, shall coordinate with ACC EZEIZA all traffic that is developed with IFR flight plan in route
W25 in the section PAYSANDU ARP and SALTO VOR or vice versa.
4.1.2 When EZEIZA ACC receive information from MONTEVIDEO ACC about the traffic operating on route W25 shall
coordinate with CONCORDIA TWR all flights that are developed below FL 075 and that may affect the operations of
CONCORDIA.
AMDT NR 45
AIS URUGUAY
AIP
URUGUAY
GEN 1.6-21
01 APR 2014
5 Operational Agreement signed between the Area Control Centres of Montevideo and Curitiba in Lima,
!Peru on September 18, 2009 (Effective Date 18 November 2010)
The objective of this Operational Agreement is to establish procedures relating to the routing of air traffic within
MONTEVIDEO and CURITIBA FIRs, the transfer and communications points and detail the coordination procedures
applicable between the control centres, parts of this Operating Agreement.
5.1 Air traffic routing ATS Routes
5.1.1 The air traffic passing through the common boundary of the indicated FIR's shall be routed through ATS routes
specified in the Aeronautical Information Publication (AIP) and En-route Charts of the States affected by this
Agreement, in accordance with Appendix 1 to this Operating Agreement.
5.1.2 Prior coordination and agreement between the two control centres may be used paths that differ from the
provisions of paragraph 5.1.1, when circumstances affect flight safety.
5.1.3 IFR air traffic using RVSM airspace between FL 290 and FL 410 shall be routed according to 5.1. In addition,
they must use the cruising levels contained in Appendix 2 of this Agreement, both for traffic entering or leaving
Curitiba and/or Montevideo FIR, respectively.
5.2 Management Measures to Control Flow
5.2.1 When strictly necessary to apply flow control measures and according to the GPI-6 initiative of the Global Air
Navigation Plan of ICAO, Montevideo or Curitiba ACC shall issue a NOTAM, besides the ATFM messages between
units, to the effects of airspace users to plan their operations considered in due time.
5.3 VFR traffic
5.3.1 VFR air traffic crossing the common boundary of the mentioned FIR must use the cruising levels in accordance with
the following:
a) Entry in the airspace of Brazil - Curitiba:
- VFR traffic coming from Montevideo FIR, will receive instructions from Montevideo ACC to keep visual flight rules
(VFR) and flight levels in accordance with ICAO Annex 2 (Appendix 2), only to the upper limit FL145.
b) Entry in the airspace of Uruguay – Montevideo:
- VFR traffic coming from Curitiba FIR, will receive instructions from Curitiba ACC to keep visual flight rules (VFR) and
flight levels in accordance with ICAO Annex 2 (Appendix 2), only to the upper limit FL195.
NOTE: The procedures specified above are subject to changes from time to time published by NOTAM.
AIS URUGUAY
AMDT NR 45
GEN 1.6-22
01 APR 2014
AIP
URUGUAY
5.4 Income Aircrafts without Flight Plan
5.4.1 PROHIBITED entry of aircraft to Montevideo and Curitiba FIR without submitting flight plan. If one of the units does not
get the flight plan, the essential data for the provision of the Air Traffic Control Services will be coordinated by the
corresponding coordination circuits.
5.5 Flight Information Service
5.5.1 Coordination needed when provided only Flight Information Services and Warning
5.5.1.1 When providing only flight information and alert services, there will be appropriate coordination with respect to VFR
and IFR crossing the common boundary of the Flight Information Regions. This coordination will include the transmission of
the following information about the flights in question:
a) Appropriate parts of the current flight plan;
b) The esteem time where it appears on the agreed transfer point, and
c) The time that was the last contact with the aircraft.
5.5.1.2 The information given will be transmitted at least fifteen (15) minutes before the aircraft leaves the Flight
Information Region by the Area Control Centre that has dictated.
5.6 Area Control Service
5.6.1 Transfer of responsibility for Control and general Air-Ground Communications
5.6.1.1 Unless otherwise coordinated, the responsibility for the provision of Air Traffic Services will be transferred from the
transferring centre to the accepting centre when the latter receives an indication that the aircraft has flown over the transfer
point specified for each route in Appendix 1 of this Operational Agreement, or other agreed transfer point.
5.6.1.2 Normally, air-ground communications will be transferred Five (5) minutes before the hour when the aircraft is
estimated to reach the agreed transfer point.
5.6.1.3 Nevertheless of what above when traffic conditions require it, the transferring Centre may delay the communication
transference until the aircraft reports having flown the agreed transfer point.
5.6.1.4 The SSR code shall be included with the proposal to control transfer. If a code is assigned to the aircraft, the
accepting Centre will taker, and the transferring Centre must promptly notify the pilot. The code changes will be made only
when strictly necessary.
5.7 Transfer of Responsibilities and Air-Ground Communications in RVSM Airspace
5.7.1 No transfers will be accepted between area control centres, of aircraft that are not-approved RVSM, except for flights
by State aircraft, maintenance, delivery or humanitarian first.
5.7.2 Non-approved RVSM aircraft, except for State aircraft, maintenance, first delivery or humanitarian, must be transferred
with available flight levels below FL 290 or above FL 410.
AMDT NR 45
AIS URUGUAY
AIP
URUGUAY
GEN 1.6-23
01 APR 2014
5.8 Minima of separation apply for the Control Transfer
5.8.1 Longitudinal Separation
5.8.1.1 The applicable minimum longitudinal separation between flights that will be transferred to the same cruising level in
the same ATS route, or routes with converging paths, shall not be less than that specified in each case in Appendix 1 to this
Operational Agreement.
5.8.2 Vertical Separation
5.8.2.1 The applicable minimum vertical separation between flights that will be transferred on the same ATS route or routes
with converging paths, shall not be less than as specified in Table 1 below.
MINIMUM VERTICAL SEPARATION
AIRCRAFT
BELOW FL 290
RVSM approved
ABOVE FL 410
1000 FT
1000 FT
Non-RVSM approved
FL 290 – FL 410
2000 FT !
2000 FT
! Only for state aircraft, maintenance, first delivery, humanitarian or contingency.
5.9 Flight levels used
5.9.1 The flight levels used between ACC are specified in Appendix 2 to this Operational Agreement.
5.9.2 The assignment of flight levels for the transfer of responsibilities shall be as described in Appendix 1 to this
Operational Agreement corresponding the levels in the column "1" for tracks from 000º to 179º and the levels of the column
"2 "for tracks between 180º to 359º.
5.9.3 The aircraft shall be authorized to overfly the transfer point in levelled flight, maintaining a cruising level specified in
accordance with the provisions above.
5.9.4 Nevertheless, when this is explicitly coordinated with the accepting centre, the transferring centre may allow aircraft to
cross the point of transfer ascending or descending with respect to the cruising level previously agreed between ACC.
5.10 Message Exchange
5.10.1 Coordination prior to the transfer of control is effected by the exchange of ATS messages prescribed for this purpose
in the DOC 4444-ATM/501 (Air Traffic Management) of ICAO
5.10.2 The exchange of ATS messages information and coordination of prior to the transfer of control between Curitiba and
Montevideo ACC shall be made, usually by means of primary or secondary, as shown in Appendix 3 to this Operational
Agreement.
AIS URUGUAY
AMDT NR 45
GEN 1.6-24
01 APR 2014
AIP
URUGUAY
5.10.3 In case of failure of ATS Oral circuit shall be used as alternative media, the following systems:
a) Montevideo AFTN
Curitiba AFTN
b) Telephone: Montevideo ACC
c) Telefax of the Telecommunication Station
d) Telephone: Curitiba ACC
e) Curitiba ACC PLN Room
SUEOZQZX
SBCWZQZX
+ 598 2604 0295
+ 598 2604 0298
+ 55 41 33563475; 55 41 32515342
+ 55 41 32515308; 55 41 32515388
5.10.4 The four-letter designators shall be used, in the ATS message addresses, after the local indicator published by
ICAO, with the following:
a) ACC - messages for IFR flights: ZQZX (Montevideo and Curitiba);
b) ACC - messages for VFR flights: ZFZX (Montevideo) and ZQZX (Curitiba).
5.10.5 Except with respect to the transmission of Repetitive Flight Plans, which are objects of another agreement, the
exchange of information shall be normally made in accordance with Annex 3 of this Agreement.
5.10.6 The transferring centre shall notify the accepting centre the major changes in the flight plan data, transmitted by the
ATS oral circuit (REDDIG) or through CHG messages.
NOTE: Major changes include among others:
a) The aircraft reports received indicating a change in the average speed of five (5%) or more (for more or
for less) with respect to the definition given in the flight plan, and/or
b) A variation of three (3) minutes or more (for more or for less) with respect to the estimated time on the
transfer point.
5.10.7 DEADLINE FOR PRE-COORDINATION, INITIAL ISSUANCE OF PERMITS, OR TO AUTHORIZE CHANGES TO
THE FLIGHT PLAN
5.10.7.1 For the purposes of the application of Chap. 10 of the DOC 4444-ATM/501, requests for approval, the deadline for
pre-coordination and issuance of initial permits will be at least FIFTEEN (15) MINUTES and maximum FORTY (40)
MINUTES of flight to the point defined for the transfer of Control.
5.10.7.2 Independent as provided in paragraph 5.10.7.1, changes in the flight levels shall be made prior coordination and
approval with the acceptant area control centre.
5.11 Alert Service
5.11.1 The responsibility of the Alert Service and the coordination tasks to provide the Service of Search and Rescue, will
be on that ATS units:
a)
b)
In which FIR has been registered the last communication, or
In which the aircraft was about to enter, if known to have already crossed the point of transfer, whether by
information obtained by radiotelephone or radar display.
5.12 Contingency Procedures
5.12. If necessary, it shall use contingency procedures described in Appendix 6 of this Agreement.
AMDT NR 45
AIS URUGUAY
AIP
URUGUAY
GEN 1.6-25
01 APR 2014
5.13 Procedures in RVSM Airspace
5.13.1 In RVSM airspace, the procedures described in Appendix 5 of this Agreement shall be applied.
!5.14 RNAV Routes
!5.14.1 To fly in RNAV5 continental routes, aircrafts must have RNAV5 approvals, otherwise they shall be
addressed by the conventional ATS Routes network.
AIS URUGUAY
AMDT NR 45
GEN 1.6-26
02 JAN 2017
AIP
URUGUAY
APPENDIX 1 to the Operational Agreement signed between the Area Control Centres of Curitiba and
Montevideo (Effective Date 26 May 2011)
TABLE OF REFERENCE FOR THE TRANSFER OF RESPONSIBILITIES
ATS
ROUTE
1
Table of levels and SSR data
to be assigned by:
Montevideo
Curitiba ACC
ACC
2
3
FL
SSR
FL
SSR
Transfer points agreed
for each route
4
Minimum applicable for longitudinal separation
Minute
Remarks
5
6
A 305
UA305 (f)
1
2
UGELO
32º40’42”S/053º08’50”W
10 (a)
(e)
A 309
1
-
UGURA
32º36’18”S/053º20’27”W
10 (a)
(e)
A 310
1
2
ASUMA
31º52’03”S/054º09’19”W
10 (a)
(e)
A314
1
2
VOR/NDB/BGE
31º23’26”S/054º06’35”W
10 (a)
(e)
G680
1
2
VOR/NDB/BGE
31º23’26”S/054º06’35”W
10(a)
(e)
UM540
1
-
AKPOD
32º27’57”S/053º33’41”W
10 (a)
(e)
UN857
1
2
!VOR/MLO
32º20’32”S/054º13’19”W
10 (a)
(e)
UM671
1
-
UM792
UA310
-
2
!VOR/MLO
32º20’32”S/054º13’19”W
!VOR/MLO
32º20’32”S/054º13’19”W
10 (a)
(e)
10 (a)
(e)
UN741
-
2
VOR/NDB/BGE
31º23’26”S/054º06’35”W
10 (a)
(e)
10 (a)
(e)
UM418 (h)
(i)
1
2
UBLAM
30º39’35”S/056º09’44”W
UM788
-
2
VOR/NDB/BGE
31º23’26”S/054º06’35”W
10 (a)
(e)
1
-
GAMOT
30º56’40”S/055º29’37”W
10 (a)
(e)
1
2
CUARA
30º22’11”S/056º26’59”W
10 (a)
(e)
UM661 (f)
(g)
1
2
OPTUR
32º50’57”S/052º57’31”W
10 (a)
(e)
UM532 (h)
1
2
CUARA
30º22’11”S/056º26’59”W
10 (a)
(e)
UM534
1
2
URURI
31º18’10”S/055º07’26”W
10 (a)
(e)
UM654
(b) (c) (d)
(i)
UL324
(h)
AMDT NR 51
(a) In case of failure of direct voice
communications between the ACC
the minimum separation between
aircraft should be 15 minutes.
(b) Montevideo ACC shall
coordinate with Curitiba ACC, with
at least thirty (30) minutes before
the estimated in GAMOT when
deemed that the aircraft will not
able to pass the reporting point
GAMOT at the authorized level due
to restricted airspaces in Santa
Maria.
(c) In the route UM 654, due to it is
a one-way route, Montevideo ACC
may use the odd levels to transfer
control to Curitiba ACC.
(d) In the route UM 654 the
minimum flight level over the
position GAMOT shall be FL 290.
(e) Prior coordination and
acceptance between ACCs may be
used a separation of five (5)
minutes at least, when the Centres
involved find satisfactory conditions
for communications and radar
coverage.
(f) Traffic entering Montevideo FIR
by routes UM661 and UA305
through OPTUR and UGELO shall
be considered as a single point for
the transfer of control and flight
level assignment.
AIS URUGUAY
AIP
URUGUAY
ATS
ROUTE
1
!UM402
(h) (j)
GEN 1.6-27
01 APR 2014
!Table of levels and SSR
data to be assigned by:
Montevideo
Curitiba ACC
ACC
2
3
FL
SSR
FL
SSR
1
2
Transfer points agreed
for each route
4
!SEKLO
30º06’29”S/056º47’58”W
Minimum applicable for longitudinal separation
Minute
Remarks
5
6
10 (a)
(e)
! (g) All traffic using UM661 route
shall be instructed to communicate
with the adjacent ACC in OPTUR
position.
! (h) Traffic entering the
Montevideo FIR by UM402, UL324,
UM532 and UM418 routes, through
KIMIK, CUARA and UBLAM shall
be considered as a single point for
the transfer of control and
assignment of flight level, and they
may be used the same flight level
when the aircraft maintain
regulatory longitudinal separation.
! (i) Traffic entering the Curitiba
FIR by UM418 and UM654 routes,
through UBLAM and GAMOT shall
be considered as a single point for
the transfer of control and
assignment of flight level, and they
may be use the same flight level
when regulatory longitudinal aircraft
to maintain separation.
! (j) The segment SEKLO - KIMIK
shall be under the jurisdiction of
Curitiba ACC.
!Note: "1" and "2" indicate the listed IFR Cruising Levels series in Appendix 3) a) ICAO Annex 2 for headings of 000
degrees to 179 degrees and 180 degrees to 359 degrees, respectively.
AIS URUGUAY
AMDT NR 45
GEN 1.6-28
01 APR 2014
AIP
URUGUAY
APPENDIX 2 to the Operational Agreement signed between the Area Control Centres of Curitiba and
Montevideo
Table of Cruising Levels in accordance with Appendix 3 of Annex 2 to the Convention on International Civil
Aviation
TRACK
From 000 degrees to 179 degrees
IFR Flights
FL
VFR Flights
FL
Altitude
Metres
From 180 degrees to 359 degrees
FL
Altitude
Metres
Feet
IFR Flights
FL
Altitude
Metres
Feet
VFR Flights
Altitude
Metres
Feet
Feet
10
30
50
70
90
300
900
1 500
2 150
2 750
1 000
3 000
5 000
7 000
9 000
35
55
75
95
1 050
1 700
2 300
2 900
3 500
5 500
7 500
9 500
20
40
60
80
100
600
1 200
1 850
2 450
3 050
2 000
4 000
6 000
8 000
10 000
45
65
85
105
1 350
2 000
2 600
3 200
4 500
6 500
8 500
10 500
110
130
150
170
190
3 350
3 950
4 550
5 200
5 800
11 000
13 000
15 000
17 000
19 000
!115
135
155
175
195 (b)
3 500
4 100
4 700
5 350
5 950
10 500
13 500
15 500
17 500
19 500
120
140
160
180
200
3 650
4 250
4 900
5 500
6 100
12 000
14 000
16 000
18 000
20 000
125
145 (a)
165
185
205
3 800
4 400
5 050
5 650
6 250
12 500
14 500
16 500
18 500
20 500
210
230
250
270
290
6 400
7 000
7 600
8 250
8 850
21 000
23 000
25 000
27 000
29 000
215
235
255
275
6 550
7 150
7 750
8 400
21 500
23 500
25 500
27 500
220
240
260
280
300
6 700
7 300
7 900
8 550
9 150
22 000
24 000
26 000
28 000
30 000
225
245
265
285
6 850
7 450
8 100
8 700
22 500
24 500
26 500
28 500
310
330
350
370
390
9 450
10 050
10 650
11 300
11 900
31 000
33 000
35 000
37 000
39 000
320
340
360
380
400
9 750
10 350
10 950
11 600
12 200
32 000
34 000
36 000
38 000
40 000
410
450
490
12 500
13 700
14 950
41 000
45 000
49 000
430
470
510
13 100
14 350
15 550
43 000
47 000
51 000
(a) Maximum visual flight level usable in CURITIBA FIR
(b) Maximum visual flight level usable in MONTEVIDEO FIR
AMDT NR 45
AIS URUGUAY
AIP
URUGUAY
GEN 1.6-29
01 APR 2014
APPENDIX 3 to the Operational Agreement signed between the Area Control Centres of Curitiba and
Montevideo
TABLE OF REFERENCE FOR THE EXCHANGE OF ATS MESSAGES
Message Type
FPL
DLA
EST
CHG
CDN
ALR
CPL
DEP
RPL
AIS URUGUAY
Cases where they are
applied
Limit time for the
Transmission
Means Used
All flights
Immediately after being
presented
AFTN/FAX
When necessary
Immediately after being
presented
AFTN/FAX
All flights
20 minutes before the
estimated time at the
transfer point (when the
flight time permitting)
When necessary
As soon as possible
after the occurrence of
the circumstance
Oral Circuits
ATS/AFTN/FAX
When necessary
As soon as possible
after the occurrence of
the circumstance
Oral Circuits
ATS/FAX/AFTN
When necessary
As soon as possible
after the occurrence of
the circumstance
Oral Circuits
ATS/FAX/AFTN
When necessary
As soon as possible
AFTN/FAX
All flights
As soon as possible
AFTN/FAX
Oral Circuits
ATS/FAX/AFTN
As specified in the Agreement Reported
AMDT NR 45
GEN 1.6-30
01 APR 2014
AIP
URUGUAY
!APENDIX 4 to the Operational Agreement between the Area Control Centres of Curitiba and
!Montevideo
!1. Table of Cruising Levels usable in RVSM airspace where RVSM procedures were suspended.
TRACK
IFR Flights
IFR Flights
From 000 degrees to 179 degrees
From 180 degrees to 359 degrees
Flight Level
Metres
Feet
290
8 850
29 000
350
410
AMDT NR 45
10 650
12 500
Flight Level
Metres
Feet
320
9 750
32 000
380
11 600
38 000
35 000
41 000
AIS URUGUAY
AIP
URUGUAY
GEN 1.6-31
01 APR 2014
Appendix 5 to the Operational Agreement between the Area Control Centres of Curitiba and Montevideo
1. PROCEDURES IN RVSM AIRSPACE
1.1 PURPOSE
1.1.1 The purpose of this Appendix is to establish procedures in RVSM airspace of both the FIR, which are part of
this Operational Agreement.
1.2 FLIGHT LEVEL
1.2.2 The assignment of flight levels for the transfer of responsibility will be as described in Appendix 1 of this
operational agreement, corresponding to "1" for directions from 000º to 179 º and "2" for directions from 180º to 359º.
1.2.3 RVSM flight levels between FL290 and FL410 levels are listed below (in accordance with Appendix 3 of Annex
2 of ICAO).
1
000º to 179º
2
180º to 359º
FL 290
FL 310
FL 330
FL 350
FL 370
FL 390
FL 410
FL 300
FL 320
FL 340
FL 360
FL 380
FL 400
1.3 TRANSFER OF RESPONSIBILITY AND COMMUNICATIONS IN RVSM AIRSPACE
1.3.1 In addition to the provisions above, the following procedures must be adjusted in case of aircraft flights in
RVSM airspace.
1.3.2 Transfers shall not be accepted between the area control centres of aircraft that are not RVSM approved,
except for flights by State aircraft, maintenance, first delivery or humanitarian missions.
NOTE: State aircraft shall be understood, those used in military, customs and police in accordance with the
Convention on International Civil Aviation.
1.3.3 Not-approved RVSM aircraft shall, except for flights by State aircraft, maintenance, first delivery or humanitarian
missions, be transferred in the flight levels available below FL290 or above FL410.
AIS URUGUAY
AMDT NR 45
GEN 1.6-32
01 APR 2014
AIP
URUGUAY
1.4 VERTICAL SEPARATION
MINIMUM VERTICAL SEPARATION
AIRCRAFT
BELOW FL 290
RVSM approved
ABOVE FL 410
1000 FT
1000 FT
Non-RVSM approved
FL 290 – FL 410
2000 FT !
2000 FT
! Only for state aircraft, maintenance, first delivery, humanitarian or contingency.
1.5 COORDINATION FOR AIRCRAFT OPERATIONS WITHOUT RVSM APPROVAL WITHIN RVSM AIRSPACE
1.5.1 The coordination for non-RVSM aircraft operations (State aircraft, maintenance, first delivery or humanitarian
reasons) for flight in RVSM airspace follow the same process above, except for the messages of esteem (EST).
1.5.2 Esteem messages (EST) for all non-RVSM aircraft (State aircraft, maintenance, first delivery or humanitarian)
intending to operate within the RVSM airspace and crossing the common boundary of both FIR, shall be transmitted,
at least 30 minutes before the estimated time of the aircraft on the transfer point in order to plan the integration of the
traffic with a minimum vertical separation of 2000 feet.
1.5.3 Include a clear indication about the approval status of a non-RVSM aircraft and its application for special
treatment as an integral part of the estimated message, with the aim of:
a) Confirmation of the data stored in the flight plan;
b) Consider the possibility of the system performance flight planning degradation, and
c) Consider if for any reason the accepting unit has not received the flight plan.
1.5.4 Oral coordination of esteem messages (EST) for operations of non-RVSM aircraft.
1.5.5 When they are using an oral coordination process for operations of non-RVSM aircrafts, the ACC transmitting
an estimate message must include at the end of it, the information contained in box 18 of the flight plan of ICAO for
RVSM operations.
1.5.6 If applicable, must be included at the end of the esteem message the term "NEGATIVE RVSM State aircraft" or
"NEGATIVE RVSM humanitarian flight" or "NEGATIVE RVSM flight maintenance," or "NEGATIVE RVSM flight of first
delivery."
1.5.7 For the case of a single aircraft that experiences a flight contingency, associated coordination messages will be
provided orally by a description of the cause of the contingency. The associated coordination messages shall
incorporate either the word:
a) RVSM impossible due to equipment or
b) RVSM impossible due to turbulence, as appropriate.
AMDT NR 45
AIS URUGUAY
AIP
URUGUAY
GEN 1.6-33
01 APR 2014
1.6 SUSPENSION OF RVSM OPERATIONS
1.6.1 Montevideo ACC and Curitiba ACC shall coordinate the procedures for suspension of RVSM within the affected
areas in Montevideo and Curitiba FIR when there are pilot reports of turbulence greater than moderate.
1.6.2 Within the areas where RVSM procedures are suspended, the minimum vertical separation between all aircraft
shall be 2 000 feet, according to the flight levels in Appendix 4 of this Operational Agreement.
1.6.3 The ACC that initiate the suspension of RVSM operations shall coordinate any restrictions/procedure with the
adjacent ATS units.
AIS URUGUAY
AMDT NR 45
GEN 1.6-34
01 APR 2014
AIP
URUGUAY
Appendix 6 to the Operational Agreement between Brazil and Uruguay
CONTINGENCY OPERATING PROCEDURES BETWEEN BRAZIL AND URUGUAY IN CASE OF ATS
SERVICES FAILURE OF CURITIBA ACC
Effective Date: 17 DEC 2009
1
FIR CONCERNED: CURITIBA and MONTEVIDEO
2
GENERAL
2.1 The purpose of this Contingency Plan is to establish procedures for entry/departure of international flights in the
airspace of Curitiba FIR, in the event of partial or total interruption of air traffic services, keeping still, the flow orderly
and safe. In partial interruption is considered, at least, the provision of Flight Information Services and Warning. In
total interruption, these services cannot be guaranteed.
2.2 The national contingency ATM unit designated by the Administration of Brazil, assigned to monitor
developments, responsible for enforcing the contingency plan and coordination of contingency arrangements is:
Name of Agency: Centro General de Navegación Aérea (CGNA).
Contact Person: Célula de Decisión y Coordinación - DCC - Gerente Nacional
Telephone: 55 21 21 2101-6449; 55 21 21 2101-6409; REDDIG: 3058
Fax:
55 21 21 2101-6504
E-mail:
[email protected]
Contact Points of with Curitiba ACC:
Telephone:
554133563475; 554132515342; 554132515308 y 554132515388.
REDDIG:
3060.
AFTN:
SBCWZQZX.
2.3 In the event of a failure of the air/ground communications, air traffic services will rely on VHF and HF frequencies
available, respectively, in each ACC or APP that has been allocated to provide services in a given ATS portion of
airspace, contained in the publications still in force or in any other designated by the Central Organ - CGNA.
2.4 Specific operational procedures for Curitiba FIR, in case of contingency, will be activated by CGNA, through the
publication of specific NOTAM.
3 PROVISIONS APPLICABLE TO THE INVOLVED ATS UNITS
3.1 Transmit, in accordance with normal procedures under consideration, the air traffic messages to the ACC in
contingency and an estimate message (EST) to the first FIR following the FIR in contingency;
3.2 Authorize the entry of an aircraft in the FIR in contingency, in accordance with the provisions of Annex A, using
at least a 15-minute longitudinal separation in the same fixed, regardless of the flight level. Depending on the speed
difference and flight time in the section on contingency and the level of degradation of the Services, the respective
Supervisors may, by mutual agreement, increase or decrease the longitudinal separation of 15 minutes.
AMDT NR 45
AIS URUGUAY
AIP
URUGUAY
GEN 1.6-35
01 APR 2014
3.3 Awaiting the guidance from the Centre for Management of Air Navigation (CGNA) for the application of
adjustments for contingency measures, until the moment that the system has returned to normal;
3.4 Coordinate with the contingency FIR ATS units, in accordance with the guidelines of the Air Navigation
Management Centre, via ATS coordination circuits or other available, with no less than 30 minutes before the
estimated hours over the entry points of the FIR in contingency;
3.5 In the event of a total interruption, instruct the pilot in command of the aircraft to maintain the last level and
speed used while overflying the FIR in contingency;
3.6 Note that the aircraft must be level, in accordance with the provisions of Annex A, at least 10 minutes prior to
entering the FIR in contingency;
3.7 Instruct the aircraft in the sense of attempting to establish communication with the adjacent ATS units with at
least 5 minutes before the scheduled time of admission to the subsequent FIR;
3.8 Note that, in case of a complete or partial interruption in the provision of air traffic services will be suspended the
entry into the FIR in contingency until the situation is evaluated and activated the contingency plan by the Centre for
Air Navigation Management - Central Body , and
3.9 Note that, during activation of the Contingency Plan will not be allowed unapproved aircraft flying in RVSM
airspace, with no exceptions.
4
PROVISIONS APPLICABLE TO AIRCRAFT
4.1 Only be permitted flights of aircraft that are conducting national or international scheduled flights, under
instrumental flight rules (IFR).
4.2 Note that, during activation of this Plan, only RVSM approved aircraft may fly between FL 290 and FL 410.
4.3 In the event of a partial disruption, maintain continuous watch on the VHF, HF or other designated, in addition to
frequency 123.45 MHz and report any climb or descent manoeuvre that circumstances so require. The message must
include: aircraft identification, position, abandoned level, crossing level and other relevant information;
4.4 Keep the navigation and collision avoidance lights continuously switched on while overflying the FIR in
contingency;
4.5 Select code 2000 if it has not been previously assigned other SSR code;
4.6 Necessarily have the TCAS, and
4.7 Perform the necessary coordinations with other aircraft using the appropriate ATC frequencies and frequency
123.45Mhz.
AIS URUGUAY
AMDT NR 45
GEN 1.6-36
01 APR 2014
5
AIP
URUGUAY
PUBLICATION OF NOTAM
5.1 The provisions applicable to ATS units and aircrafts taking off, landing or flying over the Curitiba FIR, according
to a partial or total failure in the provision of air traffic services will be activated by CGNA, through the publication of a
specific NOTAM.
6
SUSPENSION OF REPETITIVE FLIGHT PLAN (RPL)
6.1 For the duration of the contingency situation, lists of RPL will be suspended, having users to present in all cases,
the corresponding FPL in accordance with the routes set out in Annexes A or B of this appendix.
7
AUTO TRANSFER PROCEDURES
7.1 When the ATS units cannot carry out the coordination of air traffic due to failure of the Communications Fixed
Service, the following auto transfer procedures shall be applied:
7.1.1 The ATS unit must:
a) Report to the pilot the unavailability Fixed Service with the accepting ATS office, and
b) Provide information and instructions necessary for the pilot to get contact with the accepting unit.
7.1.2 The pilot must:
a) Try to contact the accepting unit, with at least 5 minutes before the ETO at the transfer fixed;
b) Inform the ATS unit that is undertaking a self transfer, and
c) Transmit the following informations: aircraft identification, origin, destination, route, flight level, transponder
code, RVSM approval status and self esteem to auto-transfer fixed.
8
PERMIT LIMIT
8.1 When the ATS units can not carry out the coordination of air traffic due to failure of the fixed communications
network, but have coverage for the communications Mobile Service, the transit permit shall be valid up to the transfer
control point, with auto transfer status performed by the pilot.
AMDT NR 45
AIS URUGUAY
AIP
URUGUAY
GEN 1.6-37
01 APR 2014
!ANNEX A to the Appendix 6 to the Operational Agreement between Brazil and Uruguay
CONTINGENCY PROCEDURES BETWEEN CURITIBA AND MONTEVIDEO ACC
PARTIAL CONTINGENCY IN CURITIBA FIR (CW - FIR)
ORIGIN
MONTEVIDEO
FIR
CURITIBA TMA
MONTEVIDEO
FIR
PORTO ALEGRE
TMA
MONTEVIDEO
FIR
FLORIANÓPOLIS
TMA
MONTEVIDEO
FIR
SÃO PAULO
TMA
AIS URUGUAY
SIMPLIFIED ROUTE NETWORK IN CASE OF CONTINGENCY IN CURITIBA FIR
TRANSFERENCE/
AUTO TRANSFERENCE
DESTINATION
ROUTE/SEGMENT
FIX
FLIGHT LEVEL
AKPOD UM540 POR VOR UW6
AKPOD
CURITIBA TMA
AKNEN UM671 CXS VOR UW6
VOR MLO
UGURA A309 POR VOR G449
UGURA
UA310 ASKED UM788 BGE VOR
BGE VOR
MONTEVIDEO
G449 POR VOR A309 PTS VOR A305
FIR
UGELO
UGELO
AKPOD UM540
AKPOD
PORTO ALEGRE
MLO VOR UN857
MLO VOR
TMA
UGURA A309
UGURA
UN857 MLO VOR
VOR MLO
MONTEVIDEO
UM534 LOBOR/UN741 BGE VOR
BGE VOR
FIR
A309 PTS VOR A305 UGELO
UGELO
Flight Levels shall
AKPOD UM540 POR VOR UN857
AKPOD
be allocated
FLORIANÓPOLIS
MLO VOR UN857 POR VOR UN857
MLO VOR
through
TMA
UGURA A309 POR VOR G677
UGURA
coordination
UN 857 POR VOR UN857 MLO VOR
MLO VOR
between Curitiba
UN857 POR VOR UM534/UN741- BGE
ACC and CGNA
MONTEVIDEO
BGE VOR
VOR
FIR
G677 POR VOR A309 PTS VOR A305
UGELO
UGELO
MLO VOR UM671 ANISE/UW25 SAT
MLO VOR
SÃO PAULO
NDB
TMA
UGURA A309 POR VOR G677 FNP
UGURA
VOR W45
UM788 VOR BGE
BGE VOR
UM788 ASKED/UM792 MLO VOR
MLO VOR
MONTEVIDEO
G449 POR VOR A309 PTS VOR A305
FIR
UGELO
UGELO
G449 POR VOR A314 BGE VOR
BGE VOR
AMDT NR 45
GEN 1.6-38
01 APR 2014
AIP
URUGUAY
!ANNEX B to the Appendix 6 to the Operational Agreement between Brazil and Uruguay
CONTINGENCY PROCEDURES BETWEEN CURITIBA AND MONTEVIDEO ACC
TOTAL CONTINGENCY IN CURITIBA FIR (CW - FIR)
ORIGIN
BRASILIA FIR
MONTEVIDEO
FIR
SIMPLIFIED ROUTE NETWORK IN CASE OF CONTINGENCY IN CURITIBA FIR
TRANSFERENCE/
AUTO TRANSFERENCE
DESTINATION
ROUTE/SEGMENT
FIX
FLIGHT LEVEL
OROKA
OROKA UN741 BGE VOR
FL 360
VOR BGE
FL 300, or
PREGO UW58 SCB VOR / UA310
PREGO
FL 320, or
ASKED/ UM792 MLO VOR
VOR MLO
FL 360
MONTEVIDEO
FL 260, or FL 280,
VTR VOR UW50 SCB VOR / ASKED/
VOR RDE
FIR
or FL 360, or FL
UM792 MLO VOR
VOR MLO
380, or FL 470
FL 260, or FL 280,
VTR VOR / UW50 MRC VOR UN857
VOR VTR
or FL 360, or FL
MLO VOR
VOR MLO
380, or FL 430, or
FL 470
MLO VOR UM671 ANISE/ UW31 SAT
VOR MLO
FL 370
NDB / DCT BCO VOR
VOR BCO
BRASILIA FIR
MLO VOR
MLO VOR UN857 DOGSU
FL 350
DOGSU
APPENDIX 7 to the operational Agreement between Brazil and Uruguay
CONTINGENCY OPERATING PROCEDURES BETWEEN BRAZIL AND URUGUAY
IN CASE OF FAILURE OF MONTEVIDEO ACC ATS SERVICES
Effective Date: 17 DEC 2009
1. FIR CONCERNED
CURITIBA - MONTEVIDEO
2. GENERAL
2.1 If activation of contingency procedures, the focal point is the Control Centre of Montevideo.
!Telephones: (598) 2604 0295; (598) 2604 0251, extension 5119
REDDIG: 6551; 6551
AFTN: SUEOZQZX
3. SELF-TRANSFERENCE
3.1 Without coordination between the jurisdiction control units will apply the method of self transfer.
3.2 The following self-transfer procedures shall be applied as follows:
a) The ATS unit must:
AMDT NR 45
AIS URUGUAY
AIP
URUGUAY
GEN 1.6-39
01 APR 2014
1. Inform the pilot the inability to communicate with the accepting ATC unit, and
2. Provide instruction to make contact with the accepting unit.
b) The pilot must:
1. Make contact with the accepting unit;
2. Report to the accepting unit that is carrying out a self-transfer;
3. Transmit their origin, destination, route, flight level, transponder code, RVSM approval status and
estimated the FIR boundary;
4. Report to the transferring unit when the accepting unit accepted the transfer.
4. SUSPENSION OF RPL
4.1 During the period of contingency it shall suspend the application of RPL lists, users must submit, in all cases, the
corresponding FPL, according to the routes specified in Annex A.
5. PERMISSION LIMIT
5.1 When en-route IFR flights have communications coverage for the aeronautical mobile service, but the ATS units
have not fixed communications between them, the permit shall be valid until the control transfer point, with the selftransfer condition performed by the pilot.
6. SSR CODE ASSIGNMENT
6.1 Although RADAR systems were out of order, the service will continue assigning SSR codes to all aircraft.
7. AIR/AIR COMMUNICATION PROCEDURES
7.1 Aircraft shall, in case that can not make self-transfer and within 50 NM of the point so listed, use the air/air
communication procedures in frequency 123.45 MHz.
8. FLIGHT PLAN NOT TRANSMITTED
8.1 In the period of contingency the ATS units shall accept flights whose FPL have not been transmitted. However,
the presentation of the FPL by the user is also required.
9.
Vertical separation
9.1 Vertical separation minimum shall be provided in accordance with the provisions of ICAO Annex 2, Appendix 3 Table a) Cruising Levels (although routes have been modified in one way flight, aircraft take flight levels for as if they
were two-way route of flight).
10. ATS ROUTES:
10.1 While the contingency plans were activated, it shall only use those routes that are detailed below in ANNEX
ALPHA.
AIS URUGUAY
AMDT NR 45
GEN 1.6-40
01 APR 2014
AIP
URUGUAY
ANNEX ALPHA: SIMPLIFIED ROUTE NETWORK IN HIGHER/LOWER AIRSPACE
From CURITIBA FIR to MONTEVIDEO FIR
Routes
Segment
FIR
!
UM792
MLO/
AROMO/
TELAK/
CRR
CURITIBA/
MONTEVIDEO
UA 305
!UGELO/
LITOS/
LDS
CURITIBA/
MONTEVIDEO
A310
BGE/
ASUMA/
MLO/
AROMO/
TELAK
CRR
CURITIBA/
MONTEVIDEO
AMDT NR 45
Restrictions
- With coordination between the FIR's (with or without radar) the
Agreements shall be apply.
- Without coordination between the FIR's: CURITIBA ACC shall
deliver the traffic to MONTEVIDEO ACC levelled with FL 260,
280, 320, 380 or 430 in MLO.
- Traffic capacity on the route: one (1) aircraft every 15 minutes in
MLO.
- Unique direction of flight: from BRAZIL to URUGUAY.
- Without coordination, use the method of self-transference, with
no less than 5' minutes before MLO.
- Aircrafts shall communicate in freq 123.45 Mhz 5' minutes
before and after VOR MLO.
- With coordination between the FIR's (with or without radar) the
Agreements shall be apply.
- Without coordination between the FIR's: CURITIBA ACC shall
deliver the traffic to MONTEVIDEO ACC levelled with FL 260,
280, 320, 380 or 430 in UGELO.
- Traffic capacity on the route: one (1) aircraft every 15 minutes in
UGELO.
- Unique direction of flight: from BRAZIL to URUGUAY.
- Without coordination, use the method of self-transference, with
no less than 5' minutes before UGELO.
- Aircrafts shall communicate in freq 123.45 Mhz 5' minutes
before and after UGELO.
- With coordination between the FIR's (with or without radar) the
Agreements shall be apply.
- Without coordination between the FIR's: CURITIBA ACC shall
deliver the traffic to MONTEVIDEO ACC levelled with a FL,
according to the table of cruising levels in ASUMA.
- Traffic capacity on the route: one (1) aircraft every 15 minutes in
ASUMA.
- Unique direction of flight: from URUGUAY to MONTEVIDEO.
- Without coordination, use the method of self-transference, with
no less than 5' minutes before ASUMA.
- Aircrafts shall communicate in freq 123.45 Mhz 5' minutes
before and after ASUMA.
AIS URUGUAY
AIP
URUGUAY
GEN 1.6-41
01 APR 2014
From CURITIBA FIR to MONTEVIDEO FIR
Routes
A305
Segment
!UGELO/
BOLAT/
LITOS/
LDS
FIR
CURITIBA/
MONTEVIDEO
Restrictions
- With coordination between the FIR's (with or without radar) the
Agreements shall be apply.
- Without coordination between the FIR's: CURITIBA ACC shall
deliver the traffic to MONTEVIDEO ACC levelled with a FL,
according to the table of cruising levels in UGELO.
- Traffic capacity on the route: one (1) aircraft every 15 minutes in
UGELO.
- Unique direction of flight: from BRAZIL to URUGUAY.
- Without coordination, use the method of self-transference, with
no less than 5' minutes before UGELO.
- Aircrafts shall communicate in freq 123.45 Mhz 5' minutes
before and after UGELO.
From MONTEVIDEO FIR to CURITIBA FIR
Routes
Segment
UM540
CRR/
MOLBI/
AKPOD
!
A309
CRR/
SOLIS/
OGMAR/
UGURA
AIS URUGUAY
FIR
MONTEVIDEO/
CURITIBA
MONTEVIDEO/
CURITIBA
Restrictions
- With coordination between the FIR's (with or without radar) the
Agreements shall be apply.
- Without coordination between the FIR's: MONTEVIDEO ACC
shall deliver the traffic to CURITIBA ACC levelled with FL 250,
270, 290, 350 or 410 in AKPOD.
- Traffic capacity on the route: one (1) aircraft every 15 minutes
in AKPOD.
- Unique direction of flight: from URUGUAY to BRAZIL.
- Without coordination, use the method of self-transference, with
no less than 5' minutes before AKPOD.
- Aircrafts shall communicate in freq 123.45 Mhz 5' minutes
before and after AKPOD.
- With coordination between the FIR's (with or without radar) the
Agreements shall be apply.
- Without coordination between the FIR's: MONTEVIDEO ACC
shall deliver the traffic to CURITIBA ACC levelled with a FL,
according to the table of cruising levels in UGURA.
- Traffic capacity on the route: one (1) aircraft every 15 minutes
in UGURA.
- Unique direction of flight: from URUGUAY to BRAZIL.
- Without coordination, use the method of self-transference, with
no less than 5' minutes before UGURA.
- Aircrafts shall communicate in freq 123.45 Mhz 5' minutes
before and after UGURA.
AMDT NR 45
GEN 1.6-42
01 APR 2014
AIP
URUGUAY
From CURITIBA FIR to FIR EZEIZA
Routes
Segment
FIR
!
UN741
BGE/
ISALA/
DALGO/
DUR/
PONPA/
PAPIX/
EZE
CURITIBA/
MONTEVIDEO/
EZEIZA
A305/
A306
!UGELO/
BOLAT/
LITOS/
LDS/
LUCIO/
DAGUS/
SARGO/
PTA
CURITIBA/
MONTEVIDEO/
EZEIZA
Restrictions
- With coordination between the FIR's (with or without radar) the
Agreements shall be apply.
- Without coordination between the FIR's: MONTEVIDEO ACC
shall deliver the traffic to CURITIBA ACC levelled with FL 260,
280, 320, 380 or 430 in BGE.
- Traffic capacity on the route: one (1) aircraft every 15 minutes in
BGE.
- Unique direction of flight: from BRAZIL to ARGENTINA.
- Without coordination, use the method of self-transference, with
no less than 5' minutes before BGE.
- Aircrafts shall communicate in freq 123.45 Mhz 5' minutes
before and after BGE.
- With coordination between the FIR's (with or without radar) the
Agreements shall be apply.
- Without coordination between the FIR's: MONTEVIDEO ACC
shall deliver the traffic to CURITIBA ACC levelled with a FL,
according to the table of cruising levels in UGELO.
- Traffic capacity on the route: one (1) aircraft every 15 minutes in
UGELO.
- Unique direction of flight: from BRAZIL to ARGENTINA.
- Without coordination, use the method of self-transference, with
no less than 5' minutes before UGELO.
- Aircrafts shall communicate in freq 123.45 Mhz 5' minutes
before and after UGELO.
From EZEIZA FIR to CURITIBA FIR
Routes
!
UN857
Segment
PTA/
DORVO/
PABOT/
LOMID/
MLO
AMDT NR 45
FIR
Restrictions
- With coordination between the FIR's (with or without radar) the
Agreements shall be apply.
- Without coordination between the FIR's: MONTEVIDEO ACC
shall deliver the traffic to CURITIBA ACC levelled with FL 250,
270, 290, 350 or 410 in MLO.
EZEIZA/
- Traffic capacity on the route: one (1) aircraft every 15 minutes in
MONTEVIDEO/
MLO.
CURITIBA
- Unique direction of flight: from ARGENTINA to BRAZIL.
- Without coordination, use the method of self-transference, with
no less than 5' minutes before MLO.
- Aircrafts shall communicate in freq 123.45 Mhz 5' minutes
before and after VOR MLO.
AIS URUGUAY
AIP
URUGUAY
Routes
GEN 1.6-43
10 DEC 2015
Segment
FIR
UL 324
EZE/
KUKEN/
TORON/
PALOL/
ANPON/
DAYMA/
GUTIL/
CUARA/
EZEIZA/
MONTEVIDEO/
CURITIBA
UM 654
EZE/
KUKEN/
GAMOT
EZEIZA/
MONTEVIDEO/
CURITIBA
A305/
A306
EZE/
DORVO/
!TOKAM/
CRR/
SOLIS/
OGMAR/
UGURA
EZEIZA/
MONTEVIDEO/
CURITIBA
Restrictions
- With coordination between the FIR's (with or without radar) the
Agreements shall be apply.
- Without coordination between the FIR's: MONTEVIDEO ACC shall
deliver the traffic to CURITIBA ACC levelled with FL 250, 270, 290,
350 or 410 in CUARA.
- Traffic capacity on the route: one (1) aircraft every 15 minutes in
CUARA.
- Unique direction of flight: from ARGENTINA to BRAZIL.
- Without coordination, use the method of self-transference, with no
less than 5' minutes before CUARA.
- Aircrafts shall communicate in freq 123.45 Mhz 5' minutes
before and after CUARA.
- With coordination between the FIR's (with or without radar) the
Agreements shall be apply.
- Without coordination between the FIR's: MONTEVIDEO ACC shall
deliver the traffic to CURITIBA ACC levelled with FL 290, 350, or
410 in GAMOT. Minimum level in GAMOT FL 290.
- Traffic capacity on the route: one (1) aircraft every 15 minutes
in GAMOT.
- Without coordination, use the method of self-transference, with no
less than 5' minutes before GAMOT.
- Aircrafts shall communicate in freq 123.45 Mhz 5' minutes
before and after GAMOT.
- With coordination between the FIR's (with or without radar) the
Agreements shall be apply.
- Without coordination between the FIR's: MONTEVIDEO ACC
shall deliver the traffic to CURITIBA ACC levelled with a FL,
according to the table of cruising levels in UGURA.
- Traffic capacity on the route: one (1) aircraft every 15 minutes
in UGURA.
- Unique direction of flight: from ARGENTINA to BRAZIL.
- Without coordination, use the method of self-transference, with
no less than 5' minutes before UGURA.
- Aircrafts shall communicate in freq 123.45 Mhz 5' minutes
before and after UGURA.
NOTE 1: The traffic between CURITIBA FIR and MONTEVIDEO FIR shall be one (1) aircraft every fifteen (15 ')
minutes, which forms a maximum flow of four (4) aircraft per hour between the two FIR's., by transfer point, regardless
of the flight level used by aircraft.
NOTE 2: When the transfer point is common to the Upper and Lower Airspace the traffic spacing shall be
independent for each airspace, but no more than four (4) aircraft per hour in each space.
NOTE 3: Depending on the level of degradation of the Services, the respective Supervisors may, by agreement,
coordinate the accommodation of a greater number of aircraft by transfer points.
AIS URUGUAY
AIRAC AMDT NR 02
GEN 1.6-44
01 APR 2014
AIP
URUGUAY
RIVERA INTERNATIONAL AIRPORT
5.14 Coordination on flights between Porto Alegre and Rivera/Uruguayana
5.14.1 When only provide Flight Information Service and Alerting Service will be made the appropriate coordination
with respect to VFR and IFR flights that cross the common boundary of the Flight Information Regions. This
coordination will include the transmission of the following information about the flights in question:
a) appropriate parts of the current flight plan, and
b) the time of the last contact with the aircraft.
5.14.2 The information given will be transmitted at least fifteen (15) minutes before the aircraft leaves the Flight
Information Region by the ACC that has dictated.
5.14.3 The Transferring Centre will assign an appropriate level, prior coordination with the Receptor Centre, which
must be reached, whenever possible, before the aircraft reaches the FIR boundary, except that the availability of point
to point links through the REDDIG with the degree of reliability required by ICAO and radar coverage of both centres,
it may be done radar transference applying a minimum longitudinal separation between aircraft at the same level of 20
NM.
5.14.4 Flights between Rivera and Porto Alegre/Uruguayana, shall proceed according to the FPL submitted
establishing radio contact with Curitiba ACC five (5) minutes after takeoff.
Note: The Administration of Brazil no make objections to the implementation of departure procedures and eventual
climb straight of runway 04 Rivera Intl Airport with subsequent penetration of the Curitiba FIR, pointing out that these
procedures shall be made by turning right at reaching 1.300 feet.
AMDT NR 45
AIS URUGUAY
AIP
URUGUAY
GEN 1.7-1
01 AUG 2015
GEN 1.7 DIFFERENCES FROM ICAO STANDARS,
RECOMMENDED PRACTICES AND PROCEDURES
1. ANNEX 1 – PERSONNEL LICENSING (TENTH EDITION): Amendment 160 (Executive Decree 312/995)
2. ANNEX 2 – RULES OF THE AIR (TENTH EDITION): Amendment 41 (DINACIA Resolution NR 16/009)
Chap. 3
3.3.1.2
General Rules
Flight plan must be submitted in all cases except for VFR flights in space G.
!
!
3.3.5.4
When the pilot presents a flight plan within national boundaries, know before starting it, than any of the
procedures in this Schedule for giving notice of arrival (ARR) is practicable, shall place on record that
inability scoring in the box 18 of the flight plan form, the following: ARR/NIL.
Note: Entries ARR/NIL, held in box 18 of the Flight Plan form avoid to be activated unnecessarily the
alerting services, search and rescue.
3.6.2.2.1
Not applicable.
3.6.3.1.1
Not applicable.
Cap. 4
Visual Flight Rules
4.3
VFR flights shall operate from 30 minutes before the sunrise until 30 minutes after the sunset.
Nocturnal VFR flights are authorized if they meet the requirements of the RAU 91 and 135.
4.4
c) on the sea more than 20 NM (37 km) of coastline, for over an hour,
d) over clouds, fog and other weather formations when they obstruct the continuous visual reference
with the ground.
4.5
a) VFR levels are used only up to FL 195.
!
!
PROCEDURES FOR AIR NAVIGATION SERVICES – AIR TRAFFIC MANAGEMENT (PANS-ATM Doc. 4444
ATM/501) Fifteenth Edition 2007 – Amendment 2
CHAPTER 4 General Provisions for Air Traffic Services
4.3.2.1.1. literal c) does not apply
4.10.4.6. Not provided QFE altimeter setting.
AIS URUGUAY
AMDT NR 48
GEN 1.7-2
01 AUG 2015
AIP
URUGUAY
CHAPTER 5 Separation Methods and Minima
5.4.2.2.2.1 Not applicable at the time of the transfer of responsibilities, when flights will cross international borders.
Instead apply the procedures set out in Agreement signed with Ezeiza, Resistencia and Curitiba,
ACC's.
5.4.2.3.3.1 Not applicable at the time of the transfer of responsibilities, when flights will cross international borders.
!
!
!
CHAPTER 9 Flight Information Service and Alerting Service
9.2.2.1
By regional agreement the period is three minutes.
REGIONAL SUPPLEMENTARY PROCEDURES (Doc 7030) (FOURTH EDITION)
See differences in ENR 1.8-1.
3. ANNEX 3 – METEOROLOGICAL SERVICE FOR INTERNATIONAL AIR NAVIGATION (DECIMOQUINTA
EDICIÓN): Amendment 74 (DINACIA Resolution NR 19/009)
Appendix 3
4.3.4
Averaging
a) 10 minutes for local routine and special reports and for visual presentations of runway visual range at the
offices of Air Traffic Services.
4. ANNEX 4 – AERONAUTICAL CHARTS (TENTH EDITION): Amendment 53 (DINACIA Resolution NR 428/005)
Chap. 3 Aerodrome Obstacle Chart - ICAO Type A (Operating Limitations)
Currently these plans are not published but are under construction
Chap. 4 Aerodrome Obstacle Chart - ICAO Type B
Currently these plans are not published but are under construction
Chap. 5 Aerodrome Obstacle Chart - ICAO Type C
Currently these plans are not published but are under construction
Chap. 16 World Aeronautical Chart – ICAO 1:1 000 000
Currently publishes the chart with nationwide coverage on a single sheet but not with the coverage defined in
Appendix 5 where Uruguay corresponds to the chart 3434.
AMDT NR 48
AIS URUGUAY
AIP
URUGUAY
GEN 1.7-3
01 AUG 2015
5. ANNEX 5 – UNITS OF MEASUREMENT TO BE USED IN AIR AND GROUND OPERATIONS
(FOURTH EDITION): Amendment 15 (Executive Decree 335/988)
6. ANNEX 6 – OPERATION OF AIRCRAFT
(PART I EIGHTH EDITION): Amendment 30 (DINACIA Resolution NR 056/007).
(PART II SEVENTH EDITION): Amendment 27 (DINACIA Resolution NR 18/009).
(PART III SIXTH EDITION): Amendment 11 (DINACIA Resolution NR 023/007)
7. ANNEX 7 – AIRCRAFT NATIONALITY AND REGISTRATION MARKS (FIFTH EDITION):
Amendment 5 (DINACIA Resolution NR 162/006).
8. ANNEX 8 – AIRWORTHINESS OF AIRCRAFT (TENTH EDITION): Amendment 100 (DINACIA Resolution NR
161/006)
9. ANNEX 9 - FACILITATION, (DUODÉCIMA EDICIÓN): Amendment 20 (DINACIA Resolution NR 217/007)
2.9
Not applicable (Resolution NR 42/005).
10. ANNEX 10 – AERONAUTICAL TELECOMUNICATIONS,
(VOLUME I SIXTH EDITION): Amendment 80 (DINACIA Resolution NR 003/006)
(VOLUME II SIXTH EDITION): Amendment 80 (DINACIA Resolution NR 003/006)
(VOLUME III FISRT EDITION): Amendment 80 (DINACIA Resolution NR 003/006)
(VOLUME IV FOURTH EDITION): Amendment 77 (DINACIA Resolution NR 003/006)
(VOLUME V SECOND EDITION): Amendment 77 (DINACIA Resolution NR 003/006)
11. ANNEX 11 – AIR TRAFFIC SERVICES (THIRTEENTH EDITION JUL 2001) Amendment 46 (DINACIA
Resolution NR 060/2009)
Chap. 3
3.3.5
Air Traffic Control Service
c) Not applicable in the Uruguayan airspace, there are no agreements with neighbouring countries to
implement
3.6.1.3.1 c) Does not apply to aircraft on arrival
3.10
Not available surface movement radar (SMR)
12. ANNEX 12 – SEARCH ADN RESCUE (EIGHTH EDITION): Amendment 17 (DINACIA Resolution NR
065/006)
AIS URUGUAY
AMDT NR 48
GEN 1.7-4
01 AUG 2015
AIP
URUGUAY
13. ANNEX 13 – AIRACFT ACCIDENT AND INCIDENT INVESTIGATION (NINETH EDITION):
Amendment 11 (DINACIA Resolution NR 449/006)
14. ANNEXO 14 - AERODROMES (VOLUME I FIFTH EDITION, VOLUME II THIRD EDITION)
Volume I: Amendment 9 (DINACIA Resolution NR 451/009)
Volume II: Amendment 3 (DINACIA Resolution NR 067/006)
15. ANNEX 15 – AERONAUTICAL INFORMATION SERVICES (TWELFTH EDITION): Amendment 33
(DINACIA Resolution NR 120/006)
3.6. The Uruguay AIP, AIP Supplements and Aeronautical Information Circulars (AIC), do not include a text
in English language for the parts expressed in plain language.
16. ANNEX 16 – ENVIRONMENTAL PROTECTION (VOLUME I FIFTH EDITION, VOLUME II
THIRD EDITION)
Volume I: Amendment 9 (DINACIA Resolution NR 015/009)
Volume II: Amendment 6 (DINACIA Resolution NR 015/009)
17. ANNEX 17 - SECURITY (OCTAVA EDICIÓN): Amendment 11 (DINACIA Resolution NR
241/006)
18. ANNEX 18 – THE SAFE TRANSPORT OF DANGEROUS GOODS BY AIR
(THIRD EDITION): Amendment 9 (DINACIA Resolution NR 062/010)
AMDT NR 48
AIS URUGUAY