Date: 202010
Local time of day: 0601-1200
Location: ZZZ.TRACON, US
Aircraft: Small Transport; Low Wing; 2 Turbojet Eng
Flight plan: IFR
Flight phase: Final Approach
Airspace: Class B ZZZ
ATC / advisory: TRACON ZZZ
Second aircraft: Commercial Fixed Wing
Reporter organization: Government
Reporter function: Approach
Reporter qualification: Air Traffic Control Fully Certified
Anomaly: ATC Issue All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Result: General None Reported / Taken
Contributing factors: Environment - Non Weather Related; Human Factors
Primary problem: Human Factors

Narrative: First aircraft inbound for ZZZ; we're on a north operation.  Aircraft X comes from the SW; checks on with correct ATIS; I assign him Runway XXL tell him to expect radar vectors for a visual approach; second aircraft; Aircraft Y checks on with correct ATIS from NE I assign him radar vectors VA XX L; third aircraft checks on from SW Aircraft Z; checks on with correct ATIS tell him to expect visual approach XXL and I give him a caution wake turbulence because he'll be following Aircraft Y.  Since Aircraft X was my first aircraft it's customary for me to get flight conditions; winds bases etc.I wasn't very busy; some departures from ZZZ and nearby satellites; got one VFR for flight following.  I know something had gone wrong at some point with our radar; something with ASR and I think some shout lines also OTS (Out of Service) which I believe Supervisor was working on due to phone calls in background.  CIC was watching the satellite sector he seemed to be getting busy.  I vector Aircraft X to the back of the box; for a straight in visual approach approximately 15 miles; I get the last of the PIREP; I clear him and switch.  I slowed Aircraft Y on downwind to follow; and I had vectored Aircraft Z towards final.  Aircraft Y calls field in sight; I withhold clearance to give Aircraft X room to get off runway.  Finally give a turn and clearance to Aircraft Y and switch to Tower.  Then I hook Aircraft Z to join the final approach course and advise field when I notice go-around; and Aircraft Y going to XXL; I assumed FOD on runway; I immediately change the runway on Aircraft Z; tell him to plan on a VA app; and told him to stand by while I find the localizer frequency; he says he has field in sight so I clear him to XXL; at some point I switch him. Aircraft X comes off; I start my point out with my satellite; climb him to 4;000; and turn him.  I asked him if he went around due to FOD; I don't think he understood my questions; I asked him if he went around due to FOD; what was reason for go-around and he said runway was closed; he went around when he saw the flashing 'X' on runway then he asked the tower controller if runway closed. That's when I realized I had been vectoring to wrong runway and forgotten west complex [was] closed.  I had been previously distracted prior to taking position from union forcing us to no longer social distance and having to train; so that had been something I was discussing with my peers and the possibility of changing schedules for a sixth time this year that had definitely been a major distraction when I came to work today.  In the end it's on me; I'd like to know if ATIS was correct because I had three pilots all check in with current ATIS and no one balked at XXL.  Also straight in; over 15 miles; tagged for the wrong runway; and tower didn't look at the scope or out the window and cleared for the wrong runway.  Just a lot of Swiss cheese [stuff] went down. A lot of things went wrong; involving a lot of people; maybe I should have taken sick leave today.




Synopsis: Approach Controller reported vectoring three aircraft to a closed runway and not realizing it until the first aircraft went around.