Showing posts sorted by date for query qrss. Sort by relevance Show all posts
Showing posts sorted by date for query qrss. Sort by relevance Show all posts

Wednesday, February 28, 2024

2024 10m QRSS Challenge: - VK4BAP in Australia 28th Feb


As part of a challenge for 2024, I've decided to see how many QRSS signals I could capture on the 28 MHz band during the year. On the 28th of February, I noticed VK4BAP Queensland, Australia.

For my first attempt above, I managed to get a positive ID on the signal. However, a very strong OH station from Finland just above using WSPR was playing havoc with my audio levels. I tried to adjust the volume as best as I could and managed some sort of screen grab.

Finland is just one F2 layer hop from my location on the south coast of Ireland and signals are usually very strong. The QRSS signal from Australia by contrast is just about visible in the noise.

It's a bit like waiting on the bank of a river and waiting for a fish to bite. I'd start to get a reasonable QRSS signal from VK4BAP only for the OH station to then clobber it! :o)

Eventually, the timing got to a stage so that the VK station started just after the OH station had finished transmitting and I managed to get a reasonable if somewhat weak screengrab.


My target at the end of the day is to get a full screengrab of a signal which can be positively identified regardless of how weak it is.

The distance was about 16,070 kms and the propagation mode was via multiple F2 layer hops. There may have been some chordal hop in there as well. The time for the reception reports was about 09:00 UTC.


In summary... That brings the QRSS tally so far for 2024 up to 16-callsigns & 9 DXCC.

1) 08 Jan 2024: VE1VDM - DXCC #1
2) 10 Jan 2024: VA1VM
3) 15th Jan 2024: G0MBA - DXCC #2
4) 15th Jan 2024: G0PKT
5) 15th Jan 2024: AE0V - DXCC #3
6) 16th Jan 2024: RD4HU - DXCC #4
7) 16th Jan 2024: W1BW
8) 17th Jan 2024: OH5KUY - DXCC #5
9) 18th Jan 2024: TF3HZ - DXCC #6
10) 6th Feb 2024: VA3RYV
11) 16th Feb 2024: IK2JET - DXCC #7
12) 16th Feb 2024: N8NJ
13) 21st Feb 2024: PY3FF - DXCC #8
14) 26th Feb 2024: VE6NGK
15) 27th Feb 2024: NM5ER
16) 28th Feb 2024: VK4BAP - DXCC #9

Addendum: Brian, VK4BAP reports that this was his first day ever transmitting QRSS. He was using 1 watt to a Moxon beam pointing to Europe.

Tuesday, February 27, 2024

2024 10m QRSS Challenge: - NM5ER 27th Feb


As part of a challenge for 2024, I've decided to see how many QRSS signals I could capture on the 28 MHz band during the year. On the 27th of February, I managed to get a good capture of NM5ER in New Mexico.

The QRSS signal of NM5ER can be seen above at the top of the screen and this was the best one of several that I saw today. It really was a marginal signal and it didn't take much fading for me to lose large parts of the signal.

By contrast, the other signals listed about were a lot more consistent.


The distance was about 7800kms and I suspect the propagation mode was either two long or three shorter F2 layer hops.

In summary... That brings the QRSS tally so far for 2024 up to 15-callsigns & 8 DXCC.

1) 08 Jan 2024: VE1VDM - DXCC #1
2) 10 Jan 2024: VA1VM
3) 15th Jan 2024: G0MBA - DXCC #2
4) 15th Jan 2024: G0PKT
5) 15th Jan 2024: AE0V - DXCC #3
6) 16th Jan 2024: RD4HU - DXCC #4
7) 16th Jan 2024: W1BW
8) 17th Jan 2024: OH5KUY - DXCC #5
9) 18th Jan 2024: TF3HZ - DXCC #6
10) 6th Feb 2024: VA3RYV
11) 16th Feb 2024: IK2JET - DXCC #7
12) 16th Feb 2024: N8NJ
13) 21st Feb 2024: PY3FF - DXCC #8
14) 26th Feb 2024: VE6NGK
15) 27th Feb 2024: NM5ER

Addendum: Evans NM5ER confirms that his location is Las Cruces in New Mexico (DM62qq). He is running about 1.75 watts into a MFJ-1982LP End Fed Half-Wave Wire antenna tuned to 28 MHz.


Monday, February 26, 2024

2024 10m QRSS Challenge: - VE6NGK 26th Feb


As part of a challenge for 2024, I've decided to see how many QRSS signals I could capture on the 28 MHz band during the year. On the 26th of February, I managed to get a good capture of VE6NGK in the city of Calgary in the province of Alberta, Canada.

As can be seen from the image above, there was quite a bit of frequency drift on the QRSS signal. In reality, the signal only drifted upwards about 5Hz over the space of about 8 minutes but in the world of QRSS, these small changes are easily visible.

About 20 minutes later, I got a second screen capture when the signal was stronger.


The distance from Calgary to my location on the south coast of Ireland is about 6620kms. The propagation mode was probably two F2 layer hops but what make this path more of a challenge is that it goes well to the north.


I also saw NM3ER in New Mexico but I was unable to get a good screen grab. Another day.

In summary... That brings the QRSS tally so far for 2024 up to 14-callsigns & 8 DXCC.

1) 08 Jan 2024: VE1VDM - DXCC #1
2) 10 Jan 2024: VA1VM
3) 15th Jan 2024: G0MBA - DXCC #2
4) 15th Jan 2024: G0PKT
5) 15th Jan 2024: AE0V - DXCC #3
6) 16th Jan 2024: RD4HU - DXCC #4
7) 16th Jan 2024: W1BW
8) 17th Jan 2024: OH5KUY - DXCC #5
9) 18th Jan 2024: TF3HZ - DXCC #6
10) 6th Feb 2024: VA3RYV
11) 16th Feb 2024: IK2JET - DXCC #7
12) 16th Feb 2024: N8NJ
13) 21st Feb 2024: PY3FF - DXCC #8
14) 26th Feb 2024: VE6NGK

Addendum: Kam, VA6CA reports the following... "VE6NGK is my other call. I was running 5W at the time I believe. Was at 500mW at the beginning but not getting anywhere.

Below is the transmitting station.  It's a homebrew project using components from my junk box. The controller uses TTL logic chips. and the dual tone audio generator (the bottom board) uses two "tuning fork resonators" at frequencies 410 Hz. I physically trimmed one to get the audio tone frequency difference I need. The 410Hz was 4X up using PLL to get the output harmonics outside the FT817 SSB filter to minimize splattering."

Wednesday, February 21, 2024

2024 10m QRSS Challenge: - PY3FF 21st Feb


As part of a challenge for 2024, I've decided to see how many QRSS signals I could capture on the 28 MHz band during the year. On the 21st of February, I managed to get a good capture of PY3FF in Brazil, South America.

The QRSS signal from PY3FF can be seen at the top of the screen grab above. Rafael reports running 700 milliwatts into a dipole from his location in the south of Brazil.


The path length was around 10,000kms and it's likely it was three F2 layer hops. The G0MBA/G0PKT duo also shown in the screen grab are from the east coast of England and are about 700kms from my location. I believe that I am getting those signals via F2 layer backscatter.

The VOACAP propagation map below shows that the path from my location to the south of Brazil is reasonably good.


It is however one of my worst directions as I have a hill that is 3-degrees above the horizon. On 28 MHz, the signals must have been above that angle.

In summary... That brings the QRSS tally so far for 2024 up to 13-callsigns & 8 DXCC.

1) 08 Jan 2024: VE1VDM - DXCC #1
2) 10 Jan 2024: VA1VM
3) 15th Jan 2024: G0MBA - DXCC #2
4) 15th Jan 2024: G0PKT
5) 15th Jan 2024: AE0V - DXCC #3
6) 16th Jan 2024: RD4HU - DXCC #4
7) 16th Jan 2024: W1BW
8) 17th Jan 2024: OH5KUY - DXCC #5
9) 18th Jan 2024: TF3HZ - DXCC #6
10) 6th Feb 2024: VA3RYV
11) 16th Feb 2024: IK2JET - DXCC #7
12) 16th Feb 2024: N8NJ
13) 21st Feb 2024: PY3FF - DXCC #8

Saturday, February 17, 2024

2024 10m QRSS Challenge: - IK2JET & N8NJ 16th Feb


As part of a challenge for 2024, I've decided to see how many QRSS signals I could capture on the 28 MHz band during the year. On the 16th of February, I managed to get screen captures of IK2JET in the north of Italy and N8NJ in Ohio in the US.

1) IK2JET... At 16:17 UTC, I managed to get a successful screen capture of the QRSS signal from Alberto, IK2JET.


As can be seen from the image above, the signal wasn't too strong but it was a positive ID all the same and a new DXCC for 2024.

You can note how the QRSS signal has a slight 'fuzz' to it and is slightly distorted. It's similar to the backscatter signals from G0PKT & G0MBA which are going across the centre of the screen.

2) N8NJ... At 16:24 UTC, I got another screen capture and this time, I got a nice QRSS signal from Larry, N8NJ in Ohio.


The signal from N8NJ can be seen above at the top of the screen and it looks cleaner with less 'fuzz' than some of the other signals.

These are the WSPR decodes that I got from N8NJ during that hour and it suggests that the QRSS signal might have been in the region of -10dB.

local   y-m-d txCall txGrid rxCall rxGrid MHz W SNR drift kms  
2024-02-16 17:00 N8NJ EN81go EI7GL IO51tu 28.126084 1 -13 0 5574 
2024-02-16 16:50 N8NJ EN81go EI7GL IO51tu 28.126082 1 -5 0 5574 
2024-02-16 16:40 N8NJ EN81go EI7GL IO51tu 28.126084 1 -13 0 5574 
2024-02-16 16:30 N8NJ EN81go EI7GL IO51tu 28.126083 1 -10 0 5574 
2024-02-16 16:20 N8NJ EN81go EI7GL IO51tu 28.126084 1 -10 1 5574 
2024-02-16 16:10 N8NJ EN81go EI7GL IO51tu 28.126084 1 -7 0 5574 
2024-02-16 16:00 N8NJ EN81go EI7GL IO51tu 28.126084 1 -12 0 5574

Propagation Modes???.... What were the propagation modes responsible for these signals? I generated this propagation map below with VOACAP and the stations are marked in black.



N8NJ at 5570kms seems to be about right for two F2 layer hops and that one is easily explained.

The signal from IK2JET at 1550kms is more difficult. If it was a few more hundred kms away, I'd be more certain of one F2 hop but it seems a bit close. 

It could be Sporadic-E but we're in the middle of February and not the Summer Sp-E season. I did note plenty of other of WSPR signals on the day from the white skip zone around my location.

The signal as noted had some 'fuzz' to it which is unlike a nice clean one hop signal and that might suggest a back scatter or multi-path quality about it.

Sometimes, you just look at the evidence and it's hard to come to any firm conclusion.

In summary... That brings the QRSS tally so far for 2024 up to 12-callsigns & 7 DXCC.

1) 08 Jan 2024: VE1VDM - DXCC #1
2) 10 Jan 2024: VA1VM
3) 15th Jan 2024: G0MBA - DXCC #2
4) 15th Jan 2024: G0PKT
5) 15th Jan 2024: AE0V - DXCC #3
6) 16th Jan 2024: RD4HU - DXCC #4
7) 16th Jan 2024: W1BW
8) 17th Jan 2024: OH5KUY - DXCC #5
9) 18th Jan 2024: TF3HZ - DXCC #6
10) 6th Feb 2024: VA3RYV
11) 16th Feb 2024: IK2JET - DXCC #7
12) 16th Feb 2024: N8NJ

Tuesday, February 6, 2024

2024 10m QRSS Challenge: - VA3RYV 6th Feb


As part of a challenge for 2024, I've decided to see how many QRSS signals I could capture on the 28 MHz band during the year. On the 6th of February, I managed to get a good capture of VA3RYV in Ontario, Canada.

The QRSS signal of VA3RYV can be seen in the image above. It starts with a 'Slow Hell' image of the VA3RYV callsign followed by the signal in morse code. The whole sequence lasted about 6-minutes.

Wes, VA3RYV was using 100-milliwatts output power into a have-wave dipole about 15m above ground level. The path length was around 5,255kms and it's likely it was two F2 layer hops.


In summary... That brings the QRSS tally so far for 2024 up to 10-callsigns & 6 DXCC.

1) 08 Jan 2024: VE1VDM - DXCC #1
2) 10 Jan 2024: VA1VM
3) 15th Jan 2024: G0MBA - DXCC #2
4) 15th Jan 2024: G0PKT
5) 15th Jan 2024: AE0V - DXCC #3
6) 16th Jan 2024: RD4HU - DXCC #4
7) 16th Jan 2024: W1BW
8) 17th Jan 2024: OH5KUY - DXCC #5
9) 18th Jan 2024: TF3HZ - DXCC #6
10) 6th Feb 2024: VA3RYV

Friday, January 19, 2024

2024 10m QRSS Challenge: - TF3HZ 18th Jan


As part of a challenge for 2024, I've decided to see how many QRSS signals I could capture on the 28 MHz band during the year. On the 18th of January, I managed to get a good capture of TF3HZ in Iceland.

On the 17th of January, I had seen the QRSS signal of TF3HZ in between G0MBA and G0PKT so I knew where to look. on the 18th at 12:14 UTC, the signal appeared out of the noise.

This is a good example of how useful QRSS is in that you can 'see' the propagation changing. It shows how within the space of a minute, the path between Ireland and Iceland opened up.


In the next cycle, I got a nice strong QRSS signal and screengrab for TF3HZ.

The path distance was 1576kms so it's hard to know for certain what the propagation mode was. Was it F2 layer? Was it some mid-Winter Sporadic-E? The sudden appearance of the signal is very similar to a lot of the QRSS signals I have seen during the Sporadic-E season but it's not conclusive evidence. I think it's just one of those cases where no-one can be certain which of the propagation modes it was.



In summary... That brings the QRSS tally so far for 2024 up to 9-callsigns & 6 DXCC.

1) 08 Jan 2024: VE1VDM - DXCC #1
2) 10 Jan 2024: VA1VM
3) 15th Jan 2024: G0MBA - DXCC #2
4) 15th Jan 2024: G0PKT
5) 15th Jan 2024: AE0V - DXCC #3
6) 16th Jan 2024: RD4HU - DXCC #4
7) 16th Jan 2024: W1BW
8) 17th Jan 2024: OH5KUY - DXCC #5
9) 18th Jan 2024: TF3HZ - DXCC #6

Thursday, January 18, 2024

2024 10m QRSS Challenge: - OH5KUY 17th Jan


As part of a challenge for 2024, I've decided to see how many QRSS signals I could capture on the 28 MHz band during the year.

QRSS are very slow morse code transmissions where the dots and dashes are several seconds long and the signals are decoded by looking at a waterfall display on a screen rather than listening to the signal.

The QRSS signals are usually just below the WSPR signals on the amateur radio bands. This means it's possible to have your PC decoding WSPR signals up around 1500 Hz while you look at the QRSS signals about 500 Hz or so lower in the audio spectrum at the same time.

2024 #8 - OH5KUY... The 8th QRSS signal that I managed to capture this year was Ari, OH5KUY in Finland. Ari reports that he is running 1.5-watts into a C610 vertical antenna. His locator square is KP41DB.


The distance is from OH5KUY to my location is about 2437kms, an ideal distance for F2 layer propagation when the 28 MHz opens up to these northern latitudes.

Ari's signal was actually very strong for a QRSS signal and I had to adjust the volume settings on the radio because it was too strong compared to the rest. Most QRSS signals are buried in the noise and you get to see them only on a screen. Ari's signal by contrast was up to S4 here and it was a loud clear signal.


This is the signal in more detail. As you can see, something happened at Ari's location at about 13:52 to cause a slight rise in frequency. It's only about 4Hz but it can be seen.

That's the beauty of QRSS, you can actually 'see' the signal. You can see the frequency drift , you can see how the strength of the signal changes over time and you can see any unusual propagation effects.

With digital modes like FT8 and WSPR, you either get a decode or you didn't and if there isn't a decode, you're often not sure why. With SSB or CW, you're listening to an audio signal but it's what's happening here and now. You're missing those visual clues of QRSS which add so much more information.

The one that got away... It looks as if there was Sporadic-E on the band as well on the 17th. TF3HZ in Iceland popped out of the noise and I was all ready to get a nice screengrab but I lost it when I changed some settings on the SpectrumLab software. Lesson... screengrab first, adjustments later. Another day...

In summary... That brings the QRSS tally so far for 2024 up to 8-callsigns & 5 DXCC.

1) 08 Jan 2024: VE1VDM - DXCC #1
2) 10 Jan 2024: VA1VM
3) 15th Jan 2024: G0MBA - DXCC #2
4) 15th Jan 2024: G0PKT
5) 15th Jan 2024: AE0V - DXCC #3
6) 16th Jan 2024: RD4HU - DXCC #4
7) 16th Jan 2024: W1BW
8) 17th Jan 2024: OH5KUY - DXCC #5



Wednesday, January 17, 2024

2024 10m QRSS Challenge: - RD4HU & W1BW 16th Jan


As part of a challenge for 2024, I've decided to see how many QRSS signals I could capture on the 28 MHz band during the year.

QRSS are very slow morse code transmissions where the dots and dashes are several seconds long and the signals are decoded by looking at a waterfall display on a screen rather than listening to the signal.

The QRSS signals are usually just below the WSPR signals on the amateur radio bands. This means it's possible to have your PC decoding WSPR signals up around 1500 Hz while you look at the QRSS signals about 500 Hz or so lower in the audio spectrum at the same time.

2024 #6 - RD4HU... Most QRSS signals take the form of very slow morse code transmissions but sometimes, other modes are used. The screen capture above shows the slow-Hellschreiber mode which is more often referred to as "slow Hell".

RD4HU is located in the city of Samara on the Volga River in European Russia and was using 5-watts as far as I know. His signal was strong as can be seen by the clear trace.


The distance to my location on the south coast of Ireland is about 3855 kms which is ideal for one F2 layer hop, hence the strong signal.

2024 #7 - W1BW... Another method of sending a signal is as a symbol or character. This is where some degree of artistic flair comes into play.

Bruce, W1BW in Boston has a flying 'W' that he uses for QRSS. W1BW is running 200mW from a Hermes Lite 2 and the antenna is a random dipole about 25m long on the rooftop of a condominium building in the city of Boston, about 25m AGL and 2m above roof level..


W1BW is located just over 4700kms from my location and the mode of propagation was probably two hops from the F2 layer of the ionosphere.

In summary... That brings the QRSS tally so far for 2024 up to 7-callsigns & 4 DXCC.

1) 08 Jan 2024: VE1VDM - DXCC #1
2) 10 Jan 2024: VA1VM
3) 15th Jan 2024: G0MBA - DXCC #2
4) 15th Jan 2024: G0PKT
5) 15th Jan 2024: AE0V - DXCC #3
6) 16th Jan 2024: RD4HU - DXCC #4
7) 16th Jan 2024: W1BW

Tuesday, January 16, 2024

2024 10m QRSS Challenge: - G0PKT, G0MBA & AE0V 15th Jan


As part of a challenge for 2024, I've decided to see how many QRSS signals I could capture on the 28 MHz band during the year.

QRSS are very slow morse code transmissions where the dots and dashes are several seconds long and the signals are decoded by looking at a waterfall display on a screen rather than listening to the signal.

The QRSS signals are usually just below the WSPR signals on the amateur radio bands. This means it's possible to have your PC decoding WSPR signals up around 1500 Hz while you look at the QRSS signals about 500 Hz or so lower in the audio spectrum at the same time.

2024 #3 & #4 - G0MBA & G0PKT... The QRSS signals shown above were captured at about 10:40 UTC and it shows the QRSS trace from G0MBA and G0PKT who are 650kms to the east of my location in Essex, England. From what I know, I think both are running 0.2-watts into vertical antennas.


You'll notice that the signals have a slight 'fuzz' as opposed to a clean tone. I hear/see these two stations practically every day and I think the signals are F2 layer backscatter. If I was to try again during the Sporadic-E season during the summer, both signals would be nice and clean.

At 650kms, both signals from G0MBA & G0PKT are way too far for ground wave and too close for normal F2. The signals are probably being propagated off the F2 layer, being reflected in some distant region and then returning to my location.


2024 #5 - AE0V...In the afternoon, I got a capture of the QRSS signal of AE0V in Minnesota (EN34FU) in the USA who is about 6,000kms from my location.

Ned, AE0V reports using a solar powered transmitter with no battery storage running 100mW into a 1/4 wave stainless whip about 8m above the ground.


The signal from the USA is easily explained as it's via multi-hop F2 layer propagation. 

In summary... That brings the QRSS tally so far for 2024 up to 5-callsigns & 3 DXCC.

1) 08 Jan 2024: VE1VDM - DXCC #1
2) 10 Jan 2024: VA1VM
3) 15th Jan 2024: G0MBA - DXCC #2
4) 15th Jan 2024: G0PKT
5) 15th Jan 2024: AE0V - DXCC #3

Wednesday, January 10, 2024

2024 10m QRSS Challenge: - VA1VM 10th Jan


As part of a challenge for 2024, I've decided to see how many QRSS signals I could capture on the 28 MHz band during the year.

QRSS are very slow morse code transmissions where the dots and dashes are several seconds long and the signals are decoded by looking at a waterfall display on a screen rather than listening to the signal.

The QRSS signals are usually just below the WSPR signals on the amateur radio bands. This means it's possible to have your PC decoding WSPR signals up around 1500 Hz while you look at the QRSS signals about 500 Hz or so lower in the audio spectrum at the same time.

2024 #2 - VA1VM... The first signal I captured in 2024 was from Vernon, VE1VDM in Nova Scotia, Canada back on the 8th of January. This is outlined in this previous post.

Conditions on the 28 MHz band were better on the 10th of January and the 'VDM' QRSS signal was in again but stronger as can be seen above. For this beacon, Vernon was using a QrpLabs U3S with low pass-filter into a QrpLabs power amplifier delivering 1-watt on 10m. The antenna was ground mounted Hustler 6BTV vertical.

In the last 24-hours, Vernon has put a second QRSS transmitter on the air with the callsign VA1VM. You can see this as a weaker signal in the image above.

The VA1VM signal is from a 150 milliwatt transmitter into a  Hustler 10m 1/4 wave resonator mounted on a 1.37-metre long Hustler mast extender. It really is amazing that a 0.15 watt signal can make it across the Atlantic.

Both beacons are located in the town of Truro in Nova Scotia and are just a few kms apart. The antenna on my side was a simple CB type half-wave vertical.


The map above shows the location of the transmitter and receiver. The distance is about 4000kms which is ideal for 1-hop of F2 layer propagation.

Even though it's the same person, it's a second QRSS signal. That brings the QRSS tally so far for 2024 up to 2-callsigns & 1 DXCC.

08 Jan 2024: VE1VDM
10 Jan 2024: VA1VM

Monday, January 8, 2024

2024 10m QRSS Challenge: - VE1VDM 8th Jan


As part of a challenge for 2024, I've decided to see how many QRSS signals I could capture on the 28 MHz band during the year.

QRSS are very slow morse code transmissions where the dots and dashes are several seconds long and the signals are decoded by looking at a waterfall display on a screen rather than listening to the signal.

The QRSS signals are usually just below the WSPR signals on the amateur radio bands. This means it's possible to have your PC decoding WSPR signals up around 1500 Hz while you look at the QRSS signals about 500 Hz or so lower in the audio spectrum at the same time.

2024 #1 - VE1VDM... The first signal I captured in 2024 was from Vernon, VE1VDM in Nova Scotia, Canada.

Vernon was using a QrpLabs U3S with low pass-filter into a QrpLabs power amplifier delivering 1-watt on 10m. The antenna was ground mounted Hustler 6BTV vertical.

The antenna on my side was a simple CB type half-wave vertical.


The map above shows the location of the transmitter and receiver. The distance is about 4000kms which is ideal for 1-hop of F2 layer propagation.

So that's the QRSS tally so far for 2024... 1-callsign & 1 DXCC.

Monday, December 18, 2023

Meteor scatter experiment with the 2023 Geminid shower


In this post, I'll outline how I used an amateur radio beacon 500kms away to find the peak of the 2023 Geminids meteor shower and what else I noticed.

Introduction... Back in 2022, a new radio beacon called GB3MBA was put on air on the 50 MHz band and its primary purpose was carrying out meteor scatter experiments. Located near the town of Mansfield in the centre of England, the beacon runs 75-watts into a small Moxon antenna which beams straight up.

Unlike most amateur radio beacons, this one is basically a carrier that is on nearly all of the time which is exactly what is needed for meteor scatter experiments. The main coverage area is the UK itself but as I'm 502 kms from the beacon, I'm close enough for it to be of use.

I expected that most of the signals that I would hear would be from meteors burning up over Wales and would be arriving at my location about 20 degrees above the horizon.


Experiment Objectives... This is what I wanted to do...

  • Carry out an experiment as a 'proof of concept', take measurements, gain experience and see how I could improve on it.
  • Take 'hard measurements' with real data as opposed to just forming an opinion.
  • See if I could plot and find the peak of the 2023 Geminid meteor shower as a form of 'citizen science'.
Methodology & Equipment... For the previous few days before the peak, I was listening to meteor bursts from the beacon to establish the best method to carry out the experiment.

Radio... I was using an old Kenwood TS-690 amateur radio transceiver which still works fine and is pretty sensitive. I tuned it to 50.408 MHz and set the mode to CW. It drifts a few Hz with the changes of temperature in the shack but it was fine for this experiment. I just needed to be careful to make sure I was always on frequency.

Antenna... In the run up to the experiment, I used a 2-element Yagi in my attic beaming 120-degrees (east-south-east) to get ready. This was beaming about 45 degrees away from the beacon and being indoors, it wasn't optimum. Just before the experiment, I built a vertical T2LT (flowerpot) half-wave antenna and mounted it about 6-metres above the ground. It had a clear view of the sky towards Wales and the beacon.

Software... I used the SpectrumLab programme to look at the audio spectrum so that I could see any bursts and pings of signal. Under the 'Quick Settings', I used Slow Morse Reception ("QRSS") and I then selected 'Slow CW, 30 sec/dot'. 

I knew it wasn't practical to look at a screen for hours on end. At this setting, the audio spectrum is about 30 Hz wide and it takes about 1h 20m for the signals to drift from right to left across the screen. What this meant in reality was that I could look at the screen every 60-80 mins, count the signals on the screen and record the number of pings and bursts.


What to record?... I knew whatever I did, it had to be consistent for the observing period. I decided to use the number of signals seen in a 30-minute period. If it was a long burst or a short ping, I counted it as one signal. 

This raises the obvious question... should I count the number of pings and bursts, should I record the strong signals versus the number of weak signals? The problem is where do I draw the line? I knew I'd see long bursts, short pings and everything in between. It was the same for the signal strength... what's a 'strong signal'? 

I decided I just wanted 'hard data'. Was there a meteor scatter signal present on the screen... Yes or No. It's simple and there's no ambiguity.

Time period... For the experiment, I counted the number of meteor scatter signals from 17:30 UTC on the 14th of December to 22:00 UTC on the 15th of December 2023...a period of 28 hours and 30 minutes. This time frame coincided with the predicted peak of the Geminid meteor shower.

Results... This is the chart that I generated for the 28.5 hour period.


The recording period starts at 17:30 UTC on the 14th of December when the Geminid constellation and radiant point would be just above the horizon. I'll break down the chart in more detail below but the key thing to note is the peak at about 20:00 UTC on the 14th of December.

I had intended to stop recording early in the morning of the 15th but I was wondering if the peak was really the peak? Would there be another peak 24-hours later when the radiant point would be at the some position in the sky? As you can see, there was no peak 24-hours later. I had actually recorded the peak of the Geminids on the 14th.

Results - Time Frame - 17:30 UTC 14th Dec to 05:30 UTC on the 15th of December... The peak, the dip and the highest radiant...


The first 12-hours is shown above in more detail.

The start... I did a search on Google and it said that the constellation Gemini would rise above the horizon in London at 17:23 UTC. I'm 8.5 degrees west which means it would be 33 mins later... 17:56 UTC. The mid point might be say 17:39 UTC? I found another website which said that the radiant point would rise around 16:07 UTC??

This is further complicated by the fact that we're really looking at a time when meteors from radiant point in the Geminids would be hitting the atmosphere 100kms about Wales? I think 17:30 was a good enough time to start.

The peak... Between 19:00 and 20:30 UTC, I had counts of 15, 19 & 21 for each of the 30-minute intervals.

This is a screenshot I took during this period.


First, I'll explain what you are looking at. The vertical axis is a 30 Hz wide segment of the audio spectrum. The screen is moving from right to left and the white dotted lines are the 5-minute time intervals.

If I was hearing the beacon signal directly, it would be a solid yellow line running from right to left across the centre of the screen.

What you are looking at are the pings and bursts of meteor scatter signals which are spread out across the audio spectrum due to doppler shift.

Prior to the shower, I had seen that the peak was expected at 19:30 UTC on the 14th of Dec. Looking at my screenshot, I think the peak of the 2023 meteor shower occurred between 19:55 and 20:20 UTC on the 14th of December.

The dip??... I did make a note of how weak the reflections were from 22:30 and 00:00 UTC and this can be clearly seen in the chart above. 

As the meteor shower radiant moves slowly across the sky, the angles between the transmitter, receiver and the trails of the meteors will change. At some points, the meteor trails will be parallel between my location and the beacon and at other points, the trails will be perpendicular.

I suspect the dip is due to the geometry of the meteor trails but I'm not sure. It could also be just a statistical error. I would need to repeat the observations on several days around this time period to see if it repeats.

Maximum elevation... At about 01:30 UTC, the radiant point was supposed to be at its highest elevation which was about 71 degrees above the horizon.

Before the experiment, I was wondering if this mattered? Would there be some sort of peak when the radiant peak was at its highest point in the sky? The answer seems to be no, there is no peak.

Results - Time Frame - 01:30 UTC to 11:00 UTC on the 15th of December... The daily morning peak...


When it comes to random meteors entering the atmosphere, the best time for signals tends be around 6am local time. This is because the speed of the earths rotation is added to the speed of the meteors resulting in more energy to dissipate.

This enhancement can be clearly seen in the chart above. It increases after 02:00 UTC and decreases after 10:00 UTC. For me at least, it seemed to be an eight hour window.


The converse is also true. At 6pm local time, the speed of the earth's rotation is subtracted from the original speed of the meteors.

This means that the peak of the 2023 Geminids at about 20:00 UTC happened just two hours after 6pm for me which isn't a great time.

As I was looking at the original chart with the 28.5 hour display, I realised that I was looking at two peaks but both were completely different. One is a fixed peak and the other is a variable peak.

The fixed peak was the peak of the Geminids at about 20:00 UTC on the 14th of December. That's fixed, the peak is the peak.

The morning peak however will depend on where you are. Somewhere in the world, the peak of the Geminids meteor shower will coincide with 6am local time. That turns out to the western half of the Pacific. Anyone in say Hawaii, Alaska, Korea, Japan, east China and the Philippines should have seen some very good meteor bursts and pings. That is of course conditional on having the radiant point above the horizon and that will depend on the location.

Results - Time Frame - 09:00 to 22:00 UTC on the 15th of December... This is the last 13 hours of the plot in more detail...


The radiant point for the Geminids sets about 10:00 UTC and a drop in numbers can be seen. The signals from about 10:00 to 17:30 UTC are random meteors and are not Geminids as the radiant point is below the horizon.

You can see it was particularly poor from 16:30 to 17:30 UTC. Then the Geminids radiant point comes above the horizon and the numbers increase again.

Other observations... Aircraft Scatter... I've seen plenty of aircraft scatter on signals before but I was really surprised to see it on a signal from 500kms away.


These can be very easy to miss. On the QRSS 3 setting, these appear as almost horizontal lines due to the larger vertical scale and faster scrolling speed. On QRSS 30 as used above, the slant becomes a lot more obvious.

As you can see, the doppler shift is in the region of 5-7 Hz. When I was seeing these signals appear, I would check FlightRadar 24 and sure enough, there was often a large plane to the west of Aberstwyth on the west coast of Wales. This is around the halfway point from the beacon to my location.

This suggests to me that while the GB3MBA beacon is 'beaming straight up', there is plenty of RF heading towards the horizon as well.

You'll notice as well that the trails last for about 90 seconds which should be enough for digital modes like MSK144 or possibly FT4? I'd have no doubt that a lot of those one off FT8 decodes on the 10m and VHF bands that people get are due to aircraft scatter like this.

Additional Notes...

  • I couldn't tell if any meteor heard was a Geminid or not for the time the radiant was above the horizon.
  • Despite all of the 'streaks' visible on the screen, the signals were actually pretty weak. Many were not audible to my ear and I'd say the strongest signals were probably something like 519. 
  • The process that I used was very labour and time intensive. I literally had to set an alarm to wake up every 60-80 mins overnight and take the measurements.
  • My resolution was 30 mins which may have limited the resolution in that I couldn't tell if two very close bursts were one or two.


In Conclusion... I think the experiment overall was a success. I was able to see the peak of the 2023 Geminid meteor shower which was from 19:55 to 20:20 UTC on the 14th of December.

I'm sure there is room for improvement but I think this is a useful 'citizen science' project which can be done by anyone with a good receiver and antenna. This method is also easy enough that it's not restricted to those from a radio background. 

Anyone with a serious interest in astronomy and meteor research could do this and consider it as an additional tool. This system works regardless of the weather. While 'visual' amateur astronomers need clear skies, the 'radio' based amateur astronomer can carry on regardless.

It might make an excellent project for an astronomy or radio club and maybe give a presentation to students as part of a STEM outreach programme

I think it proves that GB3MBA is indeed a very useful beacon for meteor scatter research and I think the challenge now is for them to make more people aware of it.

You can tell from the length of this post that this was a deep dive down the rabbit hole for me. As soon as I had one question answered, I thought up of two more additional questions.

The future??.. I'd see these as areas for improvement.

  1. My antenna was a vertical half-wave which is omni-directional. I think something like a 3-element Yagi would give me at least 6dB more gain, reduce noise and result in more pings and bursts.
  2. My experiment was for 28.5 hours with a resolution of 30 mins. I think in the future, I would use QRSS 3 with a finer resolution of 10 minutes and plot the period around the predicted peak in more detail.

More information...

For more information on the GB3MBA beacon, go to https://ukmeteorbeacon.org/

There is also the BRAMS beacon in Belgium on 49.970 MHz which might be of interest... https://brams.aeronomie.be/