37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 931024 |
Time | |
Date | 201102 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZHN.ARTCC |
State Reference | HI |
Aircraft 1 | |
Make Model Name | B767-300 and 300 ER |
Operating Under FAR Part | Part 121 |
Flight Phase | Climb |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 129 |
Flight Phase | Cruise |
Person 1 | |
Function | Departure Enroute |
Qualification | Air Traffic Control Fully Certified |
Events | |
Anomaly | ATC Issue All Types Deviation - Procedural Published Material / Policy |
Narrative:
We have been having problems with ZOA abiding by the letter of agreement (LOA) with hcf. All attitudes for an eastbound one way route are hcf's above FL280. In the past 6 months; some of the controllers are just using wafdof without coordination. This has caused many fights; distractions; unrest; and uproar at the sectors. What usually happens is during the rush; we clear all our aircraft on their routes and altitudes as agreed upon in the LOA. When we are close to terminating radar and during transfer of info; ZOA controller will say unable because they have used our altitude without coordination. This causes a scramble to get the affected aircraft another altitude. It's usually an altitude they don't want and usually a lot lower. They are usually mad with us because sometimes they have sat at the airport with a delay to wait for their requested altitude; only to find that ZOA has put themselves in a bind and have used our altitude.last night it happened to me with aircraft X. After departure and during transfer; ZOA said they could not take him and that he either had to climb or descend. They did not coordinate their traffic with us in advance. It was a 'cross flight' air carrier Y. We did not even get a transfer on the air carrier Y for another 2 hours. Another analogy of this issue would be: a departure controller at an approach control is launching aircraft out of his departure corridor. He flashes an aircraft at the receiving controller and the receiving controller refuses to take the hand off because he has opposite direction traffic coming at the approach controller in the departure corridor. This would be totally unacceptable; unsafe; and poor control technique at any facility.
Original NASA ASRS Text
Title: HCF Controller reported ZOA is assigning altitudes contrary to Letter of Agreement (LOA) without prior coordination. This results in altitudes not being available for eastbound departures.
Narrative: We have been having problems with ZOA abiding by the Letter of Agreement (LOA) with HCF. All attitudes for an eastbound one way route are HCF's above FL280. In the past 6 months; some of the controllers are just using WAFDOF without coordination. This has caused many fights; distractions; unrest; and uproar at the sectors. What usually happens is during the rush; we clear all our aircraft on their routes and altitudes as agreed upon in the LOA. When we are close to terminating radar and during transfer of info; ZOA Controller will say unable because they have used our altitude without coordination. This causes a scramble to get the affected aircraft another altitude. It's usually an altitude they don't want and usually a lot lower. They are usually mad with us because sometimes they have sat at the airport with a delay to wait for their requested altitude; only to find that ZOA has put themselves in a bind and have used our altitude.Last night it happened to me with Aircraft X. After departure and during transfer; ZOA said they could not take him and that he either had to climb or descend. They did not coordinate their traffic with us in advance. It was a 'Cross Flight' Air Carrier Y. We did not even get a transfer on the Air Carrier Y for another 2 hours. Another analogy of this issue would be: a Departure Controller at an Approach Control is launching aircraft out of his departure corridor. He flashes an aircraft at the receiving Controller and the receiving Controller refuses to take the hand off because he has opposite direction traffic coming at the Approach Controller in the departure corridor. This would be totally unacceptable; unsafe; and poor control technique at any facility.
Data retrieved from NASA's ASRS site as of April 2012 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.