ZTL controller describes a problem while training that causes a distraction to the controllers and a...

Narrative:

During eram implementation; second day my trainee took a hand-off on aircraft Y and asked me why 'side' was in the fourth line [of the data block]. We called the eram (en route automation modernization) sme (subject matter expert) over and he began to discuss the possible scenarios for the side in the data block. During this time; after we observed on the replay; aircraft X auto popped on the sector. No handoff was received from east departure sector (16). While trainee was working dbn hi had issues with aircraft Y and that kept my attention. I never observed aircraft X's data block going through the airspace. By the time I returned to scanning the sector; the trainee had dropped the data block because it was in ZJX sector 72's airspace with an right indicating someone other than us had the handoff. East departure radar controller calls and ask us what we wanted to do with aircraft X which made us aware of the aircraft. At that time east departure initiated the handoff and we called ZJX to ask what they required us to do with the aircraft. Aircraft that pop up may need to look different from an aircraft that is handed off already. Do not discuss issues with eram cadre during training sessions. Wait until off position.

Original NASA ASRS Text

Title: ZTL Controller describes a problem while training that causes a distraction to the Controllers and an aircraft that auto-pops on their radar. The Controller didn't observe the data block going through the airspace.

Narrative: During ERAM implementation; second day my trainee took a hand-off on Aircraft Y and asked me why 'side' was in the fourth line [of the data block]. We called the ERAM (En Route Automation Modernization) SME (Subject Matter Expert) over and he began to discuss the possible scenarios for the side in the data block. During this time; after we observed on the replay; Aircraft X auto popped on the sector. No handoff was received from East Departure Sector (16). While trainee was working DBN Hi had issues with Aircraft Y and that kept my attention. I never observed Aircraft X's data block going through the airspace. By the time I returned to scanning the sector; the trainee had dropped the data block because it was in ZJX sector 72's airspace with an R indicating someone other than us had the handoff. East Departure Radar controller calls and ask us what we wanted to do with Aircraft X which made us aware of the aircraft. At that time East Departure initiated the handoff and we called ZJX to ask what they required us to do with the aircraft. Aircraft that pop up may need to look different from an aircraft that is handed off already. Do not discuss issues with ERAM cadre during training sessions. Wait until off position.

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.

Attributes
ACN	1223132
Time
Date	201411
Local Time Of Day	1801-2400
Place
Locale Reference	ZTL.ARTCC
State Reference	GA
Environment
Light	Night
Aircraft 1
Make Model Name	Medium Transport Low Wing 2 Turbojet Eng
Operating Under FAR Part	Part 121
Flight Phase	Cruise
Flight Plan	IFR
Aircraft 2
Make Model Name	Medium Transport Low Wing 2 Turbojet Eng
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) 21
Events
Anomaly	ATC Issue All Types Airspace Violation All Types Deviation - Procedural Published Material / Policy

ZTL controller describes a problem while training that causes a distraction to the controllers and an aircraft that auto-pops on their radar. The controller didn't observe the data block going through the airspace.