Narrative:

Aircraft X had check on to lindbergh tower's local control position and was operating in the san diego bravo airspace within 1 mile to 1 1/2 miles south of the final approach course. The position tag (south) dropped. Local controller noticed it; attempted to retag but it indicated 'dup identification'. San local control had to retag aircraft X using a different identification. When san local control check the call sign it indicated it was now being used by 2T. 2T is lax tower. Prior report was filed for the same occurrence and the practice of lax twr dropping san tags to be used by them. It is inexcusable for any controller to think it is okay to remove someone else's flight plan. Ever! I was notified by the cpc that lax was still doing this reckless behavior. Lax doing this with a carrier tag between la arrival and lax twr was the topic of a video in recurrent training. Why is it still occurring? I don't know how to be clearer. It has to stop!I recommend individual; face-to-face briefing on the proper etiquette of air traffic control. How one should not remove flight plans that do not belong to that facility! The last response from lax was that 'this conduct would no longer be condoned'. What? When would it ever be condoned? Sct originates our loas. Sct could keep a master list of all call sign usage to alleviate dual use. We have tours that operate in the san bravo. Sct san diego area has sky diving. We were both attempting to use 'sky' as an identifier when talking to our individual aircraft company's. We coordinated with each other to use different ids; but those call signs used could be on a master list to let others know it isn't available.

Related reports:

Google
 

Original NASA ASRS Text

Title: SAN Tower Front Line Manager reported of duplicate aircraft identifications in the SAN and LAX Area. Someone was attempting to use a call sign; saw that it was being used; but dropped the data tag anyways.

Narrative: Aircraft X had check on to Lindbergh tower's local control position and was operating in the San Diego Bravo airspace within 1 mile to 1 1/2 miles south of the final approach course. The position tag (S) dropped. Local controller noticed it; attempted to retag but it indicated 'dup ID'. SAN Local control had to retag Aircraft X using a different ID. When SAN LC check the call sign it indicated it was now being used by 2T. 2T is LAX Tower. Prior report was filed for the same occurrence and the practice of LAX Twr dropping SAN Tags to be used by them. It is inexcusable for any controller to think it is okay to remove someone else's flight plan. Ever! I was notified by the CPC that LAX was still doing this reckless behavior. LAX doing this with a carrier tag between LA Arrival and LAX Twr was the topic of a video in recurrent training. Why is it still occurring? I don't know how to be clearer. It has to stop!I recommend individual; face-to-face briefing on the proper etiquette of Air Traffic Control. How one should not remove flight plans that do not belong to that facility! The last response from LAX was that 'This conduct would no longer be condoned'. What? When would it ever be condoned? SCT originates our LOAs. SCT could keep a master list of all call sign usage to alleviate dual use. We have tours that operate in the SAN Bravo. SCT San Diego area has sky diving. We were both attempting to use 'SKY' as an identifier when talking to our individual aircraft company's. We coordinated with each other to use different IDs; but those call signs used could be on a master list to let others know it isn't available.

Data retrieved from NASA's ASRS site 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.