A controller working local control combined with controller in charge reported an aircraft reported ...

Narrative:

I was working the local 3 position as well as controller in charge (controller in charge). Aircraft X; on about a 1.5 mile final reported seeing a yellow drone east of the final at 900 ft. From there I began the process of reporting the unauthorized uas event first via a report. On my initial attempt to file the report; the page used to file the report was not working correctly. It only allowed me to select the type of report; but not the information regarding the event. I restarted the report and kept experiencing the same problem. At this point; I had 3 additional aircraft arriving. I issued each it's landing clearance as well as an advisory of the reported uas. Those 3 arriving aircraft reported seeing no uas in the vicinity of their respective final. I contacted the roc (command center) regarding the reporting issue. With their help I was able to fill in information regarding the unauthorized uas event. From there; I began to look for the checklist regarding unauthorized uas events. I was unable to find the checklist at the controller in charge desk. I was able to find the uas binder; however I did not find the reporting checklist. I also checked the ace-ids under the checklist section and was not able to find the uas checklist. I tried to recall from memory; my controller in charge training on what is supposed to be reported. Not being able to find the correct checklist led me to not report the event to the additional required parties. I now know that I still needed to report this event to the den [domestic event network] and pct; as well as broadcast the event on the iad ATIS. In retrospect; I also think that I could have recalled another controller from the breakroom for assistance.I would suggest adding the uas reporting checklist to the checklist section of the ace ids. I would also add this checklist the uas binder for quicker reference.

Original NASA ASRS Text

Title: A Controller working Local Control Combined with Controller in Charge reported an aircraft reported sighting a drone in their airspace but was unable to find the appropriate checklists to report the incident according to the rules.

Narrative: I was working the Local 3 position as well as CIC (Controller in Charge). Aircraft X; on about a 1.5 mile final reported seeing a yellow drone east of the final at 900 ft. From there I began the process of reporting the unauthorized UAS Event first via a report. On my initial attempt to file the report; the page used to file the report was not working correctly. It only allowed me to select the type of report; but not the information regarding the event. I restarted the report and kept experiencing the same problem. At this point; I had 3 additional aircraft arriving. I issued each it's landing clearance as well as an advisory of the reported UAS. Those 3 arriving aircraft reported seeing no UAS in the vicinity of their respective final. I contacted the ROC (Command Center) regarding the reporting issue. With their help I was able to fill in information regarding the Unauthorized UAS Event. From there; I began to look for the checklist regarding Unauthorized UAS Events. I was unable to find the checklist at the CIC desk. I was able to find the UAS Binder; however I did not find the reporting checklist. I also checked the ACE-IDS under the checklist section and was not able to find the UAS checklist. I tried to recall from memory; my CIC training on what is supposed to be reported. Not being able to find the correct checklist led me to not report the event to the additional required parties. I now know that I still needed to report this event to the DEN [Domestic Event Network] and PCT; as well as broadcast the event on the IAD ATIS. In retrospect; I also think that I could have recalled another controller from the breakroom for assistance.I would suggest adding the UAS reporting Checklist to the Checklist Section of the ACE IDS. I would also add this checklist the UAS binder for quicker reference.

Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.

Attributes
ACN	1746392
Time
Date	202006
Local Time Of Day	1801-2400
Place
Locale Reference	IAD.Tower
State Reference	VA
Environment
Flight Conditions	VMC
Light	Dusk
Aircraft 1
Make Model Name	Commercial Fixed Wing
Operating Under FAR Part	Part 121
Flight Phase	Final Approach
Route In Use	Visual Approach
Flight Plan	IFR
Person 1
Function	Local Supervisor / CIC
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (mon) 6
Events
Anomaly	ATC Issue All Types Airspace Violation All Types

A controller working local control combined with controller in charge reported an aircraft reported sighting a drone in their airspace but was unable to find the appropriate checklists to report the incident according to the rules.