TCASII RA creates an altitude deviation altitude undershot overshot by PIC.

Attributes
ACN	193677
Time
Date	199111
Day	Wed
Local Time Of Day	1801 To 2400
Place
Locale Reference	atc facility : buj
State Reference	TX
Altitude	msl bound lower : 5500 msl bound upper : 5500
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : dfw
Operator	common carrier : air carrier
Make Model Name	Medium Large Transport, Low Wing, 2 Turbojet Eng
Navigation In Use	Other Other
Flight Phase	descent other
Route In Use	arrival other arrival star : star enroute : on vectors
Flight Plan	IFR
Aircraft 2
Make Model Name	Any Unknown or Unlisted Aircraft Manufacturer
Flight Plan	VFR
Person 1
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : atp pilot : instrument pilot : commercial pilot : flight engineer
Experience	flight time last 90 days : 220 flight time total : 9000
ASRS Report	193677
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 170 flight time total : 12000
ASRS Report	193682
Events
Anomaly	non adherence : clearance other anomaly other
Independent Detector	aircraft equipment other aircraft equipment : unspecified other controllera
Resolutory Action	flight crew : took evasive action
Consequence	faa : reviewed incident with flight crew
Miss Distance	vertical : 100
Supplementary
Primary Problem	Aircraft
Air Traffic Incident	Pilot Deviation other

Narrative:

A target popped up on the TCASII screen. We got the TA followed by about 2 seconds later by an RA. ATC was trying to issue instructions, but the warning voice from TCASII was so loud we could not hear the controller. We told the controller to stand by because we were reacting to a TCASII TA/RA. This is in direct compliance with our operating manual. After the incident, the controller made the comment that we should review our procedure for we should have reacted to his instructions and not the RA command of our TCASII. This would be in direct conflict with our operating manual. It is my opinion that controllers should be instructed on TCASII as to how and why it works and the pilot's responsibility to its commands. Also the aural warning on our aircraft is too loud. As in this case we could not hear the controller even though we had headsets on.

Original NASA ASRS Text

Title: TCASII RA CREATES AN ALTDEV ALT UNDERSHOT OVERSHOT BY PIC.

Narrative: A TARGET POPPED UP ON THE TCASII SCREEN. WE GOT THE TA FOLLOWED BY ABOUT 2 SECONDS LATER BY AN RA. ATC WAS TRYING TO ISSUE INSTRUCTIONS, BUT THE WARNING VOICE FROM TCASII WAS SO LOUD WE COULD NOT HEAR THE CTLR. WE TOLD THE CTLR TO STAND BY BECAUSE WE WERE REACTING TO A TCASII TA/RA. THIS IS IN DIRECT COMPLIANCE WITH OUR OPERATING MANUAL. AFTER THE INCIDENT, THE CTLR MADE THE COMMENT THAT WE SHOULD REVIEW OUR PROC FOR WE SHOULD HAVE REACTED TO HIS INSTRUCTIONS AND NOT THE RA COMMAND OF OUR TCASII. THIS WOULD BE IN DIRECT CONFLICT WITH OUR OPERATING MANUAL. IT IS MY OPINION THAT CTLRS SHOULD BE INSTRUCTED ON TCASII AS TO HOW AND WHY IT WORKS AND THE PLT'S RESPONSIBILITY TO ITS COMMANDS. ALSO THE AURAL WARNING ON OUR ACFT IS TOO LOUD. AS IN THIS CASE WE COULD NOT HEAR THE CTLR EVEN THOUGH WE HAD HEADSETS ON.

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.