09.12.2012 Views

August 25 2011 Notices to Airmen - FAA

August 25 2011 Notices to Airmen - FAA

August 25 2011 Notices to Airmen - FAA

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

International<br />

3−INTL−48<br />

<strong>Notices</strong> <strong>to</strong> <strong>Airmen</strong><br />

Pilots may be requested by ATC <strong>to</strong> provide an estimate for when the flight can accept the next higher<br />

altitude(s). If requested, pilots should provide this information as soon as possible.<br />

Westbound aircraft entering RVSM or MNPS airspace in the New York FIR:<br />

Pilots should include in the initial position report the time or location that the next higher altitude can be<br />

accepted.<br />

EXAMPLE−<br />

“Global Air 543, 40 north 40 west at 1010, flight level 350, estimating 40 north 50 west at 1110, 40 north 60 west.<br />

Next able flight level 360 at 1035.”<br />

NOTE−<br />

Pilots may include more than one altitude if that information is available.<br />

EXAMPLE−<br />

(after stating initial report) “Able flight level 360 at 1035, able flight level 370 at 1145, able flight level 390 at<br />

1300.”<br />

MANDATORY PILOT REPORTS<br />

In addition <strong>to</strong> reading back altitude assignments, pilots shall report reaching any altitude assigned within<br />

RVSM airspace. This serves as a double check between pilots and controllers and reduces the possibility of<br />

operational errors. This requirement for altitude readback and reports of reaching assigned altitudes applies<br />

<strong>to</strong> both RVSM and CVSM altitudes (i.e., flight levels 330, 340, 350, 360, and 370).<br />

EXAMPLE−<br />

(initial altitude readback): “Global Air 543 climbing <strong>to</strong> flight level 360.”<br />

(upon reaching assigned altitude): “Global Air 543 level at flight level 360.”<br />

CARIBBEAN, SOUTH AMERICA, AND GULF OF MEXICO<br />

FDC 2/8646 ZFW TX.. Due <strong>to</strong> the lack of terrain and obstacle clearance data, accurate au<strong>to</strong>mation data bases<br />

are not available for providing minimum safe altitude warning information <strong>to</strong> aircraft overflying Mexico. Air<br />

traffic facilities along the United States/Mexico border have inhibited minimum safe altitude warning<br />

computer programs for aircraft operating in Mexican airspace until accurate terrain data can be obtained.<br />

(ATP−130 7/29/02)<br />

FDC 2/8645 ZHU TX.. Due <strong>to</strong> the lack of terrain and obstacle clearance data, accurate au<strong>to</strong>mation data bases<br />

are not available for providing minimum safe altitude warning information <strong>to</strong> aircraft overflying Mexico. Air<br />

traffic facilities along the United States/Mexico border have inhibited minimum safe altitude warning<br />

computer programs for aircraft operating in Mexican airspace until accurate terrain data can be obtained.<br />

(ATP−130 7/29/02)<br />

FDC 2/8644 ZAB NM.. Due <strong>to</strong> the lack of terrain and obstacle clearance data, accurate au<strong>to</strong>mation data bases<br />

are not available for providing minimum safe altitude warning information <strong>to</strong> aircraft overflying Mexico. Air<br />

traffic facilities along the united states/Mexico border have inhibited minimum safe altitude warning<br />

computer programs for aircraft operating in Mexican airspace until accurate terrain data can be obtained.<br />

(ATP−130 7/29/02)<br />

ENHANCEMENT OF THE MEXICO VHF NETWORK<br />

On May 1, 2003 ARINC declared its Mexico VHF Voice Network (MEXNET) operational. This network<br />

is operated as part of the existing ARINC Domestic VHF Network Service, controlled from the ARINC New<br />

York Communications Center on network frequency 130.700 MHz. In 2006, ARINC installed additional<br />

VHF voice ground stations at Villahermosa, (MX/VSA) and Veracruz (MX/VER) <strong>to</strong> provide improved<br />

enroute and on−ground coverage at these airports. Effective May 1, 2007, the ARINC San Francisco<br />

Communications Center assumed control of this network.<br />

SECTION 2

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

Saved successfully!

Ooh no, something went wrong!