ZAU controller described an unsafe situation due to the functionality of eram which is unlike prior ...

Narrative:

We were in the middle of a six day eram run. The cirrus was VFR dct..cgt..arrival at 10;500 ft; slow descent to 3;500 ft. I put the aircraft in hard at VFR/035 so the flight plan would pass to sbn approach and I could do an automated hand off. I initiated the hand off and called to coordinate the slow descent with approach. By the time I got off the phone the data block disappeared and all that was left was a limited data block with the block 'I' and a discreet code. I called sbn approach back and asked if they had removed strips. They said no. I called over the eram sme. He investigated the situation and said that someone had removed strips on the cirrus flight plan. I was still talking to the cirrus; so I didn't even have a record of his call sign and no indication that he was still on my frequency. When I typed a request for a full route and got an error message flid not stored. Luckily he was grayed out in esdt< so I quickly selected to keep the line in the esdt. The old NAS didn't allow flight plan data to get passed back to the center's computer. Apparently; eram does. So controllers need to be taught not to remove strips on aircraft they are not responsible for. If this had been an IFR aircraft the results may have been disastrous.

Original NASA ASRS Text

Title: ZAU Controller described an unsafe situation due to the functionality of ERAM which is unlike prior equipment; the reporter emphasized that controllers must not 'remove strips' for aircraft under their control.

Narrative: We were in the middle of a six day ERAM run. The Cirrus was VFR DCT..CGT..ARR at 10;500 FT; slow descent to 3;500 FT. I put the aircraft in hard at VFR/035 so the flight plan would pass to SBN APCH and I could do an automated hand off. I initiated the hand off and called to coordinate the slow descent with approach. By the time I got off the phone the data block disappeared and all that was left was a limited data block with the BLOCK 'I' and a discreet code. I called SBN Approach back and asked if they had removed strips. They said no. I called over the ERAM SME. He investigated the situation and said that someone had removed strips on the Cirrus flight plan. I was still talking to the Cirrus; so I didn't even have a record of his call sign and no indication that he was still on my frequency. When I typed a request for a full route and got an error message FLID not stored. Luckily he was grayed out in ESDT< SO I quickly selected to keep the line in the ESDT. The old NAS didn't allow FLIGHT PLAN data to get passed back to the Center's computer. Apparently; ERAM does. So controllers need to be taught not to remove strips on aircraft they are not responsible for. If this had been an IFR aircraft the results may have been disastrous.

Data retrieved from NASA's ASRS site as of July 2013 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	1036435
Time
Date	201209
Local Time Of Day	1201-1800
Place
Locale Reference	ZAU.ARTCC
State Reference	IL
Aircraft 1
Make Model Name	SR22
Operating Under FAR Part	Part 91
Flight Phase	Descent
Flight Plan	VFR
Person 1
Function	Enroute
Qualification	Air Traffic Control Fully Certified
Events
Anomaly	ATC Issue All Types

ZAU controller described an unsafe situation due to the functionality of eram which is unlike prior equipment; the reporter emphasized that controllers must not 'remove strips' for aircraft under their control.