ZMA controller describes situation where another controller passes him flight information but passes...

Attributes
ACN	1189431
Time
Date	201407
Local Time Of Day	0001-0600
Place
Locale Reference	ZMA.ARTCC
State Reference	FL
Environment
Light	Night
Aircraft 1
Make Model Name	Widebody Low Wing 2 Turbojet Eng
Operating Under FAR Part	Part 121
Flight Phase	Cruise
Flight Plan	IFR
Aircraft 2
Make Model Name	Large Transport Low Wing 2 Turbojet Eng
Operating Under FAR Part	Part 121
Flight Phase	Cruise
Flight Plan	IFR
Person 1
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 6
Events
Anomaly	ATC Issue All Types Airspace Violation All Types Deviation - Procedural Published Material / Policy Deviation - Procedural Clearance

Narrative:

I was working the cigar sector when I noticed an incomplete data block flashing at me from ZJX. ZJX called me and inquired if aircraft X was flashing at the correct sector. I told them that he was but I had limited flight plan information on the flight. I only had a call sign; altitude; and code. This has been a continuing problem that has been occurring with ZJX between their host system and our eram system. Occasionally the flight information will not pass properly and manual coordination must be completed. Apparently when the ZJX controller passed the flight plan information he inadvertently passed info on aircraft Y; going to mia instead of aircraft X going to mia. I did not recognize the wrong call sign in the coordination and as a result; I input the wrong type in the flight plan that I entered going to mia approach resulting in a deviation.fix eram!!! The 'temporary workaround' of manually coordinating flights that do not pass with the ZJX host/ZMA eram compatibility errors were the contributing factor in this deviation.

Original NASA ASRS Text

Title: ZMA Controller describes situation where another controller passes him flight information but passes the wrong aircraft call sign which leads to an airspace deviation. Problem may be associated with ERAM at ZMA and Host at ZJX.

Narrative: I was working the CIGAR Sector when I noticed an incomplete data block flashing at me from ZJX. ZJX called me and inquired if Aircraft X was flashing at the correct sector. I told them that he was but I had limited flight plan information on the flight. I only had a call sign; altitude; and code. This has been a continuing problem that has been occurring with ZJX between their HOST system and our ERAM system. Occasionally the flight information will not pass properly and manual coordination must be completed. Apparently when the ZJX Controller passed the flight plan information he inadvertently passed info on Aircraft Y; going to MIA instead of Aircraft X going to MIA. I did not recognize the wrong call sign in the coordination and as a result; I input the wrong type in the flight plan that I entered going to MIA approach resulting in a deviation.FIX ERAM!!! The 'temporary workaround' of manually coordinating flights that do not pass with the ZJX HOST/ZMA ERAM compatibility errors were the contributing factor in this deviation.

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.

ZMA controller describes situation where another controller passes him flight information but passes the wrong aircraft call sign which leads to an airspace deviation. Problem may be associated with eram at ZMA and host at ZJX.