Narrative:

I approved the point out on aircraft Y and aircraft X via the new automated point out function climbing to FL290. Then after the aircraft got to FL290 a new 'P' appeared on the data block with FL330 as the new t-ed in altitude. I did not approve the automated point out because I believe this violates the 7110; because any changes to the aircraft after the first point out was completed needs to be verbally coordinated. ZNY climbed the aircraft without coordination or approval to do so. They also turned the aircraft after I took the point out without coordination. We need to establish clear rules for automated point out procedures.

Google
 

Original NASA ASRS Text

Title: ZBW Controller reported a non-coordinated change to an aircraft's data block; heading and altitude; after initial point out was made. Controller stated lack of clear rules for new automated point out procedure contributed to the event.

Narrative: I approved the point out on Aircraft Y and Aircraft X via the new automated point out function climbing to FL290. Then after the aircraft got to FL290 a new 'P' appeared on the data block with FL330 as the new T-ed in altitude. I did not approve the automated point out because I believe this violates the 7110; because any changes to the aircraft after the first point out was completed needs to be verbally coordinated. ZNY climbed the aircraft without coordination or approval to do so. They also turned the aircraft after I took the point out without coordination. We need to establish clear rules for Automated Point Out procedures.

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.