Date: 202009
Local time of day: 1801-2400
Location: ZZZ.ARTCC, US
Aircraft: U2/TRI
Operator: Military
Flight plan: IFR
Flight phase: Cruise
Airspace: Class A ZZZ
ATC / advisory: Center ZZZ
Reporter organization: Government
Reporter function: Traffic Management
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown
Anomaly: ATC Issue All Types; Airspace Violation All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Provided Assistance
Contributing factors: Airspace Structure; Company Policy; Procedure; Human Factors
Primary problem: Ambiguous

Narrative: ZZZ1 started a side-stream handoff on Aircraft X at 60;000 ft. to ZZZ ARTCC. Center flight plan showed the route of flight ZZZ5 […] ZZZ5. The flight plan showed a delay of 4+55 at ZZZ4 and never coming close to ZZZ. The pilot ended up on an incorrect ZZZ UHF frequency and they in turn shipped the aircraft to the correct sector frequency which was the sector that the aircraft was in. The CIC (Controller in Charge) called the ZZZ1 supervisor to try and figure out the route of flight. The CIC was unsuccessful in finding out what the exact route of flight was. I was told about the situation and I directed our TMU (Traffic Management Unit) to contact ZZZ1 TMU to try and determine what the aircraft's intentions were. ZZZ MOS (Military Operation Specialist) was able to contact ZZZ1 MOS and they faxed a depiction of the route of flight which had no flight plan information. The depiction showed the aircraft flying southeast after ZZZ2 but the map did not have the range to display ZZZ's portion of the flight. I called the ZZZ1 Operation manager who was not aware of the situation. The ZZZ1 MOS provided a point of contact (Person A) for the mission. I called Person A and he was unwilling to provide the route of flight. I explained that this aircraft was in controlled airspace and the controllers had no idea where the aircraft was going. By this time the aircraft was 190 miles inside of our airspace. He said that he was unable to provide the route of flight on an unsecured line. He said that the aircraft was going to go a little bit further east and then make a loop back to ZZZ2. Then he said that the aircraft was going to go to ZZZ3 and make a loop. I said that he obviously knew what the points along the flight plan was and that is what I was looking for. He again was unwilling to provide the route of flight. I inquired about this 'loop'. I asked if the aircraft was making a left turn direct ZZZ2 after ZZZ3. We were concerned about the aircraft turning right into Mexico. Person A stated that a loop meant that the aircraft would do one turn in holding with a 30 mile leg at ZZZ3. Then he stated that the pilot may make another loop 100 miles east of ZZZ2 before heading to ZZZ2. Person A stated that this was all coordinated with ZZZ1. I explained that the aircraft is now over 200 miles inside of ZZZ's airspace and that we have no coordination of what is happening. The aircraft flew from ZZZ2 to ZZZ3 where the pilot made a left hand turn in holding and then proceeded to the ZZZZZ area and made a right hand turn in holding and then back into ZZZ1 airspace.ZZZ put in a route that would get the datablock to process back to ZZZ1 but was still not the exact routing that the pilot was cleared. We never did figure out what the route of flight was. ZZZ1 needs to properly update an aircraft's route of flight before making a handoff. These types of missions need to be coordinated with ZZZ's airspace and procedures office before the mission begins.




Synopsis: A Center Traffic Management Specialist reported a military aircraft entered their airspace without proper coordination from the adjacent Center.