Hcf controller reports of problems associated with flying from a radar environment into a non-radar ...

Attributes
ACN	1245761
Time
Date	201503
Local Time Of Day	0001-0600
Place
Locale Reference	HCF.TRACON
State Reference	HI
Environment
Light	Night
Aircraft 1
Make Model Name	Widebody Low Wing 2 Turbojet Eng
Operating Under FAR Part	Part 121
Flight Phase	Cruise
Route In Use	Oceanic
Flight Plan	IFR
Aircraft 2
Make Model Name	Widebody Low Wing 2 Turbojet Eng
Operating Under FAR Part	Part 121
Flight Phase	Climb
Route In Use	Oceanic
Flight Plan	IFR
Person 1
Function	Approach Departure Enroute
Qualification	Air Traffic Control Fully Certified
Experience	Air Traffic Control Time Certified In Pos 1 (yrs) 20
Events
Anomaly	ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy

Narrative:

In accordance with the pacific chart supplement aircraft entering or exiting hcf airspace should file a named fix/waypoint along the hcf/ZOA boundary. The reason for this requirement is simple. Hcf does not have the capability to display an aircraft's route of flight to ensure lateral separation is maintained between aircraft transitioning from radar to oceanic non-radar. Hcf airspace was designed with many fixes along the boundary to ensure oceanic non-radar lateral separation will exist if aircraft actually fly over them. However; aircraft routinely file and are cleared via latitude/long's that cannot be determined by the controller without getting up and relying on a grease pencil/dry erase marker to plot route on an overhead plexi-glass display. Another example of non-compliance with these procedures occurred. Aircraft X was inbound over sayto dct scoon at FL390. Aircraft Y was cleared off of hnl dct fites dct 2100N/15000W climbing to FL390. The boundary estimate for aircraft X was XX00Z and the boundary estimate for aircraft Y was xx+04Z. Needless to say there wasn't any form of separation ensured between these 2 aircraft. Aircraft Y needed to file over a boundary fix (fapis) to ensure lateral separation would exist at the boundary between these 2 aircraft.all aircraft entering or exiting hcf airspace must file a named fix or waypoint along the hcf boundary.

Original NASA ASRS Text

Title: HCF Controller reports of problems associated with flying from a radar environment into a non-radar environment and not being able to display routes to look for issues.

Narrative: In accordance with the Pacific Chart Supplement aircraft entering or exiting HCF airspace should file a named fix/waypoint along the HCF/ZOA boundary. The reason for this requirement is simple. HCF does not have the capability to display an aircraft's route of flight to ensure lateral separation is maintained between aircraft transitioning from radar to oceanic non-radar. HCF airspace was designed with many fixes along the boundary to ensure oceanic non-radar lateral separation will exist if aircraft actually fly over them. However; aircraft routinely file and are cleared via LAT/LONG's that cannot be determined by the controller without getting up and relying on a grease pencil/dry erase marker to plot route on an overhead plexi-glass display. Another example of non-compliance with these procedures occurred. Aircraft X was inbound over SAYTO DCT SCOON at FL390. Aircraft Y was cleared off of HNL DCT FITES DCT 2100N/15000W climbing to FL390. The boundary estimate for Aircraft X was XX00Z and the boundary estimate for Aircraft Y was XX+04Z. Needless to say there wasn't any form of separation ensured between these 2 aircraft. Aircraft Y needed to file over a boundary fix (FAPIS) to ensure lateral separation would exist at the boundary between these 2 aircraft.All aircraft entering or exiting HCF airspace must file a named fix or waypoint along the HCF boundary.

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.

Hcf controller reports of problems associated with flying from a radar environment into a non-radar environment and not being able to display routes to look for issues.