Narrative:

Air carrier X inbound to las and flashing from ZLC46 to ZLA32. ZLA32 is an ultra-hi sector. Air carrier X was at FL320 and should have been flashing at ZLA33. This occurs on a daily basis and has since ZLC started operating with eram. This problem has been documented thoroughly; but has not been fixed. Previous statements by agency officials and contractors indicated that the problem would be fixed. Despite these occurrences; and numerous others that have a direct impact on the safety of the national airspace system (NAS); the agency continues to require ZLC to operate with eram. While I was collecting eram problem reports from the area impacted by eram at ZLC; a controller related to me an incident that speaks volumes on how dangerous our current operations are. He stated that he was working at sector 32 earlier in the day and had mistakenly taken a hand off on a las arrival at FL320 that was flashing on his scope instead of sector 33. By the time he realized his error; the ZLC46 controller had shipped the aircraft to sector 33 without a hand off. This is a disaster waiting to happen and needs to be addressed! On a related; yet somehow unrelated note; I read with great interest last week how the agency is embracing saftey management system (sms) and will conduct sms reviews on all equipment; procedures; and practices prior to their introduction into the NAS. Approximately one month ago; I had requested a copy of the sms conducted for eram implementation at ZLA; and to date; have seen nothing. Recommendation; turn off eram at ZLC and fix the critcal and high problems reported by the controllers at ZLC.

Related reports:

Google
 

Original NASA ASRS Text

Title: ZLA Controller expressed concern regarding ERAM's performance; describing personnel and related ERAM anomalies; noting that ERAM should be turned off until critical problems are fixed.

Narrative: Air Carrier X inbound to LAS and flashing from ZLC46 to ZLA32. ZLA32 is an ultra-hi sector. Air Carrier X was at FL320 and should have been flashing at ZLA33. This occurs on a daily basis and has since ZLC started operating with ERAM. This problem has been documented thoroughly; but has not been fixed. Previous statements by agency officials and contractors indicated that the problem would be fixed. Despite these occurrences; and numerous others that have a direct impact on the safety of the National Airspace System (NAS); the agency continues to require ZLC to operate with ERAM. While I was collecting ERAM problem reports from the area impacted by ERAM at ZLC; a Controller related to me an incident that speaks volumes on how dangerous our current operations are. He stated that he was working at Sector 32 earlier in the day and had mistakenly taken a hand off on a LAS arrival at FL320 that was flashing on his scope instead of Sector 33. By the time he realized his error; the ZLC46 Controller had shipped the aircraft to Sector 33 without a hand off. This is a disaster waiting to happen and needs to be addressed! On a related; yet somehow unrelated note; I read with great interest last week how the agency is embracing Saftey Management System (SMS) and will conduct SMS reviews on all equipment; procedures; and practices prior to their introduction into the NAS. Approximately one month ago; I had requested a copy of the SMS conducted for ERAM implementation at ZLA; and to date; have seen nothing. Recommendation; turn off ERAM at ZLC and fix the critcal and high problems reported by the controllers at ZLC.

Data retrieved from NASA's ASRS site as of April 2012 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.