Permits for a Desert Poker Run

A desert poker run can look like a casual ride with a few checkpoints, but organizing one involves more than choosing a route and inviting riders. In Arizona, the permits and permissions depend on which land the course crosses, how the event is run, and where vehicles stage. This article explains the main checks organizers should make before advertising a date or sending riders onto the route.

Start With the Land, Not the Poker Cards

A poker run’s route may cross several types of land, and each can have different access rules. A route that appears continuous on a map might pass from private property to federal or state-managed ground. Permission from one land manager does not grant access to the next.

Before you promote the event, map the proposed route and identify the land manager for every segment, checkpoint, staging area, and parking location. Check the access rules for the precise roads or trails you plan to use. A trail being open to the public for ordinary riding does not automatically mean that a group event, checkpoint, or commercial activity is allowed there.

Common land categories to check include:

• Private land: Get the owner’s permission for the route and any staging or checkpoint areas. Confirm whether the permission covers the full event, including setup and cleanup.
• Arizona State Trust Land: Check the state land rules and permit requirements for the activities and locations involved. An individual recreational permit should not be assumed to authorize an organized event.
• Bureau of Land Management land: Ask the relevant office whether your planned event needs a special recreation permit or another approval. The answer can depend on the activity, route, group, and event setup.
• National Forest System land: Contact the responsible Forest Service office about event authorization and route restrictions. A route may be subject to seasonal closures or other limits.
• Tribal land: Access and event permissions are determined by the relevant tribal authority. Do not treat nearby public roads or trails as permission to enter tribal land.

Organizers can use Arizona Permits for an Organized Ride as a starting point, but they still need to confirm requirements directly with the land managers for their specific route. For land categories and individual access, see Arizona State Trust Land Recreational Permits, BLM Permit Rules in Arizona, Forest Service Permits Arizona Riders Need, and Tribal Land and OHV Access in Arizona.

Do not rely on a route shared by another group without checking it yourself. It may have been approved for a different event, may no longer be open, or may use private access that the other organizer arranged separately. If a route crosses a boundary you cannot verify, leave that segment out until you have clear permission.

A simple route worksheet can keep the checks organized:

Route element	What to confirm	Who to contact
Riding segments	Land ownership, open status, vehicle restrictions, and event approval	Land manager or private owner
Checkpoints	Permission to stop, place signs, or staff a station	Manager or owner for that location
Start and finish	Event use, parking capacity, access hours, and setup rules	Site manager or owner
Public roads	Whether the route is legal for the machines and riders using it	Relevant road authority and motor vehicle guidance
Cleanup and recovery	Access for support vehicles and procedures for removing event materials	Land manager or owner

The route’s land status is only one part of the plan. If the event involves a staging area, vendor, guide, paid entry, or a large group, explain those details when you contact the land manager. Do not describe an event as an informal ride if you are setting up organized checkpoints or inviting the public.

Keep Land Authorization Separate From Rider Requirements

A land-use approval for the event does not replace the requirements that apply to each machine or rider. The reverse is also true: a rider having the required decal or registration does not grant the event organizer permission to use a route, stage at a site, or set up a checkpoint.

For visiting riders, check the rules that apply to their machines and the areas where they will ride. Arizona’s visitor requirements may differ according to registration, vehicle use, and where the machine will be operated. Arizona OHV Rules for Visiting Riders and Arizona’s Non-Resident OHV Decal cover visitor-specific questions. A street-legal plate or an OHV decal addresses vehicle requirements; neither should be treated as event authorization or a land-access permit.

This distinction matters for events with riders arriving from different states. Ask participants to check their own machine’s paperwork and equipment before traveling. As the organizer, provide clear information about the route and any requirements you have confirmed, but do not promise that one document covers every trail or land type.

Also make clear where the event begins and where riding is expected to occur. A machine transported on a trailer to a staging area may have different obligations from one ridden on public roads or off-road. A decal requirement can depend on how and where the machine is used; Arizona Decal Rules for a Machine Never Ridden Off-Road helps explain why the intended use matters. For staging, keep in mind that Why a Decal Alone Will Not Let You Stage addresses a frequent misunderstanding: vehicle paperwork and permission to occupy a location are separate questions.

For an event with participants under 18, communicate applicable youth and supervision rules in advance. Do not assume that a parent’s paperwork or event registration makes a young rider eligible to operate any machine on any route. Ask riders to verify their own situation and check the rules for the land involved.

A useful pre-event message should state:

• Which machines the route is designed for, including any width or access limits you have confirmed.
• Whether participants need to transport machines to the start rather than ride to it.
• What land-access approvals the organizer has obtained and which areas are excluded.
• Where riders should check their decal, registration, insurance, and equipment requirements.
• Whether the route includes public-road sections, and where riders must follow separate road rules.
• That participants must stay on the approved route and obey closures or directions from land managers.

Avoid telling participants that “the event is permitted” without explaining the scope. Approval might cover a specific date, route, group, or activity—not every nearby trail or any route a rider chooses after leaving a checkpoint.

Confirm the Event Details With Each Land Manager

When you contact a land manager, give enough detail for the office to assess the actual event. A vague request for permission to “hold a poker run in the desert” may not identify the route, scale, or activities that determine which approvals apply.

Prepare a concise event description that includes:

1. The proposed date and the time needed for setup, the event, and cleanup.
2. A map or route description identifying trail and road segments, checkpoints, start and finish areas, and any alternate route.
3. An estimate of the number of riders, machines, staff, and support vehicles.
4. Whether entry fees, prizes, vendors, advertising, or guided services are involved.
5. What signs, tables, tents, markers, or other materials you intend to place.
6. How you will manage parking, sanitation, trash, recovery, emergencies, and route closures.

Ask specific questions rather than requesting a general yes or no. For example: Does this activity require an event or special recreation permit? Does approval cover the checkpoints as well as the riding route? Are there limits on group size, parking, signs, or support vehicles? Is a separate approval needed for vendors or commercial activity? Are there seasonal restrictions or fire-related closures that could affect the date?

Write down the name of the office or staff member you spoke with, what they told you, and any follow-up they requested. If the route crosses multiple land jurisdictions, contact each one. Keep written approvals and route maps together, and make sure the event staff use the approved version. If a change is needed, such as moving a checkpoint or adding a trail, get confirmation before using it.

Start early enough to allow for questions, revisions, or a different route. Do not assume an application or email inquiry is itself an approval. If an office says a permit is required, follow its process and wait for authorization before treating the event as cleared. Requirements, application procedures, and timing can change, so confirm current instructions with the responsible agency rather than relying on an old event packet.

A land manager may also tell you that a proposed route or activity is not allowed, or that the event cannot be accommodated on the date requested. Treat that answer as a route-planning constraint, not an invitation to use a nearby alternative without checking. Revise the course, obtain the relevant permission, or choose another location.

Build a Practical Plan for Event Day

Even with approvals in hand, an organized run needs a plan that helps participants stay within the approved area. Share the route and event rules before the ride, then repeat the essentials at check-in. If the approved route changes because of a closure or unsafe conditions, tell riders clearly; do not let them improvise a substitute route through unknown land.

Design checkpoints to minimize impact. Get permission for each location, keep signs and materials within the approved area, and remove them after the event if required. Do not block a trail, road, gate, or access point. Keep staging and parking within the site’s allowed boundaries, and make sure staff know where support vehicles may travel.

Plan for problems that could disrupt the route:

• A closure or fire restriction: Check official notices before the event and again close to departure. Have a permitted backup plan, or be ready to postpone or cancel.
• A stalled or damaged machine: Decide how riders can report a breakdown and where recovery vehicles may go. Do not send support vehicles onto routes they are not allowed to use.
• A lost participant: Give riders a clear route map, checkpoint sequence, and contact procedure. Set a turnaround or return plan that does not depend on cell service everywhere.
• Trash or event materials: Assign staff to inspect the start, checkpoints, and finish and remove what the event brought in.
• A route mistake: Tell riders not to cut across closed, private, or unverified land to rejoin the course. The approved route is the route; a shortcut can create a separate access problem.

At check-in, keep the paperwork and instructions accessible to the event leads. Staff should know which route is approved, where the boundaries are, how to report an incident, and whom to contact if a land manager changes access conditions. Participants should know that joining the event does not authorize riding outside the course or ignoring signs, gates, or closures.

Finally, check staging separately from the route. A trailhead or roadside area may have its own parking and access rules, and permission to ride a trail does not necessarily permit a large group to gather there. Arizona Trailhead Parking and Staging is useful background for this part of planning. Verify the selected site’s capacity and conditions with its manager, and avoid sending attendees to a start location until you know it can accommodate the event.

A desert poker run is much easier to manage when approvals are treated as specific to the route, land, dates, and activities. Map the course, contact every land manager involved, separate event permits from rider requirements, and make the approved plan clear to staff and participants. If any part remains uncertain, change the route or hold off on advertising it as ready.

Disclaimer

This article is for general informational purposes only and does not constitute professional advice. Laws, prices and regulations vary by location and change over time. Consult a qualified professional for guidance on your specific situation.