"I remember no urgent procedure for that combination.  You?"

He looks at the instrument panel, to confirm that the backup emergency radio beacon switched on (it has), and then starts manually examining all of the indicators to see if anything looks Anomalous in a way that got past the computers.  They"My memory says probable cause solar flare, 

Oh, that's not good.  Satellite frequencies are 1.5GHz for the global positioning system, their transponder lock runs on 3.5GHz, and Network access is 60GHz.  They're not in the middle of a thunderstorm, just some clouds, there's no thunderstorm scheduled to be near them, there's no solar weather warnings, and the X-Ray/UV component of a sudden solar flare and subsequent ionospheric disturbance shouldn't wipe all of those bands simultaneously.  GPS and transponder systems are located at the head of the plane, Network access is on the tail.

That implies (1) the problem is on their plane, and spread across a wide volume of it; or (2) there was a problem with a lot of satellites simultaneously; or (3) something non-obvious is going on.  None of those possibilities are particularly fun.

That's one track of the First Officer's mind; the other is checking that the first emergency backup radio beacon has automatically switched on (it has) and broadcast that an exception is in progress, now five seconds old.  He flips the "Return to your seats nonurgently" light for the rest of the passengers on board the aircraft, which creates some optionality in case anything else is about to go wrong; leaving the reason blank will create some worry about what the pilots have to do that's more important than explaining the seat-return light, but it's not like that worry is unjustified, and the absence of an explanation for the Network outage will also be conspicuous.

Once he's done that he turns to look at the Captain.  "First-order-belief-formed about what we do next."

Oh, that's not good.  Satellite frequencies are 1.5GHz for the global positioning system, their transponder lock runs on 3.5GHz, and Network access is 60GHz.  They're not in the middle of a thunderstorm, just some clouds, there's no thunderstorm scheduled to be near them, there's no solar weather warnings, and the X-Ray/UV component of a sudden solar flare and subsequent ionospheric disturbance shouldn't wipe all of those bands simultaneously.  GPS and transponder systems are located at the head of the plane, Network access is in the rear.

That implies (1) the problem is on their plane, and spread across a wide volume of it; or (2) there was a problem with a lot of satellites simultaneously; or (3) something non-obvious is going on.  None of those possibilities are particularly fun.

That's one track of the First Officer's mind; the other is checking that the first emergency backup radio beacon has automatically switched on (it has) and broadcast that an exception is in progress, now five seconds old.  He flips the "Return to your seats nonurgently" light for the rest of the passengers on board the aircraft, which creates some optionality in case anything else is about to go wrong; leaving the reason blank will create some worry about what the pilots have to do that's more important than explaining the seat-return light, but it's not like that worry is unjustified, and the absence of an explanation for the Network outage will also be conspicuous.

Once he's done that he turns to look at the Captain.  "First-order-belief-formed about what we do next."

Oh, that's not good.  Satellite frequencies are 1.5GHz for the global positioning system, their transponder lock runs on 3.5GHz, and Network access is 70GHz.  They're not in the middle of a thunderstorm, just some clouds, there's no thunderstorm scheduled to be near them, there's no solar weather warnings, and the X-Ray/UV component of a sudden solar flare and subsequent ionospheric disturbance shouldn't wipe all of those bands simultaneously.  GPS and transponder systems are located at the head of the plane, Network access is in the rear.

That implies (1) the problem is on their plane, and spread across a wide volume of it; or (2) there was a problem with a lot of satellites simultaneously; or (3) something non-obvious is going on.  None of those possibilities are particularly fun.

That's one track of the First Officer's mind; the other is checking that the first emergency backup radio beacon has automatically switched on (it has) and broadcast that an exception is in progress, now five seconds old.  He flips the "Return to your seats nonurgently" light for the rest of the passengers on board the aircraft, which creates some optionality in case anything else is about to go wrong; leaving the reason blank will create some worry about what the pilots have to do that's more important than explaining the seat-return light, but it's not like that worry is unjustified, and the absence of an explanation for the Network outage will also be conspicuous.

Once he's done that he turns to look at the Captain.  "First-order-belief-formed about what we do next."

Oh, that's not good.  Satellite frequencies are 1.5GHz for the global positioning system, their transponder lock runs on 3.5GHz, and Network access is 70GHz.  They're not in the middle of a thunderstorm, just over clouds, there's no thunderstorm scheduled to be near them, there's no solar weather warnings, and the X-Ray/UV component of a sudden solar flare and subsequent ionospheric disturbance shouldn't wipe all of those bands simultaneously.  GPS and transponder systems are located at the head of the plane, Network access is in the rear.

That implies (1) the problem is on their plane, and spread across a wide volume of it; or (2) there was a problem with a lot of satellites simultaneously; or (3) something non-obvious is going on.  None of those possibilities are particularly fun.

That's one track of the First Officer's mind; the other is checking that the first emergency backup radio beacon has automatically switched on (it has) and broadcast that an exception is in progress, now five seconds old.  He flips the "Return to your seats nonurgently" light for the rest of the passengers on board the aircraft, which creates some optionality in case anything else is about to go wrong; leaving the reason blank will create some worry about what the pilots have to do that's more important than explaining the seat-return light, but it's not like that worry is unjustified, and the absence of an explanation for the Network outage will also be conspicuous.

Once he's done that he turns to look at the Captain.  "First-order-belief-formed about what we do next."

Oh, that's not good.  Satellite frequencies are 1.5GHz for the global positioning system, their transponder lock runs on 3.5GHz, and Network access is 70GHz.  They're not in the middle of a thunderstorm, just over clouds, there's no thunderstorm scheduled to be near them, there's no solar weather warnings, and the X-Ray/UV component of a sudden solar flare and subsequent ionospheric disturbance shouldn't wipe all of those bands simultaneously.  GPS and transponder systems are located at the head of the plane, Network access is in the rear.

That implies (1) the problem is on their plane, and spread across a wide volume of it; or (2) there was a problem with a lot of satellites simultaneously; or (3) something non-obvious is going on.  None of those possibilities are particularly fun.

That's one track of the First Officer's mind; the other is checking that the first emergency backup radio beacon has automatically switched on (it has) and broadcast that an exception is in progress, now five seconds old.  He flips the "Return to your seats nonurgently" light for the rest of the passengers on board the aircraft, which creates some optionality in case anything else is about to go wrong; leaving the reason blank will create some worry about what the pilots have to do that's more important than explaining the seat-return light, but it's not like that worry is unjustified, and the absence of an explanation for the Network outage will also be conspicuous.

Once he's done that he turns to look at the Captain.  "First-order-belief-formed about what we do next."  You form that opinion yourself before the other person speaks, to prevent opinion cascades.