37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1279395 |
Time | |
Date | 201507 |
Local Time Of Day | 1801-2400 |
Place | |
Locale Reference | HCF.TRACON |
State Reference | HI |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Large Transport Low Wing 2 Turbojet Eng |
Operating Under FAR Part | Part 121 |
Flight Phase | Initial Climb |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Military Transport |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Climb |
Flight Plan | IFR |
Person 1 | |
Function | Enroute |
Qualification | Air Traffic Control Fully Certified |
Experience | Air Traffic Control Time Certified In Pos 1 (yrs) 21 |
Events | |
Anomaly | ATC Issue All Types Airspace Violation All Types Deviation - Procedural Clearance Deviation - Procedural Published Material / Policy Deviation - Track / Heading All Types |
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.
Original NASA ASRS Text
Title: HCF Controller reports of departure procedures off of Lihue Airport that need to be corrected. Aircraft are departing and flying into low terrain areas.
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.
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.