Date: 201406
Local time of day: 1201-1800
Location: ZDC.ARTCC, VA
Weather elements / visibility: Thunderstorm
Light: Daylight
Aircraft: B737 Undifferentiated or Other Model
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: Airbus Industrie Undifferentiated or Other Model
Reporter organization: Government
Reporter function: Traffic Management
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Time Pressure; Communication Breakdown; Confusion
Second reporter function: Enroute
Anomaly: ATC Issue All Types; Airspace Violation All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter Weather / Turbulence
Detector: Person Air Traffic Control
When detected: In-flight
Result: Air Traffic Control Issued New Clearance
Contributing factors: Airspace Structure; Procedure
Primary problem: Airspace Structure

Narrative: Severe weather forecast for the afternoon showed moderate coverage along the ZID/ZDC/ZOB boundary and extended into the western portion of ZNY. Traffic was being rerouted via the Command Center to the south reference that forecast. ZFW/ZHU traffic destined to EWR/LGA/BOS were being reroute via ZTL via the VUZ play book. The Command Center wanted to reroute the EWR/LGA/BOS traffic departing ZLA/ZAB on the BNA playbook which brought them into ZID and entering ZDC via BKW/J42. ZDC was TMA'ing for EWR and LGA and military airspace was active; both Patuxent and R6611/R6613 from surface to 600 thereby limiting vectoring ability for ZDC10/12. ZDC explained this to the Command Center as to why ZDC was unable the BNA playbook. The Command Center stated the wind routes weren't working and that there were 70 flights coming from ZTL and 'only' 4-6 per hour on the BNA playbook. ZDC again requested that all the traffic enter ZDC on the single flow from ZTL via the VUZ playbook as ZDC would then have to merge the ZTL flow with the ZJX flow. Command Center said just pass back whatever MIT was needed as the traffic was coming. ZDC advised ZID of possible hold due to the complexity of taking this additional traffic with the military areas active reducing any vectoring ability. ZDC then passed back 50 MIT and the Command Center denied the request.No J42 to the NY airports; especially when the military airspace is active. If a facility says they are unable that they can't take a flow of traffic other alternatives are explored.


Second narrative: I had just got done filling out a report for the error my trainee had and before I got a break I was paged back to work. Traffic [was] busy and complex; unusual restricted area in effect. Twice a year R6611 goes active above 10;000. Today it was active to 60;000. I vectored Aircraft Y away from other traffic and he was resuming his normal route. I must have vectored too close to R6611 as our ever helpful TMU called the area Supervisor to advise him that an aircraft had gotten one hit inside R6611. R6611 does not have aircraft in it so we're allowed to go up to the line but not inside. I reviewed the FALCON and zoomed into an 8 mile range and I did indeed get one hit inside the line.


Synopsis: Four reports of a restricted area that was hot up to an unusual altitude on a day with weather that hindered the routes available for controllers to use. All reports discuss violation of a restricted area.