Narrative:

I started the shift as controller in charge; my co-worker at local control 2; with all positions combined. I took the local control 2 position and received a briefing which included; airport runway closures; 16R/34L; 8/26; 16L/34R. I gave the position to a relieving controller; briefing included all runways except 16R/34L closed; this was a normal long term closure. Shortly after I was asked why there was a vehicle on runway 35R/17L. I told the flm I was not aware of any and that runway 35R was open all morning. Here is what happened as I know it. Airport operations planned and issued a NOTAM for a runway 35R closure for the evening; however; it never got passed along to the current shift crew. Airport operations was conducting practice snow removal on multiple runways. Airport operations asked permission to enter runway 35R for snow removal practice and it was granted. Later operations reported clear of runway 35R. After; it was discovered operations had been on and off the runway as if it were closed. The city claimed when they reported clear they also stated the runway would remain closed. Normal procedure would be for operations to request the closure; and the controller would read back runway 35R closed; and take care of the runway lighting placards and ATIS and TRACON notifications. All the controller heard was; 'we're clear of runway 35R.' recommendation; educate the airport on proper runway closed phraseology; require the use of hold bar activation when runways are closed. Develop a system that would ensure relieving flm/controller in charge are informed of all pending runway closures.

Related reports:

Google
 

Original NASA ASRS Text

Title: DEN Controller described confused communications with airport operators regarding the status of a runway being used for practice snow removal; the reporter claiming proper closure phraseology was not used by airport personnel.

Narrative: I started the shift as CIC; my co-worker at Local Control 2; with all positions combined. I took the Local Control 2 position and received a briefing which included; airport runway closures; 16R/34L; 8/26; 16L/34R. I gave the position to a relieving controller; briefing included all runways except 16R/34L closed; this was a normal long term closure. Shortly after I was asked why there was a vehicle on Runway 35R/17L. I told the FLM I was not aware of any and that Runway 35R was open all morning. Here is what happened as I know it. Airport Operations planned and issued a NOTAM for a Runway 35R closure for the evening; however; it never got passed along to the current shift crew. Airport Operations was conducting practice snow removal on multiple runways. Airport Operations asked permission to enter Runway 35R for snow removal practice and it was granted. Later Operations reported clear of Runway 35R. After; it was discovered Operations had been on and off the runway as if it were closed. The city claimed when they reported clear they also stated the runway would remain closed. Normal procedure would be for Operations to request the closure; and the Controller would read back RUNWAY 35R closed; and take care of the runway lighting placards and ATIS and TRACON notifications. All the Controller heard was; 'we're clear of Runway 35R.' Recommendation; educate the airport on proper runway closed phraseology; require the use of HOLD BAR activation when runways are closed. Develop a system that would ensure relieving FLM/CIC are informed of all pending runway closures.

Data retrieved from NASA's ASRS site as of April 2012 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.