Date: 201507
Local time of day: 1801-2400
Location: HCF.TRACON, HI
Light: Daylight
Aircraft: Large Transport; Low Wing; 2 Turbojet Eng
Operator: Air Carrier
Operating under: Part 121
Flight plan: IFR
Mission: Passenger
Flight phase: Initial Climb
Airspace: Class E HCF
ATC / advisory: TRACON HCF
Second aircraft: Military Transport
Reporter organization: Government
Reporter function: Enroute
Reporter qualification: Air Traffic Control Fully Certified
Human factors: Distraction; Situational Awareness; Confusion
Anomaly: ATC Issue All Types; Airspace Violation All Types; Deviation - Track / Heading All Types; Deviation / Discrepancy - Procedural Clearance; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Air Traffic Control
When detected: In-flight
Contributing factors: Human Factors; Procedure; Airspace Structure
Primary problem: Procedure

Narrative: These two aircraft were actually involved on two separate days with the same exact problem that I have previously filed a report on without any resolution. These are two more accounts of a problem that has existed for years in this facility but has not been addressed by management. After experiencing this same situation happen again on two successive evenings; I feel compelled to report this again in the hopes that this will finally be addressed.Aircraft X called for release off of LIH airport. The controller had coordinated that this aircraft had been issued a clearance with a Hold For Release. The LOA between LIH and HCF states that the LIH tower controller will issue a clearance to an aircraft utilizing the OFDPS [Offshore Flight Data Processing System] generated strip. When Aircraft X called for release; I released the aircraft on course and issued the aircraft a void time. When the aircraft departed; the aircraft checked in 'on runway heading' climbing to FL340. This aircraft was not climbing on his filed/precoordinated route of flight.[The next day two hours earlier] LIH tower called for a clearance on Aircraft Y. Aircraft Y had filed an incorrect flight plan with a departure point of LIG which resulted in no strip being generated for LIH tower. I verbally issued a clearance to LIH tower and then proceeded to correct the erroneous flight plan that was filed. About 5 minutes later the LIH tower controller called for release of Aircraft Y. Once again I simply told the LIH tower controller 'Aircraft Y released'. And yet again; Aircraft Y checked in on frequency 'runway heading; climbing to 130'. Except this time; this aircraft departed runway 35 and this runway heading was taking this aircraft into terrain. Do not just simply put this information into your database and have this facility continue to ignore this problem. Something needs to be done about this. Departure procedures need to be developed for aircraft to be able to transition from the LIH terminal environment into the HCF enroute structure. These DP's [Departure Procedures] must be developed to allow aircraft to depart LIH and proceed on course V15 or to transition to the oceanic egress fixes - ZIGIE; APACK; CLUTS; EBBER; FITES; SCOON; THOMA; DANNO; KATHS; CHOKO; CARRP.




Synopsis: HCF Controller reports of departure procedures off of Lihue Airport that need to be corrected. Aircraft are departing and flying into low terrain areas.