Air Traffic Control Developmental
Air Traffic Control Time Certified In Pos 1 (yrs) 2.5
Situational Awareness; Troubleshooting; Distraction; Workload; Communication Breakdown; Confusion
ATC Issue All Types; Airspace Violation All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Air Traffic Control Provided Assistance
Human Factors; ATC Equipment / Nav Facility / Buildings; Procedure
Aircraft X landing at CGE from sector 38 entered our airspace at FL270 and was given a straight decent to FL130 with out a restriction. The aircraft was PVD [Plan View Display] to sectors 21 below us and 11 north of us. The R side pointed the aircraft out to sector 21. The aircraft was handed off to TAPPA sector in PCT. We then noticed the altitude in the data block read FL070 but neither the R side or myself did that. I called sector 11 and referenced this aircraft who had the PVD and asked if they put in FL070. They said no and that they didn't have track control. I called TAPPA and asked if they put in FL070. He said yes and I mentioned that we have never seen PCT be able to put in an ALT on our scope before. He said to just keep the aircraft going to FL130.  The R side kept him going to FL130 and switched the aircraft to TAPPA freq. Sector 11 called me and asked if Aircraft X had a crossing restriction.  I said no; he has a straight decent to FL130.  My prior reference of this aircraft and them calling me asking about a restriction was all done prior to the aircraft entering sector 11's airspace.  They said ok and hung up the line.I asked the R side if he had been pointed out to 11.  He thought I had done it and I thought he had done it and that 11 was well aware of the aircraft due to the two prior calls but then phrase 'Point out approved' was never stated on the land line.  The R side and I also had confusion about this point out due to the conversation and calls regarding the altitude of FL070 somehow being entered in to the data block by the TAPPA controller at Potomac Approach.When the aircraft was at about FL185 I called 11 to confirm the aircraft was point out approved and they confirmed that it was even though the aircraft was already in their airspace.Less confusion about what Potomac Approach can do to change the altitude of the data block on our scope.  The aircraft should have been pointed out.  It was a confusion between the R side and I and with the R side at 11.
ZDC controller reports of something he hadn't ever seen before. PCT has the ability to change altitudes of data tags on his center scope. Controller reports that a sector at PCT did this and it caused confusion and an airspace deviation by them doing so.