Boeing Company Undifferentiated or Other Model
Flight Crew Flight Instructor; Flight Crew Air Transport Pilot (ATP); Flight Crew Instrument; Flight Crew Multiengine
Flight Crew Last 90 Days 241; Flight Crew Total 5300; Flight Crew Type 1300
Communication Breakdown
ATC Issue All Types; Deviation / Discrepancy - Procedural Published Material / Policy; Inflight Event / Encounter Fuel Issue
Air Traffic Control Provided Assistance; Flight Crew Requested ATC Assistance / Clarification
Human Factors; Procedure; Airspace Structure
My crew and I departed on [a] standard routing to Guam planned with Max payload. The flight was routine and uneventful until ATC advised us that we would be receiving new routing to due to 'military exercise/airspace' east of Guam. We were given a reroute. Shortly after uploading the new route into the FMC and noticing that our planned arrival fuel had fallen by roughly 3000 pounds; we then Sat-Phoned our Dispatch the new route to verify that we still met ETOPS and fuel requirements. Unfortunately; at this point; we had been encountering headwinds 20 kts stronger than planned for majority of the flight. We received ACARS from Dispatch that we were unable to proceed on the requested reroute due to stronger headwinds and insufficient fuel to meet depressurization scenarios. We informed ATC that we could not accept the reroute and they then asked us [if we wanted] to 'declare [low fuel]'; we told them we would call them back ASAP; as we had roughly 1 hour before joining the northerly rerouted course. We then Sat-Phoned our Dispatch and [the personnel] was able to conference call the Chief Pilot; I asked what he wanted me to do as our options were to turn for KWAJALEIN or Declare a Fuel Emergency. To turn for KWAJALEIN; it would've involved traversing a rather large area of weather that included a SIGMENT which wasn't ideal; unless it was an utmost emergency. After discussing the options over the Sat-Phone with our dispatch and the Chief Pilot I was instructed that I needed to 'declare [low fuel]' to get our jet safely to its destination. Repeatedly during the discussion; our Dispatcher said he had no information on the NOTAMED airspace/exercise and this was reconfirmed by me and my crew by re-reviewing the FIR NOTAM packet we reviewed at the onset of that day's flight. This also is why initially we never were planned around this exercise. I informed ATC that we were 'declaring [low fuel]' and that we requested to remain on our route as it was originally planned. ATC asked us if we could return to [departure airport]; I informed them that this was not possible at this time due to fuel remaining. ATC cleared us to return to original routing and advised us that we would be entering military airspace. We were given a discrete squawk prior to entering the military airspace and Guam Center. Once two-way radio contact was made with Guam Center; we were asked if we were under a fuel emergency and we advised them that we were no longer [low fuel]; which was the result of being allowed to fly the planned route. We proceeded and landed at Guam with no further incidence. I must further state and stress that when we left; our NOTAM package and accompanying usual routing gave me nor my crew any indication that we would be needing to avoid a restricted or prohibited area along our route. Later communications with the [Dispatcher] revealed that a 'glitch' in the NOTAM retrieval process led to this error. It was further stated that it was neither my crew nor the specified Dispatcher's fault for this error. The Manager at [the Flight Planning Service] soon after landing communicated that processes for retrieval of these type of NOTAMS were immediately being put in place to rectify this error to never let this happen againI want to commend everyone who helped deal with this unfortunate situation and hope measures are put in place to avoid it.
Air carrier Captain reported the NOTAM system had not provided important Oceanic airspace information to both the Captain and the Dispatcher.