NORTH AND SOUTH AMERICA - CNATRA - The US Navy

3-6 BRAZIL
to conduct flights in RVSM airspace and that are capable of
meeting the minimum aircraft system performance specification
(MASPS) height-keeping requirements (or equivalent).
(2) Brazilian operators shall contact Civil Aviation
Department (DAC) to obtain operational approval for RNP 10
capability. Other operators shall consult their relevant State
authority.
j. FLIGHT PLANNING REQUIREMENTS
(1) The following flight planning requirements will apply
to operators of RVSM approved civil aircraft intending to conduct
flights within the EUR/SAM Corridor RVSM airspace:
(a) For RVSM Approved Civil Aircraft
(b) Operators of RVSM approved civil aircraft shall
indicate the approval status by inserting the letter W in Item 10 of
the ICAO flight plan form regardless of the requested flight level.
(c) Operators of RVSM approved civil aircraft
intending to operate within the EURISAM Corridor RVSM airspace
shall include the following in Item 15 of the ICAO flight plan form:
1 The entry point at the lateral limits of the
EURISAM Corridor RVSM airspace and the requested flight level
for that portion of the route commencing immediately after the
RVSM entry point.
2 The exit point at the lateral limits of the
EURISAM Corridor RVSM airspace and the requested flight level
for that portion of the route commencing immediately after the
RVSM exit point.
(d) For RVSM Approved State Aircraft
(e) Operators of RVSM approved State aircraft shall
indicate the approval status by inserting the letter W in Item 10 of
the ICAO flight plan form regardless of the requested flight level,
except that operators of formation flights of State aircraft shall not
insert the letter W in Item 10 of the ICAO flight plan form
regardless of the RVSM approval status of the aircraft concerned.
(f) Operators of formation flights of State aircraft
intending to operate within the EURISAM Corridor RVSM airspace
as General Air Traffic (GAT) shall include STS/NONRVSM in Item 18
of the ICAO flight plan form regardless of the RVSM approval
status of the aircraft concerned.
(g) Operators of RVSM approved State aircraft
intending to operate within the EURISAM Corridor RVSM airspace
shall include the following in Item 15 of the ICAO flight plan form:
1 The entry point at the lateral limits of the
EURISAM Corridor RVSM airspace and the requested flight level
for that portion of the route commencing immediately after the
RVSM entry point.
2 The exit point at the lateral limits of the
EURISAM Corridor RVSM airspace and the requested flight level
for that portion of the route commencing immediately after the
RVSM exit point.
(h) For NON-RVSM Approved state Aircraft
(i) Operators of non-RVSM approved State aircraft
with a requested flight level between FL290 and FL410 shall insert
STS/NONRVSM in Item 18 of the ICAO flight plan form.
(j) Operators of formation flights of State aircraft
shall not insert: the letter W in Item 10 of the ICAO flight plan form
regardless of the RVSM approval status of the aircraft concerned.
Operators of formation flights of State aircraft intending to
operate within the EUR/SAM Corridor RVSM airspace as General
Air Traffic (GAT) shall include STS/NONRVSM in Item 18 of the
ICAO flight plan form.
(k) Operators of non-RVSM approved State aircraft
intending to operate within the EUR/SAM Corridor RVSM airspace
shall include the following in Item 15 of the ICAO flight plan form:
1 The entry point at the lateral limits of the
EUR/SAM Corridor RVSM airspace and the requested flight level
for that portion of the route commencing immediately after the
RVSM entry point and
2 The exit point at the lateral limits of the
EUR/SAM Corridor RVSM airspace and the requested flight level
for that portion of the route commencing immediately after the
RVSM exit point.
k. Special Procedures for crossing traffic (East/West)
operations.
(1) For the purpose of this application, crossing traffic is
defined as all that traffic entering or leaving the EUR/SAM RVSM
Airspace along its Eastern or Western Boundaries (i.e. at any
point other then its Northern Canarias) or Southern (Brazil)
boundaries.
(2) Crossing traffic can flight plan to enter and leave the
RVSM airspace at any point along its boundaries indicating in the
flight plan the coordinates and estimated time of the entering
and exit points into the RVSM airspace and of the crossing of
each of the fixed ATS routes.
(3) Except when flying on published crossing
routes/tracks, all crossing traffic intending to operate through the
RVSM airspace must obtain an ATC Clearance. This should be
requested sufficiently in advance to preclude C operational
difficulties from the ACC responsible for the first RVSM airspace
to be entered or in case of communications difficulties from any
of the ACCs concerned with the EUR/SAM RVSM airspace or still
from any other adjacent ACC.
l. Mandatory Pilot Reports
(1) In addition to reading back altitude assignments,
pilots shall report reaching any altitude assigned within RVSM
airspace. This serves as a double check between pilots and
controllers and reduces the possibility of operational errors. This
requirement for altitude read back and reports of reaching
assigned altitudes applies to both RVSM and CVSM altitudes (i.e.
flight levels 330, 340, 350, 360, and 370).
EXAMPLE:
initial altitude read back): "Global Air 543 climbing to flight level
360.”
upon reaching assigned altitude): "Global Air 543 level at flight
level 360.”
m. ACAS
(1) If ACAS (TCAS) is installed in RVSM compliant
aircraft, the equipment should be updated to Change 7 or a later
approved version for optimum performance in RVSM airspace.
n. TRANSITION AREA