37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1158518 |
Time | |
Date | 201403 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Dusk |
Aircraft 1 | |
Make Model Name | Skyhawk 172/Cutlass 172 |
Operating Under FAR Part | Part 91 |
Flight Phase | Final Approach |
Route In Use | Other Instrument Approach |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Fighting Falcon F16 |
Operating Under FAR Part | Part 91 |
Flight Phase | Final Approach |
Route In Use | Visual Approach |
Flight Plan | IFR |
Person 1 | |
Function | Ground |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 27 |
Events | |
Anomaly | ATC Issue All Types Conflict NMAC Deviation - Procedural Published Material / Policy |
Miss Distance | Horizontal 250 Vertical 0 |
Narrative:
I was working ground control; weather was VFR and traffic was light to moderate with no adverse conditions. Training was being accomplished on the east arrival/departure position. I had recently relieved the ground controller and the previous controller was still in the cab as well as the local controller. I saw that local control had a UH60 helicopter landing at the ramp located on the northeast side of the departure end of runway 33 (active runway). Runway 1 was also active and I also noticed an IFR cessna on a VOR 1 approach that was planning a published missed approach. The pm takes the aircraft directly across runway 33 climbing from 800 to 3;200 ft. I looked up and saw a flight of two F16's on a 1-2 mile initial descending out of 2;300 ft for the 1;800 ft break. I thought a collision could occur and asked the local control what he was doing. He said nothing and I told him to turn the cessna to a 270 heading immediately and he started to coordinate with radar first. I told him again to turn the aircraft immediately which he did. The local controller is my trainee on radar so he did what I told him to do!! The other controller in the tower was also telling him to turn the cessna. The cessna started his turn and the F16's started the break with zero vertical separation and maybe 200-300 ft lateral. A minute later another flight of F16's came in for the overhead approach and if the cessna had happened to miss the first 2 fighters; the 2nd two might not have. The procedure at this airport is the F16's are IFR until they reach initial which is 3-5 miles on final. The cessna was IFR though and his climb-out instructions totally conflicted with any overhead pattern. Because of all three aircraft being in a wing up attitude; I am not sure any of them saw another.at least 3 sets of eyes (radar instructor; radar trainee; and local controller) had to have seen this confliction developing. The tag on the cessna was V1P (VOR 1 approach with published missed approach). The F16's were tagged O3. (Overhead approach to runway 33); well in advance. If I was looking it would be apparent there was a problem brewing. The radar controllers made no attempt to correct the error. You should get at least 5 reports on this event. The 3 people in the tower and at least 2 in the radar room. It is a known event as I saw the radar replay. I hate to say it but the instructor in the radar room has had issues (near midair collision/oe's) with F16's on several occasions in the past 2 years. Also; management was aware of this event and left the controller and trainee on position for nearly another hour after the event.
Original NASA ASRS Text
Title: A Ground Controller in Class C airspace observes a near-miss between a C172 and 2/F16's and provides Local Control input to help resolve the situation.
Narrative: I was working Ground Control; weather was VFR and traffic was light to moderate with no adverse conditions. Training was being accomplished on the East Arrival/Departure position. I had recently relieved the Ground Controller and the previous controller was still in the cab as well as the Local Controller. I saw that LC had a UH60 Helicopter landing at the ramp located on the northeast side of the departure end of Runway 33 (active runway). Runway 1 was also active and I also noticed an IFR Cessna on a VOR 1 Approach that was planning a Published Missed Approach. The PM takes the aircraft directly across Runway 33 climbing from 800 to 3;200 FT. I looked up and saw a flight of two F16's on a 1-2 mile initial descending out of 2;300 FT for the 1;800 FT break. I thought a collision could occur and asked the LC what he was doing. He said nothing and I told him to turn the Cessna to a 270 heading immediately and he started to coordinate with radar first. I told him again to turn the aircraft immediately which he did. The Local Controller is my trainee on radar so he did what I told him to do!! The other Controller in the Tower was also telling him to turn the Cessna. The Cessna started his turn and the F16's started the break with zero vertical separation and maybe 200-300 FT lateral. A minute later another flight of F16's came in for the overhead approach and if the Cessna had happened to miss the first 2 fighters; the 2nd two might not have. The procedure at this airport is the F16's are IFR until they reach initial which is 3-5 miles on final. The Cessna was IFR though and his climb-out instructions totally conflicted with any overhead pattern. Because of all three aircraft being in a wing up attitude; I am not sure any of them saw another.At least 3 sets of eyes (Radar Instructor; Radar Trainee; and Local Controller) had to have seen this confliction developing. The tag on the Cessna was V1P (VOR 1 Approach with Published Missed Approach). The F16's were tagged O3. (Overhead Approach to Runway 33); well in advance. If I was looking it would be apparent there was a problem brewing. The radar controllers made no attempt to correct the error. You should get at least 5 reports on this event. The 3 people in the tower and at least 2 in the radar room. It is a known event as I saw the radar replay. I hate to say it but the instructor in the radar room has had issues (NMAC/OE's) with F16's on several occasions in the past 2 years. Also; management was aware of this event and left the controller and trainee on position for nearly another hour after the event.
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.