Section 7. Mexican Movement and Control Messages (Transborder Flights Only)

1. GENERAL

1. Except as outlined in this section, handle transborder Mexican movement and control messages as described in Chapter 6, Section 1, Section 2, and Section 3. IFR flight plans to Mexico require the ICAO flight plan form.
2. Do not include ADCUS in flight plan remarks for flight plans to Mexico; Mexican Customs authorizations are the obligation of the pilot. Do not include ADCUS in flight plan remarks for flights plans from Mexico to the U.S. because U.S. FSSs no longer alert U.S CBP. U.S. APIS authorizations are the obligation of the pilot for flights departing and entering the U.S., as stated in 19 CFR 122. APIS resources for pilots are available at http://www.cbp.gov.

1. INBOUNDS FROM MEXICO

1. When received in the proper format, VFR flight notification messages are automatically acknowledged and suspended by the operational system.
2. Acknowledge receipt of a flight notification message as soon as practicable by transmitting the letter R followed by the full aircraft identification.

1. Suspense VFR flight notification messages until arrival or closure information is received. File IFR messages.

1. OUTBOUNDS TO MEXICO

1. Mexican customs notification is the obligation of the pilot. U.S. CBP authorizations for flights outbound from the U.S. to Mexico are also the obligation of the pilot and must be obtained via the APIS process. APIS resources for pilots are available at http://www.cbp.gov.

1. If the pilot still intends to land at a destination other than an airport‐of‐entry, advise the pilot that the flight plan will not be used for customs or SAR service in Mexico.
2. Transmit the flight notification message to the regional flight dispatch office, not the destination tie‐in station.

1. VFR flight plans.

1. Upon notification of departure of VFR flights, transmit a flight notification message. Address messages to the ICAO addressee for the appropriate destination location.
2. If a VFR flight plan is filed with a destination other than an airport‐of‐entry, transmit the flight notification message to the regional flight dispatch office, not the destination tie‐in station. If the correct addressee cannot be determined, transmit to the nearest border regional flight dispatch office.

1. Address messages to the ICAO addressee for the appropriate destination location. Transmit the following information:

1. Type of flight.
2. Aircraft identification.
3. Aircraft type.
4. Departure point.
5. Destination.
6. ETA.
7. Remarks.

1. If acknowledgment is not received within 30 minutes after departure, transmit a “request acceptance” message to the destination station tie‐in addressee and to the regional flight dispatch office. Manually address the message to the designated regional flight dispatch office.

1. The regional flight dispatch office involved will then normally send an acknowledgment to the departure station and assume responsibility for the flight notification message.
2. If acknowledgment/acceptance is not received within one hour of the departure, use interphone/telephone or other available means to deliver the message to the appropriate regional flight dispatch office. See TBL 6-7-1 for telephone numbers. For a complete address, add “XMXO” to the identifier.

1. Do not accept round‐robin flight plans to Mexico.