Mode spec correction
Include the mode name, published source, timing field, VIS or N-VIS value, and whether the correction affects public documentation or app-derived timing.
Contribute
Send evidence we can check.
The most useful contribution is specific: a source link, UTC time, mode, frequency, receiver path, decoded image, and a short note about what should change.
Activity source
Include the official page or operator announcement, UTC start/end if published, downlink, satellite or callsign, and the mode named by the source.
Received image note
Include permission to publish, the decoded image, UTC time, approximate location or grid if comfortable, frequency, receiver, antenna, and audio path.
Evidence standards
| Claim | Best evidence | How it will be used |
|---|---|---|
| Mode timing is wrong | Primary mode table, implementation source, or decoded sample that shows the mismatch. | Update the mode page and source notes, or mark the row for verification. |
| Public event is active | Official ARISS, AMSAT, operator, or mission page with UTC details. | Add to the static activity check after source review. |
| Equipment note is useful | Station setup, failure mode, before/after decode, and repeatable settings. | Fold into Field Notes as a credited or anonymised station note. |
Do not send private messages, passwords, licence documents, or personal data that is not needed for the correction. Use the support page for contact details and app-specific help.