Date: 202105
Local time of day: 1201-1800
Location: ZDC.ARTCC, VA
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Cruise
Airspace: Class A ZDC
ATC / advisory: Center ZDC
Second aircraft: Fighter
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Communication Breakdown; Confusion
Second reporter function: Enroute
Anomaly: Conflict Airborne Conflict; Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Clearance
Detector: Automation Aircraft RA; Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Separated Traffic; Air Traffic Control Provided Assistance; Flight Crew FLC complied w / Automation / Advisory
Contributing factors: Airspace Structure; Procedure; Manuals; Human Factors
Primary problem: Procedure

Narrative: I was working Sector 18 Woodstown; but not actually Woodstown (sitting at Sector 17). I was to be only working the Compton and Reading military airspace; which had Aircraft Y's and a Aircraft Z in it at the time. I witnessed the Aircraft Y refueling with the tanker at FL256 with out communicating that to me. Shortly there after; Aircraft Y separated from the tanker without communicating to me; and what I assume was descending back to the fighter cap altitudes of FL230-FL240 of which he was initially cleared to be at. Aircraft Y turned at the southern portion and descended; and then I saw him at FL227 below his assigned altitude. Aircraft X; was at FL220 right underneath him. I immediately asked the pilot if he was FL230-FL240; he responded that he was. At the same time the altitudes on the data block went back to FL230-FL240. The Sector 19 Controller; who was working Sector 18's airspace (even thought Sector 18's airspace was assigned to me sitting physically at Sector 17); said that Aircraft X was responding to an RA and descended. I immediately called the traffic to the fighter jet at that time. Filed previous reports regarding the Presidential airspace over Delaware. Procedures are not defined; there is no LOA or SOP; and the workforce was not properly briefed. There are many sited violations FAA Orders associated with this unsafe operation in addition to automation issues that can cause unsafe situations with Sector 18 not being utilized correctly. Request an LOA for the procedures; and for the boundaries; altitudes; refueling operations; and reroutes to all be negotiated with affected parties and implemented correctly in an LOA. A fighter jet got too close to an airliner jet in this situation; and the pilot did not even seem to understand the issue or care. They need to at the very least stay at their assigned altitudes; and they should be communicating with us on refueling operations to avoid situations like this.


Second narrative: Aircraft X was level at FL220 and given the descent clearance for the PHLBO 3 arrival.  Aircraft Y was a single military fighter in COMPTON Airspace. Aircraft Y descended out of the Airspace without coordination and caused Aircraft X to react to an RA alert.  Traffic was issued to Aircraft X and he eventually continued his descent via the PHLBO3 arrival.There is much confusion on how the Biden airspace should be managed.  Some controllers work EWR arrivals while others don't.  The current assignment of airspace makes it difficult for processing hand-offs and point-outs correctly.  Although this airspace confusion had no implication on the military aircraft leaving the confines of the restricted airspace; it needs to be address for clarification and safety.  Point-outs and hand-offs may be missed.


Synopsis: ZDC Center Controllers  reported a military fighter jet descended below the assigned altitude and into conflict with an air carrier operating below the track. The report states the military airspace and procedures for this area [Biden] are not published or defined and the controllers have not had sufficient training to conduct this operation.