Confusion; Distraction; Situational Awareness; Workload; Communication Breakdown
ATC Issue All Types; Deviation - Altitude Overshoot; Deviation - Altitude Excursion From Assigned Altitude; Deviation / Discrepancy - Procedural Published Material / Policy; Deviation / Discrepancy - Procedural Clearance
Air Traffic Control Issued New Clearance; Flight Crew Returned To Clearance; Flight Crew Took Evasive Action; Flight Crew Became Reoriented
Procedure; ATC Equipment / Nav Facility / Buildings; Human Factors; Airport
During our descent through 10;000 feet into ANC after our arrival fix (GASTO) we received an unexpected runway change from 7R to Runway 33. While being vectored to a visual approach we were given a heading of 070; maintain 4;000 feet to intercept and track inbound on the 7R LOC. The clearance made no sense as we had already changed nav frequencies to our assigned runway. We changed back to the 7R LOC only to realize that it was not emitting a signal and did not identify audibly. While trying [to] query ATC we visually tracked inbound to Runway 7R until further clearance was given. During this time both pilots became distracted and we descended below our assigned altitude. Due to the visual conditions; the runway change and the bogus clearance I failed to back up the pilot flying and failed as the PM (Pilot Monitoring). No mention of the deviation was made by ATC. In an effort to comply with a confusing ATC clearance we became distracted from our primary flight duties of flying and monitoring.
[Report narrative contained no additional information].
A B737 crew reported while descending through 10;000 feet to ANC Runway 7R; ATC changed their Runway to 33. Confused; the crew began setting up for Runway 33 when ATC cleared them for a Runway 7R visual approach; [and to] track the localizer which they discovered out of service. By then seriously distracted; the crew descended below their assigned altitude.