37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1492389 |
Time | |
Date | 201710 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZZZ.ARTCC |
State Reference | US |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Helicopter |
Flight Phase | Descent |
Route In Use | None VFR Route |
Flight Plan | VFR |
Aircraft 2 | |
Make Model Name | Medium Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 91 |
Flight Phase | Takeoff |
Route In Use | None |
Flight Plan | IFR |
Person 1 | |
Function | Other / Unknown |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 1.0 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy |
Narrative:
I had been monitoring local control for about 15 minutes at the time of the event. The supervisor took the local control position then had a trainee sign on position with him. Aircraft X was a helicopter that was inbound from the north to land on a helipad. As the helicopter was approaching the airport from the north local control issued a clearance to remain east of the runway and cleared him to land on a helipad and then departed aircraft Y. Looking out of the window I would estimate the two aircraft separated by less than 200 feet diagonally opposite direction. I don't believe I heard traffic calls to either aircraft. I looked at a falcon radar replay afterward but it was not useful; our radar is being worked on and is not useful below 400 feet.the supervisor began asking about this when aircraft X was well north of the airport; but he did not stop the loss of separation. He just told the trainer that he should keep a close eye on the aircraft. It was very hard to hear their conversation from where I was located. This is a loss of separation in accordance with facility directives. This is worthy to mention because many of the other reports I have filed on the violation of these standards are from this supervisor's crew. He either does not understand or maybe does not enforce the requirements set forth by NTSB; wsa qcg; and our district after several high profile incidents in this notice.I decided to speak to the supervisor when he came down from the cab. It did not go well. He stated that the directive was stupid; then he told me that I was doing a internal review in the cab. I told him I was just monitoring for my required familiarization time. He said he had to leave and shouted as he walked down the hallway; 'then you better report this to ...'; the air traffic manager. I told him 'I am speaking to you; I don't need to report it to anyone else'. He shouted it again as he walked into the elevator.clearly there is an issue. I am not sure how to approach this. I am a support specialist. He is management. If the workforce thinks that I am upstairs spying on them; they can easily not allow us to get my required monitor time. Help. I think I just identified the reason our facilities performance has not been improving as much as it should have by now. The supervisor needs to be made to comply with requirements or requirements need to be changed. In my opinion the requirements are reasonable and safe they should not be changed.
Original NASA ASRS Text
Title: A Tower System Support Specialist observed the Local Controller allow a simultaneous helicopter arrival and aircraft departure in violation of facility directives.
Narrative: I had been monitoring Local Control for about 15 minutes at the time of the event. The Supervisor took the Local Control position then had a trainee sign on position with him. Aircraft X was a helicopter that was inbound from the north to land on a helipad. As the helicopter was approaching the airport from the North Local Control issued a clearance to remain east of the runway and cleared him to land on a helipad and then departed Aircraft Y. Looking out of the window I would estimate the two aircraft separated by less than 200 feet diagonally opposite direction. I don't believe I heard traffic calls to either aircraft. I looked at a FALCON radar replay afterward but it was not useful; our Radar is being worked on and is not useful below 400 feet.The Supervisor began asking about this when Aircraft X was well north of the airport; but he did not stop the loss of separation. He just told the Trainer that he should keep a close eye on the aircraft. It was very hard to hear their conversation from where I was located. This is a loss of separation in accordance with facility Directives. This is worthy to mention because many of the other reports I have filed on the violation of these standards are from this Supervisor's crew. He either does not understand or maybe does not enforce the requirements set forth by NTSB; WSA QCG; and our District after several high profile incidents in this notice.I decided to speak to the Supervisor when he came down from the cab. It did not go well. He stated that the directive was stupid; then he told me that I was doing a Internal Review in the cab. I told him I was just monitoring for my required familiarization time. He said he had to leave and shouted as he walked down the hallway; 'then you better report this to ...'; the Air Traffic Manager. I told him 'I am speaking to you; I don't need to report it to anyone else'. He shouted it again as he walked into the elevator.Clearly there is an issue. I am not sure how to approach this. I am a Support Specialist. He is management. If the workforce thinks that I am upstairs spying on them; they can easily not allow us to get my required monitor time. Help. I think I just identified the reason our facilities performance has not been improving as much as it should have by now. The Supervisor needs to be made to comply with requirements or requirements need to be changed. In my opinion the requirements are reasonable and safe they should not be changed.
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.