SOTA Activation: Unnamed Summit 12306 (W0C/SR-129)

It is always fun to do the first Summits On The Air (SOTA) activation of a peak. Most of the Colorado peaks have been climbed by someone along the way but there are still many that have never been activated for SOTA using amateur radio.

Bob K0NR SR-129
Bob/K0NR takes shelter from the wind behind the rocks on the summit of 12306.

I noticed that an unnamed summit not too far from our cabin, referred to as 12306 or W0C/SR-129 had not been activated. At first glance, I thought this was because it was difficult to access. Further investigation revealed US Forest Service info on the Hayden Gulch Road (FS 396) that goes to the Hayden Gulch Trailhead at the west edge of the Buffalo Peaks Wilderness area.

Note that this area is closed to motor vehicles seasonally.

Joyce/K0JJW and I approached the trailhead from the west, starting at Granite, CO on Hwy 24, turning east onto FS 397 (marked at the highway) and then quickly looking for signs for FS 396. The San Isabel National Forest map is somewhat helpful but the Latitude 40 recreational map for Salida/Buena Vista is much better.  The road is mostly easy 4WD but it is narrow in many places and moderate difficultly in a few spots. We saw crossover SUVs carefully driving the road with success. It was easy-peasy in our Jeep Wrangler.

The trailhead sign at the edge of Buffalo Peaks Wilderness.

Starting the hike, we followed the Hayden Gulch trail to the east. We actually had to search a bit to make sure we were really on the trail as we left the trailhead, as it was not super obvious. Hint: stay to the north (left) of the trailhead sign.

Our GPS track followed the Hayden Gulch trail into the wilderness area, then diverted north toward the summit.

The trail follows an old road that was likely closed when the wilderness area was formed. Once we cleared the trees (shown accurately on the map above), we left the trail and traveled off-trail towards the summit, trying to follow the contour lines and not lose a bunch of elevation. The hike promised to be very pleasant except that we had 30 to 40 mph winds from the west. This was not enough to stop us but certainly made the hike less enjoyable. The views were spectacular but a little difficult to enjoy with the wind blowing.

Our first view of SR-129 from the Hayden Gulch Trail, just as we emerged from the trees.

The hike was 1.8 miles one-way with about 1000 feet of vertical gain. Once on the summit, we got out the standard VHF SOTA gear: Yaesu FT-90 transceiver, LiFe battery and 3-element Arrow yagi. We both quickly worked Bob/W0BV, Walt/W0CP, Steve/WG0AT and Brad/WA6MM. WG0AT was on his way down from Eagle Rock (W0C/SP-113) so we missed a Summit-to-Summit opportunity with him. (We did work him earlier when he was on the summit but we were not.) WA6MM was a successful S2S contact from Mount Logan (W0C/FR-017).

This turned out to be a successful activation and a fun hike. We both concluded that we need to do it again…with a little less wind.

73 Bob K0NR

Pikes Peak SOTA: Hike from Devils Playground

Stock photo of Pikes Peak with snow on it.

I’ve been up Pikes Peak (W0C/FR-004) a zillion times via the Pikes Peak Highway and the Pikes Peak Cog Railway (currently out of service) doing SOTA activations, working VHF contests, participating in the Colorado 14er Event, maintaining repeaters and escorting visitors from out of town. See my previous post on activating by driving up the mountain: How To Do a SOTA Activation on Pikes Peak.

Joyce/K0JJW and I had Pikes on our SOTA activation list for 2018 but wanted to do a hike to access the summit. The classic climbing route up Pikes is via Barr Trail, a 13-mile trail that ascends 7800 vertical feet. This is a difficult climb for most humans but I will note that serious runners routinely run up the mountain just for fun. See Fred/KT5X’s comments on the SOTA database about running up the mountain and then doing a SOTA activation.

Another hiking alternative on the northwest side of Pikes Peak is the Crags Trail, also known as the Northwest Slopes route. This route starts about 4 miles south of Divide, CO at the Crags Campground. This hike is 7 miles one-way with 4300 vertical feet. This is easier than Barr Trail but still a significant climb.

The hiking route from Devils Playground to the summit of Pikes Peak.

Devils Playground

There is a shorter option that does not get much attention (except from some of the locals). The Northwest Slopes route crosses the Pikes Peak Highway at Mile 16 at a popular spot called Devils Playground. There is a large parking area there and the Northwest Slopes trail can be accessed at this point. Just cross the road, step over a cable fence (intended to block vehicles, not people) and follow the obvious trail to the summit.

Note: currently access to the summit by car is restricted due to summit house construction and Devils Playground is a staging area for free shuttle buses that take visitors to the summit.

This trail is 2.6 miles one way and 1300 feet vertical (mostly uphill but some up and down action). The last quarter mile before the summit is rocky and steep. The trail becomes more difficult to follow at this point but careful attention to the cairns will keep you on the right path. As shown on the map, this trail tends to stay close to the road so you will see vehicles along the way. All in all, this was a nice hike on a good trail.

Once on top, we set up our standard 2m FM station: Yaesu FT-90 and the Arrow 3-element yagi antenna. We quickly had a pileup on 146.52 MHz. It is kind of crazy up there when everyone starts calling because you are hearing everyone but the chasers are not.

Bob/K0NR using the Alinco HT and the PC board yagi to make a 1.2 GHz radio contact.

It was great to work Steve/WG0AT on Mt Herman (W0C/FR-063)  and Brad/WA6MM on Mount Morrison (W0C/FR-092). I also worked Paul/W0RW on 1.2 GHz with my Alinco HT driving a two-element yagi PC-board antenna.  (A quick comparison between the rubber duck and the yagi confirmed that the yagi does have some gain.) We ended up in a bit of a hurry as the clouds moved in but tried to work everyone we could. Our best DX on 2m FM was Dave/N0KM near Del Norte, about 100 miles away. On our way down, the clouds were in and out but no storms or lightning.

All of the usual warnings apply for hiking above treeline: start early and get off the mountain before the storms move in.

73 Bob K0NR

Colorado 14er Event: Mount Princeton (W0C/SR-005)

This photo of Mount Princeton was taken in spring time with plenty of snow still on the summit.

For the Colorado 14er Event, Joyce/K0JJW and I decided to activate Mount Princeton (W0C/SR-005).  I had climbed this summit many years ago, well before Summits On The Air (SOTA) was a thing. Princeton is a majestic peak that towers over Buena Vista and the surrounding area. We see that mountain quite often when we are up at the cabin, so I kept thinking it would be great to activate it for SOTA. Despite it being a popular 14er, it had only been
activated 2 times before (now 4 times with Joyce and me).

Hiking route to Mount Princeton shown on map (click to enlarge).

For complete information on climbing this summit, spend some time studying the 14ers.com web site. You will see references to the upper trailhead and the lower trailhead. A 4WD road leads to the upper trailhead which is where we started our hike at 11,800 feet. The lower (or main) trailhead is way down at the bottom (8900 feet) which makes for a much longer hike.  Also, you end up hiking on the road, which tends to be boring.

The Road

The 4WD road is mostly “easy 4WD” with some challenging spots inserted along the way. It was no problem to drive the road with our Jeep Wrangler. A crossover-style SUV would have trouble in several spots but can probably make it with very careful wheel placement. The road has sections that are very narrow, so be prepared to back up if you meet someone coming from the other direction. We parked very close to the upper trailhead, just pulling off to the side of the road, but there is not much room there. There is a lot more parking near the communications towers shown on the map but you have to hike another mile or so on the road. We made sure we had a parking spot by arriving at the upper trailhead at 5:30 AM; we were the first ones there.

Joyce/K0JJW on the trail to Mount Princeton.

The trail starts out very distinct and is easy to follow. Later, the terrain turns to talus (fields of large rocks) which continues for the entire climb. In some spots, the trail fades and is difficult to follow. Even when you are “on the trail” you get to do a lot of rock hopping. There is a reason they call these the Rocky Mountains. By my GPS app, the distance was 2.1 miles (one way) with 2360 vertical feet.

Summits On The Air

For radio operating, we focused on 2m FM using the Yaesu FT-90 Transceiver with LiPo battery, putting out 30W into a 3-element Arrow yagi antenna. I did have my very first DMR SOTA contact with Terry/KE0HNW, using my Tytera MD-380 handheld on 70 cm. I also made a few calls on 446.0 MHz but never got a reply.

Obligatory summit photo of Joyce/K0JJW and Bob/K0NR.

Here’s my log…Joyce’s is about the same but with fewer QSOs.

UTC   Band  Mode Callsign
15:38 144MHz FM KD0VHD mobile
15:40 144MHz FM KS0E Jefferson
15:42 144MHz FM KI6YMZ Maroon Peak (W0C/WE-002)
15:46 144MHz FM N0MTN Mt Sherman (W0C/SR-061)
15:47 144MHz FM K0ETT Huron Peak (W0C/SR-010)
15:48 144MHz FM WA6MM Mt Bierstadt (W0C/PR-015)
15:49 144MHz FM KN0MAP
15:50 144MHz FM KD0YOB on his way up Mt Flora
15:53 144MHz FM KE0HNW
15:54 144MHz FM KE0RMY
15:55 433MHz DV KE0HNW My first SOTA DMR contact
15:57 144MHz FM W0AJO
16:17 144MHz FM K0BLL Mount Belford (W0C/SR-006)
16:30 144MHz FM W0ASB Mount Antero (W0C/SR-003)
This extra large cairn (trail marker) is placed such that you don’t miss an important turn.

We worked six other mountaintop stations, all of them 14ers. I also worked a few more summits on our way down the mountain but we were outside the activation zone, so I submitted those as a chaser log.

Thanks to everyone that came out to play!

73 Bob K0NR

Double SOTA: Mosquito Peak and London Mountain

Mosquito Pass is a popular 4WD road in Colorado that takes you to 13,185 feet in elevation. It also provides access to two excellent SOTA summits, both over 13k feet: Mosquito Peak (W0C/SR-068) and London Mountain (W0C/SP-025). Joyce/K0JJW and I activated both summits on the same day. Fortunately, the weather cooperated nicely.

K0NR operating 2m FM on the summit of London Mountain.

The Road

We drove the road to the pass from the east (via Highway 9, heading north out of Fairplay then turning west onto County Rd 12 / Mosquito Pass Road). Consult the Pike National Forest map for more detail.

We’ve driven over this pass many times over the years and the condition of the road has varied quite a bit. Right now, I’d call this a moderate 4WD road. You will find trail descriptions online that call Mosquito Pass “easy 4WD” but I think that information is out of date. Our stock Jeep Wrangler had no problem with it but I would not recommend driving the road with a Subaru-class crossover SUV.

Map of the area shows driving tracks in orange and hiking tracks in blue.

Be aware that this road is closed by snow early in the fall and opens late in the summer. It is very unlikely to be passable in June and typically opens sometime in July. We decided to wait until August. Did I mention the road exceeds 13,000 feet in elevation? Check BushDucks for usually reliable pass information.

Mosquito Peak (W0C/SR-068)

Mosquito Peak as seen from the summit of London Mountain.

At Mosquito Pass, we took an unmarked 4WD north towards Mosquito Peak. This road is not shown on the Pike National Forest map. The road was in good condition but is a narrow shelf road with limited opportunities to turn around.  We parked the Jeep at an obvious turn-around spot and hiked on up the south ridge to the summit. No consistent trail, but a few cairns here and there. The one-way distance was about half a mile with 500 feet of vertical gain, so not very difficult.

It was quite windy on top so we hunkered down behind some rocks to provide some shelter. Using the Yaesu FT-90 transceiver and the 3-element Arrow 2m yagi, we worked these stations without much trouble: W0BV, N0EMU, KN0MAP, W0DLE, KD0VHD and W9GYA. Our best DX was N0EMU near Calhan, CO at about 100 miles.

London Mountain (W0C/SP-025)

London Mountain as seen from Mosquito Peak. Note the Mosquito Pass road at the bottom of the mountain. Our hiking route followed the top of the ridge starting from the right (west side).

To hike London Mountain, we drove back down the pass to the west end of the mountain and parked the Jeep at the point another 4WD road heads off to the south (see map). This road was gated closed and marked “no trespassing”.

We followed an obvious but unmarked trail leading from this small parking spot up the ridge of London Mountain. For the most part, we were able to follow this trail all the way to the summit. In a few spots it faded out but we stayed near the top of the ridge and always found it again. There were times when we really wondered if the trail’s route was the best option but it worked out fine. There are a few steep sections and places where we used our hands on rocks. The variety of rocks on this mountain (including marble) made it an interesting and fun hike. Following the top of the ridge also provided some ups and downs and many small false summits. The one-way distance is 0.85 miles with 600 vertical feet.

On top, we worked W0BV, W0DLE, N0EMU, KC0PBR, KN0MAP and KL7GLK on 2m FM. The wind dissipated a bit so it was more pleasant to hang out on this summit.  We left the summit around 1 pm local with blue skies and a few puffy clouds all around.

Joyce/K0JJW and Bob/K0NR hanging out on London Mountain.

These two summits are a great double-summit opportunity, as long as you have a capable 4WD vehicle. I suppose you could hike up the road but you probably can’t do both of the summits in one day.

73, Bob K0NR

Technician License Class – Black Forest, CO

Time: Saturday Sept 15 and Saturday Sept 22 (8 AM to 5 PM) 2018

Location: Black Forest Fire Station 1
(intersection of Burgess Rd. & Teachout Rd., Black Forest, Colorado)
Sponsored by the Tri-Lakes Monument Radio Association

The FCC Technician license is your gateway to the world-wide excitement of Amateur Radio, and the very best emergency communications capability available!

  • Earn your ham radio Technician class radio privileges
  • Pass your FCC amateur radio license exam right in class on the second day
  • Multiple-choice exam, No Morse Code Required
  • See live equipment demonstrations
  • Learn to operate on the ham bands, 10 Meters and higher
  • Learn to use the many VHF/UHF FM repeaters in Colorado
  • Find out how to participate in emergency communications

For more background on ham radio, see Getting Started in Ham Radio.

Registration fee: $30 adults, $20 under age 18
In addition, students must have the required study guide:

HamRadioSchool.com Technician License Course
New Edition, effective 2018 – 2022, $22.95

Advance registration is required (No later than one week before the first session, earlier is better, first-come sign up basis until class is full.)

To register for the class, contact: Bob Witte KØNR
Email: bob@k0nr.com

Operating Tips for VHF SOTA

Bob K0NR SOTA Joyce K0JJWHere are some operating tips that I have found useful when doing Summits On The Air (SOTA) on VHF. I’ve been using VHF and higher frequencies for SOTA exclusively and have activated over 100 summits in Colorado (and other states such as California, Wyoming, New Mexico, North Carolina and Tennessee.)

The challenge with VHF and higher is that the radio range is limited compared with HF. (It really does help to bounce those signals off the ionosphere.) VHF propagation will vary depending on a lot of factors but for SOTA activations our range is typically 50 to 100 miles. In the backcountry of Colorado, a 50 mile radius may not include very many active radio amateurs, so you may come up short in terms of radio contacts. For your first activation(s), you may want to stay close to a metropolitan area.

First, take a look my blog posting about the basics: How To Do a VHF SOTA Activation

Next, here are some additional tips to having a successful activation:

Send Invitations

Get the word out to people that may be within range. I try to keep track of who I’ve worked in the past or know to be in a particular area and let them know when I’ll be activating. In some cases, I’ll go ahead and make a specific sked with a station. That is, we’ll meet on a particular frequency at a particular time, perhaps on CW or SSB for maximum weak signal performance.

Create an Alert and then Spot yourself on the sotawatch.org web page (using smartphone app).

Make Your Call

By the rules, SOTA contacts are always simplex, so on 2 meters the place to try is usually 146.52 MHz, the National Simplex Calling Frequency. (Some areas have established other 2m simplex frequencies to use for SOTA, so inquire locally.) This is the place to try calling.

Who are you going to find there? Hard to say. SOTA chasers will often listen to “five two”…that’s where they find SOTA activators. Also, there are radio hams that just like to hang out on 52…they like 2m FM operating but they don’t like repeaters so they listen here. You will also find that many mobile stations monitor 146.52 as they drive through rural areas. Basically, they are listening for anyone around but aren’t flipping from repeater to repeater as they change location. I’ll often hear 4WD enthusiasts, hikers, boaters, campers, etc. using Five Two.

We usually say something short and sweet one operating FM repeaters (“K0NR Monitoring”) but for SOTA we need to make a longer call. Realize that not everyone knows about SOTA so they may not know what the heck you are doing. Make a call such as this: “CQ CQ this is Kilo Zero November Romeo operating from Pikes Peak – Summits On The Air – anyone around?” Or “CQ 2 meters this is K0NR on Pikes Peak – Summits On The Air.” Do a little bit of “selling” when you make your call. Sound like you are having fun.

Sometimes people have their radios to set to scan multiple frequencies with 146.52 MHz set as one of the channels. If your transmission is too short, they will miss it. Also, it is helpful to mention the frequency you are calling on…sometimes I’ll say “CQ Five Two This is Kilo Zero November Romeo…”

Be Patient

Be patient. Sometimes it just takes time to accumulate your 4 QSOs to qualify for activator points. The few times I have been skunked on QSOs were when I did not have enough time, usually because storms were moving in. Keep calling every few minutes, taking a break once in a while to enjoy the view.

Try Other Frequencies

You may want to try other simplex frequencies, so know the band plan for the area you are activating in. Another trick is to get on a local 2m repeater and ask for someone to move over to simplex to work you. I have not had to do this very often but it does work. Have some of the local repeaters programmed into your radio.

Most of the SOTA VHF activity is on the 2 meter band, so that will be the “go to” band for most activations. However, it is fun to try other bands such as 6m and 70cm. I’ve been playing around with 1.2 GHz also (23 cm).

Improve Your Station

Hopefully by now you know that using an HT with a rubber duck antenna is a bad idea. Get at least a half-wave vertical or roll-up j-pole antenna. Better yet, get a small yagi antenna to add 5 or 6 dB to your signal. It can make a big difference on who you can work.  I’ve even started carrying a small 2m/70cm transceiver to get my 2m transmit power up to 30W. The objective is to extend your operating range.

Another angle is to use SSB and CW, which are much better for weak signal performance (compared to FM). This sets you up to work the serious VHF stations which tend to use these modes and have large high-gain antennas (horizontally polarized). Think about extending the range of your communications from a 50 mile radius to 200 miles, what a difference! (My best 2m distance on SOTA is 229 miles, using 2m CW on Capulin Mountain.)

73, Bob K0NR

Dakota SOTA Adventure

Most of our Summits On The Air (SOTA) activity is here in Colorado but every once in a while, Joyce/K0JJW and I get the opportunity to branch out to other locations. It’s a fun thing to do with SOTA…do a little hiking, sightseeing and ham radio operating. On this trip, we decided to visit the Black Hills region of South Dakota, a place we had enjoyed many years ago.

SOTA Bob K0NR
Bob/K0NR operating 2m FM using a Yaesu FT-90 driving a 3-element yagi antenna.

Our general approach was to identify a list of SOTA summits that were not too difficult, with reasonable activator points (>6) and in locations we wanted to visit. (One good method is to use the SOTA database to sort summits by points, then look for ones that have been activated the most. Those are usually easy to access.) I noticed that Gary/KT0A had activated all of the summits on my list so I emailed him and received some great advice. Gary has also provided most of the activation notes in the SOTA database, which proved to be helpful. Thanks, Gary.

We use VHF and UHF exclusively for our SOTA activations, so I was a bit concerned about whether we’d find enough VHF activity in the area. Typically, we can work 100 miles or so on 2m FM from a summit without too much trouble but if no one is out there, it’s kind of difficult to make radio contact. South Dakota is not the most populous state, so it was a concern.

We spent three days in the western South Dakota area: did three summits the first day, three summits the second day and two summits the third day. The Black Hills are about a 6 hour drive from the Denver area, which makes for a good SOTA destination from Colorado.

Scotts Bluff (W0N/PH-005)

Hey, wait a minute, this one is in Nebraska, not the Dakotas. It turns out Nebraska (W0N) has 15 SOTA summits, most of them in the pan handle of the state. Scotts Bluff (4649 feet) is located in Scotts Bluff National Monument and has historical significance as an important landmark on the Oregon Trail. This is an excellent example of the SOTA program providing that extra incentive to visit a new location that we otherwise would have skipped.

summit photo Scotts Bluff
Joyce/K0JJW, Bob/KC0OZ, Bob/K0NR and Leeloo on the summit of Scotts Bluff.

We drove to the parking lot near the summit followed by a short hike to the actual high point. (You can hike up from below if you’d prefer more of an ascent.) We ran into Bob/KC0OZ who is a volunteer at the national monument (and his dog Leeloo).  I wasn’t sure how much VHF activity I would encounter on a weekday but we found quite a few friendly folks lurking on 2m FM in the area. I think Bob knew everyone that we worked on the 2m band.

Rankin Ridge (W0D/BB-089)

Inside Wind Cave National Park, Rankin Ridge is a 1-mile (200 feet vertical) loop trail in good condition, providing an easy hike to a lookout tower. (The lookout tower was marked “no entry”.) This was a very enjoyable hike and should be on the “must do” list for this area.

Rankin Ridge lookout tower (not in use).

Mount Coolidge (W0D/BB-012)

Mount Coolidge is a drive-up summit (good gravel road, 2WD), easily accessible from Highway 87 in Custer State Park. It is the site of an historical rock lookout tower which is now encroached on by many radio towers. The Custer State Park web site says the road to Mount Coolidge is generally open 9 am – 5 pm from Memorial Day into late September.

Mount Coolidge lookout tower

This summit is easy to access and provides some very good views of the Black Hills. Even though I’m a fan of radio towers and antennas, the way they surround the historic lookout tower really detracts from the summit. Don’t come here expecting a wilderness experience.

Odakota Mountain (W0D/BB-002)

At 7210 feet, Odakota is the second highest summit in South Dakota. This summit is a relatively easy bushwhack hike through grass and over some downed timber, less than a 1/2-mile in distance and only 100 feet vertical. You’ll want to have the Black Hills National Forest map guiding you to this summit. Actually, that map is useful for all of these summits in South Dakota.

Bob/K0NR cranking out CW on the 2m band using the FT-817.

Bear Mountain (W0D/BB-029)

Next up was Bear Mountain, another summit that has a lookout tower now accompanied by radio towers. (Not as bad as Mount Coolidge.) There is a good gravel road to the summit suitable for 2WD vehicles. Again, the Black Hills National Forest map is a great resource for access information.

Atlantic Hill (W0D/BB-037)

This summit was a reasonable bushwhack hike with lots of tall grass and significant downed timber. My GPS app measured the distance at 0.45 miles with 450 feet vertical.

Joyce/K0JJW standing near the summit of Atlantic Hill.

We followed KT0A’s instructions from the SOTA website which took us to the west side of Atlantic Hill. Again, use the Black Hills National Forest map for guidance. The map below shows the road as “297 1G” but it was just labeled “G”. Also, note that the road is gated closed for part of the year. The “G” road looked a bit sketchy but turned out to be easy to navigate with our crossover SUV. The map below shows the track we took. There was no trail and at times the grass was very tall. All things considered this was a good hike and the summit is quite pleasant.

Our hiking route up Atlantic Hill.

Cicero Peak (W0D/BB-009)

Cicero Peak has a rocky road (FS 338) to the summit, OK for high clearance 2WD vehicles. There’s a small radio site at the summit. The views are probably wonderful but we did not see any because of the low hanging clouds when we were there. This road also has a gate at the bottom and is closed seasonally.

Cicero Peak map
Road to Cicero Peak.

Custer Mountain (W0D/BB-010)

Custer Mountain was the toughest hike of the trip…a bushwhack through tall grass, downed timber and plenty of rock near the summit. Actually, the worst part was the swarms of gnats that followed us everywhere — they were out in full force after some rainy weather. Actually, I think it was the gnats that wore us out…difficult to step over rocks and logs when you’re swatting the little buggers.

Bob/K0NR on the summit of Custer Mountain.

Again, we followed KT0A’s activation notes on the SOTA web site. There is really no “good” way to ascend the mountain but the map below shows the track we used to descend the mountain. It has a few less rocks and downed trees to climb over. The key is to approach the summit from the west/northwest. The distance recorded on my GPS app was 0.83 miles and 650 feet vertical.

Custer Mountain map
Hiking route up Custer Mountain.

Radio Operating

Our radio gear varied from summit to summit but we always carried a Yaesu FT-90 2m/70cm transceiver, an Arrow 3-element yagi for 2m, dualband j-pole for 2m/70cm and a gaggle of handheld transceivers. On most of the summits, we also had the FT-817 so we could work CW/SSB on 2m and 6m. As usual, most of the contacts were on 146.52 MHz FM, using the FT-90.

NC0K and W0FUI were listening a lot and worked us on 5 summits, KE0LXT snagged us on 4 summits (and met us in person on Bear Mountain). We worked KD0UST from 2 summits.

Our longest distance QSOs were with Jim/WD0BQM in Mitchell, NE (grid DN81cw). From Scotts Bluff we both worked Jim on 2m FM at relatively short range. On Odakota Mountain, we worked Jim/WD0BQM in Mitchell, Nebraska (Grid DN81cw) on 2m at a distance of 139 miles. I initially worked Jim on CW with very good signals. Joyce also worked him on SSB but she had to work a bit to complete that contact. From Bear Mountain, I worked Jim on 2m CW again with some difficulty because signals were clearly weaker but Joyce was not able to complete using SSB.  Thanks for getting on the air with us, Jim!

I made one 6m ssb contact with K0CX from Bear Mountain. Other stations worked during the trip: KC0WVE, N8XBD, WB0VAO, KB0ZXH, KL7MH, N0SQ, W0SSB, KD0QDG, KD0ZIP, AF0DJ, KD0ZIR, W0NIL, W7REA, K0CX, WB0PZQ, N0DUX, N0DUW, KC0GWU, W3MEB, W7LFB, W0LFB, KF0XO. We managed to make at least 4 QSOs on each summit without too much difficulty by calling on 146.52 MHz. On Custer Mountain, we got impatient and went over to the 146.85 MHz (Bear Mountain) repeater to beg for a simplex contact. Thanks, KF0XO.

It was a great trip to a beautiful part of the western United States. We met some really nice hams along the way. Thanks to everyone that took the time to work us on the summits.

73, Bob K0NR

Signal Butte (W0C/FR-165): SOTA Activation

Signal Butte
This view of Signal Butte shows the classic conical shape of the summit.

Signal Butte (W0C/FR-165) is a popular Summits On The Air (SOTA) summit about 8 miles north of Florrisant, Colorado. Joyce/K0JJW and I had this one on our SOTA list for a while now and finally got around to activating it. At an elevation of only 9459 feet, it is not a big mountain but it provides a spectacular 360 degree view of the surrounding area. Signal Butte is within the Hayman Wildfire burn area from June 2002 and you can still clearly see the effects of that fire.

Signal Butte trail map
The well-established trail starts at the end of FS 362A. The red line shows our hiking route as recorded on my GPS app.

To get to the trailhead, consult the USFS Pike National Forest Map. Drive to the trailhead using FS 362, then turning onto FS 362A which leads to a well-used parking area. These roads are easy-peasy 4WD and high-clearance 2WD is probably sufficient.

This is the view of Signal Butte from the trailhead.

The well-constructed trail is only a half mile long and 540 feet vertical, with many tight switchbacks and rock steps. I’d call this a good visitor hike because it will get most people huffing and puffing so they feel like they really did some climbing but then reward them with outstanding views on top.

A look at a typical section of trail with Pikes Peak in the distance.

On the Air

We both operated mostly on 2m FM (146.52 MHz) with the Yaesu FT-90 cranking out 30W into an 3-element yagi antenna. The best DX for the day was Dave/N0KM about 107 miles away in the San Luis valley (DM67vr). Note that our signals had to find their way across several mountain ranges for us to make contact. Who says VHF is only line of sight?

Steve/WG0AT showed up on Mount Herman (W0C/FR-063) for a summit-to-summit SOTA QSO. Then later, Doug/KD5OUG called us from the summit of Mount Evans (W0C/FR-003) for another summit-to-summit contact. Apparently Doug was just playing tourist and decided to pull out his 2m HT and give a call. Thanks to these stations that contacted us: K0LJW, W0RW, WG0AT, KC0PBR, K0MGL, KD0MRC, N0KM, N0EMU, KD0VHD, K0PV, K0PWO, W0BV, WB0TGE, K0GPA, K0TPC, WZ0N, KD0OUG

Signal Butte 2m fm Pikes Peak
Bob/K0NR cranking out the 2m FM contacts with Pikes Peak in the background.

As you can see from the photos, the weather was excellent so we really enjoyed the activation. We both had a great time with it and we will undoubtedly be back. This SOTA summit is highly recommended because of the easy access, reasonable difficulty, established trail and excellent radio and optical horizons.

73, Bob K0NR

Colorado 14er Event (2018)

August 4 & 5, 2018
Saturday and Sunday
www.ham14er.org

Amateur Radio operators from around Colorado will be climbing many of Colorado’s 14,000-foot mountains and Summits On The Air (SOTA) peaks to set up amateur radio stations in an effort to communicate with other radio amateurs across the state and around the world. Join in on the fun during the 27th annual event and see how many of the mountaintop stations you can contact. The covers the entire weekend but many mountaintop activators will hit the trail early with the goal of being off the summits by noon due to lightning safety concerns.

Now including Summits On the Air (SOTA), which adds over 1700 potential summits! If you aren’t up to climbing a 14er, there are many other summits to choose from (with a wide range of difficulty). See the Colorado SOTA web page at w0c-sota.org

Radio operators who plan to activate a summit should post their intent on the ham14er Yahoo Group. To subscribe to the “ham14er” email list, visit the Yahoo groups site at http://groups.yahoo.com/group/ham14er/ . Also, be sure to check out the event information at http://www.ham14er.org  It is also a great idea to post an ALERT on the SOTAwatch.org website.

Frequencies used during the event
Activity can occur on any amateur band including HF and VHF. The 2m fm band plan uses a “primary frequency and move up” approach. The 2m fm primary frequency is 147.42 MHz.  At the beginning of the event, operators should try calling on 147.42 MHz. As activity increases on that frequency, move on up the band using the 30 kHz steps. Don’t just hang out on 147.42 MHz…move up! The next standard simplex frequency up from 147.42 MHz is 147.45 MHz, followed by 147.48 and 147.51 MHz.

Frequency (MHz) Comments Frequency (MHz) Comments
147.42 Primary 2m FM Frequency, then up in 30 kHz steps  7.032 40m CW Frequency
147.45 Alternate 2m FM frequency  7.185 40m SSB Frequency
147.48 Alternate 2m FM frequency 10.110 30m CW Frequency
147.51 Alternate 2m FM frequency 14.060 20m CW Frequency
446.000 Primary 70 cm FM frequency 14.345 20m SSB Frequency
446.025 Alternate 70 cm FM frequency 18.092 17m CW Frequency
1294.50 Primary 23cm FM frequency 18.158 17m SSB Frequency
144.200 2m SSB calling frequency 21.060 15m CW Frequency
50.125 6m SSB calling frequency 21.330 15m SSB Frequency
28.060 10m CW Frequency
Other Bands/Modes Standard calling frequencies and/or band plans apply. 28.350 10m SSB Frequency

Warning: Climbing mountains is inherently a dangerous activity.
Do not attempt this without proper training, equipment and preparation.

More operating information here: www.ham14er.org

Sponsored by The Colorado 14er Event Task Force

Download:  Colorado 14er Event Flyer 2018

FT8 Adoption: The New Cool Thing

The new cool digital mode for amateur radio is FT8, made possible by Joe Taylor/K1JT and the WSJT software. At first, FT8 seemed like just the next digital mode to try but it is turning out to have a bigger impact than that. Jeff/KE9V recently posted about the popularity of FT8 here:

FT8 is so far out in front that other digital modes are a foregone conclusion. CW only remains relevant because of its popularity in contests. Even phone, the Holy Grail of wannabe HF operators everywhere, is a nearly forgotten mode compared to FT8.

This reminded me of some of the classic research on adoption of new innovations. What are the factors that cause a new thing to really take off versus languish on the shelf? How do these apply to the quick adoption of FT8?

Diffusion of Innovations

In Diffusion of Innovations, E. M. Rogers lists five factors will influence how quickly a new innovation gets adopted:

Relative Advantage: The degree to which the innovation is superior to ideas it supersedes.

If an innovation is clearly superior to the present way of doing things, people will be more likely to adopt it without too much concern about its usefulness. If it’s not clearly better, people will tend to question whether it is worth the trouble of changing.

Compatibility: The degree to which the innovation is consistent with existing values, past experiences, and the needs of the user.

If an innovation is similar to existing practice and blends in well with user needs and expectations it is more likely to be adopted.  If it requires change on the part of the user or represents an inconsistency with the user’s past experience, it may be rejected.

Complexity:  The degree to which the innovation is relatively difficult to understand and use.

The more complex something is, the more likely people will reject it because “it’s just too much trouble.”  Understandable ideas will tend to be considered more carefully and are more likely to be adopted.

Trialability:  The degree to which an innovation may be tried on a limited basis (in other words, without committing to full-scale, total operational change.)

The easier it is for an individual or organization to try something out without being fully committed, the more likely they will give a new innovation a try.  If the innovation can only be tried with full-scale change and great expense, it will tend to get rejected.

Observability:  The degree to which the results from the use of an innovation are visible and easily communicated to users and other decision-makers.

If the results of an innovation are difficult to measure or see, rejection is more likely.  If the results are clearly visible, then the adopting individual or organization can more easily correlate the results to the innovation.  Generally, a decision-maker wants to be sure that the intended results can be measured, otherwise how can the innovation be evaluated?

Adoption of FT8

It is very clear that FT8 has a strong relative advantage to other modes. Just listen to the many comments from hams like “the band conditions are really bad but I’m still making contacts.” One could argue that FT8 is not that compatible with existing operating habits (think CW or SSB) but the mega-trend of using “sound card modes” is a huge enabler. For some time now, hams have been using the PC platform as a digital signal processing engine, using the sound card to handle the analog-to-digital conversion (and back). Perhaps this traces back to PSK31 as one of the major forces that caused hams to connect their transceivers to their computer. In that sense, FT8 is very compatible with existing sound-card-enabled stations, making it strong on compatibility and trialability. Just load up the WSJT-X software and give it a try. Of course, observability is strong too…now I’m making QSOs when I wasn’t before.

There is a bit of a learning curve with FT8, which could be a barrier to adoption. You need to learn the software and fiddle around with the settings to make it work. But for many hams, this is not a barrier but a fun challenge to take on. Most of us like to try new things, as long as they aren’t too frustrating.

The final point I’ll make is that the popularity of FT8 reinforces my contention that Ham Radio Is Not For Talking. FT8 is all about making a radio contact and does not enable conversations. Sure, most hams like to talk (usually about radios) but when the bands are poor they like making radio contacts via FT8. Making QSOs is king.

Those are my thoughts. What do you think?

73, Bob K0NR

Things On The Air (TOTA) Launched

The Sundance Mountain Radio Association (Palmer Lake, CO) today announced the creation of the Things On The Air (TOTA) program. The radio association’s Need More Lists Committee spent the past year analyzing the effect of various “on the air” programs, including the Islands On The Air (IOTA), National Parks On The Air (NPOTA) and Summits On The Air (SOTA).

The overall trend is clear. The ham radio community used to be satisfied with the basic DXCC list (a list of countries that aren’t really countries so we have to call them entities). But over time, additional lists to be worked have been created. For example, the Islands On The Air was created in 1964. More recently, the Summits On The Air program was established in 2002. It seems that every year or so we hear of another “something” on the air program. Even the normally docile satellite grid chasers created a Walmart Parking Lots On The Air (WMPLOTA) event.

Unfortunately, this has created a miss-mash of programs with inconsistent and conflicting rules. The Need More Lists Committee concluded that the best solution to this problem is to fast-forward to the likely end state: pretty much everything can be put on the air. Inspired by the latest technology hype, the Internet Of Things (IoT), the committee named this program Things On The Air (TOTA).

To be comprehensive and inclusive, the TOTA program is based on the existing Maidenhead Grid system. There are 324 fields defined (AA through RR), each having 100 squares (although they really are not square). Each square contains 576 subsquares indicated by aa through xx. So using the six-character locator results in 324 x 100 x 576 = 18,662,400 unique locators. Or, as the Committee likes to say, about 18 million locators. In North America, the six-character locator represents a rectangle about 3 miles by 4 miles. This raises the question of how many things need to be on the list inside a typical 3 x 4 mile rectangle. An in-depth study (actually just Leroy randomly selecting objects) revealed there are a lot of things that might need to be listed in even a small area.

For TOTA to achieve the vision of being the “last list of things on the air”, it must accommodate an unlimited number of listed things. To start out, a 15-digit serial number is appended to the 6-character locator to indicate a TOTA thing. As the program grows and new Things are added to the list, the 15-digit number can be extended indefinitely.

Here’s an example listing of some of the first TOTA designators:

Locator  Serial Number      Description
DM79nb   000000000000001    Walmart Parking Lot
DM79nb   000000000000002    Home Depot Parking Lot
DM79nc   000000000000001    Leroy's home QTH
DM79nc   000000000000002    Leroy's barn
DM79nc   000000000000003    The big tree behind Leroy's house
DM79db   000000000000001    Charlie's home QTH
DM78lu   000000000000001    Pikes Peak Summit
DN70di   000000000000001    Rocky Mountain National Park
EN71jb   000000000000001    US Home of ZF2PF
EM48ox   000000000000001    WZ0W Tiki Bar

When making a valid TOTA contact, the activating station must give a signal report and the TOTA designator: 6-character locator followed by the serial number (at least 15 digits but may be longer). The official TOTA list is currently maintained on an Excel spreadsheet on Leroy’s computer but a HDFS database is under construction to handle the expected large dataset.

The Committee requests the help of all amateur around the world to submit additional entries into the TOTA list. Eventually, this process will be automated via the ThingsOnTheAir.com web site but for now submissions can be made in the comments field below.

VHF SOTA: Abajo Peak (W7U/SU-014)

While on a canyon country hiking/Jeeping trip in Utah, Joyce/K0JJW and I decided to do a couple of Summits On The Air (SOTA) activations. Abajo Peak (W7U/SU-014) showed up as a suitable target, being an easy-access drive-up summit at 11,360 feet, just west of Monticello. While the forest service map shows this as a 4WD route, it turned out to be a well-maintained road that most 2WD vehicles can handle.

The radio site on the summit of Abajo Peak

The map below shows the area. The only real challenge was finding B102 heading south/southwest out of Monticello. This later turns into route 0087, which swings south of another SOTA summit: South Peak (W7U/SJ-003) and up over Dickson Pass. (South Peak could be a second summit for a double activation.)

 

Abajo Peak is an excellent summit for VHF/UHF propagation with a good radio horizon in all directions. There is a substantial radio communications site on top which did create some local interference on 2m and 70cm. Moving a bit away from the actual summit caused the interference to mostly disappear.

I was concerned that we would not find enough activity on VHF in this rural location, so I put the word out to some of the hams in Utah and western Colorado with capable 2m SSB stations. Our equipment was a Yaesu FT-817 (all mode, 5W) driving a 3-element yagi antenna. We also had a 50W Yaesu FT-90 that can provide a bit more power out on 2m FM. And we had the usual collection of HTs.

The longest distance contacts for the day plotted on a map (click to enlarge).

Around noon, we started calling on 146.52 MHz and worked N7VWX in Nucla, CO (about 57 miles away). We switched over to 144.200 SSB and worked W0DSW in Cedaredge, CO (113 miles). Then we worked Bill/K0UK in Grand Junction (95 miles) on 144.200 SSB…not real strong but we made it. A bit later we came across KB7REB on 146.52 FM who said he was out hiking in a canyon and was surprised to hear anyone.  We also worked KB7TRA on 146.52 (I think he was mobile east of us). We also worked W0DBB in Montrose, CO. I kept beaming to the west looking for W7DHH and I eventually heard him calling on 144.200 CW. I tried getting back to him but he was apparently not hearing me. N7KMK (same vicinity as W7DHH) came on the air and I was able to copy him on SSB. He also had trouble hearing me, but for a few seconds the signals came up a bit and we made the contact. N7KMK was my best DX for the day at 154 miles.

Four contacts are required to get the SOTA activation points and we probably would have been successful just randomly calling on 146.52 MHz FM. However, taking along the SSB transceiver and alerting the 2m weak-signal crowd certainly paid off with some longer distance QSOs. It is always a blast to be working over 100 miles on VHF QRP.

73, Bob K0NR

Phone Contesting Tips For DX Contests (AE6Y)

Proper use of a phonetic alphabet can be very helpful when working phone under marginal conditions. I’ve written a basic article on phonetics over at HamRadioSchool.com, so you might want to review that. I recently came across an article by Andy/AE6Y on some tips and tricks to use during contests. He does a super job of explaining why the ITU phonetic alphabet isn’t always the best choice. I don’t usually reprint other author’s work on this blog but somehow this article really got my attention. Reprinted here with permission. – Bob K0NR

Phone Contesting Tips For DX Contests

Andy Faber, AE6Y
3/29/18

This article is prompted by the recent WPX SSB contest, in which I worked thousands of guys from Aruba as P49Y, which engendered much reflection (and teeth-gnashing, to be sure) about how U.S. hams can be best understood from the DX end.  I’m not addressing this to relatively clear-channel domestic contests but to the situation where you are trying to get through to a DX station that may be hearing a pileup, plus noise, ear-splitting splatter from adjacent stations and all of the other sonic annoyances that make many contesters prefer CW. If there is no pileup and you know the DX station can hear you completely clearly, then you’ll get through regardless, but if not, here are some suggestions:

First, be sure you are calling on his exact frequency.  In CW contests, it can be helpful to separate yourself from the pack by calling off frequency, but that’s not true in SSB.  Off-frequency stations sound distorted and are hard to understand.  The DX station may well come back to a weaker, but more intelligible station that is on frequency, even if you are louder.  In order to work you, he has to figure out which way to adjust the RIT, and then go ahead and do it. A tired operator on the other end may just not bother, until he has worked everyone else.

Second, make sure your audio is clean.  It is so much easier to understand clear audio, even if it is weaker than a louder, distorted signal.  KH7XS mentioned in his 3830 posting that this year there particularly seemed to be over-processed signals coming from South America, and I noticed the same thing.  It used to be that the Italians who were the worst offenders, but they seem to be better now.  This weekend, the Cubans were particularly hard to understand. The prize for the easiest audio to understand goes each contest to the hams from the British Isles.  The G’s, M’s and their derivatives invariably have very clean (and usually nicely treble) audio that can be understood even when the signal doesn’t budge the S-meter.  On several occasions I chose a weak but clear Brit over a loud, but distorted, competitor.

Ok, so you have a clean signal and are calling on frequency, now how do you get the information through, both your callsign and your contact number (for WPX)?

Here are some tips:

If you are loud enough and have an easily recognizable call, you can skip phonetics.  So this weekend, when K1AR called, he was easy to pick out, same for K3UA, K3ZO, N6AA, and a few others. But for most guys, and when in doubt, use phonetics.  Endless bandwidth has been expended on the subject of phonetics, and people have differing opinions on the topic, but here are my thoughts from being on the DX end:

The first thing to understand is that the standard, “recommended” international alphabet works dismally in marginal conditions.  The words are too short, and some don’t have unique sounds. Generally speaking, the one-syllable words just get lost, while the two syllable words are better, and the longer ones are even better.

Thus, one-syllable words like “Fox”, “Golf” and “Mike” are horrible.  Some of the two-syllable ones are OK (e.g., “Hotel” and “Quebec”), but others, such as “Alpha” and “Delta”, or “X-ray” and “Echo”, “Kilo” and “Tango” sound very similar, so are easily confused.  I worked a guy with the suffix XXE, and had to get a number of repeats until he finally said “X-Ray X-ray Ecuador,” which did the trick.

There are two basic cures for these problems. The first is only to use these crummy phonetics the first time as a trial.  If the DX station asks for a repeat, say your call twice, once with the standard phonetics and once with different ones.  Don’t just keep repeating your call the same way.  Something in either the way you say it or the way the DX hears it is creating ambiguity.  If you keep repeating the call the same way it may well be that part of it is just hard to decipher, and it may not get any easier.

If the DX station is a good English speaker then custom phonetics may work, such as “King George Six…” In fact when I thought a KK4 station was a K4, he used a very effective phonetic, “King Kong Four…” WA2JQK uses “Jack Queen King” in domestic contests, but that won’t work well for non-native speakers.  The Wyoming station N7MZW uses “Many Zebras Walking” sometimes domestically, but I noticed he was using normal phonetics in WPX.

The second approach is to switch to the geographical phonetic alphabet.  This features longer and more distinctive-sounding words, which are much easier to understand.  For example if your suffix is, say, HLF, then you can say “Hotel Lima Fox,” then try “Honolulu London Florida.” When I give my call with last letter “Yankee” and get asked for a repeat it works much better to say “Last letter Yankee, last letter Yokohama.” Many of the geographic phonetics work particularly well for speakers of Romance languages like Spanish and Italian (e.g., terms like “Guatemala”, “Nicaragua”, and “Santiago”). There are a few letters for which there are not good geographic equivalents.  Obviously, “X-ray” is one of them. For “Echo”, “England” is sometimes used, but “Ecuador” is better.  Although “London” and “Lima” are both geographic terms, “London” is much better.  And “Denmark Mexico” is many times superior to “Delta Mike.”

Numbers in the callsign can also cause trouble.  What if the station comes back to “K3” instead of “K6”? In general, just try to repeat the number, but if he still doesn’t get it, you can try counting, e.g. “Kilo Six, 1, 2, 3, 4, 5, 6.” Or for us West Coasters, “Kilo Six in California, West Coast” can be useful.

Which brings me to the subject of numbers in exchanges like WPX.  I commented in a 3830 post a few years ago that the English numbers that everyone uses are just too ambiguous, most of them being plain too short.  I recommended using some Spanish numbers, like “cuatro” and “ocho”, but that suggestion went nowhere, so I hereby drop it, unless you are trying to get through to a native Spanish or Italian speaker.  In fact, In WPX, I just couldn’t understand a number from a CO8 station with terrible audio. I kept asking, “your number 424?”, “your number 242?”, “your number 224”, etc. Normally, one doesn’t confuse “two” and “four,” but this guy’s audio was driving me crazy and I wasn’t sure how well he was understanding me either.  Finally I had the presence of mind to ask in Spanish, and when he said “dos cuatro cuatro,” he was in the log.  If he had said that in the beginning I would have understood him in spite of his maladjusted audio.

One source of confusion for the DX station is not knowing how many digits there are, particularly later in the contest when a number can have 1, 2, 3, or 4 digits.  There are a couple of ways to help. For example: suppose the DX station thinks he hears “[garble] six six” and he asks: ”your number six six?” If your number is just 6, you can say to be helpful “Negative. My number zero zero six, number six.” Adding the word “number” in front of the digit indicates there are no missing digits.  If your number is 66, just say “Roger, roger.” If it’s 56, say “Negative, number five six, fifty–six.” If it’s 256, say, “Negative. Number two five six, two fifty-six (or even “two hundred and fifty-six”). I know we were taught that it is incorrect to say “two hundred and fifty-six,” and we should just say “two hundred fifty-six,” but using the “and” makes it more intelligible.

In general, it’s usually best to say your number twice, in two different ways.  For example it’s often hard to discern, “two three” from “three three”. So you can say: “five nine, two three, twenty-three,” since “twenty” and “thirty” sound very different.  Similarly if your number is 15 and you say “one five”, that might be confused with “one nine”, so say “one five, fifteen.” If it’s late in the contest and you might be expected to have a three-digit number you can say “zero two three, only twenty-three”. And if you have a one digit number late in the contest, it’s best to add zeros, saying, e.g., “zero zero nine, number nine”, not just “nine.”

I hope these tips from the DX end are helpful.  They should be even more useful in the next few years, as declining sunspots forcing us increasingly into the QRM alleys of 20 and 40 meters.

Return to SOTA Summit W0C/SP-094

Back in the summer of 2013, I did the first Summits On The Air (SOTA) activation for W0C/SP-094. This is an unnamed summit (10350) near Trout Creek Pass not far from our cabin. Although I did activate it, I only made two radio contacts from the summit (so no activator points awarded). A thunderstorm had moved in and I decided to abandon the effort. Actually, I don’t recall much from that activation other than getting skunked due to weather.

Summit of W0C/SP-094
Joyce/K0JJW on the summit of W0C/SP-094

So today, Joyce/K0JJW and I returned to the summit to set things right. Following Walt/W0CP’s suggestion, we drove the Jeep from the south (Hwy 24) taking FR 305 to FR 376 and parked just off the road at 38.86967, -106.03146. FR 305 is a good 2WD gravel road; FR 376 is easy 4WD (or high clearance 2WD). (Be aware of the seasonal road closures from Dec 1 to April 15.) A winter storm warning was in effect the night before we hiked, so I wondered if the weather was going to win again. As it turns out, we had 3 or 4 inches of new snow on the ground which was not a problem.

SP-094 hiking route
Hiking route shown in blue.

From the parking spot, the hiking route is not critical. Just head for the summit. We decided to swing slightly to the east which gave us a little less slope. It also provided us a nice walk across the top of the ridge that extends out to the southeast. As you can see from the photo, the summit is flat with a reasonable number of trees. Round trip distance is 1.5 miles with 700 feet of vertical. Easy peasy.

Once on top, we called on 146.52 MHz and worked Bob/W0BV, Skip/W9GYA, Jim/KD0MRC, Walt/WZ0N, Dave/N0KM and Ken/WA6TTY. We also made a couple of 446.0 MHz contacts with some of the same stations.

Summit-to-Summit

Earlier, as we left for the trailhead, I got an email from Steve/WG0AT that he was headed up Mt Herman (W0C/FR-063). This sounded like a great summit-to-summit opportunity! I figured we’d need our best 2m fm station, so I got out the Yaesu FT-90 and the Arrow 3-element yagi. I saw him spotted on SOTAwatch so I called him multiple times on 2m fm. Finally, I heard someone else talking to him on 146.52 which caused me to swing the antenna back and forth. Sure enough, I could hear him…barely…with the antenna pointed way south of his location. This often happens in the mountains…the direct path is not always the best path on VHF. I just barely worked Steve and got him in the log.

We stayed on the summit for a while, enjoying the view of Mt Princeton, then hiked down. It was a wonderful activation…much better than the first time.

73, Bob K0NR

Are Recent Technicians Getting on the Air?

Our radio club (Tri-Lakes Monument Radio Association) offers a 2-day Technician license class which has resulted in over 300 new Technician licenses in past years. We also offer a number of activities to help new licensees get started in ham radio. Still, we wonder how many of our newly-minted Techs have actually gotten on the air and are actively using amateur radio.

To assess that, I surveyed 258 people that went through our Technician license class from 2010 to 2017. We’ve actually had more students than that get their license but I don’t have valid email addresses for all of them. To improve the response rate, I kept the survey short at 5 questions.

The response rate was 42% which is quite good for this type of survey. I suspect there is a response bias in that active ham radio folks are probably more likely to reply to this survey. People that have lost interest are less likely to reply. That’s just my opinion; I don’t have data to support that.

 

Almost half of our Technician class students upgraded to General but only a few went on to Extra. Overall, I see this as a good result but I expected to see a few more Extra class licensees.


 

Most of the respondents have been on air recently: 60% of them have made a radio contact in the past 6 months. On the other hand, that means about 40% of not made a contact in half a year. It is disappointing to see that 13% have never made a ham radio contact.


There is quite a range on how active the respondents are with 45% making 10 or fewer contacts in 6 months.

 

About one half of the survey respondents are members of our radio club. Some of them are also members of other radio clubs in the area. Some of our students travel a long distance, up to 100 miles, to attend this class so it makes sense that they find a radio club near their home.

 

Most of the respondents reported being active on 2m/70cm FM. About 18% of them are on HF Phone. The total for all forms of HF operating (CW, digital and phone) is not shown on the chart but it is roughly 20%. While roughly half of the respondents have their General or Extra class license, only 20% are actually using the resulting HF privileges.

Conclusions

My broad conclusion is that our radio club should continue to provide opportunities for our members to develop their operating skills and expand their radio operating. I filtered the responses to our club members only to see if our club member responses are any different from the larger group. Basically, our members indicate they are somewhat more active than the rest of the respondents but the overall story does not change.

Obviously, this is a small slice of data relevant to our local situation. It may not apply to other parts of the country.

What do you think?

73, Bob K0NR

ZF2NR: Another Slacker DXpedition

Operating from countries outside the US can be a lot of fun. I just completed another another Slacker DXpedition, this time to the Cayman Islands. The formula for this type of operation is simple: identify an interesting vacation spot that is also considered DX, travel there with friends & family, take along some compact radio gear and get on the air. A key point is to not overdo the radio operating or the friends & family will veto any radio activity on future trips.

Licensing for the Cayman Islands is relatively easy if you hold a US FCC amateur radio license. Complete info can be found on the OFREG web site. Licensing for the Caymans is typical of many Caribbean countries: fill out the application form, send it to OFREG by email along with a copy of your US license, passport and $25US. Visitor call signs have the prefix ZF2 and you can request your favorite two-letter suffix. That’s how I got ZF2NR.

I was issued a Class A license which has all operating privileges. My spouse Joyce/K0JJW holds a US General Class license and was issued a Cayman Class B license, which has limited HF privileges (no phone on 40m, 20m, or 17m). So keep that in mind if you have a General Class license. [Update: ZF1EJ told me that this was an error, she should have been issued a Class A license.]

Grand Cayman is in grid EK-99 and is IOTA NA-016.

My equipment strategy was the same as my V29RW operation on Antigua (see V29RW: Slacker DXpedition to Antigua).  The basic kit is a Yaesu FT-991 driving a  end-fed halfwave (EFHW) wire antenna for the band of interest. Never underestimate the power of getting a halfwave antenna up into the air. The FT-991 fits in my carry-on bag and it covers all bands from HF through 70cm.

There is a 2m repeater (146.76 MHz) on Grand Cayman that works quite well. We received a friendly welcome on the repeater from Phil ZF1PB and several other Cayman hams.

Vacation Home

Our group rented a nice vacation home near Rum Point on the north side of Grand Cayman. This place is right on the water with an excellent sand beach. Denny KB9PDF/ZF2PF and I put up the EFHW 20m antenna supported by my SOTAbeams pole strapped to a palm tree. This setup worked quite well and we soon had a nice pileup of stations calling us on 20m. We did have some issues with local noise sources, the worst of which was traced to some dimmer switches in the house. This is one of the problems with a portable setup like this…you never know what RFI problems you’ll encounter. Later in the week, we put up a 40m EFHW and made a few contacts on that band, too.

Denny KB9DPF/ZF2PF watches as Bob K0NR/ZF2NR operates 20m ssb at the vacation home.
The view from the vacation home. Look closely and you can see the SOTAbeams pole attached to a palm tree supporting the 20m EFHW antenna.

ZF1A

Bruce/K0BJ suggested that I check into using the Cayman Amateur Radio Society club station (ZF1A) which they make available to visiting hams. I connected with Eden/ZF1EJ who confirmed that the station was available later in the week. Again, I did not want to overdo the radio thing, so we settled on operating at ZF1A during the middle of the day on Wednesday.

The HF log periodic antenna at ZF1A.

This turned out to be a great move. ZF1A has multiple towers with some very capable antennas. Like I always say: Never underestimate the power of using a large directional antenna on top of a big tower.  Eden/ZF1EJ met us at the station (it is literally in his backyard) and helped us get situated. Our operating strategy was simple: use the highest HF phone band that had good propagation and work as many stations as possible. We were also prepared to use FT8 if things were really bad but that was not needed. It turned out that 15m was dead but 17m was open into North America and Europe, so we did most of our operating there.

Bob/K0NR operating as ZF2NR at the ZF1A club station

Here’s a short video to give you a taste of the pileup.

I did work some of the folks back home, which was a treat: K0AV, W0CP, K0BJ, W0RLY, W0GAS, WG0AT, KD0RQU. I had noticed that Steve/WG0AT was doing a Summits On The Air (SOTA) activation on Crooked Top Mountain (W0C/SP-090) and I gave him a call. Being QRP, his signal was very weak at my location but he could hear me with no problem.

Here’s the QSO audio that Steve recorded on his end:

Satellites

We worked two OSCAR satellite passes (AO-91, AO-92) using a pair of handheld radios and an Arrow 2m/70cm yagi antenna. The pair of handhelds gave us full-duplex capability: I ran the 70cm uplink on my HT while Denny ran the downlink on 2m. No surprise to find the FM satellites quite busy and a bit frustrating to work. I logged these stations from ZF2NR: KI0G, K3SV, TI2CDA, TI4DJ, HP2VX.

Results

My ZF2NR log shows 376 HF QSOs, most of them made by me. Joyce K0JJW/ZF2JW braved the pileup to make a few contacts. Denny/KB9DPF had some additional contacts as ZF2PF.  QSL to our home callsigns.

I’ve loaded the ZF2NR log into Logbook of The World.

Band Mode QSOs
   7 LSB    5 
  14 USB   65
  18 USB  306
 Total    376

In retrospect, I realized that we had the antenna pointed north most of the time and we probably should have looked in other directions. In particular, we only worked a few South American stations.

Most important is that a good time was had by all. Thanks to everyone that worked us while we were in the Cayman Islands.

73, Bob K0NR/ZF2NR

WØC Summits On The Air Dinner

It is time for another W0C (Colorado) Summits On The Air dinner!

2017 W0C SOTA Dinner: (left to right) Wayne AD0KE, Brad WA6MM, Caleb W4XEN, Carey KX0R, John N0TA, Curtis KC5CW, Mark N0MTN, Joyce K0JJW, Steve K7PX, Al KH7AL, James KI0KN, Walt W0CP
2017 W0C SOTA Dinner (left to right): Joyce K0JJW, Steve K7PX, Al KH7AL, James KI0KN, Walt W0CP, John N1OIE, Steve WG0AT, Wayne AD0KE, Brad WA6MM, Caleb W4XEN and Carey KX0R.

Last year, we had 15 people get together for an informal dinner in south Denver (Lone Tree): Steve WG0AT, Wayne AD0KE, Brad WA6MM, Caleb W4XEN, Carey KX0R, John N0TA, Curtis KC5CW, Mark N0MTN, Bob K0NR, Joyce K0JJW, Steve K7PX, Al  KH7AL, James KI0KN, Walt W0CP and John N1OIE. It was so much fun meeting people and swapping SOTA stories that we are going to do it again this year.

Wednesday March 21th  at 6 pm
Chili’s, 10460 Park Meadows Dr, Lone Tree, CO 80124-5413

Dinner details:
   No agenda, no organization, just have fun, pay for your meal
Please wear something with your name/callsign (name tag, shirt, cap, etc.) to aid in making connections

Please send this to anyone you know that might be interested.
RSVP back to Bob K0NR: bob@k0nr.com so we have an accurate count for the reservation.

I hope to see you all there!

73, Bob K0NR

Rescue on Uncompahgre Peak (1992)

I came across this story in my archives, written by me way back in August 1992. This was before mobile phones were commonly available, so ham radio turned out to be critical in this incident. Even today, there are many places in the Colorado backcountry where mobile phones don’t work but amateur radio can communicate. My callsign at the time was KBØCY

Something happened on the way to Uncompahgre Peak on August 8, 1992.

Around noon, my brother, my two nephews and I made it to the summit and had just signed the log. I called on 146.52 and contacted Chris, NQ5V, who was somewhere to the east of me (Creede, I think). This must be his summer location, since his callbook address is Texas. We talked about the trail up Uncompahgre, since he was interested in hiking it.

After I signed clear with NQ5V and was about to start down the mountain, a teenage boy came up to me and said he had been sent to “find the guy with the radio” because a girl had been hit by a rock down below and was hurt. I am not sure how they knew I had a radio, other than I used it once on the way up the trail. The story seemed rather sketchy and I was skeptical but asked NQ5V to standby on frequency because we may have a medical emergency. At that time, Arnold, W7JRC, from Cedaredge, CO, came on frequency and said he had a phone nearby. (NQ5V did not have a phone available.) A second, older teenager came up the the trail with more information. He said he was a pre-med student and had search and rescue experience. He had more detailed info which made the story more clear. At this time, I concluded that we had a real emergency and asked W7JRC to call the authorities. I handed my HT to the older teenager and had him describe the victim’s condition to W7JRC. W7JRC had some trouble contacting the police, but eventually got through to the Ouray County Sheriff’s Office. (It turned out we were in Hinsdale County, but we did not know that at the time.)

Jim, NR5Y (also close to Creede, I think) came on frequency and said that he was close to a telephone. I was not always able to communicate with NR5Y, so NQ5V relayed to NR5Y. Since W7JRC was having trouble with getting the telephone call through, I asked NR5Y to also try to place a call. He called the Mineral County Sheriff, who relayed to Hinsdale County. All this time, I was moving down the mountain to try to get closer to the victim without losing my radio contact. About this time, my HT battery went dead, so I switched to my spare (Good thing I had one!) As I moved onto the saddle below Uncompaghre, I lost contact with W7JRC and contact with NQ5V got much worse, but usable. About this time, Doug, NØLAY, came on the air and his signal was very strong at my location which allowed me to stay on low power and conserve my HT batteries. N0LAY apparently came on the air in response to a call from the Hinsdale County Sheriff. N0LAY also had a radio which was on the sheriff’s frequency and relayed information from me to the sheriff’s dispatch.

I had not proceeded down any further because I was certain that I would lose radio contact with NØLAY. The victim had several people with her that had First Aid training and was about 1000 feet below me at the bottom of a cirque. I sent the older teenager back down to the victim with instructions to signal me as to her condition. We both had signal whistles – two whistles meant her condition was the same (stable), three whistles meant her condition had deteriorated. After I got the two whistles back, I felt like things were going to be OK.

About that time, NØLAY relayed that an ambulance had been dispatched to the trailhead and a search and rescue person was on the way up the trail with a trail bike. Also, a helicopter had been dispatched from Montrose. It took us a little while to communicate to the sheriff where the victim was, but we had a pretty good topo map, so we eventually gave them an accurate fix on the location. As I was listening to NØLAY relay, I realized that my Kenwood TH-77A could receive most police frequencies. NØLAY provided me with the frequency and I programmed it into the HT, scanning between 146.52 and the sheriff’s frequency. This allowed us to listen in on what was going on. In fact, many times I was clearly hearing the various parties while they were having trouble communicating.

The S&R guy on the trail bike made it to the accident scene without us noticing him. He had parked his bike about half a mile away from us and had scrambled down to the victim. The first time I was aware of his position was when he transmitted from the accident site. He confirmed that the girl was pretty bashed up, but stable, and needed a helicopter ride out. About this time, the sheriff’s dispatch reported that the helicopter was about 5 minutes out (I think it turned out to be more like 15 minutes away). Soon the helicopter came up on the sheriff’s frequency and I could hear the S&R guy coordinating with the helicopter pilot The two-seater helicopter landed and they put the girl in the second seat. Apparently, she was stable enough to walk to the helicopter with some assistance. The alternative was to put her outside the chopper in a litter. The helicopter lifted off and set back down a few minutes later near the ambulance which was near the trailhead. The two-seater chopper was not a medical evacuation helicopter and the plan was that Flight-For-Life from Grand Junction would pick up the victim at the ambulance location. It turned out that Flight-For-Life was unavailable so they took the victim to a hospital by ambulance (to a local clinic, then Gunnison, I think).

We stayed on the ridge until the chopper headed for home, then we did the same. On the way down, the S&R guy on the trail bike caught up with us and we talked about the accident. He said the girl lost some teeth, had facial cuts, internal bleeding and swelling in the face, but was in stable condition. He said that without the radio report that they would be just getting the initial call at the time he was heading home. That is, we saved about 5 hours on the response time with amateur radio.

I have carried my HT on every 14er hike I have ever done and had considered the possibility of using of using it for emergency communications. I guess I never gave it too much thought because people venturing into the backcountry need to have a self-sufficient attitude. That means being prepared and preventing or handling any emergency situation on your own. But the unexpected happens, and here I was in the middle of a medical emergency. It certainly has caused me to take this emergency communications thing more seriously.

Things I learned that day:

  • Always carry an extra HT battery (or two)
  • Always carry a decent portable antenna (more than a rubber duck)
  • Always carry a good topo map, even if you don’t need it to follow the trail.
  • Make note of what county you are hiking in when in unfamiliar parts of the state. This aids in getting to the right Sheriff’s office. (This is important because the person you contact via radio is likely to be two or three counties away.)
  • My signal whistle (which has caused considerable abuse from a few hiking companions) is actually useful.
  • Extended coverage receive is very useful in emergencies. (I am still thinking about extended transmit — I clearly could have used it in this case.)

I was very pleased that everyone reacted quickly but in a professional manner. The radio amateurs all helped out when they could be stayed out of the way when appropriate. I am sure we can find some things that could have been done better, but I felt like things went well overall.

– Bob KØNR

Flair For Your Radio Bag

Yet another bag for carrying radio gear

The world is divided into two groups: Bag Guys and Not Bag Guys. (I am using “guy” as gender neutral.) I am a Bag Guy. I am always looking for just the right backpack, computer bag, luggage or duffel bag. For example, I’ve got this special bag, a backpack, that I use for hauling my portable VHF/UHF radio gear. You might call it a Go Bag but it really only has radio gear in it.

My gear for Summits On The Air (SOTA) has expanded a bit, so obviously it was time for a new bag. I decided to buy this backpack because it has solid construction and plenty of pockets. I don’t plan to actually use this as a backpack, it will be more of a “toss the gear into the back of the Jeep” bag…but having backpack straps on it will come in handy. This bag will carry a variety of radios, cables, chargers, batteries and stuff that I keep with the radios but won’t take on the trail.

 

USA and Colorado state flags

I chose the “Coyote” color for two reasons: 1) my kids keep making fun of me for always buying black bags and 2) it doesn’t show the dirt as much.  This bag came with a US flag attached to it, which was a nice bonus. I kind of like patches but I don’t actually attach them to my gear or clothing very often. My interest in any particular patch changes with time and location. And I don’t want to put on so many of them that I look like a Boy Scout with a sash full of merit badges.

Well, the military has solved this problem through the use of hook-and-loop attachments (“Velcro”) on tactical gear. Feel like a little flair? Slap on a patch. Get tired of it, just take it off. Brilliant. For a little background on proper flair, see this video clip from the movie Office Space.

Label your bag

I thought the US Flag was pretty cool, so I found a Colorado flag to add to the collection. Then I got to thinking about using patches to label the bag. I noticed the many vendors that make custom text patches (often referred to as “Name Tapes”). These work great for labeling bags, pouches, etc. I ordered mine from a third-party on Amazon: 3 Inches/Hook Fastener/ Personalized Custom Name Tape

Of course, another option is to put my name on the patch. By name, I really mean name and call sign. If there are a pile of radio bags, everyone will know which one is mine. This is where it can get tricky because my call sign has a zero in it and not all vendors know how to handle the slash-zero thing. I decided to give it a try by just inserted a slash-zero character into the entry field on the web page. As you can see in the photo, it worked out just fine.

 

Do a little websearching and you’ll find plenty of military/tactical gear that has hook-and-loop fasteners built into the design. But, you may already have your favorite backpack that doesn’t have this feature. No problem, go ahead and attach a strip or two of the fuzzy (loop) material to it and you can slap your favorite patch on it.

I can already see how this may will get out of hand. There are so many packs, pouches, bags, hats, jackets that could use some proper labeling, or maybe just a little flair.

73, Bob K0NR