Narrative:

We were cruising wbound at FL280 direct dbq VOR when ZAU gave us a heading vector of 230 degrees for traffic. Shortly thereafter a descending target at about 1 O'clock position set off a TA, and then as he was descending through FL294, we received an RA to descend. We followed the advisory to about FL275 whereupon conflict was resolved and returned to FL280. There was probably never any real traffic conflict. I think because the opposite direction traffic was descending at a fairly high rate to FL290 it triggered the TCASII resolution software.

Google
 

Original NASA ASRS Text

Title: FLC OF A B767 DSNDED IN RESPONSE TO A TCASII RA FROM ANOTHER ACFT DSNDING FROM ABOVE.

Narrative: WE WERE CRUISING WBOUND AT FL280 DIRECT DBQ VOR WHEN ZAU GAVE US A HDG VECTOR OF 230 DEGS FOR TFC. SHORTLY THEREAFTER A DSNDING TARGET AT ABOUT 1 O'CLOCK POS SET OFF A TA, AND THEN AS HE WAS DSNDING THROUGH FL294, WE RECEIVED AN RA TO DSND. WE FOLLOWED THE ADVISORY TO ABOUT FL275 WHEREUPON CONFLICT WAS RESOLVED AND RETURNED TO FL280. THERE WAS PROBABLY NEVER ANY REAL TFC CONFLICT. I THINK BECAUSE THE OPPOSITE DIRECTION TFC WAS DSNDING AT A FAIRLY HIGH RATE TO FL290 IT TRIGGERED THE TCASII RESOLUTION SOFTWARE.

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.