Narrative:

I was training a developmental. Aircraft X was climbed to 17;000 ft and handed off to ZNY sector 51. Sector 51 called after communications transfer and said they showed 14;000 ft for his final. We showed FL380 for his final. Later in the shift I did a sprint and saw that the trainee entered 14;000 ft hard; then FL380. I then went through the strips and found a utm message on the altitude change. I was briefed late that there is a problem with too many utms and its effects on hand offs. They changed the time it prints from 5 minutes down to 2. There was no yellow 'U' in uret; indicting a utm. I believe this may be due to the band aid they put in place for the utm. The host should be fixed so that if you get a utm you can't do an automated hand off.

Google
 

Original NASA ASRS Text

Title: ZBW Controller described a wrong altitude transfer of information to an adjacent sector noting a post review of the event revealed HOST vs. URET anomalies.

Narrative: I was training a developmental. Aircraft X was climbed to 17;000 FT and handed off to ZNY Sector 51. Sector 51 called after communications transfer and said they showed 14;000 FT for his final. We showed FL380 for his final. Later in the shift I did a sprint and saw that the trainee entered 14;000 FT hard; then FL380. I then went through the strips and found a UTM message on the altitude change. I was briefed late that there is a problem with too many UTMs and its effects on hand offs. They changed the time it prints from 5 minutes down to 2. There was no yellow 'U' in URET; indicting a UTM. I believe this may be due to the band aid they put in place for the UTM. The host should be fixed so that if you get a UTM you can't do an automated hand off.

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.