37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1283057 |
Time | |
Date | 201507 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZNY.ARTCC |
State Reference | NY |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Small Transport Low Wing 2 Turboprop Eng |
Operating Under FAR Part | Part 91 |
Flight Phase | Cruise |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Widebody Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Cruise |
Flight Plan | IFR |
Person 1 | |
Function | Enroute |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 10 |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
I handed off aircraft X to hto sector. I still had communications with aircraft X. I had radar and communications on aircraft Y. I climbed a departure off of jfk to FL190 ref these aircraft. The hto sector changed the data block on aircraft X to show FL190 and was handing the aircraft to the sardi sector. I asked my handoff if he gave control and he said no. I called the hto sector and asked what he was doing. He asked for control and I said no due to traffic. I asked him to change the data block back to FL210. I then realized I hadn't switched communications and switched aircraft X to hto. As soon as hto had communications with aircraft X they put FL190 in the data block and handed the aircraft off to sardi. I called back to hto sector and asked if he was descending aircraft X. He asked me if I gave him control. I said no and he said then I'm not descending him. I told the hto controller to put back the assigned altitude because I'm getting conflict alerts on aircraft X and aircraft Y. He never did and I advised my supervisor.do not change data blocks in other controller's airspace.
Original NASA ASRS Text
Title: A ZNY Controller reports of another Controller changing the data block of his aircraft. The other Controller asks for control of aircraft and the reporter advises no due to traffic. The Controller then transfers communication to other Controller and other Controller changes data block again. The reporter asks other Controller if he gave them control and he said no. The reporter asked again for other Controller to put the correct altitude in the data block. The conflict was because of the other Controller changing the altitude in the scratch pad area.
Narrative: I handed off Aircraft X to HTO sector. I still had communications with Aircraft X. I had radar and communications on Aircraft Y. I climbed a departure off of JFK to FL190 ref these aircraft. The HTO sector changed the data block on Aircraft X to show FL190 and was handing the aircraft to the SARDI sector. I asked my handoff if he gave control and he said no. I called the HTO sector and asked what he was doing. He asked for control and I said no due to traffic. I asked him to change the data block back to FL210. I then realized I hadn't switched communications and switched Aircraft X to HTO. As soon as HTO had communications with Aircraft X they put FL190 in the data block and handed the aircraft off to SARDI. I called back to HTO sector and asked if he was descending Aircraft X. He asked me if I gave him control. I said no and he said then I'm not descending him. I told the HTO controller to put back the assigned altitude because I'm getting conflict alerts on Aircraft X and Aircraft Y. He never did and I advised my supervisor.Do not change data blocks in other controller's airspace.
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.