Narrative:

We were requested to climb from FL330 to FL370, were unable FL370 and then cleared to FL350. Next sector requested us to climb FL370 on check-in, still unable. Requested FL350 and told to standby. Heard air carrier Y on frequency at FL350, northbound, cleared direct avelo. Y appeared on TCASII and communication was established on 130.55. We and Y agreed to deviate left. After initiating turn, RA was received and responded to. Center was informed and we were told to maintain FL370. TCASII resolution was over by FL360 at XA58Z, 132 NM south of miq VOR. Supplemental information from acn 303466: we were at our altitude FL330. We reported unable FL370 but miq control requested a climb to FL370 if able. We were unable, but said we could do FL350, then FL370 around albog intersection. We were then cleared to FL350. We changed controllers over miq VOR and gave standard position report to new miq control. New controller cleared us to FL370. We asked to remain at FL350 until albog intersection and was told to standby. Miq then began to rerte air carrier Y, a northbound flight same altitude as us, with direct miq VOR, the avelo. Shortly after, air carrier Y reported aircraft same altitude coming towards them. We saw air carrier Y at the same time and contacted them on 130.55. They said they were turning left, so we responded with a left turn of our own. As soon as we started turning we received a TCASII TA, then RA climb. We climbed to FL370, reporting to miq along the way. Miq told us to maintain FL370. TCASII resolution was over at approximately FL360. This TA/RA happened at approximately XA58Z. We were sbound on UA315 approximately 132 mi south of miq VOR. In my opinion, we should avoid miq airspace until the controllers are more proficient.

Google
 

Original NASA ASRS Text

Title: 2 ACR WDBS HEAD-T0-HEAD AT THE SAME ALT, IN FOREIGN AIRSPACE.

Narrative: WE WERE REQUESTED TO CLB FROM FL330 TO FL370, WERE UNABLE FL370 AND THEN CLRED TO FL350. NEXT SECTOR REQUESTED US TO CLB FL370 ON CHK-IN, STILL UNABLE. REQUESTED FL350 AND TOLD TO STANDBY. HEARD ACR Y ON FREQ AT FL350, NBOUND, CLRED DIRECT AVELO. Y APPEARED ON TCASII AND COM WAS ESTABLISHED ON 130.55. WE AND Y AGREED TO DEVIATE L. AFTER INITIATING TURN, RA WAS RECEIVED AND RESPONDED TO. CTR WAS INFORMED AND WE WERE TOLD TO MAINTAIN FL370. TCASII RESOLUTION WAS OVER BY FL360 AT XA58Z, 132 NM S OF MIQ VOR. SUPPLEMENTAL INFO FROM ACN 303466: WE WERE AT OUR ALT FL330. WE RPTED UNABLE FL370 BUT MIQ CTL REQUESTED A CLB TO FL370 IF ABLE. WE WERE UNABLE, BUT SAID WE COULD DO FL350, THEN FL370 AROUND ALBOG INTXN. WE WERE THEN CLRED TO FL350. WE CHANGED CTLRS OVER MIQ VOR AND GAVE STANDARD POS RPT TO NEW MIQ CTL. NEW CTLR CLRED US TO FL370. WE ASKED TO REMAIN AT FL350 UNTIL ALBOG INTXN AND WAS TOLD TO STANDBY. MIQ THEN BEGAN TO RERTE ACR Y, A NBOUND FLT SAME ALT AS US, WITH DIRECT MIQ VOR, THE AVELO. SHORTLY AFTER, ACR Y RPTED ACFT SAME ALT COMING TOWARDS THEM. WE SAW ACR Y AT THE SAME TIME AND CONTACTED THEM ON 130.55. THEY SAID THEY WERE TURNING L, SO WE RESPONDED WITH A L TURN OF OUR OWN. AS SOON AS WE STARTED TURNING WE RECEIVED A TCASII TA, THEN RA CLB. WE CLBED TO FL370, RPTING TO MIQ ALONG THE WAY. MIQ TOLD US TO MAINTAIN FL370. TCASII RESOLUTION WAS OVER AT APPROX FL360. THIS TA/RA HAPPENED AT APPROX XA58Z. WE WERE SBOUND ON UA315 APPROX 132 MI S OF MIQ VOR. IN MY OPINION, WE SHOULD AVOID MIQ AIRSPACE UNTIL THE CTLRS ARE MORE PROFICIENT.

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.