Narrative:

I was working the radar/radar associate position of the houston ocean east sector 72R&D. Aircraft swbound on A758 were relaying non radar position reports via new york commercial radio. Merida east controller had coordinated air carrier X, a B757/right, from mggt A758 via frish intersection, nebound at FL290. I had coordinated aircraft Y, a B722/right, via A758 to mmun swbound at FL310. Aircraft Y relayed to new york commercial radio FL310 estimate frish intersection at XA13Z. At XA12Z, aircraft X checked on my frequency estimating frish at XA18Z at FL310. I asked aircraft X to verify his altitude and position. I issued an urgent TA and informed him he should be with merida on 128.2 till frish and advised aircraft X to return immediately to 128.2 for control instructions. Aircraft X insisted merida told him to 'expect FL290,' but had xferred him to my frequency. As I could not take control action in merida's airspace, I told him to contact merida 128.2 immediately. I advised the merida controller of the urgency via the 358-shout line. Aircraft were about 3 mins apart, head-on, at this time! About 5 mins later, aircraft X checked over frish on my frequency at FL290. I advised my supervisor. He later advised me the merida supervisor had said aircraft X pilot had changed frequency without control instructions. The pilot insists he was changed to our frequency. We are to switch radio control at the fir. Aircraft are changing to our frequency up to 10 mins early and we have advised our airspace office to contact merida about this problem. Callback conversation with reporter revealed the following information: reporter states that this is a very heavily tracked route. The reporter advises that ZHU and mmid have frequency and respectful conversations to attempt to resolve ATC procedural sits. The FAA has a transmitter site, co-usage with a comrdo facility at cancun, mexico. Communication is generally adequate above FL200, marginal at the fir boundary below FL280. The reporter advised that mexico is attempting to provide funding to establish radar coverage throughout the entirety of mmid's control. But there is a difference between mmid and ZHU's 'view' of air traffic events. As long as air traffic coordination and communication is standard, english is used. Nonstandard events, attempting to validate control sits, are most likely responded to in spanish -- which may or may not be understood by the ZHU controller. ZHU controllers believe that good effort and intent is generally exercised by mmid controllers.

Google
 

Original NASA ASRS Text

Title: ZHU NONRADAR CTLR QUESTIONS B757'S ALT ON A758 STILL IN MMID AIRSPACE WITH OPPOSITE DIRECTION B727, SAME ALT, APCHING MMID FIR. ZHU ISSUES ALERT TO B757 AND MMID AND REMANDS THE B757 BACK TO MMID. THE B757 RPTS 5 MINS LATER AT FL290 AT FIR XFER POINT.

Narrative: I WAS WORKING THE RADAR/RADAR ASSOCIATE POS OF THE HOUSTON OCEAN E SECTOR 72R&D. ACFT SWBOUND ON A758 WERE RELAYING NON RADAR POS RPTS VIA NEW YORK COMMERCIAL RADIO. MERIDA E CTLR HAD COORDINATED ACR X, A B757/R, FROM MGGT A758 VIA FRISH INTXN, NEBOUND AT FL290. I HAD COORDINATED ACFT Y, A B722/R, VIA A758 TO MMUN SWBOUND AT FL310. ACFT Y RELAYED TO NEW YORK COMMERCIAL RADIO FL310 ESTIMATE FRISH INTXN AT XA13Z. AT XA12Z, ACFT X CHKED ON MY FREQ ESTIMATING FRISH AT XA18Z AT FL310. I ASKED ACFT X TO VERIFY HIS ALT AND POS. I ISSUED AN URGENT TA AND INFORMED HIM HE SHOULD BE WITH MERIDA ON 128.2 TILL FRISH AND ADVISED ACFT X TO RETURN IMMEDIATELY TO 128.2 FOR CTL INSTRUCTIONS. ACFT X INSISTED MERIDA TOLD HIM TO 'EXPECT FL290,' BUT HAD XFERRED HIM TO MY FREQ. AS I COULD NOT TAKE CTL ACTION IN MERIDA'S AIRSPACE, I TOLD HIM TO CONTACT MERIDA 128.2 IMMEDIATELY. I ADVISED THE MERIDA CTLR OF THE URGENCY VIA THE 358-SHOUT LINE. ACFT WERE ABOUT 3 MINS APART, HEAD-ON, AT THIS TIME! ABOUT 5 MINS LATER, ACFT X CHKED OVER FRISH ON MY FREQ AT FL290. I ADVISED MY SUPVR. HE LATER ADVISED ME THE MERIDA SUPVR HAD SAID ACFT X PLT HAD CHANGED FREQ WITHOUT CTL INSTRUCTIONS. THE PLT INSISTS HE WAS CHANGED TO OUR FREQ. WE ARE TO SWITCH RADIO CTL AT THE FIR. ACFT ARE CHANGING TO OUR FREQ UP TO 10 MINS EARLY AND WE HAVE ADVISED OUR AIRSPACE OFFICE TO CONTACT MERIDA ABOUT THIS PROB. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATES THAT THIS IS A VERY HEAVILY TRACKED RTE. THE RPTR ADVISES THAT ZHU AND MMID HAVE FREQ AND RESPECTFUL CONVERSATIONS TO ATTEMPT TO RESOLVE ATC PROCEDURAL SITS. THE FAA HAS A XMITTER SITE, CO-USAGE WITH A COMRDO FACILITY AT CANCUN, MEXICO. COM IS GENERALLY ADEQUATE ABOVE FL200, MARGINAL AT THE FIR BOUNDARY BELOW FL280. THE RPTR ADVISED THAT MEXICO IS ATTEMPTING TO PROVIDE FUNDING TO ESTABLISH RADAR COVERAGE THROUGHOUT THE ENTIRETY OF MMID'S CTL. BUT THERE IS A DIFFERENCE BTWN MMID AND ZHU'S 'VIEW' OF AIR TFC EVENTS. AS LONG AS AIR TFC COORD AND COM IS STANDARD, ENGLISH IS USED. NONSTANDARD EVENTS, ATTEMPTING TO VALIDATE CTL SITS, ARE MOST LIKELY RESPONDED TO IN SPANISH -- WHICH MAY OR MAY NOT BE UNDERSTOOD BY THE ZHU CTLR. ZHU CTLRS BELIEVE THAT GOOD EFFORT AND INTENT IS GENERALLY EXERCISED BY MMID CTLRS.

Data retrieved from NASA's ASRS site as of July 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.