Menu Sign In Contact FAQ
Banner
Welcome to our forums

Radios and electrical systems (VW)

From the CAA:

I believe that Yaesu are happy to make a formal statement that their airband models FTA-550 and FTA750 also meet the requirements of LA301075 in full.

I have phoned Yaesu and it seems this really is the case and an announcement is pending. I have one on order – I liked the idea of having a VOR separate from the GPS as I’ve had my skin saved by VOR/NDBs when my GPS adapter failed.

I wonder whether any other countries will follow suit in allowing these handhelds?

Last Edited by kwlf at 11 Feb 14:00

Backpacker is right here. Most people don’t seem to realise that some channels are the same frequency, but called different (131.000 / 131.005) to indicate the selectivity used.
All new 8,33 kHz radio’s are actually 8,33 / 25 kHz radio’s. On 131.000 they will have a wider selectivity compared to the 131.005.

There a lot of countries which have to convert at least 25% of their frequencies to 8,33 kHz to meet the EU regulations

JP-Avionics
EHMZ

QuoteThere should not be interference with existing 25k radios, otherwise any 8.33 usage would render existing 25k radios useless. And they would have to mandate immediate removal of all existing 25k radios and replacement of all of them with 8.33 ones which (you appear to imply) have better selectivity.

That’s exactly what’s going on. Within the next two years or so all 25 kHz radios will obsolete and useless, and may no longer be used. In fact, if you get a new aircraft or new radio installation today, it is already mandatory to have 8.33 kHz capability.

8.33 kHz radios have selectable selectivity. If you tune to an “old” frequency, it enables 25 kHz selectivity, whereas if you tune to a “new” channel, it selects 8.33 kHz selectivity. This enables the use of both 25 kHz frequencies and 8.33 kHz channels simultaneously within the spectrum, as long as there’s no overlap. But a “new” 8.33 kHz channel can only be allocated and used once the nearby 25 kHz frequency has been converted to an 8.33 kHz channel too. Otherwise there would be overlap between the 25 kHz frequency and the 8.33 kHz channel. That’s why we’re now seeing the gradual conversion from 25 kHz to 8.33 kHz: To enable the nearby 8.33 khz channels.

QuoteLondon Info from 124.60 to the next one along

Actually that only seems to be the case. Because of the trick that I talked about to distinguish a 25 kHz frequency from an 8.33 kHz channel on the same frequency. So the move from 131.000 to 131.005 (in case of EHEH) is not really a change in center frequency, but only in bandwidth/selectivity.

I can’t see the need for the 8.33 thing when eurocontrol is introducing CPDLC into the upper airspace, this cuts down the voice traffic, the first attempt at this was very good news in terms of cutting down the voice communications but they had software issues.

According to Eurocontrol these issues have been fixed however yesterday I tried to log on to The CPDLC, it connected for a few seconds and then kicked me off so may be it has some way to go before becoming fully available.

The cynic in me sees 8.33 for low altitude ATC communications as a job creation for the eurocontrol boys that we have to pick up the tab for !

Last Edited by A_and_C at 09 Feb 15:59

I recall a thread here some time ago where we discussed this.

Every 8.33k frequency has a 25k frequency right next to it. There should not be interference with existing 25k radios, otherwise any 8.33 usage would render existing 25k radios useless. And they would have to mandate immediate removal of all existing 25k radios and replacement of all of them with 8.33 ones which (you appear to imply) have better selectivity.

I think if you search on KX165A or something like that, you will find it.

As an example of my earlier post, why for example move London Info from 124.60 to the next one along, or Farnborough 125.25 to the next one along? It’s completely pointless.

Unless there is some covert plan to sell the 25k frequencies to Apple for airborne delivery of i-messages

Administrator
Shoreham EGKA, United Kingdom

Interference?

If you transmit on a 8.33 frequency (say, 131.00833, aka ‘channel’ 131.010), it interferes with aircraft and ground based sets that are tuned to the nearest 25 kHz frequency (say, 131.000 with a 25 kHz bandwidth, aka ‘channel’ 131.000 – after all, that frequency should be tolerant up to 131.0125).

Last Edited by BackPacker at 09 Feb 15:43

Every 25 kHz frequency that converts to 8.33 kHz

But, why bother? Why not just use the intermediate ones (the 8.33 ones) for new applicants?

Administrator
Shoreham EGKA, United Kingdom

QuoteOn a slight digression – given that just about all lower airspace stations are on 25kHz spacing, why would these frequencies change to 8.33 ones?

The authorities claim that the current 760 frequencies in the aeronautical VHF band are not enough to sustain future growth, so more are needed. Every 25 kHz frequency that converts to 8.33 kHz means that two more 8.33 kHz frequencies become available. So with full 8.33 kHz implementation the number of frequencies just about triples to a little over two thousand.

Quoteevery 3rd 8.33 frequency is really a 25kHz frequency

Well, not quite. It is true that the center frequency of every 3rd 8.33 kHz frequency is the same as the center frequency of a 25 kHz frequency. But the bandwidth (or “tolerable frequency variation” or whatever you’d like to call it – the amount of frequency variation that’s possible before the signal interferes with the next frequency) is cut in a third.

There’s a clever system to distinguish between the old 25 kHz spaced frequency, and the new 8.33 kHz spaced ‘channel’ which really operates on the same frequency, but with a narrower bandwidth. For example, the old EHEH 131.0 frequency was a 25 kHz frequency, so anything between 130.9875 ( 131.000 minus 25/2) and 131.0125 (131.000 plus 25/2) was fair game. The new ‘channel’ is now called 131.005 – which really means anything from 131.000 minus 8.33/2 to 131.000 plus 8.33/2.

An example of the frequency/channel conversion tables can be found here: http://www.jeppesen.com/download/briefbull/fra99-f.pdf but in short:

‘channel’ 131.000 is the old 25 kHz spaced frequency, centered around 131.000
‘channel’ 131.005 is the new 8.33 kHz spaced frequency, centered around 131.000
‘channel’ 131.010 is the new 8.33 kHz spaced frequency, centered around 131.00833
‘channel’ 131.015 is the new 8.33 kHz spaced frequency, centered around 131.01666
‘channel’ 131.020 does not exist.
‘channel’ 131.025 is the old 25 kHz spaced frequency, centered around 131.025
and so forth.

Radios with 8.33 kHz capability will automatically select 8.33 kHz or 25 kHz bandwidth as appropriate. Just like selecting 121.5 really enables a 100 kHz bandwidth instead of 25 kHz.

Last Edited by BackPacker at 09 Feb 15:39
Authorities want to tell us that European airspace was too crowded for 25 kHz spacing so they force us to 8,33 kHz radios. There is a gradual change to that in introducing more and more airspaces with required 8,33 frequency approaching 2018. One reason we had to skip the Baklan radio last year for the Trig after the deadline of November 2013 had passed for “new” radio registering so now its only 8,33 for new registrations. Vic
vic
EDME

On a slight digression – given that just about all lower airspace stations are on 25kHz spacing, why would these frequencies change to 8.33 ones?

I mean why change?

The UK proposed a frequency tax, under which an 8.33 frequency (i.e. 2/3 of the possible ones, since every 3rd 8.33 frequency is really a 25kHz frequency) was going to be 1/3 of the price. But that proposal got killed. It ran a long way, considering it’s amazing stupidity.

Administrator
Shoreham EGKA, United Kingdom
47 Posts
Sign in to add your message

Back to Top