Air carrier at cruise after departure responds to TCAS ii RA, climb, climb.

Attributes
ACN	173686
Time
Date	199103
Day	Tue
Local Time Of Day	1201 To 1800
Place
Locale Reference	atc facility : tpa
State Reference	FL
Altitude	msl bound lower : 1600 msl bound upper : 2000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : tpa tower : cak
Operator	common carrier : air carrier
Make Model Name	Medium Transport
Flight Phase	cruise other
Flight Plan	IFR
Aircraft 2
Make Model Name	Small Aircraft
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 250 flight time total : 10500 flight time type : 2800
ASRS Report	173686
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : atp pilot : instrument
Events
Anomaly	altitude deviation : overshoot conflict : airborne less severe non adherence : clearance other anomaly other
Independent Detector	other flight crewa
Resolutory Action	flight crew : returned to intended course or assigned course
Consequence	faa : reviewed incident with flight crew Other
Miss Distance	horizontal : 1500 vertical : 600
Supplementary
Air Traffic Incident	Pilot Deviation

Narrative:

Shortly after takeoff out of tpa international, heading 310 at xx:12 hours; we got a strong climb-climb from our TCAS. We were going against the setting sun under hazy conditions so we could not visly southeast the the traffic. I told the first officer to climb and we leveled off at 2000' as we saw the traffic, a single engine, crossing from left to right approximately 600' below us. I immediately notified departure controller that we had done a TCAS climb. He came back in a very belligerent and threatening tone saying that he would report it as an altitude violation and that I would be receiving a letter through the mail. This rubbed me the wrong way to say the least. I do not need to be threatened over the radio with the whole world listening, especially for doing what I am supposed to be doing. If this is their policy, fine, but it was conveyed in a very threatening and unprofessional manner by the controller. At the time, neither the tower nor departure control had advised me of any traffic ahead and below me. My TCAS had been working good all day.

Original NASA ASRS Text

Title: ACR AT CRUISE AFTER DEP RESPONDS TO TCAS II RA, CLB, CLB.

Narrative: SHORTLY AFTER TKOF OUT OF TPA INTL, HDG 310 AT XX:12 HRS; WE GOT A STRONG CLB-CLB FROM OUR TCAS. WE WERE GOING AGAINST THE SETTING SUN UNDER HAZY CONDITIONS SO WE COULD NOT VISLY SE THE THE TFC. I TOLD THE F/O TO CLB AND WE LEVELED OFF AT 2000' AS WE SAW THE TFC, A SINGLE ENG, XING FROM L TO R APPROX 600' BELOW US. I IMMEDIATELY NOTIFIED DEP CTLR THAT WE HAD DONE A TCAS CLB. HE CAME BACK IN A VERY BELLIGERENT AND THREATENING TONE SAYING THAT HE WOULD RPT IT AS AN ALT VIOLATION AND THAT I WOULD BE RECEIVING A LETTER THROUGH THE MAIL. THIS RUBBED ME THE WRONG WAY TO SAY THE LEAST. I DO NOT NEED TO BE THREATENED OVER THE RADIO WITH THE WHOLE WORLD LISTENING, ESPECIALLY FOR DOING WHAT I AM SUPPOSED TO BE DOING. IF THIS IS THEIR POLICY, FINE, BUT IT WAS CONVEYED IN A VERY THREATENING AND UNPROFESSIONAL MANNER BY THE CTLR. AT THE TIME, NEITHER THE TWR NOR DEP CTL HAD ADVISED ME OF ANY TFC AHEAD AND BELOW ME. MY TCAS HAD BEEN WORKING GOOD ALL DAY.

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.