Tower front line manager reported a runway incursion and concerns with the local controller not issu...

Narrative:

I was the flm on duty in the tower cab providing ojti to a cpc at the time of the incident. I was explaining mors (mandatory occurrence report) and significant events notifications and showing the cpc where to find the contact numbers. Traffic was light and there were only two positions open as per the covid staffing; LC1/LC2/la were combined as clearance delivery/FD/ground control were also combined. I had one other person on a break.while giving instruction and demonstrating required activity for significant mors to the cpc; I heard the asde-X alarm 'runway xr go-around' I immediately looked up and scanned runway xr to assess the situation and determine what caused the alarm. I observed aircraft Y; 1/2 mile final landing on runway xr and a small GA aircraft on taxiway [5] turning south on taxiway [3]. I didn't observe any other targets or obstructions on the runway surface area. At that time aircraft Y was already flaring out on the runway. I then asked the local control controller why wasn't aircraft Y sent around. The controller responded; 'the other aircraft cleared the runway.' I then informed the controller if the safety logic says to send someone around on a runway which the aircraft was landing it was mandatory to comply. The controller advised me that they thought it was safer to land than send the aircraft around. I then informed the controller that we are obligated to send the aircraft around per the JO7110.65 and if the pilot decided to land anyway then I would have a conversation with the pilot.remind controllers that the safety logic overrides same runway separation and that it's mandatory to comply with the safety logic instructions. I did have this conversation with my crew after the incident and was shocked to know they weren't aware of this and thought it was a discretionary decision.

Original NASA ASRS Text

Title: Tower Front Line Manager reported a runway incursion and concerns with the Local Controller not issuing a go-around instruction to an aircraft landing on the same runway.

Narrative: I was the FLM on duty in the Tower cab providing OJTI to a CPC at the time of the incident. I was explaining MORs (Mandatory Occurrence Report) and significant events notifications and showing the CPC where to find the contact numbers. Traffic was light and there were only two positions open as per the COVID staffing; LC1/LC2/LA were combined as CD/FD/GC were also combined. I had one other person on a break.While giving instruction and demonstrating required activity for significant MORs to the CPC; I heard the ASDE-X alarm 'Runway XR go-around' I immediately looked up and scanned Runway XR to assess the situation and determine what caused the alarm. I observed Aircraft Y; 1/2 mile final landing on Runway XR and a small GA aircraft on Taxiway [5] turning South on Taxiway [3]. I didn't observe any other targets or obstructions on the runway surface area. At that time Aircraft Y was already flaring out on the runway. I then asked the LC Controller why wasn't Aircraft Y sent around. The Controller responded; 'The other aircraft cleared the runway.' I then informed the Controller if the safety logic says to send someone around on a runway which the aircraft was landing it was mandatory to comply. The Controller advised me that they thought it was safer to land than send the aircraft around. I then informed the Controller that we are obligated to send the aircraft around per the JO7110.65 and if the pilot decided to land anyway then I would have a conversation with the pilot.Remind controllers that the safety logic overrides same runway separation and that it's mandatory to comply with the safety logic instructions. I did have this conversation with my crew after the incident and was shocked to know they weren't aware of this and thought it was a discretionary decision.

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	1767753
Time
Date	202010
Local Time Of Day	1801-2400
Place
Locale Reference	ZZZ.Tower
State Reference	US
Aircraft 1
Make Model Name	Small Aircraft High Wing 1 Eng Fixed Gear
Operating Under FAR Part	Part 91
Flight Phase	Taxi
Route In Use	None
Flight Plan	VFR
Aircraft 2
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	Supervisor / CIC
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 15
Events
Anomaly	ATC Issue All Types Deviation - Procedural Published Material / Policy Ground Incursion Runway

Tower front line manager reported a runway incursion and concerns with the local controller not issuing a go-around instruction to an aircraft landing on the same runway.