Air carrier on descent receives TCASII re due traffic opposite direction at their assigned altitude.

Attributes
ACN	270851
Time
Date	199405
Day	Thu
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : arg
State Reference	AR
Altitude	msl bound lower : 29000 msl bound upper : 31000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tower : msp
Operator	common carrier : air carrier
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Navigation In Use	Other Other
Flight Phase	cruise other descent other
Route In Use	enroute airway : zme
Flight Plan	IFR
Aircraft 2
Operator	common carrier : air carrier
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Flight Phase	cruise other
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 200 flight time total : 18000 flight time type : 600
ASRS Report	270851
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Events
Anomaly	altitude deviation : excursion from assigned altitude non adherence : published procedure other anomaly other
Independent Detector	aircraft equipment other aircraft equipment : unspecified other flight crewa
Resolutory Action	flight crew : took evasive action
Consequence	faa : reviewed incident with flight crew
Miss Distance	horizontal : 9000 vertical : 2000
Supplementary
Primary Problem	ATC Human Performance
Air Traffic Incident	other

Narrative:

In cruise at FL350 ZME cleared flight to descend to FL290. While descending through FL310, center requested that we expedite to FL290 and at the same time, we got a TCASII TA. At FL300 we got a TCASII RA and a 'climb' command from TCASII. There was opposite direction traffic at FL290 (visual contact also) and we climbed up to FL310. I informed ZME that we were responding to a TCASII resolution conflict and were climbing. Opposing traffic also stated that they had a TCASII warning. Resolution was cleared and we were given a frequency change. We were then cleared to a lower altitude by the new controller and the graham arrival into nashville. No comments at all from any controllers. Perhaps the original controller meant to clear my flight to FL280 or lower, but stated FL290 as the descent altitude. I know I read back FL290 as the descent altitude. Conclusion, TCASII does work.

Original NASA ASRS Text

Title: ACR ON DSCNT RECEIVES TCASII RE DUE TFC OPPOSITE DIRECTION AT THEIR ASSIGNED ALT.

Narrative: IN CRUISE AT FL350 ZME CLRED FLT TO DSND TO FL290. WHILE DSNDING THROUGH FL310, CTR REQUESTED THAT WE EXPEDITE TO FL290 AND AT THE SAME TIME, WE GOT A TCASII TA. AT FL300 WE GOT A TCASII RA AND A 'CLB' COMMAND FROM TCASII. THERE WAS OPPOSITE DIRECTION TFC AT FL290 (VISUAL CONTACT ALSO) AND WE CLBED UP TO FL310. I INFORMED ZME THAT WE WERE RESPONDING TO A TCASII RESOLUTION CONFLICT AND WERE CLBING. OPPOSING TFC ALSO STATED THAT THEY HAD A TCASII WARNING. RESOLUTION WAS CLRED AND WE WERE GIVEN A FREQ CHANGE. WE WERE THEN CLRED TO A LOWER ALT BY THE NEW CTLR AND THE GRAHAM ARR INTO NASHVILLE. NO COMMENTS AT ALL FROM ANY CTLRS. PERHAPS THE ORIGINAL CTLR MEANT TO CLR MY FLT TO FL280 OR LOWER, BUT STATED FL290 AS THE DSCNT ALT. I KNOW I READ BACK FL290 AS THE DSCNT ALT. CONCLUSION, TCASII DOES WORK.

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.