37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1289265 |
Time | |
Date | 201508 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | HCF.TRACON |
State Reference | HI |
Environment | |
Light | Night |
Aircraft 1 | |
Make Model Name | Large Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach |
Route In Use | Visual Approach |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Large Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Final Approach |
Route In Use | Other Instrument Approach |
Flight Plan | IFR |
Person 1 | |
Function | Approach |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 21 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
Narrative:
I was working R5 combined with D5 when I issued aircraft X a visual approach to runway 17 at koa airport. Koa airport is served by a contract tower and as such has absolutely no authority to provide radar service to any aircraft. After vectoring aircraft Y off of its assigned routing to achieve the proper spacing to follow aircraft X; I then cleared aircraft Y for an ILS runway 17 approach with aircraft Y approximately 7-8 miles in trail of aircraft X to runway 17. I switched aircraft X to koa tower frequency about 15 miles from the airport. I then proceeded to update and 'stuff' my flight progress strips. When I turned my attention back to the radar scope; I noticed that aircraft X was now proceeding directly eastbound across final and not towards the airport. This resulted in a rapidly decreasing amount of separation between this now eastbound aircraft X and the aircraft Y that was inbound on the localizer course. I proceeded to call traffic to aircraft Y and this aircraft reported the aircraft X in sight. I then recleared aircraft Y for a visual approach to runway 17 with the restriction to follow aircraft X. I then called the supervisor over to observe what was occurring. The supervisor noted that it appeared that koa tower may have turned aircraft X to follow a VFR aircraft that was inbound to koa. Next I measured the distance between these 2 aircraft and now there was less than 5 miles. After being relieved from position I discussed this situation with the supervisor and he relayed to me that he had talked to the 'controller' at koa tower. The koa controller said he turned aircraft X because a VFR cessna checked in on tower frequency 'kind of late'. The koa controller tried to explain his actions and justify what he did by stating that he had both aircraft X and aircraft Y in sight. This is absolutely irrelevant in the fact that koa tower has absolutely no authority to ever vector or slow down (both require radar qualification) an IFR aircraft. As is obvious in this situation; the reason being that it may result in a loss of IFR separation to subsequent aircraft that are also inbound to the airport.these types of occurrences have been happening at koa tower for years. If the FAA was really interested in safety and efficiency of flight; then they would make the airspace around koa a class C. They would install an ASR radar; hire radar qualified controllers to staff koa tower; and establish an approach control sector to work the traffic. But instead; they develop dva's [diverse vector areas] that do not meet any of the criteria necessary for creating dva's and insist that radar procedures can be used when the radar being used at koa is an ARSR with no primary radar capabilities. Also; the controllers at koa tower need to be briefed that they are not now; nor will they ever be in the near future allowed to provide radar service to aircraft.
Original NASA ASRS Text
Title: HCF Controller described a situation where the KOA Tower Controller vectored an aircraft to avoid another. KOA controllers are not allowed to provide vectors and this led to a loss of separation with an inbound aircraft.
Narrative: I was working R5 combined with D5 when I issued Aircraft X a visual approach to Runway 17 at KOA airport. KOA airport is served by a contract tower and as such has absolutely no authority to provide radar service to any aircraft. After vectoring Aircraft Y off of its assigned routing to achieve the proper spacing to follow Aircraft X; I then cleared Aircraft Y for an ILS Runway 17 approach with Aircraft Y approximately 7-8 miles in trail of Aircraft X to Runway 17. I switched Aircraft X to KOA tower frequency about 15 miles from the airport. I then proceeded to update and 'stuff' my flight progress strips. When I turned my attention back to the radar scope; I noticed that Aircraft X was now proceeding directly eastbound across final and not towards the airport. This resulted in a rapidly decreasing amount of separation between this now eastbound Aircraft X and the Aircraft Y that was inbound on the localizer course. I proceeded to call traffic to Aircraft Y and this aircraft reported the Aircraft X in sight. I then recleared Aircraft Y for a visual approach to Runway 17 with the restriction to follow Aircraft X. I then called the supervisor over to observe what was occurring. The supervisor noted that it appeared that KOA tower may have turned Aircraft X to follow a VFR aircraft that was inbound to KOA. Next I measured the distance between these 2 aircraft and now there was less than 5 miles. After being relieved from position I discussed this situation with the supervisor and he relayed to me that he had talked to the 'controller' at KOA tower. The KOA controller said he turned Aircraft X because a VFR Cessna checked in on tower frequency 'kind of late'. The KOA controller tried to explain his actions and justify what he did by stating that he had both Aircraft X and Aircraft Y in sight. This is absolutely irrelevant in the fact that KOA tower has absolutely no authority to ever vector or slow down (both require radar qualification) an IFR aircraft. As is obvious in this situation; the reason being that it may result in a loss OF IFR separation to subsequent aircraft that are also inbound to the airport.These types of occurrences have been happening at KOA tower for years. If the FAA was really interested in safety and efficiency of flight; then they would make the airspace around KOA a Class C. They would install an ASR radar; hire radar qualified controllers to staff KOA tower; and establish an approach control sector to work the traffic. But instead; they develop DVA's [Diverse Vector Areas] that do not meet any of the criteria necessary for creating DVA's and insist that radar procedures can be used when the radar being used at KOA is an ARSR with no primary radar capabilities. Also; the controllers at KOA tower need to be briefed that they are not now; nor will they ever be in the near future allowed to provide radar service to aircraft.
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.