Commercial Fixed Wing
Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Time Pressure; Situational Awareness; Distraction; Confusion; Communication Breakdown; Workload
ATC Issue All Types; Airspace Violation All Types; Deviation - Altitude Crossing Restriction Not Met; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Inflight Event / Encounter Unstabilized Approach; Inflight Event / Encounter Weather / Turbulence
General None Reported / Taken
Environment - Non Weather Related; Human Factors; Weather
On arrival into ZZZ from the south; we were vectored off of the ZZZZZ procedure and held high due to traffic. We had been previously queried as to our RVR requirements for [Runway] XXR. We were set up and briefed for CATIII approach to XXR. Just prior to ZZZZZ waypoint; we heard traffic ahead cleared to descend via ZZZZZ arrival landing north. We were then given clearance to descend via the arrival landing north and were unable to meet the new crossing restrictions. Due to 71 knot crosswinds our heading was 320. The vector we were given for descent was 340. This was assumed to be a 360 for descent. As we turned through a heading of 260 ish we were told to make an immediate right turn for restricted airspace. We complied. We continued on the arrival and had an uneventful hand off to approach.I believe that the ATC is currently overworked due to COVID cutbacks. Many communications are being missed in the last months because ATC are covering too many sectors. Our lack of fore warnings regarding the changes to airport configuration left us with inadequate situational awareness. We followed the vectors given to us with incorrect assumptions. I'm grateful that this situation was resolved without incident. My recommendation is that we begin to re-staff ATC to normal pre-COVID operation.
Flight was left high on the ZZZZZ Arrival.   ATIS had us landing on [Runway] XXR.   We were cleared for the ZZZZZX but never informed by ATC that ATIS X special was issued at XA22z we only learned that there was a runway change due from listing to arrival aircraft in front of us.   We were now high for landing [Runway] YYL by 6;000 feet at the same time we were instructed to slow to 190 kts.  We can slow down but not go down at the same time.   We were instructed to fly heading 340 as we descended the controller once again said turn left 340 which we were on and we assumed he wanted us to do a 360 which is common to loose altitude and rejoin the arrival.   He was busy with several other aircraft left high the weather was poor in mild turbulence.  The next call was for us to turn I believe 040 because he said we are going to hit a restricted area.I was heads down retrieving the new ATIS as well and programming the FMS for a different runway.    This was a combination of change of runways; poor weather; and aircraft being left high by two controllers and high winds with an approach to mins.   This was a series of events that lead to an aircraft being out of position.When the weather is poor we cannot skimp on air traffic controllers they need to be tentative to aircraft and where they are going.   If the aircraft is out of position.  It should be quickly realize especially when a runway change has been posted and an aircraft may not have received the special ATIS.
Air carrier flight crew reported airspace; heading; and altitude deviations during approach.  The Captain stated a late runway change and Controller workload were contributing factors.