 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Hcf controller describes a new procedure that is timely to use and doesn't work correctly in the sector.
| Attributes | |
| ACN | 1186685 |
| Time | |
| Date | 201407 |
| Local Time Of Day | 0001-0600 |
| 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 | Cruise |
| Route In Use | Oceanic |
| Flight Plan | IFR |
| Person 1 | |
| Function | Approach |
| Qualification | Air Traffic Control Fully Certified |
| Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 15 |
| Events | |
| Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
Prior to XA05 zulu; the r-side gave aircraft X a squawk and started a 'preserved track;' which is a new procedure at sector R7. This procedure is very time consuming; and it increases the work load at an already busy sector. Aircraft X was scheduled to cross fapis at XA05. At time XA10; I noticed that aircraft X had still not tagged up yet. The r-side asked aircraft X his position; and I believe he said that he was approximately 60 miles from fites. At this point; aircraft X should have tagged up. The preserved track was still frozen outside of fapis; which is our new procedure. We did finally see a target; but it did not automatically tag up; and the preserved track stayed outside of fapis. And; yes; the code was correct. Preserved track did not work; and r-side had to manually track start the aircraft.preserved track did not work; and if it does not work; please do not require us to keep using it. It creates extra workload at an already busy sector. Sector R7 should just have its airspace re-configured. It's too busy to work four different frequencies with all that busy traffic. Controllers almost had a mid-air at this sector; please; please; please; figure out a better procedure than adding extra workload. Re-configure the sector. Split the sector by frequencies. 126.6 is one sector; and 127.6 should be a second sector. Please; I don't want another near-miss in this airspace. And; yes; you have my permission to share this report and any other reports that I have written.
Original NASA ASRS Text
Title: HCF Controller describes a new procedure that is timely to use and doesn't work correctly in the sector.
Narrative: Prior to XA05 Zulu; The R-Side gave Aircraft X a squawk and started a 'preserved track;' which is a new procedure at Sector R7. This procedure is very time consuming; and it increases the work load at an already busy sector. Aircraft X was scheduled to cross FAPIS at XA05. At time XA10; I noticed that Aircraft X had still not tagged up yet. The R-Side asked Aircraft X his position; and I believe he said that he was approximately 60 miles from FITES. At this point; Aircraft X should have tagged up. The preserved track was still frozen outside of FAPIS; which is our new procedure. We did finally see a target; but it did not automatically tag up; and the preserved track stayed outside of FAPIS. And; yes; the code was correct. Preserved track did not work; and R-side had to manually track start the aircraft.Preserved track did not work; and if it does not work; please do not require us to keep using it. It creates extra workload at an already busy sector. Sector R7 should just have its airspace re-configured. It's too busy to work four different frequencies with all that busy traffic. Controllers almost had a mid-air at this sector; please; please; please; figure out a better procedure than adding extra workload. Re-configure the sector. Split the sector by frequencies. 126.6 is one sector; and 127.6 should be a second sector. Please; I don't want another near-miss in this airspace. And; yes; you have my permission to share this report and any other reports that I have written.
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.