Air Traffic Control Fully Certified
Air Traffic Control Time Certified In Pos 1 (yrs) 20
Workload; Situational Awareness; Distraction
ATC Issue All Types; Conflict Airborne Conflict; Deviation / Discrepancy - Procedural Published Material / Policy
Air Traffic Control Provided Assistance
Environment - Non Weather Related; Human Factors
Aircraft X reported on the Local Control frequency having seen a drone pass off of the right hand side of the aircraft on final Runway XX Left. The Local Assist Controller advised me and began looking through their binoculars to see if they could observe the drone. The Local Controller advised the subsequent traffic inbound to ZZZ and the Local Assist advised TRACON finals sectors. The traffic was fairly busy with moderate complexity. At the time I was monitoring Ground Control as there was a chance of having no gates for arrivals as well as repositions for overnight aircraft servicing. I picked up the CIC binder which spewed itself onto the floor because someone had left the rings partially open. Having to put the binder back together took some time and eventually I found the section about UAS unauthorized activity. I started an report; had Ground Control check with the pilot about additional information; and the pilot asked for the number to provide the details. The pilot called a few minutes later and provided all the details that were requested on the form. I then followed up with a call to TRACON; Center; DEN (Domestic Event Center); and finally the ROC (Regional Office Center) due to the significant nature. I was assigned the CIC (Controller in Charge) due to the remaining present controllers all being ineligible. There were 3 late staying people on break; of which two were CIC eligible. I am not sure how the FLM (Front Line Manager) got out of the shift and a CIC always assigned. 3 of us were in the last 90 minutes of a 10 hour day. When calling into the ROC; it was mentioned that I should not be in charge of the operation as well as doing the paperwork. I paused and thought to myself that is a set up for operational failure in a situation like this. This was definitely an operationally urgent notification; as any subsequent report of the drone would shut down the arrivals until we could establish it was safe to do so once again. There was one follow-up sheet of questions that I waited until the late staying controllers came back and give up CIC to take care of.While filling out the report and making the calls; I was no longer actively engaged in monitoring the operation; however I could hear everything that was going on in the background. The team worked remarkably well with Local Control reporting the drone activity for almost an hour; and the Local Assist continually looking to see if they could see it; even though when the pilot called in it was described as unlit.Looking at the event in review; I can see the checklist is great for guidance and there were some really important elements to cover; as this was a very unusual event. Getting the ATIS done; having Local broadcast; notifying TRACON; the airport; and the DEN are all important. I was very happy to follow up and complete the processes; but it kind of bothers me that with all of these great check lists and all; when I called the ROC the QCG (Quality Control Group) person told me if I should not do this without direct monitoring of the operation; then leave it for tomorrow. I don't think that it is very realistic to get the very specific recallable details and information conveyed as this was an aircraft security event. Next time I will call a CIC capable controller back from break to fill out the paperwork and make the calls; and let them figure out the breaks after I go home since the worst case scenario would be about 2 hours and 25 minutes until a mid shift person was able to come and get them out.
Tower Controller in Charge reported an arrival aircraft reported a drone close to them on final.