2 MD88's in class a airspace had a coordination TCASII RA.

Attributes
ACN	421110
Time
Date	199811
Day	Sun
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : gso
State Reference	SC
Altitude	msl bound lower : 26000 msl bound upper : 26400
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	MD-88
Navigation In Use	Other
Flight Phase	cruise other
Flight Plan	IFR
Aircraft 2
Operator	common carrier : air carrier
Make Model Name	MD-88
Navigation In Use	Other
Flight Phase	climbout : intermediate altitude
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : commercial pilot : flight engineer pilot : instrument
Experience	flight time total : 12000 flight time type : 1708
ASRS Report	421110
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial
Events
Anomaly	conflict : airborne less severe other anomaly other
Independent Detector	aircraft equipment other aircraft equipment : unspecified other flight crewa
Resolutory Action	flight crew : took evasive action other
Consequence	Other
Miss Distance	horizontal : 18000 vertical : 1000
Supplementary
Air Traffic Incident	other

Narrative:

I was the captain on flight abc nov/xa/98. The first officer was flying the aircraft. At XA15Z we received a TA on the TCASII (scope on 20 NM below) at 9 O'clock position and 1500 ft below with a climb arrow and approximately 6 mi away (traffic going west). It turned into an RA with command to 'climb.' it was clear but I could not get a visual on the conflict. I told the first officer to start a slow climb from FL260. At the same time, I notified ATC that we had an RA and were climbing. I was still looking for the traffic and finally spotted him at 8 O'clock position and instructed first officer to go back to FL260. Maximum altitude deviation was 400 ft to FL264. ATC stated that the RA would have to be recorded. At the same time the conflict aircraft said he also got an RA. The RA stayed red until target was at our 6 O'clock position. Since I did not have visual on aircraft when RA arose, I had to deviate until I could get a visual on the conflicting traffic.

Original NASA ASRS Text

Title: 2 MD88'S IN CLASS A AIRSPACE HAD A COORD TCASII RA.

Narrative: I WAS THE CAPT ON FLT ABC NOV/XA/98. THE FO WAS FLYING THE ACFT. AT XA15Z WE RECEIVED A TA ON THE TCASII (SCOPE ON 20 NM BELOW) AT 9 O'CLOCK POS AND 1500 FT BELOW WITH A CLB ARROW AND APPROX 6 MI AWAY (TFC GOING W). IT TURNED INTO AN RA WITH COMMAND TO 'CLB.' IT WAS CLR BUT I COULD NOT GET A VISUAL ON THE CONFLICT. I TOLD THE FO TO START A SLOW CLB FROM FL260. AT THE SAME TIME, I NOTIFIED ATC THAT WE HAD AN RA AND WERE CLBING. I WAS STILL LOOKING FOR THE TFC AND FINALLY SPOTTED HIM AT 8 O'CLOCK POS AND INSTRUCTED FO TO GO BACK TO FL260. MAX ALTDEV WAS 400 FT TO FL264. ATC STATED THAT THE RA WOULD HAVE TO BE RECORDED. AT THE SAME TIME THE CONFLICT ACFT SAID HE ALSO GOT AN RA. THE RA STAYED RED UNTIL TARGET WAS AT OUR 6 O'CLOCK POS. SINCE I DID NOT HAVE VISUAL ON ACFT WHEN RA AROSE, I HAD TO DEVIATE UNTIL I COULD GET A VISUAL ON THE CONFLICTING TFC.

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.