Narrative:

Aircraft X was VFR orbiting over mko when I took over the sector. The previous controller advised me aircraft X would be looking for an IFR clearance back to pwa at some point. When aircraft X was finished with the orbit over mko they requested to return to pwa VFR at 10;500. I instructed aircraft X to maintain VFR and eram [en route automation modernization] initiated an auto handoff as the aircraft neared tul approach airspace. I noticed fail flashing in the 3rd line and pointed aircraft X out to tul approach on the 5 line. As aircraft X approached stillwater low (K62); I initiated a handoff using 'K'. Fail flashed in the third line again and I initiated a directed handoff to 'K62'. As the aircraft neared the ZKC/ZFW boundary I observed the cid of the aircraft change and an right appear in the data block and proceded to transfer communications to swo low. Approximately 10 minutes later swo low called me on the 51 line and requested I initiate a flash to okc approach. I informed the controller that I did not have track control of the aircraft. The ZKC controller advised me they did not have track control or radar identification of the aircraft and that it just showed up on their frequency. I was unable to manually take track control of the aircraft via /ok or trk /ok and K62 performed the coordination needed with okc approach. I'm not sure what happened within eram that caused aircraft X to show as being under another sectors control when neither sector had control of the aircraft but the consequences could be serious if an IFR aircraft enters another controllers airspace without coordination. Eram should be looked at to understand how this automation failure occurred and correct any bugs or mis-configurations that caused it.

Related reports:

Google
 

Original NASA ASRS Text

Title: Fort Worth Center Controller reported a problem with En Route Automation Modernization and an airspace violation relating to the problem.

Narrative: Aircraft X was VFR orbiting over MKO when I took over the sector. The previous controller advised me Aircraft X would be looking for an IFR clearance back to PWA at some point. When Aircraft X was finished with the orbit over MKO they requested to return to PWA VFR at 10;500. I instructed Aircraft X to maintain VFR and ERAM [En Route Automation Modernization] initiated an auto handoff as the aircraft neared TUL APCH airspace. I noticed FAIL flashing in the 3rd line and pointed Aircraft X out to TUL APCH on the 5 line. As Aircraft X approached Stillwater Low (K62); I initiated a handoff using 'K'. FAIL flashed in the third line again and I initiated a directed handoff to 'K62'. As the aircraft neared the ZKC/ZFW boundary I observed the CID of the aircraft change and an R appear in the data block and proceded to transfer communications to SWO Low. Approximately 10 minutes later SWO Low called me on the 51 line and requested I initiate a flash to OKC approach. I informed the controller that I did not have track control of the aircraft. The ZKC controller advised me they did not have track control or radar identification of the aircraft and that it just showed up on their frequency. I was unable to manually take track control of the aircraft via /ok or trk /ok and K62 performed the coordination needed with OKC Approach. I'm not sure what happened within ERAM that caused Aircraft X to show as being under another sectors control when neither sector had control of the aircraft but the consequences could be serious if an IFR aircraft enters another controllers airspace without coordination. ERAM should be looked at to understand how this automation failure occurred and correct any bugs or mis-configurations that caused it.

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.