 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Tower controller witnessed a conflict involving a corporate jet arrival and a departing helicopter; questioning the local controllers lack of positive action.
| Attributes | |
| ACN | 886722 |
| Time | |
| Date | 201005 |
| Local Time Of Day | 1801-2400 |
| Place | |
| Locale Reference | ZZZ.Airport |
| State Reference | US |
| Aircraft 1 | |
| Make Model Name | Helicopter |
| Flight Phase | Cruise |
| Aircraft 2 | |
| Make Model Name | HS 125 Series |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Landing |
| Route In Use | Visual Approach |
| Flight Plan | IFR |
| Person 1 | |
| Function | Flight Data / Clearance Delivery |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy |
Narrative:
I was working clearance delivery; and had just completed relief briefing when I looked out window and noticed a helicopter on an east southeast track; fly nearly directly over a hawker on about a 1-2 mile final for runway xxl. About the same time ground controller (who was wearing two hats; as he was also the controller in charge) noticed the same thing; and spoke up to local controller about the traffic. Local controller then issued traffic to the helicopter but looking out the window it was obvious that they already had passed. I don't know if the targets actually merged on the radar. When I first noticed it; my first thought was that local controller must have issued the traffic and the helicopter must have been providing his own visual separation. But after local controller issued the late (inaccurate) traffic advisory; it became apparent that local controller wasn't utilizing positive separation; and to the best of my recollection; they probably had only 200 to 300 ft vertical separation. Looking out the window it didn't appear that either aircraft attempted any avoidance maneuver. Staff the cab supervisor position instead of combining it with another position. It is rare that we see a supervisor in the cab.
Original NASA ASRS Text
Title: Tower Controller witnessed a conflict involving a corporate jet arrival and a departing helicopter; questioning the Local Controllers lack of positive action.
Narrative: I was working Clearance Delivery; and had just completed relief briefing when I looked out window and noticed a helicopter on an east southeast track; fly nearly directly over a Hawker on about a 1-2 mile final for Runway XXL. About the same time Ground Controller (who was wearing two hats; as he was also the Controller In Charge) noticed the same thing; and spoke up to Local Controller about the traffic. Local Controller then issued traffic to the helicopter but looking out the window it was obvious that they already had passed. I don't know if the targets actually merged on the RADAR. When I first noticed it; my first thought was that Local Controller must have issued the traffic and the helicopter must have been providing his own visual separation. But after Local Controller issued the late (inaccurate) traffic advisory; it became apparent that Local Controller wasn't utilizing positive separation; and to the best of my recollection; they probably had only 200 to 300 FT vertical separation. Looking out the window it didn't appear that either aircraft attempted any avoidance maneuver. Staff the Cab Supervisor position instead of combining it with another position. It is rare that we see a supervisor in the cab.
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.