Date: 202108
Local time of day: 1801-2400
Location: ZZZ.TRACON, US
Light: Night
Aircraft: Large UAS (At or above 1320 lbs)
Operator: Military
Operating under: Part 91
Flight phase: Cruise
Airspace: Class A ZZZ1
ATC / advisory: TRACON ZZZ
Reporter organization: Government
Reporter function: Supervisor / CIC
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown
Second reporter function: Approach; Supervisor / CIC
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Automation Air Traffic Control; Person Air Traffic Control
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Human Factors
Primary problem: Human Factors

Narrative: UAS crew called on telephone to activate UAS airspace. The CIC (Controller In Charge) answered the phone and took the request. Part of the request was for airspace X and airspace Y ATCAAs (ATC Assigned Airspace) which has to be released by ZZZ1. A few minutes later the phone rang and the CIC was working aircraft on ZZZ [sector] so I took the call and it was the flight crew asking about the airspace. I informed them that I was not the person they had spoken too a few minutes ago and to restate the request. When they said they wanted airspace X and airspace Y I asked for the altitude and I heard AOA (At or Above) FL400. I then verified with the CIC that the ATCAAs were released and was given a affirmative indication. I then proceeded to clear the UAS for the ATCAAs AOA FL400. I also marked this on the flight strip. When the mid crew came in I briefed that the UAS had AOA FL400 and after the overlap left the control room. About XA35 the CIC when the clearance was issued came to me and asked what I had given the UAS and asked what I had cleared him. I told him and he said that he had coordinated AOA FL430 and not FL400. Apparently when the crew made the original request they told the CIC AOA FL430 and that was what was coordinated with ZZZ1. FL400 was coordinated when the error was discovered.I made a crucial mistake here and that was I assumed; and we know the trouble that can cause; that the crew told me the same information as the CIC and the old adage of 'Trust but verify' would have prevented this event. If I had also verified the coordinated altitude with the CIC when I asked if we had the airspace.


Second narrative: I had been working CIC (Controller In Charge) combined with sector when a special operation called for an airspace clearance. The controllers working the sector had been busy at the time; so I had the individual call back in 10 minutes. Most of the airspace requests were usual except for the airspace X and airspace Y ATCAAs (ATC Assigned Airspace) FL430 and above. While waiting for the ZZZ2 sector to finalize clearing out the airspace for the special operation; I called ZZZ1 for the ATCAAs as requested. I ended up having to work a few aircraft when they special operation called back and the other controller took the call to issue the Special Use Airspace clearances since he had no aircraft to work at the time. I thought everything was fine until the overnight crew took over the positions and mentioned that there was a discrepancy between what I got from ZZZ1 and what the other controller cleared the special operation; by 3;000 feet (cleared at or above FL400 instead of FL430). Upon finding out; I called ZZZ1 to acquire the airspace X and airspace Y ATCAAs at or above FL400 to match the clearances. Upon asking the controller what happened; he forgot which altitudes I had acquired from ZZZ1 and just asked the special operations what they needed which he said they changed to FL400 and just cleared them those altitudes in the ATCAA instead of clarifying with me. I'm unsure if any errors actually happened as we lost our review capabilities.Only thing I can think of to help is make a written note to hand off if needed for the special clearances instead of trying to verbally coordinate the specifics.


Synopsis: TRACON controllers reported communication problems resulting in incorrect altitudes assigned to a UAS.