Narrative:

We departed aca for lax as flight yy on apr/xx/97. We were cleared as filed at an initial altitude of FL310 (see attached flight plan). After departure we were cleared to FL310 with a restr to be above FL180 by 50 DME from aca. We climbed through FL180 as we passed 46 DME wnw of aca, and were told to contact mexico center passing zihuatanejo. We were level at FL310 when we checked in with mexico center over zihuatanejo. The controller said 'radar contact, maintain FL310.' we acknowledged and proceeded along J1 towards manzanillo. Although we had omega on board, I was navigating the aircraft by using vors. When we were 33 DME wnw of manzanillo (116.8), the time was XX30Z, the TCASII which was selected to the 25 mi range gave a 'traffic' warning. I switched to the 10 mi range to get a better picture of the approaching target and saw that we had a relative altitude difference of only 100 ft. At a closure rate I would estimate was in excess of 900 KTS per hour, the TA immediately turned into an RA, indicating a climb was necessary to miss the oncoming aircraft. Since we were in the clear on a beautiful, almost cloudless day and the TCASII did not indicate that any other aircraft were in the area, I disconnected the autoplt and started a climb of approximately 2500 FPM. Although all 3 of us were doing our best to locate the oncoming traffic visually we were unable to do so. At approximately FL320 the TCASII gave a 'monitor vertical speed' and I started to level the aircraft. I leveled the aircraft at FL325 and first officer reported to mexico center the situation and the evasive action that we were taking. As we leveled at FL325 we got a visual contact with an air carrier jet (DC9 or md-something or other, I can't tell the difference) passing below FL310 just off to our right side. I immediately started a descent back to FL310 while first officer informed mexico center of our actions and asked for an explanation. We were immediately switched to mazatlan center when we again asked for an explanation. They said it was a center problem and asked us to contact mexico center on the previous frequency. We went back to mexico center but they didn't want to talk to us and had us immediately switch back to mazatlan center. When we returned to mazatlan center he asked us in very broken english and a round about way if we had received an 'explanation.' we said no and that was the end of it as far as mexican ATC was concerned. The climb to FL325 was quick but smooth, and neither the flight attendants nor the passenger were ever aware of our maneuver to avoid the other aircraft. It is the opinion of all 3 of us that the air carrier aircraft never deviated from his flight path or altitude. That would lead me to believe that they either had no TCASII, it wasn't working, or it wasn't turned on. We also all agreed that had the TCASII not given us the warning, we more than likely would have missed the other aircraft horizontally, but it would have been very close! I am going to file a NASA report on this incident not because I am concerned about this crew's possible error, but because I think that it is important that this incident become part of the statistical record. Callback conversation with reporter revealed the following information: reporter was disturbed and frustrated that ARTCC did not acknowledge oncoming traffic. When the traffic was reported as sighted, ARTCC quickly had them change center frequencys. When the flight crew queried the new controller, he had the reporter switch back to the old frequency, but even there, no one wanted to talk to them. Reporter stated that they were being switched back and forth because no ground controller was going to be responsible for what had happened. Flight crew is grateful for TCASII. Had they not had it, they believe they would have missed the oncoming traffic, but not by much. The other aircraft took no evasive action and probably never saw reporter's aircraft. Not all air carrier aircraft in mexico have TCASII.

Google
 

Original NASA ASRS Text

Title: A B727-200 CHANGES ALT BECAUSE OF TCASII RA. FLC THEN SEES AN ACR ACFT FLY UNDERNEATH THEM AT THE ALT THEY WERE CRUISING. ARTCC SEEMS TO HAVE MADE AN ERROR IN SEPARATION BUT DOES NOTHING TO ACKNOWLEDGE THE ERROR.

Narrative: WE DEPARTED ACA FOR LAX AS FLT YY ON APR/XX/97. WE WERE CLRED AS FILED AT AN INITIAL ALT OF FL310 (SEE ATTACHED FLT PLAN). AFTER DEP WE WERE CLRED TO FL310 WITH A RESTR TO BE ABOVE FL180 BY 50 DME FROM ACA. WE CLBED THROUGH FL180 AS WE PASSED 46 DME WNW OF ACA, AND WERE TOLD TO CONTACT MEXICO CTR PASSING ZIHUATANEJO. WE WERE LEVEL AT FL310 WHEN WE CHKED IN WITH MEXICO CTR OVER ZIHUATANEJO. THE CTLR SAID 'RADAR CONTACT, MAINTAIN FL310.' WE ACKNOWLEDGED AND PROCEEDED ALONG J1 TOWARDS MANZANILLO. ALTHOUGH WE HAD OMEGA ON BOARD, I WAS NAVING THE ACFT BY USING VORS. WHEN WE WERE 33 DME WNW OF MANZANILLO (116.8), THE TIME WAS XX30Z, THE TCASII WHICH WAS SELECTED TO THE 25 MI RANGE GAVE A 'TFC' WARNING. I SWITCHED TO THE 10 MI RANGE TO GET A BETTER PICTURE OF THE APCHING TARGET AND SAW THAT WE HAD A RELATIVE ALT DIFFERENCE OF ONLY 100 FT. AT A CLOSURE RATE I WOULD ESTIMATE WAS IN EXCESS OF 900 KTS PER HR, THE TA IMMEDIATELY TURNED INTO AN RA, INDICATING A CLB WAS NECESSARY TO MISS THE ONCOMING ACFT. SINCE WE WERE IN THE CLR ON A BEAUTIFUL, ALMOST CLOUDLESS DAY AND THE TCASII DID NOT INDICATE THAT ANY OTHER ACFT WERE IN THE AREA, I DISCONNECTED THE AUTOPLT AND STARTED A CLB OF APPROX 2500 FPM. ALTHOUGH ALL 3 OF US WERE DOING OUR BEST TO LOCATE THE ONCOMING TFC VISUALLY WE WERE UNABLE TO DO SO. AT APPROX FL320 THE TCASII GAVE A 'MONITOR VERT SPD' AND I STARTED TO LEVEL THE ACFT. I LEVELED THE ACFT AT FL325 AND FO RPTED TO MEXICO CTR THE SIT AND THE EVASIVE ACTION THAT WE WERE TAKING. AS WE LEVELED AT FL325 WE GOT A VISUAL CONTACT WITH AN ACR JET (DC9 OR MD-SOMETHING OR OTHER, I CAN'T TELL THE DIFFERENCE) PASSING BELOW FL310 JUST OFF TO OUR R SIDE. I IMMEDIATELY STARTED A DSCNT BACK TO FL310 WHILE FO INFORMED MEXICO CTR OF OUR ACTIONS AND ASKED FOR AN EXPLANATION. WE WERE IMMEDIATELY SWITCHED TO MAZATLAN CTR WHEN WE AGAIN ASKED FOR AN EXPLANATION. THEY SAID IT WAS A CTR PROB AND ASKED US TO CONTACT MEXICO CTR ON THE PREVIOUS FREQ. WE WENT BACK TO MEXICO CTR BUT THEY DIDN'T WANT TO TALK TO US AND HAD US IMMEDIATELY SWITCH BACK TO MAZATLAN CTR. WHEN WE RETURNED TO MAZATLAN CTR HE ASKED US IN VERY BROKEN ENGLISH AND A ROUND ABOUT WAY IF WE HAD RECEIVED AN 'EXPLANATION.' WE SAID NO AND THAT WAS THE END OF IT AS FAR AS MEXICAN ATC WAS CONCERNED. THE CLB TO FL325 WAS QUICK BUT SMOOTH, AND NEITHER THE FLT ATTENDANTS NOR THE PAX WERE EVER AWARE OF OUR MANEUVER TO AVOID THE OTHER ACFT. IT IS THE OPINION OF ALL 3 OF US THAT THE ACR ACFT NEVER DEVIATED FROM HIS FLT PATH OR ALT. THAT WOULD LEAD ME TO BELIEVE THAT THEY EITHER HAD NO TCASII, IT WASN'T WORKING, OR IT WASN'T TURNED ON. WE ALSO ALL AGREED THAT HAD THE TCASII NOT GIVEN US THE WARNING, WE MORE THAN LIKELY WOULD HAVE MISSED THE OTHER ACFT HORIZLY, BUT IT WOULD HAVE BEEN VERY CLOSE! I AM GOING TO FILE A NASA RPT ON THIS INCIDENT NOT BECAUSE I AM CONCERNED ABOUT THIS CREW'S POSSIBLE ERROR, BUT BECAUSE I THINK THAT IT IS IMPORTANT THAT THIS INCIDENT BECOME PART OF THE STATISTICAL RECORD. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR WAS DISTURBED AND FRUSTRATED THAT ARTCC DID NOT ACKNOWLEDGE ONCOMING TFC. WHEN THE TFC WAS RPTED AS SIGHTED, ARTCC QUICKLY HAD THEM CHANGE CTR FREQS. WHEN THE FLC QUERIED THE NEW CTLR, HE HAD THE RPTR SWITCH BACK TO THE OLD FREQ, BUT EVEN THERE, NO ONE WANTED TO TALK TO THEM. RPTR STATED THAT THEY WERE BEING SWITCHED BACK AND FORTH BECAUSE NO GND CTLR WAS GOING TO BE RESPONSIBLE FOR WHAT HAD HAPPENED. FLC IS GRATEFUL FOR TCASII. HAD THEY NOT HAD IT, THEY BELIEVE THEY WOULD HAVE MISSED THE ONCOMING TFC, BUT NOT BY MUCH. THE OTHER ACFT TOOK NO EVASIVE ACTION AND PROBABLY NEVER SAW RPTR'S ACFT. NOT ALL ACR ACFT IN MEXICO HAVE TCASII.

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.