ZJX center controller reported the data tags for two aircraft with similar callsigns acquired on the...

Attributes
ACN	1744044
Time
Date	202005
Local Time Of Day	1201-1800
Place
Locale Reference	ZJX.ARTCC
State Reference	FL
Aircraft 1
Make Model Name	Medium Transport
Operating Under FAR Part	Part 91
Flight Phase	Climb
Route In Use	Vectors
Flight Plan	IFR
Aircraft 2
Make Model Name	Medium Transport
Operating Under FAR Part	Part 91
Flight Phase	Initial Climb
Route In Use	Vectors
Flight Plan	IFR
Person 1
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 9
Events
Anomaly	ATC Issue All Types Deviation - Procedural Published Material / Policy

Narrative:

The event requires more research. Aircraft X was handed off at the last minute to me. The data block tagged up correctly and I took the radar handoff and issued heading a 360 heading to stay clear of my arrivals. Aircraft X checked in on heading 360 climbing to 20;000 feet as instructed. TRACON called to handoff on aircraft Y and I informed them I see him; but had no data block on the aircraft. We often have automation problems. I instructed TRACON to put the aircraft on my frequency while I attempted to identify and climb the aircraft. I had both aircraft verify their codes and ident as I tried to understand why I couldn't pick up aircraft Y. I climbed aircraft X to 26;000 feet and handed him off to with a call explaining the situation. After several minutes we determined that the aircraft were tagged incorrectly and the flight plans were incorrect. Aircraft X departed another airport and was in ZMA airspace.

Original NASA ASRS Text

Title: ZJX Center Controller reported the data tags for two aircraft with similar callsigns acquired on the wrong target and the flight plans were not accurate.

Narrative: The event requires more research. Aircraft X was handed off at the last minute to me. The data block tagged up correctly and I took the radar handoff and issued heading a 360 heading to stay clear of my arrivals. Aircraft X checked in on heading 360 climbing to 20;000 feet as instructed. TRACON called to handoff on Aircraft Y and I informed them I see him; but had no data block on the aircraft. We often have automation problems. I instructed TRACON to put the aircraft on my frequency while I attempted to identify and climb the aircraft. I had both aircraft verify their codes and ident as I tried to understand why I couldn't pick up Aircraft Y. I climbed Aircraft X to 26;000 feet and handed him off to with a call explaining the situation. After several minutes we determined that the aircraft were tagged incorrectly and the flight plans were incorrect. Aircraft X departed another airport and was in ZMA airspace.

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.

ZJX center controller reported the data tags for two aircraft with similar callsigns acquired on the wrong target and the flight plans were not accurate.