Narrative:

At approximately XA30Z in dark clear conditions; just prior to the intersection of our airway; UL795; in curacao airspace; the TCAS sounded a 'traffic; traffic' alert. The traffic on the display was converging from our right at our altitude. I spotted the aircraft lights and judged his path to be a constant bearing; decreasing range. The TCAS a few seconds later sounded a 'climb; climb' warning. The captain smoothly responded to the TCAS commands. The other aircraft passed under us with approximately 1500 ft vertical separation; 1/4 mi laterally. We returned to FL330 after clear and contacted curacao. Prior to entering curacao airspace we were in kingston airspace between gelog and dibok for 20 mins. Just past the middle of this leg we received clearance and climbed to FL330. We made repeated attempts to contact curacao control; all no joy until after the RA; as was the case I believe for the other aircraft. The curacao controller stated that she thought we were at FL310. We coordination to remain at FL330. We made 123.45 contact with the other aircraft and learned they were flying at their assigned altitude. We then contacted dispatch. Supplemental information from acn 733837: aircraft was passing from kingston airspace to curacao airspace at FL330 in clear; night conditions. Near the intersection of ul-395 and A-319 (approximately 75 NM south of dibok) we received a TCAS alert. Once the TA changed to an RA; we climbed and the other aircraft descended. The closest point of approach was .25 NM horizontal and 1000-1500 ft vertically. Both aircraft told curacao ATC near miss reports would be filed. Our dispatcher was quickly notified on satcom; no injuries were incurred.

Google
 

Original NASA ASRS Text

Title: A B767 IN CURACAO AIRSPACE HAD A TCAS RA WITH ANOTHER ACFT; BOTH ASSIGNED TO FL330. ATC DID NOT RESPOND TO PREVIOUS CALLS FROM EITHER ACFT.

Narrative: AT APPROX XA30Z IN DARK CLR CONDITIONS; JUST PRIOR TO THE INTXN OF OUR AIRWAY; UL795; IN CURACAO AIRSPACE; THE TCAS SOUNDED A 'TFC; TFC' ALERT. THE TFC ON THE DISPLAY WAS CONVERGING FROM OUR R AT OUR ALT. I SPOTTED THE ACFT LIGHTS AND JUDGED HIS PATH TO BE A CONSTANT BEARING; DECREASING RANGE. THE TCAS A FEW SECONDS LATER SOUNDED A 'CLB; CLB' WARNING. THE CAPT SMOOTHLY RESPONDED TO THE TCAS COMMANDS. THE OTHER ACFT PASSED UNDER US WITH APPROX 1500 FT VERT SEPARATION; 1/4 MI LATERALLY. WE RETURNED TO FL330 AFTER CLR AND CONTACTED CURACAO. PRIOR TO ENTERING CURACAO AIRSPACE WE WERE IN KINGSTON AIRSPACE BTWN GELOG AND DIBOK FOR 20 MINS. JUST PAST THE MIDDLE OF THIS LEG WE RECEIVED CLRNC AND CLBED TO FL330. WE MADE REPEATED ATTEMPTS TO CONTACT CURACAO CTL; ALL NO JOY UNTIL AFTER THE RA; AS WAS THE CASE I BELIEVE FOR THE OTHER ACFT. THE CURACAO CTLR STATED THAT SHE THOUGHT WE WERE AT FL310. WE COORD TO REMAIN AT FL330. WE MADE 123.45 CONTACT WITH THE OTHER ACFT AND LEARNED THEY WERE FLYING AT THEIR ASSIGNED ALT. WE THEN CONTACTED DISPATCH. SUPPLEMENTAL INFO FROM ACN 733837: ACFT WAS PASSING FROM KINGSTON AIRSPACE TO CURACAO AIRSPACE AT FL330 IN CLR; NIGHT CONDITIONS. NEAR THE INTXN OF UL-395 AND A-319 (APPROX 75 NM S OF DIBOK) WE RECEIVED A TCAS ALERT. ONCE THE TA CHANGED TO AN RA; WE CLBED AND THE OTHER ACFT DSNDED. THE CLOSEST POINT OF APCH WAS .25 NM HORIZ AND 1000-1500 FT VERTICALLY. BOTH ACFT TOLD CURACAO ATC NEAR MISS RPTS WOULD BE FILED. OUR DISPATCHER WAS QUICKLY NOTIFIED ON SATCOM; NO INJURIES WERE INCURRED.

Data retrieved from NASA's ASRS site as of January 2009 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.