Summit logging is a thumb problem. Treat it like one.

The cone is not a desk

SOTA logging fails in three boring ways: you cannot hit the keys, you cannot see the screen, and you cannot reach a server. Fix those before you worry about cluster spots.

Oversized call field. UTC already ticking. Band and mode as large targets, not a spinner. Red-night theme if you are still there at dusk. The log has to keep up with a paddle. If it cannot, you will skip QSOs you already worked.

Summit reference on the line, not a laminated card

Association, summit code, points. You looked them up at the trailhead or the night before. They should already be the activation context when you sit down. Chasers expect the reference in the pileup. Your ADIF should have it without a second editor on the drive home.

Chaser mode is the other half. Distance, azimuth, and DUPE so you do not work the same summit twice on 40. A cluster is useful when you have a path. It is not required to write a QSO.

• Enter the summit before you leave the car park.
• Log with gloves. If you cannot, the UI is wrong.
• Write locally. Submit to the SOTA program when you are below the tree line.

GPS that still works when maps do not

Maidenhead from the phone GNSS is enough. Basemap tiles are a luxury. If the canyon eats GPS, type a grid and keep running. The rest of the log — DUPE, radio, clock — should not care.

After the descent

Recovery snapshots matter when the phone dies in the pack. The activation should restore. Then ADIF, then the SOTA database. Log73 is the tactical log for that loop — not a replacement for the program’s own submission rules.

Field trial is open for operators who actually hike with a KX2 or a 705. If your current logger needs a bar of LTE on the cone, you already know the problem.