37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1018143 |
Time | |
Date | 201206 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | HNL.Airport |
State Reference | HI |
Aircraft 1 | |
Make Model Name | Caravan Undifferentiated |
Operating Under FAR Part | Part 135 |
Flight Phase | Landing |
Flight Plan | VFR |
Aircraft 2 | |
Make Model Name | Skyhawk 172/Cutlass 172 |
Operating Under FAR Part | Part 91 |
Flight Phase | Taxi |
Flight Plan | VFR |
Person 1 | |
Function | Local |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types |
Narrative:
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.
Original NASA ASRS Text
Title: 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.
Narrative: 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.
Data retrieved from NASA's ASRS site as of July 2013 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.