What’s SATVOICE I can hear?

SATVOICE. Easy peasy. Well, until until you’re routing from San Francisco to Tokyo for the first time in your shiny new G550 and its 2am, you’re passing  W177°, you think you filed M3 but aren’t sure if you’re actually M2, and there is a full moon and now you’re not so sure anymore…

Here is a look at some common questions about SATVOICE which we have seen come up.

Feel free to send us more. We aren’t experts but know one folk who are.

What is SATVOICE?

Satellite voice communications. Sometimes it is lumped in with SATCOM but this can include messaging systems as well (your Datalink type things). The ‘VOICE’ bit is the giveaway – we are specifically talking about talking.

An INMARSAT satellite

What is it used for?

Communicating. 

More specifically, communicating over big areas where there are not many ground stations (which you need for VHF comms). SATVOICE systems *can be (and note the asterix there) used as a Long Range Communications System (LRCS).

So, SATVOICE is talking, via satellites, and it can be used to do things like give voice position reports. It is also sometime used as a backup when HF is not functioning. What it is not (currently) is a replacement for HF. Just as CPDLC isn’t allowed as a replacement because it is not suitable for emergency of non-routine comms.

Where can I use it?

Anywhere where there is satellite coverage. And anywhere where ATC are using it as a means of LRCS. They may not be capable.

For example, the FAA provide Inmarsat and Iridium SATVOICE services for air-to-ground (and vice versa) calls directly with Oakland, NY and Anchorage ARTCCs, and New York and San Fran radio. These are, again, supplemental to HF which means they don’t expect you to use it unless there is some issue with HF. Times of bad HF propagation like HF blackouts would be a good time to give SATVOICE a go.

Right now, SATVOICE is not the primary means of communication in many spots. VHF and HF remain the main ones, with Datalink comms (CPDLC). So it is unlikely you will be using it all that much, unless something else is not working. When you are in CPDLC/ADS-C airspace, the controller is normally going to communicate via Datalink. They might elect to use SATVOICE, but it is not a replacement for ADS-C/CPDLC or HF/VHF.

So you also need to check out the airspace you’re flying into. The AICs will generally contain info on whether an airspace/ ATS has SATVOICE capability.

ICAO says – “Some ANSPs may allow the flight crew to use SATVOICE only for certain types of communications (e.g. of an urgent nature) or may place limitations on use of SATVOICE directly to the controller. Other ANSPs may allow its use only as an additional capability to existing radio equipment carriage requirements.” (Section 3.4, SVGM).

So, where CAN’T I use it?

Inmarsat satellites are geostationary and orbit around the equator which means above a latitude of 82° North (and South) you are in a satellite-less areas because of the (often debated, definitely real) curvature of the earth means a lack of line of sight which is required for your communications to be able to bounce back and forth from the satellites.

Some manuals suggest you might start to run into a bit of trouble from 70°N, and that trouble is most pronounced on the W120 longitude. It is also dependant on atmospheric conditions, where your antenna is and what services are contracted though.

An image of the satellite positions and coverage of the Iridium Network

Iridium satellites do not suffer the same SATCOM shadow because they operate in a low earth (as opposed to geostationary) orbit.

So, in the NAT HLA where HF is mandatory, and where Datalink is also mandatory (except for the bits where it isn’t), you are going to need HF and Datalink. Not one or the other. If an airspace requires two LRCS then one can be SATVOICE, but the other must be HF.

If the airspace requires 1 LRCS then that means HF.

So, you cannot use your SATVOICE system as a “get out of cancelling a flight” free card if your HF is broken and you are routing through somewhere which requires LRC systems onboard.

Which brings us to the asterix…

The Asterix

*SATVOICE can be approved as a Long Range Communications System (LRCS) but whether it qualifies is something you will need to check, and that is most easily found in your MEL. It comes down to the Required Communications Performance (RCP) of your system.

In other words, just because you have a SATVOICE system onboard and are in a spot where ATS utilises SATVOICE, does not mean you are automatically allowed to do so. Not even if you put it on your flight plan.

RCP240 is the number to know – to be PBCS (performance based communication and surveillance) eligible your aircraft system must achieve RCP240 (and RSP180) standards. RCP240 is the max number of seconds (the transaction time) taken for a controller to issue an instruction and receive a response.

Your RSP180 is the surveillance standard, the RCP240 is the comms standard. We wrote all about PBCS here if you need a recap.

Oldie but still what you need to know

What do I need to do to use it then?

Go back up to our bit about having an approved system and it being in your MEL…

And read this bit as well.

So, you need it in your MEL/MMEL, and what that means is having a system which meets the requirements laid out by your authority.

The FAA put out this info on getting approved. AC 20-150B – ‘Airworthiness Approval of Satellite Voice (SATVOICE) Equipment Supporting Air Traffic Service (ATS) Communication.

It is an AIC about getting airworthiness approval for SATVOICE, and contains all the design considerations, software requirements, minimum performance requirements, CVR, and a lot of other things you probably need to know about.

ICAO recommend that Operators need to establish policy and procedures for crew involved in SATVOICE ops. This includes descriptions of the system operating procedures, limitations, flight planning requirements, what to do if it does’t work… Check out section 3.3.3 of the ICAO SVGM manual for more on this.

In summary – your system needs to be approved. To be approved it needs to meet certain standards and criteria. You also need to have procedures and policy in place for the operation of the system.

Where is all the official info on this?

In ICAO Doc 9869, also known as the PBCS manual, also known as the GOLD manual (because its full title is Global Operational Data Link). You can find the 2017 edition of this in our Doc Library if you want to take a look.

Here is the ICAO SVGM (Satellite Voice Guidance Manual) which we mentioned.

Then there is ICAO Doc 7030 which contains regional supplementary procedures and will contain some info on Datalink, for example, over the North Atlantic.

I have the system and the approval, but need to find a number?

Well, this is where it can get a little tricky. There are different systems. Inmarsat and Iridium.

There is also MTSAT, the Japanese geostationary satellite network.

If you have Inmarsat satellite compatible system then you can use those SATCOM short codes (the six digit ones starting with a 4). You can also dial the 10-digit PSTN phone number. The 6 digit numbers are converted to the PTSN number as they wiggle through the Inmarsat system.

PTSN, incase you’re going to ask, is the Public Switched Telephone Network which is what the aeronautical SATVOICE system uses. So these are what you want to call via your Iridium system.

Numbers are generally to be found in places like the AICs, in your Jeppesen, LIDO, or whatever other chart and manual provider you are signed up to.

One tip, when you do dial up – don’t be yakking away like you’re on a normal telephone. The operator the other end is going to expect standard radio etiquette. Callsigns, readbacks and all that.

What do I put in my flight plan?

You need to include your SATVOICE capability and you do this in Item 10 by inserting either:

  • M1 for Inmarsat RTF capability;
  • M2 for MTSAT RTF capability;
  • And/or an M3 for Iridium RTF capability.

In Item 18 you insert the aircraft registration and also the indicator code and the aircraft address expressed in the form of an alphanumerical code of 6 characters.

If you are operating through airspace requiring HF and yours is broken, then you may be able to file with only your SATVOICE system as the LRCS if it is a flight to return the aircraft for HF maintenance.

Again, just having a system and whacking the info about it onto a flight plan does not qualify you to use it. It needs to be approved.

An HF MEL

What if I get a random SATVOICE call?

You should only act on the clearances or instructions given to you if a SATVOICE call has a priority level 2/High/Q12 or 1/EMG/Q15. You might have to disconnect and initiate a new call to get confirmation that it is something to act on, and not just some rogue person who has discovered a way to call you on it.

I am not signed up to any provider. Can I still just sort of call?

If you can answer this then please send us your info 🤷




GPS U/S in the US

We have written a fair amount on worldwide GPS Jamming issues. Here is what we said about it in ‘GPS Jamming: All the Wrong Signals’. But there is another GPS problem though which is a little closer to home (if your ‘aviation’ home is in the US anyway).

What’s the deal?

Let’s take a step back to 2017, when the NBAA and a bunch of other stakeholders took part in the 2017 RTCA tactical operation committee. That’s the Radio Technical Commission for Aeronautics and they are great – they try and help find compromises amongst the competing interests on critical aviation modernization issues.

One of these very issues is with GPS.

The FAA’s NextGen modernization program is using more and more GPS ‘stuff’. Stuff that is critical for commercial flight operations safety and efficiency. The US Department of Defense on the other hand is sort of doing the opposite – they are running GPS Jamming tests which are critical for National Security and the big problem with this is that the jamming tests often interfere with the GPS signals civil aircraft are using.

What was the 2017 outcome?

After they talked about it in 2017, the compromise was that the DoD will notify the FAA at least 120 hours before any planned tests. This should give the FAA time or put out Notams to warn crew and operators.

The May 2021 testing schedule

Problem solved?

Unfortunately not. The 120 hours notification is given, but the information which filters down to the pilots and operators who need to know about it often not sufficient. One of the difficulties is that the Notams have to provide information on different outage locations and this means loooooooong Notams filled with lots of Lat and Longs and times and dates. And this means critical information can sometimes get buried inside and makes it difficult or confusing for the crew to find it, extrapolate it (or even be aware of it in the first place).

What’s the plan now?

Well, the NBAA have reported on this, and say that the FAA are taking their concerns onboard. They plan to revisit the idea of producing visual representations of the outage areas. These will be much easier to digest than lines of lat and longs, and would hopefully enable crew to use them in conjunction with planning apps in the future.

There has also been a reminder issued to crew asking them to report outages and issues. If you find yourself in a jammy area, let ATC know. Tell them what you have lost so that they can warn other aircraft in the immediate area. The reminder has been sent to ATC as well because in the past, when aircraft have made these reports, the information has not always been shared out to other operators in the near vicinity.

What do you need to look out for?

What an outage means, practically, is interference to the GPS signals which your navigation system is using. The result can be a degradation in accuracy, or a full loss of the system (GPS primary).

If you are enroute, let ATC know your capability has been degraded so you can get the support you need to continue navigating safely.

Some aircraft are particularly sensitive to disruption in the GPS signals, and it can lead to you losing that system until it is reset on the ground. This means RNAV/RNP approaches might not be flyable anymore. Having an awareness of what this means for your aircraft is important. Think about your plan B for approaches in case you do loose GPS navigation capability.

Notams are out there and it might be frustrating picking out the areas which could impact you, but knowing about the outage spots in advance will help.

A display of WAAS services

Where can you look for info?

The 5G Update

We thought we’d throw in a little update in on this as well.

Last year we saw increasing concerns about possible interference from 5G networks because they operate on the same slice of radio spectrum usually reserved for Radio Altimeter signals (the 3.7-3.98 GHz band).

The big concern here is that interference could result in degradation of accuracy from spurious emissions, or outright failures in the radio altimeters. Not sure how much of a risk that means? Well, Turkish Airlines TK1951 crashed in EHAM/Amsterdam Schiphol in 2009 and one of the primary factors was attributed to a malfunctioning radio altimeter which sent an erroneous -8ft reading to the autothrottle system, commanding it to idle.

The NBAA are fronting a campaign here as well. Twenty organizations have joined forces to send the FAA a letter raising their concerns over this, in response to a report issued on March 3 that they don’t feel addresses the threat with enough analysis.

You can read the letter here.

Military aircraft and UAVs are also at risk here. Their radio altimeters use the same C-band frequencies, but they tend to fly a lot nearer the ground a lot more often. A very good summary of the issue can be found here.