Mem radar controller expresses frustration regarding military call signs.

Attributes
ACN	580783
Time
Date	200304
Day	Thu
Local Time Of Day	1201 To 1800
Place
Locale Reference	airport : mem.airport
State Reference	TN
Altitude	msl single value : 10000
Environment
Flight Conditions	Mixed
Light	Daylight
Aircraft 1
Controlling Facilities	tracon : mem.tracon
Operator	other
Make Model Name	MD-80 Series (DC-9-80) Undifferentiated or Other Model
Operating Under FAR Part	Part 91
Flight Phase	descent : approach
Route In Use	arrival star : mem
Flight Plan	IFR
Aircraft 2
Controlling Facilities	tracon : mem.tracon
Operator	general aviation : corporate
Make Model Name	Citation II S2/Bravo
Operating Under FAR Part	Part 91
Route In Use	arrival star : mem
Flight Plan	IFR
Person 1
Affiliation	government : faa
Function	controller : approach
Qualification	controller : radar pilot : instrument
Experience	controller limited radar : 10 controller non radar : 10 controller radar : 20 controller supervisory : 3 controller time certified in position1 : 23 flight time total : 3500
ASRS Report	580783
Person 2
Affiliation	government : military
Function	flight crew : single pilot
Events
Anomaly	other anomaly other
Independent Detector	other controllera
Resolutory Action	none taken : anomaly accepted
Consequence	faa : reviewed incident with flight crew
Supplementary
Problem Areas	ATC Human Performance Company Flight Crew Human Performance
Primary Problem	ATC Human Performance

Narrative:

An FA18 was inbound on mem STAR level 10000 ft and rapidly overtook a C550 on the arrival, level at 10000 ft. What created the situation was a very confusing call sign on the FA18. I was working combined arrival sectors and by the time I became aware of the overtake, immediate action was required. I did not understand the tactical call sign of the FA18 on initial contact. After numerous calls to the FA18, without response, and then giving the C550 evasive vectors, the FA18 finally asked if I was calling 'FA18.' this very confusing call sign nearly resulted in a tragic situation. Military call signs should be obvious especially when certain letters are used as part of that call sign.

Original NASA ASRS Text

Title: MEM RADAR CTLR EXPRESSES FRUSTRATION REGARDING MIL CALL SIGNS.

Narrative: AN FA18 WAS INBOUND ON MEM STAR LEVEL 10000 FT AND RAPIDLY OVERTOOK A C550 ON THE ARR, LEVEL AT 10000 FT. WHAT CREATED THE SIT WAS A VERY CONFUSING CALL SIGN ON THE FA18. I WAS WORKING COMBINED ARR SECTORS AND BY THE TIME I BECAME AWARE OF THE OVERTAKE, IMMEDIATE ACTION WAS REQUIRED. I DID NOT UNDERSTAND THE TACTICAL CALL SIGN OF THE FA18 ON INITIAL CONTACT. AFTER NUMEROUS CALLS TO THE FA18, WITHOUT RESPONSE, AND THEN GIVING THE C550 EVASIVE VECTORS, THE FA18 FINALLY ASKED IF I WAS CALLING 'FA18.' THIS VERY CONFUSING CALL SIGN NEARLY RESULTED IN A TRAGIC SIT. MIL CALL SIGNS SHOULD BE OBVIOUS ESPECIALLY WHEN CERTAIN LETTERS ARE USED AS PART OF THAT CALL SIGN.

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.