Reporter objects to volume of TCAS alert and low altitude warnings.

Attributes
ACN	171821
Time
Date	199102
Day	Tue
Local Time Of Day	0601 To 1200
Place
Locale Reference	airport : dtw
State Reference	MI
Altitude	msl bound lower : 2000 msl bound upper : 3000
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : dtw tower : sfo
Operator	common carrier : air carrier
Make Model Name	Medium Large Transport, Low Wing, 2 Turbojet Eng
Flight Phase	climbout : takeoff climbout : initial
Route In Use	departure other
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : commercial pilot : atp pilot : cfi pilot : flight engineer pilot : instrument
Experience	flight time last 90 days : 200 flight time total : 11000 flight time type : 200
ASRS Report	171821
Person 2
Affiliation	company : air carrier
Function	flight crew : first officer
Qualification	pilot : commercial pilot : atp pilot : instrument
Events
Anomaly	aircraft equipment problem : less severe other anomaly other
Independent Detector	other flight crewa
Resolutory Action	flight crew : overcame equipment problem
Consequence	Other
Supplementary
Primary Problem	Aircraft
Air Traffic Incident	other

Narrative:

I've been flying aircraft with the TCAS system installed for a couple of months now. On this particular takeoff, the system triggered an aircraft departing from an adjacent airport (approximately 3-5 mi) that were in no way a threat. First of all, during a critical phase of flight (takeoff), we do not need a tremendous distraction screaming, 'traffic-traffic!!' at an unreasonably loud level. With a climb rate of 4000 FPM and a quick level off after takeoff of 3000', we nearly busted the altitude as the TCAS alarmed us at an excessive vol. This is so distracting that it takes several precious seconds to synthesize the clutter on the display, which could lead to other serious problems while trying to fly an approach or departure. There is a 2-FOLD problem: 1) the warning is ridiculously loud. Why should this be louder than a fire warning, an engine overheat or the altimeter which makes on sound. 2) the traffic information on takeoff and departure, at critical times when you're close to the ground, clutters the display too much. I'm afraid the numerous false alarms, worse yet, the verbal distraction during critical phases, will cause pilots to disarm the system.

Original NASA ASRS Text

Title: REPORTER OBJECTS TO VOLUME OF TCAS ALERT AND LOW ALT WARNINGS.

Narrative: I'VE BEEN FLYING ACFT WITH THE TCAS SYS INSTALLED FOR A COUPLE OF MONTHS NOW. ON THIS PARTICULAR TKOF, THE SYS TRIGGERED AN ACFT DEPARTING FROM AN ADJACENT ARPT (APPROX 3-5 MI) THAT WERE IN NO WAY A THREAT. FIRST OF ALL, DURING A CRITICAL PHASE OF FLT (TKOF), WE DO NOT NEED A TREMENDOUS DISTR SCREAMING, 'TFC-TFC!!' AT AN UNREASONABLY LOUD LEVEL. WITH A CLB RATE OF 4000 FPM AND A QUICK LEVEL OFF AFTER TKOF OF 3000', WE NEARLY BUSTED THE ALT AS THE TCAS ALARMED US AT AN EXCESSIVE VOL. THIS IS SO DISTRACTING THAT IT TAKES SEVERAL PRECIOUS SECS TO SYNTHESIZE THE CLUTTER ON THE DISPLAY, WHICH COULD LEAD TO OTHER SERIOUS PROBS WHILE TRYING TO FLY AN APCH OR DEP. THERE IS A 2-FOLD PROB: 1) THE WARNING IS RIDICULOUSLY LOUD. WHY SHOULD THIS BE LOUDER THAN A FIRE WARNING, AN ENG OVERHEAT OR THE ALTIMETER WHICH MAKES ON SOUND. 2) THE TFC INFO ON TKOF AND DEP, AT CRITICAL TIMES WHEN YOU'RE CLOSE TO THE GND, CLUTTERS THE DISPLAY TOO MUCH. I'M AFRAID THE NUMEROUS FALSE ALARMS, WORSE YET, THE VERBAL DISTR DURING CRITICAL PHASES, WILL CAUSE PLTS TO DISARM THE SYS.

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.