A government aircraft's oceanic flight plan was not forwarded to enroute oceanic air traffic control...

Narrative:

Aircraft X filed an oceanic ICAO flight plan route. Flight plan was filed at base operations and addressed to at least our first ARTCC contact. The person who filed the flight plan is out sick and I couldn't get a complete list of addressees. Received the following IFR clearance prior to takeoff: 'aircraft X cleared as filed to ZZZ; climb and maintain 7;000 feet; expect FL360 10 minutes after departure. Squawk xyza.' we assumed the 'cleared as filed to ZZZ' meant a full route clearance.took off on time and all was normal until entering the warning area. After crossing ZZZ VOR outbound; center directed we contact arinc and establish enroute communications. After successfully contacting radio and advising center; ATC handed us off to control (USN fleet area control [controlling agency] for warning area) on VHF. Multiple attempts to initiate contact on VHF were unsuccessful. Finally; control called us; asking to ident if we heard. They acknowledged our ident; but apparently weren't receiving on VHF. We called control on VHF guard and started working our way up the published control frequencies in the IFR supplement. Finally obtained two-way communication with control on UHF. Asked control if they had our flight plan; answer was yes; and asked them to forward it to oceanic. Response was 'standby.' made several more inquiries and told to standby. Flew out of VHF/UHF range before we got an answer. Made position report to commercial radio; they told us to call oceanic phone number for possible pilot violation. Called ATC; they said they had no flight plan; asked us if we were proceeding due regard; and asked us to have our dispatch refile the flight plan and address it to their address code. I replied negative due regard; and oceanic asked us where we were and to remain in the warning area until they got a flight plan in the system. Started orbit to remain within the warning area. Called base ops to refile flight plan; both numbers went to voicemail. Called tower and they said airfield ops was out doing a runway sweep and to call back in 5 minutes. Called back to oceanic to start to read flight plan; by then they apparently found our flight plan and had commercial radio read us a full route clearance; matching our originally filed flight plan. Total delay in the warning area was 23 minutes. I asked the oceanic controller what the problem had been and he offered no explanation.our mission occasionally requires us to transit this warning area enroute to oceanic airspace. This dropping of flight plans when transiting the warning area is a navigation hazard; as we assumed we had full route clearance and the various controlling agencies would forward our flight plan in turn. The dropping of our IFR flight plan has happened several times before and we've called control; to be assured that the problem is fixed. They have not offered any suggestions (flight plan addressing; remarks; etc.) on how to fix this problem.

Original NASA ASRS Text

Title: A government aircraft's oceanic flight plan was not forwarded to Enroute Oceanic Air Traffic Control facilities which required a delay within a protected military warning area prior to entry into oceanic airspace.

Narrative: Aircraft X filed an oceanic ICAO flight plan route. Flight plan was filed at Base Operations and addressed to at least our first ARTCC contact. The person who filed the flight plan is out sick and I couldn't get a complete list of addressees. Received the following IFR clearance prior to takeoff: 'Aircraft X cleared as filed to ZZZ; climb and maintain 7;000 feet; expect FL360 10 minutes after departure. Squawk XYZA.' We assumed the 'cleared as filed to ZZZ' meant a full route clearance.Took off on time and all was normal until entering the Warning Area. After crossing ZZZ VOR outbound; center directed we contact ARINC and establish enroute communications. After successfully contacting radio and advising Center; ATC handed us off to Control (USN Fleet Area Control [controlling agency] for Warning Area) on VHF. Multiple attempts to initiate contact on VHF were unsuccessful. Finally; Control called us; asking to ident if we heard. They acknowledged our ident; but apparently weren't receiving on VHF. We called Control on VHF guard and started working our way up the published Control frequencies in the IFR supplement. Finally obtained two-way communication with Control on UHF. Asked Control if they had our flight plan; answer was yes; and asked them to forward it to Oceanic. Response was 'Standby.' Made several more inquiries and told to standby. Flew out of VHF/UHF range before we got an answer. Made position report to Commercial radio; they told us to call Oceanic phone number for possible pilot violation. Called ATC; they said they had no flight plan; asked us if we were proceeding due regard; and asked us to have our dispatch refile the flight plan and address it to their address code. I replied negative due regard; and Oceanic asked us where we were and to remain in the Warning Area until they got a flight plan in the system. Started orbit to remain within the Warning Area. Called Base Ops to refile flight plan; both numbers went to voicemail. Called Tower and they said Airfield Ops was out doing a runway sweep and to call back in 5 minutes. Called back to Oceanic to start to read flight plan; by then they apparently found our flight plan and had Commercial radio read us a full route clearance; matching our originally filed flight plan. Total delay in the Warning Area was 23 minutes. I asked the Oceanic Controller what the problem had been and he offered no explanation.Our mission occasionally requires us to transit this Warning Area enroute to Oceanic airspace. This dropping of flight plans when transiting the Warning Area is a navigation hazard; as we assumed we had full route clearance and the various controlling agencies would forward our flight plan in turn. The dropping of our IFR flight plan has happened several times before and we've called Control; to be assured that the problem is fixed. They have not offered any suggestions (flight plan addressing; remarks; etc.) on how to fix this problem.

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.

Attributes
ACN	1390803
Time
Date	201609
Local Time Of Day	1801-2400
Place
Locale Reference	ZZZ.Airport
State Reference	US
Environment
Flight Conditions	VMC
Light	Night
Aircraft 1
Make Model Name	Widebody Transport
Operating Under FAR Part	Part 91
Flight Phase	Cruise
Route In Use	Oceanic
Flight Plan	IFR
Component
Aircraft Component	Air/Ground Communication
Person 1
Function	First Officer
Qualification	Flight Crew Flight Instructor Flight Crew Instrument Flight Crew Multiengine Flight Crew Flight Engineer Flight Crew Air Transport Pilot (ATP)
Experience	Flight Crew Last 90 Days 50 Flight Crew Total 9000 Flight Crew Type 400
Events
Anomaly	ATC Issue All Types Aircraft Equipment Problem Less Severe Deviation - Procedural Clearance

A government aircraft's oceanic flight plan was not forwarded to enroute oceanic air traffic control facilities which required a delay within a protected military warning area prior to entry into oceanic airspace.