Regional Jet 200 ER/LR (CRJ200)
Air Traffic Control Fully Certified
Workload
Deviation / Discrepancy - Procedural Other / Unknown; Inflight Event / Encounter Weather / Turbulence
General None Reported / Taken
Staffing; Procedure; Human Factors
I was working the North Local position on the Runway 12L/R configuration. Weather was snow/sleet IFR; low visibility; low ceilings. Air Carrier Z (A320) landed and was slow to exit at Papa 4; I asked the pilot how the braking action at Papa 4 was; [and] I received a poor report past the Papa 4 intersection. I then instructed the pilot to contact Ground Control. My next landing aircraft was Air Carrier X (CRJ) which I cleared to land with a poor braking action report past Papa 4. Air Carrier Z changed his braking action report to 'NILL' on the Ground Control frequency. I recall hearing the 'NILL' report from the Ground Controller just as Air Carrier X was flaring out. Since all my arrivals had exited Runway 12L prior to Papa 4. I thought the runway was still safe to use prior to that intersection; at least for this last arrival since they were close in on final. I issued the 'NILL' braking report to Air Carrier Y past the Papa 4 intersection; and cleared them to land. Air Carrier Y exited Runway 12L prior to Papa 4 with no problem. I then recall hearing the airport manager closing Runway 12L. There was a lot going on at my North Local position at this time; wind; weather; low ceilings; compression on final; braking action advisories; watching the required staggered separation on our close parallels; and scanning the runway as well. As always it's always good to have a second pair off eyes when air traffic is complex; which it is at ZZZ. I feel a dedicated local coordinator position during busy traffic would be a great asset to each of our local positions.
Tower Controller chronicled a poor braking action landing event when the exact nature and location of the poor braking was confused and another aircraft was cleared to land; shortly after the runway was closed.