Air Traffic Control Fully Certified
Human-Machine Interface
ATC Issue All Types
ATC Equipment / Nav Facility / Buildings; Procedure
A Sky Hawk had landed on Runway 4R and was clearing at Taxiway F. A Caravan was on right traffic from the Freeway 2 arrival for Runway 4L on a short approach. The Caravan was on a dog-leg and almost directly over the HNL VORTAC when the ASDE-X alarmed for OCCUPIED Runway 4R. The ASDE-X indicated his target in conflict with the Sky Hawk; who was observed clear of the runway edge line and moving toward Taxiway C. Before I was able to key up on frequency; the Caravan cleared the Runway 4R final and the hold bars immediately illuminated on Runway 4L. No go-around was issued. ASDE-X nuisance alarm forms and an MOR was submitted by FLM. This has been a re-occurrence with ASDE-X safety logic which is responding as designed. However; because of the flexibility of the use of the parallels with our small aircraft and the helicopter operations very unique to this airport; this continues to be a problem. Our OS offered a solution to issue a point to turn base leg; i.e.; turn a one mile final. I don't know if our student pilots can navigate an ILS/DME or visualize a point in space. This is viable; however; in order to expedite traffic for efficiency or for LAHSO/No LAHSO operations; or to minimize conflictions with the diverse types of aircraft. Prior to ASDE-X; we did not have these issues. Another other possible solution is to lengthen Runway 4L and make it even with Runway 4R.
HCF Tower ASDE-X nuisance 'false' alarms are recurring. A number of recent suggestions provided at the facility level that might provide some relief are provided.