John H. Chafee NWR access reconnaissance

John H. Chafee National Wildlife Refuge, US-0514, was supposed to be a quick new park before the rest of the evening took over. Instead it turned into an access reconnaissance trip and a reminder that not every POTA reference has an obvious parking-lot answer.

At a glance

• Where: John H. Chafee National Wildlife Refuge, US-0514, South Kingstown/Narragansett area
• When: June 13, 2026, roughly 8:15 to 9:15 p.m. local
• Activation: Failed attempt; 0 QSOs, no antenna deployed
• Radio: Not deployed
• Antenna: Not deployed
• Constraint: No obvious public parking-lot operating position inside the refuge boundary, plus a hard stop for a 10 p.m. grocery pickup

Field notes

The original plan was to activate a new Rhode Island POTA reference before stopping at Clemmie’s in East Greenwich. The timing did not really support that plan. Clemmie’s closed at 9 p.m., and if I had gone straight to the refuge first I would have reached the park around 8:15 p.m. It was about twenty minutes back to the ice cream place, so that would have left only a few minutes to find a spot, set up, make contacts, tear down, and still get there before closing.

So I reversed the order: ice cream first, then the refuge. That made sense for the evening, but it turned the activation into a scouting problem. I had expected John H. Chafee National Wildlife Refuge, US-0514 to work like many of the other parks I have activated: find the signed public parking area, confirm that it is inside the reference, and operate from there with a small no-drama setup.

That assumption was wrong. The refuge did not have one obvious public parking lot that also clearly sat inside the activatable boundary. There were places to park near refuge access points, and in daylight there were probably trails or walk-in options that could have supported a classic hike-in activation. At dusk, though, I was not comfortable treating an ambiguous shoulder, lot, or access point as good enough. Looking at the geocoding and boundary data on the phone, even the parking area that looked like “the refuge parking lot” did not appear to be within the refuge polygon I was checking.

I spent about an hour and a half driving around the area, comparing the map to what I could actually see from the road. By a little after 9 p.m. it was dark enough that the reasonable options were gone. I still had to pick up a grocery order before 10 p.m., so I called it and left without putting the radio on the air.

This was frustrating in the moment, but it was still useful. Some references are fine as opportunistic stops. This one needs to be treated as a planned walk-in activation: identify the legal public access point beforehand, leave enough time to sort out the boundary on foot, and expect to walk into the refuge rather than operate from the first convenient parking spot.

What worked

• Reversing the order kept the evening from turning into a missed stop at Clemmie’s.
• Checking the boundary before deploying prevented a questionable activation from turning into a questionable log.
• The trip turned an unknown reference into a concrete scouting note for the next attempt.

To adjust next time

• Do not treat John H. Chafee National Wildlife Refuge, US-0514 as a quick parking-lot activation.
• Scout the refuge access and boundary from a desktop map before driving there again.
• Plan this one as a walk-in activation, with enough time to walk away from the road and sort out the boundary on foot.
• If the only available spot is an ambiguous parking area outside the boundary, leave it unactivated and come back with a better plan.