Air carrier has TCASII RA. Knows traffic climbing to 1000 ft below. Responds to TCASII RA with climb...

Attributes
ACN	208273
Time
Date	199204
Day	Thu
Local Time Of Day	0601 To 1200
Place
Locale Reference	atc facility : cle
State Reference	OH
Altitude	msl bound lower : 7000 msl bound upper : 7500
Environment
Flight Conditions	IMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : cle
Operator	common carrier : air carrier
Make Model Name	Medium Large Transport, Low Wing, 2 Turbojet Eng
Flight Phase	descent : approach
Route In Use	enroute : on vectors
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 150 flight time total : 17000 flight time type : 12000
ASRS Report	208273
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp
Events
Anomaly	altitude deviation : excursion from assigned altitude non adherence : clearance 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
Supplementary
Primary Problem	Flight Crew Human Performance
Air Traffic Incident	Pilot Deviation

Narrative:

On approach to cle level 7000 ft MSL we were told by RAPCON about an aircraft being vectored below us in climb to 6000 ft. In clouds and with forward visibility less than 1 mi to near 0. Our TCASII unit generated an RA climb. As per our company policy we responded with a prompt and affirmative climb until 'clear of conflict' by TCASII. Maximum deviation in altitude to 7500 ft. After 'clear of conflict' we returned immediately to 7000 ft. Notified ATC was asked to call cle approach on ground. Per that conversation 'there was no loss of separation' and the controller was 'surprised' by our action. Our manuals require this response. This flight crew acted appropriately 'by the book.' I see 2 possible solutions to this kind of incident. Vectors ahead of or behind oncoming traffic will possibly reduce TCASII conflict. Particularly where aircraft with automated climb profiles do not slow their climb/descent rates early enough. Pilots need to conscientiously control climb descent rates that last 1000 ft to 500 FPM.

Original NASA ASRS Text

Title: ACR HAS TCASII RA. KNOWS TFC CLBING TO 1000 FT BELOW. RESPONDS TO TCASII RA WITH CLB.

Narrative: ON APCH TO CLE LEVEL 7000 FT MSL WE WERE TOLD BY RAPCON ABOUT AN ACFT BEING VECTORED BELOW US IN CLB TO 6000 FT. IN CLOUDS AND WITH FORWARD VISIBILITY LESS THAN 1 MI TO NEAR 0. OUR TCASII UNIT GENERATED AN RA CLB. AS PER OUR COMPANY POLICY WE RESPONDED WITH A PROMPT AND AFFIRMATIVE CLB UNTIL 'CLR OF CONFLICT' BY TCASII. MAX DEV IN ALT TO 7500 FT. AFTER 'CLR OF CONFLICT' WE RETURNED IMMEDIATELY TO 7000 FT. NOTIFIED ATC WAS ASKED TO CALL CLE APCH ON GND. PER THAT CONVERSATION 'THERE WAS NO LOSS OF SEPARATION' AND THE CTLR WAS 'SURPRISED' BY OUR ACTION. OUR MANUALS REQUIRE THIS RESPONSE. THIS FLC ACTED APPROPRIATELY 'BY THE BOOK.' I SEE 2 POSSIBLE SOLUTIONS TO THIS KIND OF INCIDENT. VECTORS AHEAD OF OR BEHIND ONCOMING TFC WILL POSSIBLY REDUCE TCASII CONFLICT. PARTICULARLY WHERE ACFT WITH AUTOMATED CLB PROFILES DO NOT SLOW THEIR CLB/DSCNT RATES EARLY ENOUGH. PLTS NEED TO CONSCIENTIOUSLY CTL CLB DSCNT RATES THAT LAST 1000 FT TO 500 FPM.

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.