Skylane 182/RG Turbo Skylane/RG
Air Traffic Control Fully Certified
Communication Breakdown
ATC Issue All Types
General None Reported / Taken
Human Factors; Procedure
While working Local Control 2 this morning a plane landed and exited Runway 17 at A2. Local Control 1 asked to cross the aircraft but was instructed to hold short. Shortly after the plane stopped at A2; an airport vehicle asked over the frequency if we had just landed an aircraft on Runway 17 and stated that 17/35 is closed. The airport vehicle was initially instructed to standby while I stated to the supervisor and Local Control 1 Controller that the airport vehicle asked if we landed a plane on 17/35. My response back to the airport vehicle was to call the Tower for clarification. Problem: This is one of many airports where secondary operations (painting; sandblasting; sweeping; inspections) are given priority; by issuing NOTAMs to close movement areas; over the primary operation (landing and departing aircraft). [We need to] schedule secondary operations outside of the normal flying hours of the airport. Scheduling secondary operations outside of normal flying hours would drastically reduce the work load put on controllers while secondary operations are taking place. Additionally; the probability for a similar incident to happen; as described above; would be decreased significantly as traffic outside of normal flying hours is almost nonexistent. Operations vehicles are not standard with the frequency they contact the Tower on - Ground Control; Local Control 1; Local Control 2. Have all vehicles operating on the movement area contact Tower on a set frequency. Having vehicles randomly contact the Tower on numerous frequencies reduces the situational awareness of the pilots; controllers and vehicles operating on the airport.
I was working the Local Control 1 position when a C182 called inbound for landing I instructed him to enter a right base for Runway 17; After scanning the runway from the intersection of Runway 8L north; I cleared the C182 to land and hold short of Runway 8L. A few minutes later the Local Control 2 Controller told me that an airport vehicle inquired as to if someone had landed an aircraft on Runway 17/35; I told him then that I had; and it came to my attention then; that the runway was closed due to personnel and equipment working on the south end; on the numbers of Runway 35. I do not recall being briefed that the runway was closed but may have missed it in the brief. I have not listened to the tapes. We have a strip indicating 'Runway Closed' to put in strip bay. But this was not in place. The 'RID' (Runway Incursion Devise) was active in silent mode and I apparently had missed this. Another reason why I may have missed this; is the area that the men and equipment were working is not Local Control 1's area of responsibility; as this portion of the runway belongs to Ground Control per our SOP. So under even normal working conditions I would not scan this portion of the runway unless I made special coordination to use full length. Also due to the high intensity of aircraft taxing across the runway around the workers I never noticed them. Well if I missed the closure in the briefing then paying closer attention during the briefing is most important. As I said I have not listened to the tapes so am unaware at this time if the closure was included in the brief. Had the 'Runway closed' strip been in the strip bay this would most likely have made me aware of the closure. Although my traffic had slowed at the time of this event; we are normally very busy during this period; the city has chosen to work on the Runway during our busiest time of the day.
PUB Controller described a closed runway landing event; listing failed internal Tower coordination as a contributing factor.