37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1023373 |
Time | |
Date | 201207 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | PUB.Airport |
State Reference | CO |
Aircraft 1 | |
Make Model Name | Skylane 182/RG Turbo Skylane/RG |
Operating Under FAR Part | Part 91 |
Flight Phase | Landing |
Route In Use | None |
Flight Plan | VFR |
Person 1 | |
Function | Local |
Qualification | Air Traffic Control Fully Certified |
Person 2 | |
Function | Local |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types |
Narrative:
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.
Original NASA ASRS Text
Title: PUB Controller described a closed runway landing event; listing failed internal Tower coordination as a contributing factor.
Narrative: 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.
Data retrieved from NASA's ASRS site as of July 2013 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.