37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1628813 |
Time | |
Date | 201903 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZZZ.Tower |
State Reference | US |
Aircraft 1 | |
Make Model Name | Military |
Operating Under FAR Part | Part 91 |
Route In Use | Visual Approach |
Flight Plan | VFR |
Aircraft 2 | |
Make Model Name | Military |
Operating Under FAR Part | Part 91 |
Flight Plan | VFR |
Person 1 | |
Function | Other / Unknown |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 7 |
Events | |
Anomaly | ATC Issue All Types Airspace Violation All Types Conflict NMAC Deviation - Procedural Published Material / Policy |
Narrative:
Today; [an aerial demonstration team was] practicing for the air show. Their tfr significantly encroached on our airspace leaving us with no room for go-arounds. Aircraft X went around on his own and got very close to one of the [aerial demonstration team's aircraft]. I don't know how close; but if I were able to file an near midair collision; I would.none of this was briefed to us. We had no idea what the procedures were supposed to be while this tfr was in effect. We were using runway 29 for arrivals and runway 21 for departures; but we had to figure that out for ourselves. We were playing completely by ear and pretty much just hoping to get through the demo. Two controllers worked well over two hours in position and one controller stayed late because he had no one to relieve him. The tfr also was not reflected in the notams. A tfr that didn't really affect us was [in the notams]; but the one that was in effect was not; at least to my knowledge.this seems pretty obvious. When something like an air show is imminent; the controllers should receive thorough briefings on the temporary procedures and be given the opportunity to express concerns and ask questions.
Original NASA ASRS Text
Title: Tower Controller reported an NMAC that was attributed to procedures that were not clear to the reporter relating to a TFR and go-around procedures.
Narrative: Today; [an aerial demonstration team was] practicing for the air show. Their TFR significantly encroached on our airspace leaving us with no room for go-arounds. Aircraft X went around on his own and got VERY close to one of the [aerial demonstration team's aircraft]. I don't know how close; but if I were able to file an NMAC; I would.None of this was briefed to us. We had no idea what the procedures were supposed to be while this TFR was in effect. We were using Runway 29 for arrivals and Runway 21 for departures; but we had to figure that out for ourselves. We were playing completely by ear and pretty much just hoping to get through the demo. Two controllers worked well over two hours in position and one controller stayed late because he had no one to relieve him. The TFR also was not reflected in the NOTAMs. A TFR that didn't really affect us was [in the NOTAMs]; but the one that was in effect was not; at least to my knowledge.This seems pretty obvious. When something like an air show is imminent; the controllers should receive thorough briefings on the temporary procedures and be given the opportunity to express concerns and ask questions.
Data retrieved from NASA's ASRS site 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.