Commuter pilot complains that the new company call sign effective sept, 1990 is causing confusion wi...

Attributes
ACN	158655
Time
Date	199009
Day	Sat
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : sfo
State Reference	CA
Altitude	agl bound lower : 0 agl bound upper : 0
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Light Transport, Low Wing, 2 Turboprop Eng
Flight Phase	other
Route In Use	approach : svfr
Person 1
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Experience	flight time last 90 days : 180 flight time total : 3200 flight time type : 500
ASRS Report	158655
Person 2
Affiliation	government : faa
Function	controller : local
Qualification	controller : non radar
Events
Anomaly	other anomaly other
Independent Detector	other flight crewa
Resolutory Action	none taken : unable
Consequence	Other
Supplementary
Primary Problem	Ambiguous
Air Traffic Incident	other

Narrative:

Starting sept, company airlines, with the encouragement and blessing of the FAA and the FCC changed its call sign. The change was necessary since air carrier Y with similar call sign operates in the same area. To avoid having two similar call signs cause confusion, our call sign was changed. On 9/sat/90, we were in position and hold on runway 1R at sfo, and air carrier Z was in position on runway 1L. The controller confused 'air carrier Z' with 'our call sign' twice. (We also had similar flight numbers ending in a 5). The tower used our call sign with air carrier Z's number, and air carrier Z's call sign with our number when he cleared us for takeoff. Both crews were alert, the instructions clarified, and we took off. This is just one of many case where our call sign is causing confusion. Our call sign sounds like 'cactus' and cessux too! I have missed calls thinking the controller said cessna. The other day at burbank, we were call sign A66 and there was also a cessna B66. I heard a 'cactus' response to a call that was for us. There are many other examples too, but I think you get the idea. Currently, is looking into the matter. Why the FAA and the FCC authority/authorized this call sign is beyond me. The confusion it would cause should have been obvious.

Original NASA ASRS Text

Title: COMMUTER PLT COMPLAINS THAT THE NEW COMPANY CALL SIGN EFFECTIVE SEPT, 1990 IS CAUSING CONFUSION WITH OTHER ACR AND GA CALL SIGNS ALREADY BEING USED.

Narrative: STARTING SEPT, COMPANY AIRLINES, WITH THE ENCOURAGEMENT AND BLESSING OF THE FAA AND THE FCC CHANGED ITS CALL SIGN. THE CHANGE WAS NECESSARY SINCE ACR Y WITH SIMILAR CALL SIGN OPERATES IN THE SAME AREA. TO AVOID HAVING TWO SIMILAR CALL SIGNS CAUSE CONFUSION, OUR CALL SIGN WAS CHANGED. ON 9/SAT/90, WE WERE IN POS AND HOLD ON RWY 1R AT SFO, AND ACR Z WAS IN POS ON RWY 1L. THE CTLR CONFUSED 'ACR Z' WITH 'OUR CALL SIGN' TWICE. (WE ALSO HAD SIMILAR FLT NUMBERS ENDING IN A 5). THE TWR USED OUR CALL SIGN WITH ACR Z'S NUMBER, AND ACR Z'S CALL SIGN WITH OUR NUMBER WHEN HE CLRED US FOR TKOF. BOTH CREWS WERE ALERT, THE INSTRUCTIONS CLARIFIED, AND WE TOOK OFF. THIS IS JUST ONE OF MANY CASE WHERE OUR CALL SIGN IS CAUSING CONFUSION. OUR CALL SIGN SOUNDS LIKE 'CACTUS' AND CESSUX TOO! I HAVE MISSED CALLS THINKING THE CTLR SAID CESSNA. THE OTHER DAY AT BURBANK, WE WERE CALL SIGN A66 AND THERE WAS ALSO A CESSNA B66. I HEARD A 'CACTUS' RESPONSE TO A CALL THAT WAS FOR US. THERE ARE MANY OTHER EXAMPLES TOO, BUT I THINK YOU GET THE IDEA. CURRENTLY, IS LOOKING INTO THE MATTER. WHY THE FAA AND THE FCC AUTH THIS CALL SIGN IS BEYOND ME. THE CONFUSION IT WOULD CAUSE SHOULD HAVE BEEN OBVIOUS.

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.

Commuter pilot complains that the new company call sign effective sept, 1990 is causing confusion with other air carrier and GA call signs already being used.