IARU R1 Band Plan
HAM-Tools ships the IARU Region 1 band plan — 22 bands from 2200 m to 1.25 cm, complete with sub-segment breakdown (CW · SSB · Digital · Beacons · Satellite · etc.). The data comes from the bundled bandplan.json in the app bundle.
Three Ways to Access It
1. Sub-Tab in the Logbook
In the lower tab bar of every logbook type (DX, POTA, SOTA, WWFF, BOTA, Contest) there's a "Band Plan" sub-tab. It shows the active band with all sub-segments as a ruler display. The CAT frequency is drawn in as a live marker — it shifts immediately when you QSY on the radio.
2. Dedicated Window (⌘⇧P) 🆕
New in 1.8.8
The shortcut ⌘⇧P or the menu Window → Band Plan Window opens the complete band plan in a standalone window — handy on a second monitor during logging or a contest.
In the window:
- All 22 bands as horizontal rulers stacked under each other
- Sub-segments color-coded by mode (CW blue, Digital violet, SSB orange, Beacons red, …)
- The active CAT frequency as a red marker
- Tooltip per sub-segment with mode + bandwidth + license class
3. Live Awareness Pill in All QSO Forms 🆕
New in 1.8.9
When you log, a pill in the status bar tells you immediately whether your current frequency + mode are IARU compliant.
| Pill | Meaning |
|---|---|
| 🟢 in band | frequency in band, sub-segment fits the mode |
| 🟠 wrong sub-segment | in band, but in the wrong area (e.g. SSB in the CW sub-segment) |
| 🔴 outside amateur band | frequency is not in a known band |
Reacts live to CAT frequency changes. Active in all six QSO forms (DX, Contest, POTA, SOTA, WWFF, BOTA).
Implemented in BandplanChecker.swift — mode compatibility is kept tolerant: "all modes" sub-segments (e.g. wide areas from 50 MHz up) let everything through, so you don't get false positives in the 6 m band-plan wild west.
Band Overview
The app knows these bands:
| Frequency range | Designation |
|---|---|
| 135.7 – 137.8 kHz | 2200 m |
| 472 – 479 kHz | 630 m |
| 1810 – 1850 kHz | 160 m |
| 3500 – 3800 kHz | 80 m |
| 5351.5 – 5366.5 kHz | 60 m |
| 7000 – 7200 kHz | 40 m |
| 10100 – 10150 kHz | 30 m |
| 14000 – 14350 kHz | 20 m |
| 18068 – 18168 kHz | 17 m |
| 21000 – 21450 kHz | 15 m |
| 24890 – 24990 kHz | 12 m |
| 28000 – 29700 kHz | 10 m |
| 50 – 52 MHz | 6 m |
| 70 – 70.5 MHz | 4 m |
| 144 – 146 MHz | 2 m |
| 430 – 440 MHz | 70 cm |
| 1240 – 1300 MHz | 23 cm |
| 2300 – 2450 MHz | 13 cm |
| 3400 – 3410 MHz | 9 cm |
| 5650 – 5850 MHz | 6 cm |
| 10.0 – 10.5 GHz | 3 cm |
| 24.000 – 24.050 GHz | 1.25 cm |
Mode Compatibility (simplified)
| Mode | Standard sub-segment |
|---|---|
| CW | CW area (typically the band start) |
| SSB | phone area (LSB <10 MHz, USB ≥10 MHz) |
| FT8/FT4/JT65 | dedicated digital segment (e.g. 7074 kHz for FT8 on 40 m) |
| RTTY/PSK31 | digital segment (often right below SSB) |
| AM | mostly the phone segment |
| FM | only 10 m and up (29.5 MHz+, 6 m+, 2 m+) |
Band-plan-specific special areas (beacons e.g. 14.099–14.101 MHz, satellite sub-segments, EME windows) are split out into bandplan.json — mode conflicts are detected there, but handled tolerantly (orange "wrong sub-segment" instead of "outside band").
Note on Region 2 / 3
The app is designed for IARU Region 1 (Europe, Africa, Middle East). For the USA (Region 2) or Asia-Pacific (Region 3), different band edges and sub-segments apply — the pill may wrongly report "outside band" there even though the frequency would be permitted locally. A multi-region band plan is on the roadmap, but not planned for 1.x.