For 'How To Participate' information, please visit HAMsci.org/MSQP.  Questions should be sent to the HamSCI Mailbox.
 

I) Science Objectives

Generate research-worthy data resulting from 6 and 10 meter meteor scatter operation. The data will be used by the research community in an attempt to answer science questions, such as:

1. What factors influence meteor scatter propagation?
   
   • What are the similarities and differences between HF and VHF meteor scatter propagation?
   • How does propagation change between between the Perseid and Geminid meteor showers due to their different speeds and radiant geometries?
   • How does propagation change between the various sporadic sources and minor showers with their different speeds and radiant geometries?
   • How does propagation change with radiant geometries, trail direction, meteoroid size, and speed?
2. What is the typical duration of useful meteor scatter propagation?
   
   • How does this duration vary with operating frequency, transmitter–receiver distance, and meteor velocity?
3. What is the minimum size of an amateur radio station needed to work meteor scatter operations?
   
   • What defines a 'successful' MS station?  Power levels?  Antenna type (directionality, gain, elevation, height, polarization)?  System ERP (effective radiated power)?
   • Does the definition of a 'successful' station (judged by both the number of contacts and the contact distances) vary between HF and VHF bands?  If so, what are the differences?
4. How can meteor scatter communication be distinguished from other propagation modes?
   
   • What percentage of reported meteor scatter QSOs are actually meteor scatter?
   • What percentage are due to other modes (e.g., tropospheric, F-layer, E-layer, auroral)?
5. How do optical and radar meteor observations compare with amateur radio observations?

The target communities include: Seasoned meteor scatter operators, meteor scatter 'rookies' (those who are new to the mode), researchers with an interest in radio wave propagation.  Data sources will include participant's log files (ADIF format), 'spotting' databases, such as PSKReporter.info and operators' WAV files from MSK144 decodes.
 

II) Dates and Times

0000 UTC August 11 to 2400 UTC August 12,  2025 (Perseids)

0000 UTC December 12 to 2400 UTC December 13,  2025 (Geminids)

Each will be a 48 hour event  because most meteor scatter (MS) activity will be very early in your local morning, so we set a wide operating period to catch ‘early morning’ across many time zones.

III) Operating Bands and Mode

HamSCI is interested in both 6 and 10 meter MS propagation. While 6 meters is the most popular MS band, 10 meters, a band having both HF and VHF characteristics, lends itself to novel research opportunities.

1. This event is open to both Two-Way (transmit/receive) and Monitor (receive only) stations, fixed in position (no mobiles or rovers).
2. The event will use both the 6 and 10 meter bands.  (50.260 and 28.145 MHz are popular MS operating frequencies.)
3. If your station can operate both 6 and 10 meters - please operate on both, alternating bands at 20 minute intervals (xx:00, xx:20, xx:40)
4. MSK144 is the only mode for this event.
5. Be sure the receive node software (most likely, the WSJT-X suite) is properly configured, especially your 6-character Maidenhead Grid Square, for sending reports to the PSKReporter.  The data sent to, and collected by, PSKReporter will be critical to the research efforts underlying this event.
    

IV) Contest Exchange

A valid 2-way MS QSO is defined as follows:

1. Each station transmits and receives callsigns, grid squares and/or signal reports and acknowledges the other station’s information (typically by sending ‘R’ or ‘RRR’ or ‘RR 73’)
2. Any 6 or 10 meter MSK144 QSO made during the contest period and logged into the station's WSJT.adi file will qualify and be evaluated for scoring purposes.
3. There is no time limit when making a QSO.  Whether 15 seconds, 5 minutes or 15 minutes - multiple retries are common with the MSK144 mode.
4. There is no penalty for 'dupes' (duplicate QSOs), meaning it is possible for one station to work another station 2, 3 or even 5 times during the 48 hour contest period, on the same band.  All of those QSOs will count towards the scoring.  See Item  2 under VII Scoring and Recognition 

V) In-Contest Operating Aids

HamSCI encourages the use computer-based tools and websites to help locate QSO opportunities, such as pingjockey.net.  Note:  As with any ham radio contact, all QSO information must be exchanged over the air, not via chat, text or other non-radio means.

VI) Post-Event Entry Process

HamSCI would like to collect ADIF logs from all stations who make one or more 2-way QSOs during the MSQP.   Files and entrant info (transmitter, power, antenna) will collected via the MSQP Entry Form - which will appear just after the events in July and December..

The HamSCI Research Team greatly appreciates all who contribute to the Meteor Scatter QSO Party.   The Team would like to recognize all participants via postings on the HamSCI website and in other media.   Further, we may have questions for the participants as we work through the data analysis process.   Note: We will not share contact information with anyone outside the HamSCI Data Processing and Research teams.   We highly encourage all MSQP participants to complete the post-event entry process and receive a score and ranking once the results are tabulated.

 Researchers are also interested in collect WAV files of decoded signals.  Details on how HamSCI plans to collect WAV files will be forthcoming.  See notes on software setup at HAMsci.org/MSQP
 

VII) Scoring and Recognition

Scoring each participant's contribution will be challenge for the party organizers, but we are up to the task! The HamSCI team hopes torecogn ize all those who contribute to the MSQP, either as transmitting or receiving stations.

1. MSQP entries for transmit sites will be reported by three attributes: Callsign, Grid, Band, Number of 2-Way QSOs (note 
2. There is no limit on duplicate QSOs. Two stations can work each other as many times as the meteors will allow, even on the same band. We do, of course, encourage all entrants to put as many different callsigns as possible into their logs. Doing so will give the data a good geographic distribution for later analysis.
3. Receive-only sites will be reported by these attributes: Reporter (callsign or identifier), Reporter Grid, Band, Number of reception reports
4. MSQP Rookies:  First time meteor scatter operators are encouraged to self-report their 'rookie' status so they can be recognized in the results tabulation
5. Certificates?  HamSCI plans to provide electronic certificates for all participants, noting the top scorers among the transmitting and receiving stations.
6. Bonus points:​
   • ​​​​Provide Effective Radiated Power relative to a Dipole (ERPD) for your  station.  Note that two calculations may be required - one each for 6 and 10 meters.  This file can be uploaded via the MSQP Entry Form.
   • Collaboration with local astronomy clubs.  The club organization name, plus a photo of the event, with the ham station included in the photo, will enough to earn the bonus.
   • Submission of photos (PDF or JPG format) of the operator, station equipment, antennas, etc.
   • Submit photos via e-mail attachments to hamsci.seqp@gmail.com after each event (August and December) (The .seqp address may look odd...but it is the correct one.)

Some months after each event, after the HamSCI Data Processing Team has concluded their work, charts tallying the above will be published to the HamSCI website.

VIII) MSQP Entry Form 

Will be available here, after the events in August and December.

Hint on submitting ADIF files:  Ideally, your ADIF file contains only QSOs made during the MSQP.  Often, the one and only ADI file on your computer (usually called wsjt_log.adi) contains many weeks, or even months/years of QSO data.  If the entire file is submitted, HamSCI data analysts will delete the non-MSQP QSOs, and save only the MSQP QSOs.  Help us give you proper credit by copying and renaming the file before submitting:  <your_callsign>_log.adi.  Thank you!

This is Version 2.0 of the MSQP Operating Rules and Guidelines, dated 4 August, 2025.  Minor changes may occur from time to time, so please check back before the actual events.