Narrative:

[Military range] is doing [military exercise] workups in warning area X and warning area Y. When it's time for the aircraft to return to hnl it seems as though they just give us the aircraft with no regard for our traffic. We had flow control in effect at booke; crossing @ 080 250 knots and 10 miles in trail (mit). [Range] hands off on a limited data block not tagged up aircraft X manually because they don't want to troubleshoot the problem doing 500 knots and converging with my 10 mit sequenced aircraft. They've got multiple active flight plans that are active and so the [fighter aircraft] cannot tag up. Meanwhile while running a sequence I have to troubleshoot the problem while trying to get them to tag up and restructure my sequence to accommodate the fighters. It seems as though the [fighter aircraft] wait for that critical moment when they're low on fuel and expect to go number 1 in sequence. So we have to move everyone out of the way to accommodate them.in addition; a 080 crossing restriction is wrong for direction at booke and conflicts with other smaller aircraft cleared via keola to lih climbing to 080 and also the departure corridor. So if I have to turn them south for spacing (since the warning areas are active to the north) they conflict with everyone departing west bound. [Range] needs to be responsible for making sure the aircraft tag up properly before handing off to center. Hand everyone off at 250 knots and ask for a heading. Preapproved altitude is FL190 and too high when flow control in in effect.

Related reports:

Google
 

Original NASA ASRS Text

Title: HCF Controller reported of a hand off from a military facility that was not according to the LOA. The aircraft were on the wrong code; and at the incorrect altitude.

Narrative: [Military Range] is doing [military exercise] workups in Warning Area X and Warning Area Y. When it's time for the aircraft to return to HNL it seems as though they just give us the aircraft with no regard for our traffic. We had flow control in effect at BOOKE; crossing @ 080 250 knots and 10 Miles In Trail (MIT). [Range] hands off on a limited data block not tagged up Aircraft X manually because they don't want to troubleshoot the problem doing 500 knots and converging with my 10 MIT sequenced aircraft. They've got multiple active flight plans that are active and so the [fighter aircraft] cannot tag up. Meanwhile while running a sequence I have to troubleshoot the problem while trying to get them to tag up and restructure my sequence to accommodate the fighters. It seems as though the [fighter aircraft] wait for that critical moment when they're low on fuel and expect to go number 1 in sequence. So we have to move everyone out of the way to accommodate them.In addition; a 080 crossing restriction is wrong for direction at BOOKE and conflicts with other smaller aircraft cleared via KEOLA to LIH climbing to 080 and also the departure corridor. So if I have to turn them south for spacing (since the warning areas are active to the north) they conflict with everyone departing west bound. [Range] needs to be responsible for making sure the aircraft tag up properly before handing off to center. Hand everyone off at 250 Knots and ask for a heading. Preapproved altitude is FL190 and too high when flow control in in effect.

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.