Narrative:

Aircraft X on VFR advisories on a converging course with aircraft Y on an IFR flight plan. Aircraft X was issued a 135 heading and instructed to intercept the shoreline and follow the shoreline to the field; for traffic [aircraft Y] inbound from the west. Aircraft X took the heading and continued on that until about 3 miles east for final; aircraft X was then observed making a south turn towards final; disregarding their issued instructions. Aircraft Y was on a visual approach and had been switched to the tower. I issued [aircraft Y] traffic to aircraft X and canceled advisories so they could switch coms to the tower.we need to make a procedural change that removes their glide-to-land restrictions over water or we need to find a way to make the restrictions stricter so that they cannot fly across the water in a single-engine aircraft. [Aircraft X company] is a consistent safety problem for us; we really don't have much control over them. When they are IFR; they complain that they cannot remain legal unless we keep them within a certain proximity of land due to their [type aircraft] single engine glide-to-land requirements; their preferred flight path is opposite direction to the arrivals and often creates a problem for us especially when vectoring multiple aircraft for sequence to final. If we put them on a vector for traffic that does not comply with their restrictions they cancel IFR and VFR advisories and resume own navigations as a rogue 1200 code flying right through our arrival corridor; forcing us to separate and often delay our IFR aircraft from a VFR aircraft that we have no control over. Because of this we often comply with their requests and issue vectors that allow them to remain within their glide-to-land; rather than deal with a VFR aircraft that we have no control over and cannot predict their actions; but this increases our work load tremendously as we typically wouldn't put aircraft head-on with each other as part of our normal operations. This also leads to problems for the IFR inbounds trying to make a stable descent to the runway. We often have to delay their descent so they can top the [company] aircraft; which leads to an unstable quick descent for them. As you can also see by my report; they disregard ATC instructions when on VFR advisories without notifying us. In short; we don't have much of a fighting chance to keep our operations safe with aircraft X company flying around as they do. This is an ongoing everyday problem at hcf which leads to high-tensions and hostility between our controllers and aircraft X company pilots as well as other pilots and aircraft X company pilots that often have to deal with delays; RA's; and general unsafe situations to accommodate for a single air carrier that is unwilling to play by the same rules that everyone else does.

Related reports:

Google
 

Original NASA ASRS Text

Title: HCF Controller reported about a conflict between a small aircraft and a large aircraft that came close together. According to the reporter this happens all time and is because of a procedure the small aircraft company uses. The small aircraft does not have required over water equipment and tries to stay close to shore causing conflict with arriving and departing aircraft. Controller wants the company to play by the same rules as everyone else.

Narrative: Aircraft X on VFR advisories on a converging course with Aircraft Y on an IFR flight plan. Aircraft X was issued a 135 heading and instructed to intercept the shoreline and follow the shoreline to the field; for traffic [Aircraft Y] inbound from the west. Aircraft X took the heading and continued on that until about 3 miles east for final; Aircraft X was then observed making a south turn towards final; disregarding their issued instructions. Aircraft Y was on a visual approach and had been switched to the tower. I issued [Aircraft Y] traffic to Aircraft X and canceled advisories so they could switch coms to the tower.We need to make a procedural change that removes their glide-to-land restrictions over water or we need to find a way to make the restrictions stricter so that they cannot fly across the water in a single-engine aircraft. [Aircraft X Company] is a consistent safety problem for us; we really don't have much control over them. When they are IFR; they complain that they cannot remain legal unless we keep them within a certain proximity of land due to their [type aircraft] single engine glide-to-land requirements; their preferred flight path is opposite direction to the arrivals and often creates a problem for us especially when vectoring multiple aircraft for sequence to final. If we put them on a vector for traffic that does not comply with their restrictions they cancel IFR and VFR advisories and resume own navigations as a rogue 1200 code flying right through our arrival corridor; forcing us to separate and often delay our IFR aircraft from a VFR aircraft that we have no control over. Because of this we often comply with their requests and issue vectors that allow them to remain within their glide-to-land; rather than deal with a VFR aircraft that we have no control over and cannot predict their actions; but this increases our work load tremendously as we typically wouldn't put aircraft head-on with each other as part of our normal operations. This also leads to problems for the IFR inbounds trying to make a stable descent to the runway. We often have to delay their descent so they can top the [company] aircraft; which leads to an unstable quick descent for them. As you can also see by my report; they disregard ATC instructions when on VFR advisories without notifying us. In short; we don't have much of a fighting chance to keep our operations safe with Aircraft X Company flying around as they do. This is an ongoing everyday problem at HCF which leads to high-tensions and hostility between our controllers and Aircraft X Company pilots as well as other pilots and Aircraft X Company pilots that often have to deal with delays; RA's; and general unsafe situations to accommodate for a single air carrier that is unwilling to play by the same rules that everyone else does.

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.