 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
A bur local controller issued go around instructions to traffic landing runway 33 when takeoff cancellation clearance to an air carrier on runway 26 was not acknowledged. A delayed release from sct initiated the events.
| Attributes | |
| ACN | 880345 |
| Time | |
| Date | 201003 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | BUR.Tower |
| State Reference | CA |
| Aircraft 1 | |
| Make Model Name | Commercial Fixed Wing |
| Operating Under FAR Part | Part 121 |
| Flight Phase | Landing |
| Route In Use | Visual Approach |
| Flight Plan | IFR |
| Person 1 | |
| Function | Local |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Conflict Ground Conflict Less Severe Deviation - Procedural Published Material / Policy |
Narrative:
Air carrier X was issued a landing clearance on runway 33 and was short final. Air carrier Y was holding in position on runway 26 for an IFR release from sct. Sct had given us an estimate for release time and I put air carrier Y in position anticipating a release from the time given to me by sct; the time came and went. I tried multiple times to get an update from sct and had the controller in charge call for an update. Per our LOA with sct; they are supposed to give us estimated times for IFR releases and were not communicating with us. I believe they were training. I finally got the release and cleared air carrier Y for take off without delay on runway 26 and told him of traffic mile final for runway 33. Air carrier Y acknowledged takeoff clearance but did not roll in a timely manner. I then canceled his takeoff clearance and told him to hold in position. Air carrier Y did not acknowledge his cancellation and then started to roll. Air carrier X was short final and had to go around. I should have held air carrier Y in position until air carrier X landed.
Original NASA ASRS Text
Title: A BUR local controller issued go around instructions to traffic landing Runway 33 when takeoff cancellation clearance to an air carrier on Runway 26 was not acknowledged. A delayed release from SCT initiated the events.
Narrative: Air Carrier X was issued a landing clearance on Runway 33 and was short final. Air Carrier Y was holding in position on Runway 26 for an IFR release from SCT. SCT had given us an estimate for release time and I put Air Carrier Y in position anticipating a release from the time given to me by SCT; the time came and went. I tried multiple times to get an update from SCT and had the CIC call for an update. Per our LOA with SCT; they are supposed to give us estimated times for IFR releases and were not communicating with us. I believe they were training. I finally got the release and cleared Air Carrier Y for take off without delay on Runway 26 and told him of traffic mile final for Runway 33. Air Carrier Y acknowledged takeoff clearance but did not roll in a timely manner. I then CANCELED his takeoff clearance and told him to hold in position. Air Carrier Y did not acknowledge his cancellation and then started to roll. Air Carrier X was short final and had to go around. I should have held Air Carrier Y in position until Air Carrier X landed.
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.