Tower Local Controller and air carrier Captain reported a UAS flying over the runway resulted in an airborne conflict during final approach and the Controller directing the air carrier to perform a go-around. The controller reported the UAS was given authorization to fly over airport property but should not have flown over the runway.
Synopsis
Tower Local Controller and air carrier Captain reported a UAS flying over the runway resulted in an airborne conflict during final approach and the Controller directing the air carrier to perform a go-around. The controller reported the UAS was given authorization to fly over airport property but should not have flown over the runway.
Narrative
Airport ops approved a drone to be flown on the airport south of taxiway 1. Aircraft X was on approach to runway XXR. I observed the drone flying north of taxiway 1 over RWY XXL which was active. I advised Aircraft X of the drone. Then I observed the drone flying towards the approach path of RWY XXR I sent Aircraft X around. On Aircraft X second approach the arrival controller asked if they should hold the aircraft; I said yes so we could get the drone on the ground. The arrival controller told me to advise when its clear. After several failed attempts to reach the airport operation by the supervisor; Aircraft X called on approach to XXR. I advised Aircraft X of the drones position and told them if the drone headed towards them again Id send them around again. Luckily I was relieved by my sup at that time. Aircraft X landed safely without further conflict with the drone. We had no comms with the drone operator and couldn't get hold of airport ops. I recommend not flying drones on the airfield.
Second reporter narrative
Forecast planned landing fuel was 1:05. I added 10 minutes of fuel.The flight was uneventful until contacting ZZZ tower. Enroute we checked notams and did not see any drone comments. We printed 3 ZZZ ATIS' enroute and did not note drone activity mentioned. The last ATIS my FO read from JeppFD Pro while on downwind and did not note any drone activity mentioned.When we contacted ZZZ tower; the controller said there was a drone which was in front of XXL and was moving in the direction of XXR. The last he said it was between the runways. I thought that the tower controller must have good eyes or good binoculars to pick out a drone. We had just passed the FAF. Shortly there after tower directed a go around. (I don't know what it says in the controllers handbook (if there is such a thing) but can't someone tell them to be quiet for about 30 seconds after directing a go around unless absolutely necessary?) Tower directed the go around and then immediately gave my FO a heading; altitude and frequency change. I delayed the go around for a few seconds to let my FO 'catch up.' The go around was uneventful.We returned to approach control. He gave us delaying vectors in hopes that the drone would move. After about 8 minutes we were vectored back for a visual. When we got on tower I had my FO ask tower who was controlling that drone. He said the drone was authorized to fly in the vicinity of the airport. It was to remain clear of the approach to RWY XXR and that he had no control over it or a direct line to who did. One comment was he couldn't believe airport authorities allowed the drone to fly without tower input (or something to that effect) It was my impression he had to call someone to have that someone call whoever was controlling the drone.Tower then told us to continue the approach. He said he may have to direct another go around. Shortly thereafter we were given clearance to land. The visual approach; landing and taxi to the gate was uneventful.
More incidents for this aircraft family →
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.