Perseids / Perséides 2019
Quick summary of the Perseids 2019 on 144 MHz. Between August 8th and 18th, 2019, I made 43 QSO’s with the following stations : UT2UB, EW7AW, SP8OOU, EA4SG, OK2WO, EU4AX, C37MS, 9A3MR, SM3LBN, SP2MHR, UA3LID, UT9UR, LA/SM5EPO (JP72, 75, 76), SQ5GVY, SP7QJF, OH1ND, OH1MN, EM44T, UT7KF, OG2Z, YO2LSP, YU7ON, RA1TL, R5WM, SM4GGC, LZ0C, US8AR, UT8AL, EA3MS, OH1XT, SM3XGV, EB5EEO, CT7ABA, SF6F (2 QSO’s), S50TA, S51ZO, LZ2FO, SV2JAO, YO2BBT and HA6VV.
I omit the reports on purpose (MS Sprint Contest). The furthest station worked was R5WM over 2166 km. Amongst other 2000 km+ QSO’s, US8AR was using 100W/9el and UT8AL used only 25W/21el ! On August 18th in the morning, during the YO Marathon, 9A, Italian FD contests, there was an outburst. I worked YO2BBT in SSB but failed to complete with YO7FWS during a 1 min MS burst. Both called me at the end of a Tropo QSO with OK1RDO, also in OK Contest.
Most of the above mentioned QSO’s were random, few ones by taking a sked on ON4KST. 32 out of the 43 were made using MSK144, 10 were in FSK441 and 1 in SSB.
Squares worked (click on the maps below to enlarge) :
I didn’t notice a real peak of the Perseids, or perhaps on the 13th in the early morning. Also visually, it wasn’t that much a fireworks, at least when I watched outside ! This year during the Perseids, we “suffered” from the same newbies we face in FT8 : people ignoring what MS is all about, calling you via Tropo and using uncoordinated 15 sec periods, just because it is embedded as is in WSJT-X…
By making some data processing (excluding the stations < 800 km) with exports from PSK reporter in Excel and kml mapping tools outputing into Google Earth (drop me a mail at email@example.com to know how to), one comes up with the map of all the stations I heard (mostly MSK144) during the Perseids (the furthest heard was UR3EE at 2314 km) :
By making a likewise data processing for the stations that heard ON4KHG, we have (furthest was RA3EL at 2206 km) :