Dispatcher reports air carrier assigned call sign confusion problem.

Attributes
ACN	201291
Time
Date	199201
Day	Fri
Local Time Of Day	1801 To 2400
Place
Locale Reference	airport : msp
State Reference	MN
Altitude	agl bound lower : 0 agl bound upper : 0
Aircraft 1
Operator	common carrier : air carrier
Make Model Name	Widebody, Low Wing, 3 Turbojet Eng
Flight Phase	ground : preflight
Flight Plan	IFR
Person 1
Affiliation	company : air carrier
Function	other personnel other personnel other
Qualification	other other : other
ASRS Report	201291
Person 2
Affiliation	company : air carrier
Function	flight crew : captain oversight : pic
Qualification	pilot : atp
Events
Anomaly	other anomaly other
Independent Detector	other other : unspecified
Resolutory Action	none taken : detected after the fact
Consequence	Other
Supplementary
Air Traffic Incident	other

Narrative:

Air carrier a flight clearance delivery was late departing lax for hnl. An aircraft change was planned in hnl with an on time departure. Normally, the dispatcher of the outbound flight is notified by the computer of any possible conflict involving 2 flts with the same call sign in the same airspace at the same time. The system did not work this time because our company uses a marketing flight number of air carrier a abcd to comply with FAA and jcab requirements for route authority and type of flight. The hnl-fvk segment authority is owned by air carrier B and air carrier a wet leases aircraft and crews and shares marketing for the route. Air carrier a operation specifications force our company to use the air carrier a clearance delivery call sign for marketing, and jcab requires the air carrier a abcd call sign. I relieved the dispatcher who worked both inbound and outbound segments but was not informed of a possible conflict. The flight following is done by marketing numbers so no conflict was evident. The conflict occurred shortly after I accepted the shift. I believe that this situation came about as a direct result of the practice of using different marketing and ATC flight numbers, and I fully expect that the problem will occur again if no changes are made.

Original NASA ASRS Text

Title: DISPATCHER RPTS ACR ASSIGNED CALL SIGN CONFUSION PROBLEM.

Narrative: ACR A FLT CD WAS LATE DEPARTING LAX FOR HNL. AN ACFT CHANGE WAS PLANNED IN HNL WITH AN ON TIME DEP. NORMALLY, THE DISPATCHER OF THE OUTBOUND FLT IS NOTIFIED BY THE COMPUTER OF ANY POSSIBLE CONFLICT INVOLVING 2 FLTS WITH THE SAME CALL SIGN IN THE SAME AIRSPACE AT THE SAME TIME. THE SYS DID NOT WORK THIS TIME BECAUSE OUR COMPANY USES A MARKETING FLT NUMBER OF ACR A ABCD TO COMPLY WITH FAA AND JCAB REQUIREMENTS FOR RTE AUTHORITY AND TYPE OF FLT. THE HNL-FVK SEGMENT AUTHORITY IS OWNED BY ACR B AND ACR A WET LEASES ACFT AND CREWS AND SHARES MARKETING FOR THE RTE. ACR A OP SPECS FORCE OUR COMPANY TO USE THE ACR A CD CALL SIGN FOR MARKETING, AND JCAB REQUIRES THE ACR A ABCD CALL SIGN. I RELIEVED THE DISPATCHER WHO WORKED BOTH INBOUND AND OUTBOUND SEGMENTS BUT WAS NOT INFORMED OF A POSSIBLE CONFLICT. THE FLT FOLLOWING IS DONE BY MARKETING NUMBERS SO NO CONFLICT WAS EVIDENT. THE CONFLICT OCCURRED SHORTLY AFTER I ACCEPTED THE SHIFT. I BELIEVE THAT THIS SITUATION CAME ABOUT AS A DIRECT RESULT OF THE PRACTICE OF USING DIFFERENT MARKETING AND ATC FLT NUMBERS, AND I FULLY EXPECT THAT THE PROBLEM WILL OCCUR AGAIN IF NO CHANGES ARE MADE.

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.