37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1532882 |
Time | |
Date | 201804 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | HCF.TRACON |
State Reference | HI |
Environment | |
Light | Night |
Aircraft 1 | |
Make Model Name | Airbus Industrie Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Phase | Descent |
Flight Plan | IFR |
Person 1 | |
Function | Approach |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy Deviation - Speed All Types Inflight Event / Encounter CFTT / CFIT |
Narrative:
I had a sequence at maui approach. The sectors were combined; but they probably should [not] have been combined due to workload. I had cleared [an A320] for the RNAV Y runway 2 approach behind another jet. I got distracted by another issue going on to the south; and the next time I looked back at [the airbus] I saw an 80 knot overtake with the aircraft ahead of them. I tried to reduce [the airbus] to final approach speed; but it didn't happen quickly enough. I canceled the approach clearance and climbed [them] to 4;000. I turned them southeast for re-sequencing. During all of this; I had multiple calls from other sectors in my ear; and maui tower calling on the hotline. I also had several other aircraft that I was sequencing and that were departing. It was busy. I am pretty sure that [the airbus] remained within the 3;500 section of the MVA; but they may have clipped the 4;500 section.maui approach sectors should have been split for this amount of traffic. The other things distracting me were due to other controllers straying from what our SOP states (i.e. An aircraft was on a routing other than the pdr because the pilot requested it; and the previous controller had approved it; and an aircraft inbound to maui stopped at 10;000 when they are supposed to be descending to 8;000 causing them to get stuck above another aircraft and making sequencing more difficult). The SOP should be followed to avoid these unnecessary distractions.
Original NASA ASRS Text
Title: HCF Controller reported missing an overtake situation resulting in a canceled clearance. Controller reports possibly entering a higher MVA area during re-sequencing.
Narrative: I had a sequence at Maui Approach. The sectors were combined; but they probably should [not] have been combined due to workload. I had cleared [an A320] for the RNAV Y Runway 2 approach behind another jet. I got distracted by another issue going on to the south; and the next time I looked back at [the Airbus] I saw an 80 knot overtake with the aircraft ahead of them. I tried to reduce [the Airbus] to final approach speed; but it didn't happen quickly enough. I canceled the approach clearance and climbed [them] to 4;000. I turned them southeast for re-sequencing. During all of this; I had multiple calls from other sectors in my ear; and Maui Tower calling on the hotline. I also had several other aircraft that I was sequencing and that were departing. It was busy. I am pretty sure that [the Airbus] remained within the 3;500 section of the MVA; but they may have clipped the 4;500 section.Maui Approach sectors should have been split for this amount of traffic. The other things distracting me were due to other controllers straying from what our SOP states (i.e. an aircraft was on a routing other than the PDR because the pilot requested it; and the previous controller had approved it; and an aircraft inbound to Maui stopped at 10;000 when they are supposed to be descending to 8;000 causing them to get stuck above another aircraft and making sequencing more difficult). The SOP should be followed to avoid these unnecessary distractions.
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.