Air carrier descending has TCASII advisory then RA to climb.

Attributes
ACN	334032
Time
Date	199604
Day	Thu
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : rst
State Reference	MN
Altitude	msl bound lower : 28500 msl bound upper : 29000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	artcc : zmp
Operator	common carrier : air carrier
Make Model Name	DC-9 30
Operating Under FAR Part	Part 121
Flight Phase	descent other
Route In Use	enroute : direct
Flight Plan	IFR
Aircraft 2
Operator	common carrier : air carrier
Make Model Name	DC-9 Undifferentiated or Other Model
Operating Under FAR Part	Part 121
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : private pilot : instrument pilot : atp pilot : commercial
Experience	flight time last 90 days : 60 flight time total : 3300 flight time type : 35
ASRS Report	334032
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	other anomaly other
Independent Detector	aircraft equipment other aircraft equipment : unspecified
Resolutory Action	flight crew : took evasive action
Consequence	faa : reviewed incident with flight crew
Miss Distance	horizontal : 30000 vertical : 1000
Supplementary
Primary Problem	Aircraft
Air Traffic Incident	other

Narrative:

Descending to FL280 received a TCASII TA on traffic approximately 28500 ft. ZMP advised us that traffic, air carrier Y, was 12 O'clock at 27000 ft. Saw traffic. Shortly thereafter (we were at FL285) received a climb RA. We climbed to FL290. Visually spotted traffic crossing 10 O'clock at 5 NM. Air carrier Y indicated they also received a climb RA and started climb. Captain's conversation with ZMP (on ground in rst) indicated that IFR separation was not compromised. Possible TCASII fault. Callback conversation with reporter revealed the following information: reporter states his aircraft was a DC9-30. His company requires a log write-up any time a TCASII advisory is issued. They have not had any follow-up from maintenance regarding the equipment, so unable to determine if it was their TCASII, or the other aircraft TCASII. ATC indicated they received no conflict alert and were taking no action. Reporter aircraft had been advised of traffic. Reporter believes the other aircraft was also a DC9.

Original NASA ASRS Text

Title: ACR DSNDING HAS TCASII ADVISORY THEN RA TO CLB.

Narrative: DSNDING TO FL280 RECEIVED A TCASII TA ON TFC APPROX 28500 FT. ZMP ADVISED US THAT TFC, ACR Y, WAS 12 O'CLOCK AT 27000 FT. SAW TFC. SHORTLY THEREAFTER (WE WERE AT FL285) RECEIVED A CLB RA. WE CLBED TO FL290. VISUALLY SPOTTED TFC XING 10 O'CLOCK AT 5 NM. ACR Y INDICATED THEY ALSO RECEIVED A CLB RA AND STARTED CLB. CAPT'S CONVERSATION WITH ZMP (ON GND IN RST) INDICATED THAT IFR SEPARATION WAS NOT COMPROMISED. POSSIBLE TCASII FAULT. CALLBACK CONVERSATION WITH RPTR REVEALED THE FOLLOWING INFO: RPTR STATES HIS ACFT WAS A DC9-30. HIS COMPANY REQUIRES A LOG WRITE-UP ANY TIME A TCASII ADVISORY IS ISSUED. THEY HAVE NOT HAD ANY FOLLOW-UP FROM MAINT REGARDING THE EQUIP, SO UNABLE TO DETERMINE IF IT WAS THEIR TCASII, OR THE OTHER ACFT TCASII. ATC INDICATED THEY RECEIVED NO CONFLICT ALERT AND WERE TAKING NO ACTION. RPTR ACFT HAD BEEN ADVISED OF TFC. RPTR BELIEVES THE OTHER ACFT WAS ALSO A DC9.

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.