Tower Local Controller reported a pre-coordinated UAS flight deviated from its published procedure into the path of air carrier traffic on final approach; requiring the Controller to direct a go-around to avoid the UAS.

Narrative

I was working local east and responsible for runway XXR. The city had just closed XXC for scheduled maintenance. The TRACON called and said a flight check was going to be too close to the final for XXL so all of the arrivals were going to come to XXR. Within 5 minutes or so of that information reaching me the Front Line Manager (FLM) came over and said that a drone had been authorized to come up and operate in an area just west of the approach end for XXR. West of taxiway 1 is what I was told. 1 is the parallel taxiway to XXR and is approximately 500 ft west of XXR. I thought to myself; boy that's real close to my runway especially if all the traffic is coming over here. Almost immediately the drone departs in the area and starts flying around. Within a minute of that the drone starts to deviate from the plan and appears to be outside the approved area and now directly over the final. The drone appears to just higher than the tower so approximately 400ft msl. I told the first plane that was on final about the drone coming up to his flight plan. When the drone stayed on the final and the aircraft was on about a 3 mile final I sent the plane around. The Supervisor started to call the phone number we had for the drone operator and was told that that's not them. So now we had an unauthorized drone on the final. Three more aircraft were sent in for an approach to that runway and I had to send each of them around as we couldn't get a hold of the drone to move them out of the wayRecommendation: If we are going to approve drone operation so close to a runway we need to stop using that runway until the drone is back on the ground. We need to think about what could possibly happen if the drone operator does not follow directions; which is becoming more and more common here