Center Controllers dealing with unusual flow requirements; weather deviations and extra workload caused by activation of special use airspace in their sector reported a military aircraft awaiting clearance into special use airspace lost an engine and could not comply with ATC instructions which resulted in an airspace violation.

Date: 2022-08 · Aircraft: Military · Phase: cruise

Anomalies: atc-issue-all-types|aircraft-equipment-problem-critical|airspace-violation-all-types|deviation-discrepancy-procedural-published-material-policy|inflight-event-encounter-weather-turbulence

Synopsis

Center Controllers dealing with unusual flow requirements; weather deviations and extra workload caused by activation of special use airspace in their sector reported a military aircraft awaiting clearance into special use airspace lost an engine and could not comply with ATC instructions which resulted in an airspace violation.

Narrative

I was working RXX/XY including what would eventually be the Special Airspace. ZZZ arrivals were coming from sector XX/XY deviating until approximately ZZZZZ intersection. ZZZ1 called and put me in the hold because they had some 'go-arounds'. I was also vectoring ZZZ2 arrivals attempting to get the requested spacing for 1XX ZZZ3 sector. The supervisor then told me to reroute all ZZZ2 arrivals over ZZZZZ1 ZZZZZ2 etc. I verified he wanted me to turn the 3 ZZZ2 aircraft I was already vectoring in the opposite direction of an airport over 250 miles away; and he said yes. I requested a D side multiple times because of the complexity of the traffic. Sector YY called to coordinate a hearing and an altitude for Aircraft X. This was the first time I became aware that Special Airspace was going active. I can't recall exactly what altitude Aircraft X was level at but I believe it was 24;000 feet.I gave the Aircraft X a northwest heading to try to give him a box pattern until Special Airspace became active. Because of the traffic complexity and Special Airspace going active I advised I was not rerouting the ZZZ2 arrivals because it would have been a huge safety hazard to make the traffic more complex and left them on the route and attempted to get the previously requested spacing. I then issued Aircraft X a northeast heading. While dealing with the other complex traffic I noticed Aircraft X didn't turn northeast so I issued it again and he [requested priority handling] for engine failure; advised he had an engine fire indication; and he was dumping fuel. The D side that arrived was coordinating with 1XY and 1YY and we issued a northeast heading and descent prior to 1YY assuming radar contact and working them down into ZZZ4 approach airspace. Eventually Special Airspace was activated and the fighters arrived in the airspace NORDO. Because of traffic complexity; workload; etc; I did not radar ID the second fighter in the flight of two in the Special Airspace until later when workload reduced. Don't ask a sector that is busy with weather; holding; and vectoring to reroute traffic that could have been accomplished with planning ahead. Also have someone verify with the sector working Special Airspace that it is going active; and have it active prior to the tanker and fighters arriving.

Second reporter narrative

I was working the D-side. We had Aircraft X on a 290 heading I believe. Special Airspace was not active on the scope yet. Supervisor just told us to hold him until it was active. We also were in the hold for ZZZ; and vectoring for ZZZ2. Aircraft X was left on the heading for too long at 24;000 feet. so I did a point out; saying we are trying to get him to turn back to towards our airspace. As the R-side was issuing a right turn; the Aircraft X reported an [problem]; they lost an engine and had a fire indicator on. I then proceeded to point out to other sector; and try to handoff to ZZZ4 Approach. However; the Aircraft X wasn't able to turn timely; and ended up farther west and north outside of our sector. Other sector had departure traffic; so they asked for the Aircraft X on 060 heading and for communications. I told him we would try to assign him that heading; but I wasn't sure if the aircraft would be able to with an engine out. The R-side issued the 060 heading and switched the Aircraft X to the other sector. It would have been nice if routes and procedures were in place prior to the aircraft for Special Airspace arriving. We had both the Aircraft Y and the Aircraft X before the airspace was active; and before anyone was doing the procedures for Special Airspace (altitude restrictions and routes). In addition; there was confusion on why we had to do so much ZZZ2 in trail; when there was no competition; and sectors to the west of us were short cutting ZZZ2's early.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.