Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/apursley2012/travlr-getaways/llms.txt

Use this file to discover all available pages before exploring further.

A kayak may look simple, but a safe outing still depends on equipment, weather, route selection, and an honest assessment of everyone’s experience. Taking a few extra minutes before launch — checking gear, briefing the group, and leaving a float plan — is the most effective preparation a paddler can do.

Before You Paddle

Work through these steps each time you go out, regardless of how familiar the route may seem.
1

Choose a route that fits your group

Choose protected water and a manageable distance when someone is new to paddling. Ocean, river, and large-lake conditions can change quickly. Unfamiliar routes are better explored with a qualified local guide who knows the tides, currents, and local hazards.
2

Wear and fit your life jacket

Wear a properly fitted, U.S. Coast Guard-approved life jacket that is appropriate for the activity. A life jacket only works if it is on and adjusted correctly before you are in the water.
3

Inspect all equipment before launching

Check the kayak, seat, paddle, foot supports, drain plug, and any attached gear before entering the water. A missing drain plug or loose foot support discovered mid-trip is far harder to address than one found at the launch site.
4

Secure supplies in waterproof storage

Stow drinking water, sun protection, a whistle, and a reliable communication device in waterproof storage attached to the kayak. Loose items can be lost if the kayak capsizes.
5

Dress for water temperature, not just air temperature

Dress for the water temperature as well as the air temperature. An unexpected capsize changes what the body is exposed to immediately. Cold water can cause incapacitation quickly even on a warm day.
6

Check the weather forecast

The U.S. Coast Guard recommends checking weather before departure, knowing the route and how to return, and confirming that all safety equipment is functional. Do not rely on yesterday’s forecast — check current conditions on the morning you plan to paddle.
7

Leave a float plan with a responsible person

Before launching, give a float plan to someone staying ashore who can act if the group does not return.
What a complete float plan should include:
  • Who is going (names and contact information)
  • Launch point and planned route
  • Expected return time
  • Equipment on board (kayak description, life jackets, communication devices)
  • What to do — and who to call — if the group does not return by the agreed time
Leave this information with a trusted person who will actually follow through if the deadline passes. A float plan is only useful if someone will act on it.

On the Water

Preparation continues once you are underway. Conditions on the water can shift faster than they appear to from the shore.

Stay in Communication Range

Stay close enough to the group to communicate by voice or signal at all times. If someone falls behind or the group splits, wait and regroup before continuing.

Monitor Sky and Water

Watch for building clouds, whitecaps, changes in wave direction, or unusual currents. Changes in the sky are often visible well before the weather reaches your location.

Turn Around Before You Are Tired

Fatigue affects paddling control, judgment, and the ability to self-rescue. Plan the turnaround point for before — not after — the group starts to tire.

Shorten the Trip If Conditions Change

If the route, weather, or group’s energy changes unexpectedly, shorten the trip. The original destination is never worth compromising the return.
Wind that helps on the way out can make the return much harder. A tailwind that pushes the group comfortably outward becomes a headwind on the paddle back. Factor wind direction and expected changes into your route planning before you launch, and be prepared to cut the trip short if conditions build. As the U.S. Coast Guard guidance emphasizes: reaching the original destination is never more important than returning safely.

Build docs developers (and LLMs) love