 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Tower controller in charge observed a takeoff clearance being cancelled and an airport vehicle on the departure runway. The reporter noted the controller apparently failed to scan the runway prior to issuing the takeoff clearance.
| Attributes | |
| ACN | 1058669 |
| Time | |
| Date | 201301 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ZZZ.Airport |
| State Reference | US |
| Aircraft 1 | |
| Make Model Name | Super King Air 300 |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Takeoff |
| Route In Use | None |
| Flight Plan | IFR |
| Person 1 | |
| Function | Supervisor / CIC Flight Data / Clearance Delivery |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy Ground Event / Encounter Vehicle Ground Incursion Runway |
Narrative:
I was working clearance delivery and controller in charge. I had turned around to make changes to the art to reflect the correct position assignments. The local controller was a newly certified controller. Traffic was very light. Runway 4L operations had been suspended for snow removal along the outer edges. One airport operations vehicle and two snow plows were on runway 4L. The local controller had been told during the relief briefing of the runway 4L operations and had the 'runway buster' in the correct position. The BE30 had been taxied to runway 36 for departure. The local controller instructed the BE30 to cross runway 36 and cleared him for take off. A couple of seconds later I heard the local controller scream 'cancel takeoff clearance.' at that time I turned around to see what was happening. A BE30 came to a stop about 2;000 ft down the runway; and one of the snow plows was exiting the runway near mid field. Once all vehicles had cleared the runway; the BE30 was cleared for takeoff. Scanning the runway would have prevented this from occurring. More importantly; the BE30 could have been cleared for takeoff on runway 36; as there was nothing preventing it.
Original NASA ASRS Text
Title: Tower CIC observed a takeoff clearance being cancelled and an airport vehicle on the departure runway. The reporter noted the Controller apparently failed to scan the runway prior to issuing the takeoff clearance.
Narrative: I was working Clearance Delivery and CIC. I had turned around to make changes to the ART to reflect the correct position assignments. The Local Controller was a newly certified Controller. Traffic was very light. Runway 4L operations had been suspended for snow removal along the outer edges. One airport operations vehicle and two snow plows were on Runway 4L. The Local Controller had been told during the relief briefing of the Runway 4L operations and had the 'runway buster' in the correct position. The BE30 had been taxied to Runway 36 for departure. The Local Controller instructed the BE30 to cross Runway 36 and cleared him for take off. A couple of seconds later I heard the Local Controller scream 'Cancel Takeoff Clearance.' At that time I turned around to see what was happening. A BE30 came to a stop about 2;000 FT down the runway; and one of the snow plows was exiting the runway near mid field. Once all vehicles had cleared the runway; the BE30 was cleared for takeoff. Scanning the runway would have prevented this from occurring. More importantly; the BE30 could have been cleared for takeoff on Runway 36; as there was nothing preventing it.
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.