 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Jfk tower controller reported an aircraft was using the incorrect frequency during handoff; which resulted in a conflict with another aircraft.
| Attributes | |
| ACN | 1705454 |
| Time | |
| Date | 201911 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | JFK.Airport |
| State Reference | NY |
| Aircraft 1 | |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| Flight Phase | Initial Approach |
| Route In Use | Vectors |
| Aircraft 2 | |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| Flight Phase | Initial Approach |
| Route In Use | Vectors |
| Person 1 | |
| Function | Local |
| Qualification | Air Traffic Control Fully Certified |
| Events | |
| Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy |
Narrative:
I was working the local 2 position; which entails working runway 31L off-loaded departures and cba (VFR/helicopter operation in the B). Local 1 is working runway 4R/left. Aircraft X appears to be vectoring in for runway 4L and checks in on my frequency; which is the wrong frequency as he should be with local 1. I switch him to that frequency. He then appears to be disoriented and is overshooting the finals. He's now in conflict with aircraft Y; an arrival for runway 4R. Neither of them appear to be local 1 or the approach controller. I double check on my frequency and they aren't on mine either. They finally come up on local 1 and the controller separates them both.I recommend that the approach controller ensures that aircraft are either established on course and are no longer a factor with other aircraft before switching frequencies because sometimes they go to the wrong frequencies or lose communication and can become a problem; so much so that it can create an accident.
Original NASA ASRS Text
Title: JFK Tower Controller reported an aircraft was using the incorrect frequency during handoff; which resulted in a conflict with another aircraft.
Narrative: I was working the Local 2 position; which entails working Runway 31L off-loaded departures and CBA (VFR/Helicopter Operation in the B). Local 1 is working Runway 4R/L. Aircraft X appears to be vectoring in for Runway 4L and checks in on my frequency; which is the wrong frequency as he should be with Local 1. I switch him to that frequency. He then appears to be disoriented and is overshooting the finals. He's now in conflict with Aircraft Y; an arrival for Runway 4R. Neither of them appear to be Local 1 or the Approach Controller. I double check on my frequency and they aren't on mine either. They finally come up on Local 1 and the Controller separates them both.I recommend that the Approach Controller ensures that aircraft are either established on course and are no longer a factor with other aircraft before switching frequencies because sometimes they go to the wrong frequencies or lose communication and can become a problem; so much so that it can create an accident.
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.