Distance Is Not Difficulty

The crossing I think about most often when people ask me about route planning is one I never made. It appears on the chart of a coast I know well as a gap of just under two miles between a sheltered bay and a small cove with a beach that is pleasant in summer. On paper it is the obvious way to get from one place to the other. The alternative is five miles of paddling around a long headland, staying inside a series of small bays the whole way. I have watched groups look at the chart, measure the gap with a thumb and forefinger, and decide in about four seconds. The thumb says twenty minutes. The thumb is not lying about the distance. It is lying about everything else.

The two miles run past a shore of low cliffs and boulder fans for most of their length. There is no landing on that shore in the conditions for which anyone would want one. If the wind strengthens from the prevailing quarter while you are in the middle, it comes at you over open water with nothing to interrupt it, and it pushes you toward the cliffs you cannot land on. Turning back means turning your bow, or the group's bows, into that same wind and holding a line back toward the bay for roughly a mile, which is a different job entirely from drifting pleasantly across with the weather behind you. Five paddlers can make that crossing in twenty-five minutes in flat calm. In a force five from the wrong direction, some of them cannot make it back at all, and the ones who can will arrive at the cliffs rather than the bay if their ferry angle slips. I have stood on the headland above it in November and watched short wind waves break across the whole gap, white from side to side, and I have also crossed it in June on water like a pane of glass. Same two miles.

Different routes entirely.

This is the habit I want to break early, because it shapes everything else in this book: the belief that distance tells you how hard a trip will be. Distance tells you how far you will travel. It contributes to the demands of a trip, through time underway, fatigue, and how much food and water you carry. But it does not tell you what the trip demands of you, because difficulty in coastal water comes from a different set of ingredients: how long you are exposed to conditions you cannot easily escape, where you can land if something goes wrong or someone gets tired, what the tide and daylight allow and forbid, and what happens to your options if you are slower than you expected. A short crossing can carry more commitment than a long and nominally harder route, and the difference is not exotic. It is arithmetic and geography, available to anyone who looks.

Two words will carry a lot of weight in these pages, so I will define them now and then mostly use them plainly. Exposure is the time and conditions you spend in a place where shelter, landing, or retreat are limited. Commitment is the practical cost of changing your mind once you have entered a section: how hard it is to stop, turn around, or get to safety. The short crossing above scores low on distance and high on both. The five-mile detour scores high on distance and low on both, because every bay along it is a place you can stop, rest, regroup, and reconsider. When a route is described as committing, that is all the word means. It does not mean heroic. It means expensive to reverse.

Consider what each route leaves you holding if the day goes wrong. On the long route, if a paddler's shoulder starts complaining at mile three, you land in a bay, eat something, and either wait or walk the boats out at a road end a little further on. Nearly every fifteen minutes of that route contains a decision you could still make differently. On the short route, the moment you pass the last landing inside the bay, you have traded all of those decisions for one: arrive or deal with it. That trade can be reasonable. Paddlers make it deliberately all the time, in conditions they have assessed, with crews they trust. What is not reasonable is making it without noticing, which is what a thumb on a chart invites.

The forecast does not rescue you from this, and it is worth being precise about why. A marine forecast describes average conditions expected over an area and a period, usually as ranges: wind so many knots, seas of such a height. The ranges are honest, but they are averages over a large patch of ocean, and actual conditions at your particular patch, at your particular hour, can sit above the top of the range or below the bottom. The National Weather Service says this plainly in its own safe-boating guidance: plan for conditions outside the forecast range rather than treating the forecast as a guarantee. I have never met a forecaster who would disagree, and I have met plenty of paddlers who paddle as though they do. On a route with landings every mile, a forecast that turns out too optimistic costs you a shorter day. On the two-mile crossing, the same error costs you a mile of upwind struggle along a shore that will not let you stop. The forecast is the same. The route converts it differently.

I want to be careful here, because this argument has a clumsy version that I do not want to be accused of. The clumsy version says exposed routes are bad and sheltered routes are safe. That is false. A sheltered shoreline can hold shallow water that a loaded boat grounds on halfway through the tide, a surf beach that is a worse landing than the cliff you were avoiding, a tidal gate that only opens for an hour, or thick fog that removes the visibility the easy water seemed to promise. Shelter changes which problems you face; it does not cancel them. And the clumsy version in reverse, that the direct exposed crossing is always the mistake, is false too. There are days, crews, and crossings where the two-mile gap is exactly the right choice, made with eyes open, with a weather window confirmed from the water before the point of no return, and with a group that has already practised turning and holding position in the wind they might get. The problem is not the route. The problem is letting the mileage make the decision for you.

What does making the decision properly look like? It starts with reading the route as a chain of places where you choose, rather than a line between two points. On the short crossing, the chain is short: launch, the last usable beach inside the bay, the midpoint where turning back still costs less than continuing, and the cove. On the long route, the chain has a link every bay or so, and each link is a place where the plan can be revised without drama. A useful exercise, and one I will use throughout this book, is to walk a route on the chart and mark three things: every place you could land, every place you could decide to stop and reassess, and the last place where turning back is still cheaper than going on. If that third mark comes early and the exposure between it and the far side is long, you are looking at a committing route regardless of what the tape measure says. If the reassessment marks come every few hundred metres and the landings are real, you are looking at a forgiving one, regardless of how many miles it runs.

*Figure 1.1. The shorter line crosses open water with few usable decisions along the way. The longer route keeps offering places to land, stop, and reconsider.* I say real landings deliberately. A mark on a chart that says "beach" is a statement about what the shoreline is made of, not a promise about what it will be like under your keel on your day. The beach at the far side of my two-mile crossing, the one that makes the whole thing look easy, is steep and reflects wind waves in onshore conditions, and in a summer with unusual longshore drift a few years back it mostly vanished between June and September, which is a separate story I will tell later. Access rules vary shoreline by shoreline, and jurisdiction by jurisdiction, and none of that is printed on the chart next to the sand symbol. If the whole plan rests on one landing, it deserves more than a symbol. Local knowledge, current charts and notices, and where relevant a pilot volume for the region are how you check. And if you cannot verify a landing, plan as though it is not there, and see what the route looks like then. Sometimes it looks fine. Sometimes the plan collapses, which is a good thing to learn at a kitchen table rather than a mile offshore.

The same honesty applies to your own crew, especially if the crew is mixed, which most real crews are. A crossing that a strong paddler does in twenty minutes may take a nervous intermediate forty, and the two crossings are not the same crossing. The wind that the strong paddler finds bracing, the intermediate finds consuming, because every ounce of attention goes into holding course and there is nothing left for the reassessment the plan requires. I plan around the least practised essential skill in the group, not the average. If the person who cannot yet turn a kayak reliably into wind without losing fifty metres is coming along, then a route whose safety depends on everyone turning promptly into wind is not available to that group on that day, whatever its mileage. This is not a judgement about anyone. It is a constraint, the same way tide is a constraint, and pretending otherwise does not remove it. It just moves the moment you discover it.

The gap between that bay and that cove has not gotten any shorter while you read this, and I have not crossed it this year. I have paddled the long way more than once and felt briefly foolish doing so, watching some faster party skim the gap in conditions that held. But foolish is a feeling measured in minutes, and the long route keeps its receipts in bays. The question to carry forward is not which route is safer in the abstract. It is which route leaves you holding usable decisions at every point where the day might disagree with you.

The route you choose is also a question you are asking the people who will paddle it, and most trip plans never get around to phrasing the question. I have read a fair number of trip plans in committee folders, and they tend to describe water rather than crew: distances, tide windows, hazards, the launch and the landing. What they leave out is the sentence that matters, which is some version of "this route requires that everyone on board can do the following things, for this long, under these conditions, and can keep doing them after something has already gone wrong." The omission is understandable. Describing water is pleasant work. Describing what your friends can and cannot do is awkward, and describing what you can and cannot do is worse. But a route is a demand on a crew, not a stretch of coastline, and the same stretch will ask entirely different things of different boats. A four-mile exposed leg that a practiced sea kayaker covers in ninety minutes of steady work might be beyond a loaded canoe altogether, or fine for a small motorboat and lethal for a SUP. There is no difficulty label that survives contact with this fact. The honest way through is to translate the route into specific questions about handling, navigation, endurance, and recovery, then answer them for the actual people and craft going.

Start with boat handling, because it is the question most often skipped by people who have one. The question is not "can they paddle." It is: can they hold a course in the wind you have planned for, not the wind you hope for? Can they turn their boat into weather when tired, in chop, without a demonstration first? Can they control their speed coming into a landing that has some surge on it, and stop without a rescue? For a group, add the harder version: can they do these things at the back of the group, with nobody watching, when the person in front has stopped giving them a bearing to chase?

I once helped review a club trip that went wrong in an ordinary way, which is to say nobody drowned but several people decided they were done with the club. The plan was a headland rounding in a forecast of ten to fifteen knots. The forecast held. What the plan had not accounted for was that two of the six paddlers had never held a ferry angle in more than twelve knots, and the tide on the far side of the headland turned against the wind an hour earlier than the leader had estimated, steepening the chop in exactly the section with no landing for a mile and a half. The group got around. One of the two novices swam twice, was rescued competently, and spent the last hour paddling a damaged boat and a damaged ego into the takeout. The leader's report called it a successful trip with minor incidents. I would call it a trip whose written demands had never been compared against its actual crew.

Navigation is the second question, and it is more than knowing which way the point lies. On a longer coastal trip, navigation means holding a line across open water where there are no features, recognizing a landing from seaward before you are committed to it, and knowing where you are on the chart when the fog arrives and the GPS has gone into its bag to stay dry. Ask specifically: has everyone, or at least the minimum number needed to run the boat, done a crossing in restricted visibility? Do they know what a compass course is for, or have they only followed the boat in front? In a small boat with one navigator, the question becomes what happens if that person is the one who gets seasick, or is busy managing a tow, and no one else can say with confidence where the next safe landing is. I have seen that gap. It is more common than you would think, in groups where one careful person has done all the chart work for years and never been asked to hand it over.

Endurance deserves better numbers than it usually gets. Paddling distance at a touring pace is easy arithmetic, but the arithmetic that matters includes the conditions tax: a headwind of fifteen knots can cut a group's speed by a third or more, and it removes far more than that from the weakest paddler, because the weak paddler is working hardest just to stay with the group and has the least reserve left for the last hour. When you estimate time underway, estimate it for the slowest boat under the worst conditions you are willing to accept, then add a margin for the delay you have not thought of. If the resulting day is longer than the weakest person has done before, that is not a reason to cancel. It is a reason to shorten the route or identify where the day can be cut, before launching.

Recovery from delay is the question that separates routes most cleanly, and it is the one I want carried forward through the rest of this book. Every plan will be delayed by something: wind that arrives early, a swim, a mechanical problem, a group member who is simply slower than anyone predicted in March. The route's real character shows in what the delay costs. On a shoreline with a landing every half mile, an hour lost is an hour. On a committing section, an hour lost can convert a comfortable daylight crossing into an arrival after dark, against a tide that has turned, with nowhere to stop. Ask of each leg: if we are an hour late at this point, what are our options, and are they options we can execute in the conditions that made us late? A delayed group is by definition a tired group, sometimes a cold one, and the fallback that looked simple on the chart, a steep shingle beach with a shore break, may be beyond them by the time they need it.

In a mixed group, the constraint is the least practiced essential skill, and I mean essential, not impressive. Rolling is not essential if the group wears proper flotation and can rescue; holding a course in wind is. Communicating that you are struggling before you are in trouble is essential, and it is the skill leaders should worry about most, because the paddler who conceals fatigue is commoner than the one who admits it. When I plan for a mixed group, I write down the essential skills the route requires, then find the person on the trip for whom each skill is weakest, and I plan for that person's worst hour, not their best. If that sounds pessimistic, notice what it buys: a route sized so that everyone's bad hour is survivable rather than decisive. Optimistic arithmetic is cheap until the day disagrees with it.

Be specific about craft, too, because the same route description reads differently across boats. A sea kayak handles wind and rough water well and lands poorly on steep shores. A loaded canoe carries comfort and speed on flat water and becomes a liability in the same chop the kayaks shrug off. A small open boat with an engine changes the whole equation, and the temptation is to treat fuel and weather window as the only questions, when landing options in surf matter just as much. If your group is mixed craft, do not assume the route that suits the kayaks suits the canoe, or that the motorboat's presence constitutes a rescue plan, because a rescue that depends on someone else's engine starting is a plan with a single point of failure.

A practical way to do this work is to write four columns against the route, and to fill them in with names rather than generalities. First: what the route demands of boat control, in the conditions you will accept. Second: what it demands of navigation, including the visibility you would still launch in. Third: what it demands of endurance, calculated for the slowest boat in the worst acceptable wind. Fourth: what an hour's delay costs at each leg, and who pays it. Then sit with the answers for a day before you finalize anything, because the honest ones are uncomfortable and the impulse to revise them upward is strong.

I will add one caution from the administrative side of my old life. None of this capability assessment is worth much if the landings you are counting on are not actually available. Access rules, landing rights, permits, seasonal closures, and equipment requirements vary by jurisdiction and by shoreline, sometimes by individual estate, and a beach that is a legal takeout in July can be closed, private, or a protected bird colony in May. Check the current rules for the specific coast, in the season you are going, and write the confirmed landings into the plan rather than the ones you remember. Memory is not a source.

What you are left with, if you do this properly, is a route described as a series of demands with names attached to them: who has to hold what course, who has to find which landing, who has to last how long, and what happens to whom when the day slips. That description is far less flattering than a mileage figure, and far more useful. The distance between two points never once got anybody home. The next question is where, on the water, you will stop and check whether the answers you wrote on land are still true.

The most useful trip plan I ever saw written down was on the back of a tide table, in pencil, by a woman named Ruth who had been paddling the same stretch of coast for eleven years and had once, by her own account, spent an afternoon being talked out of a good decision by her own enthusiasm. Her plan for the day read, in full: launch by nine, at the island by one, off the water by four no matter what, lunch at either beach. She showed it to me at the put-in because I was the visiting instructor and she wanted me to know the terms before I offered opinions. I have thought about that pencil note more often than I have thought about any route card I have ever printed neatly on waterproof paper.

What made it a good plan was not the destinations. It was that it defined, in advance, what would count as a finished day, and the definition was off the water by four no matter what, with lunch at either beach. Ruth had already decided, on land, in dry clothes, with coffee, that the far island was an aim and not a requirement. If the wind filled in early, or the group moved slower than her optimistic arithmetic, the day could still end well, and everyone in it could still feel like they had been on a trip rather than survived an ordeal. The plan had a floor under it.

Most trip objectives don't have a floor; they have a summit. Read the average trip announcement, in a club newsletter or a group message, and you will find a destination, a distance, and a meeting time, and nothing about what happens if any part of the day disagrees. The destination does the work of a plan without being one. It tells people where they are going but not what they are committed to, and the difference between those two things is where most coastal trouble gets its start. A destination is a place, while a commitment is what it costs you to leave.

Reaching a destination and completing a sound trip are different achievements, and only one of them should be the objective. A sound trip is one that ends with everyone ashore, unhurt, at a reasonable hour, with the group's confidence and the boats intact, having made decisions that matched the conditions they actually met. That outcome is available on a full route, on a shortened route, on a late start, and on a day that was cancelled at the launch in favor of breakfast. It is not available to a group that has defined success as a headland, because a headland doesn't care what the wind does at noon.

The objection I hear most often, usually from paddlers who are fitter than I am and have more confidence than the average group deserves, is that this attitude turns every trip into a retreat before it starts. If you plan for the short version, you will get the short version. I have some sympathy for the argument, because goals do pull people, and a group that sets out expecting to be home early sometimes arrives home early out of sheer expectation. But the argument confuses the plan with the ambition. You can want the far island with your whole heart and still write down the conditions under which you will settle for the near one. Ruth wanted the island. Her pencil note was not a lack of ambition; it was ambition with a handbrake, set by the only person calm enough at nine in the morning to reach it.

There is also a social cost to leaving the objective undefined, and it is paid at the worst possible moment. Suppose the group is an hour behind schedule at the reassessment point, the wind is two categories firmer than the morning promised, and the question arises: do we continue? If no one has said in advance what the day is for, then the person who suggests turning back is proposing a failure, and the person who wants to push on is proposing adventure. That is not a fair debate. It is not even a debate about the right subject. The question on the water should be whether the conditions still match the plan's assumptions, and instead the group finds itself arguing about courage, which nobody can measure and everybody can perform. Decide on land what will count as a good day, and the on-water conversation becomes about facts: progress, wind, the state of the weakest paddler, the time remaining. Facts are arguable. Courage is only agreeable.

So here is the practice I would put in place, and it takes about ten minutes with a chart and a forecast. Write the objective as a sentence with four parts. First, the launch: where and by when, with the understanding that a late start is a shortened day, not a moral event. Second, the aim: the place you would like to reach, stated as an aim, so the word does the honest work. Third, the turnaround: a clock time, not a location, by which you reverse or change the objective whether or not you have arrived. Fourth, the acceptable alternatives: the nearer landing, the shorter loop, the sheltered side of the headland, the day called off. A real example, with invented places: launch at the slip by nine, aim for the outer cove, turn back by two o'clock regardless, and if we haven't passed the second point by noon we take the inner beach instead. Every part of that sentence can be adjusted to your coast, your crew, and your forecast, and every part of it should be. The times are placeholders; the structure is not.

Two details in that structure deserve explanation. The turnaround should be a time rather than a place because a place can be argued with. Half a mile more, the reasoning goes, and we're there. Half a mile in a building breeze, with a tired paddler, is not a small number, and the person proposing it is always comparing it to the distance already covered rather than to the distance still to come. A clock doesn't negotiate. Set the time so that the return or the alternative remains feasible with margin to spare, which means doing the arithmetic for the slowest boat in the group, in conditions worse than the forecast, and then believing the answer even when it is smaller than you hoped.

The alternatives deserve their own attention, because an alternative is not a vague intention to be flexible. Flexibility, in my experience of committees and of paddling groups, is usually the word people use for a decision they plan to make later under worse conditions. A real alternative is a named beach, checked for access and for season, that you can reach from the reassessment point if the plan starts to fray. A beach shown on a chart is not necessarily a legal landing, and a legal landing in July may be a closed bird colony in May. Whatever alternatives you write down, confirm them, and write the confirmed version into the plan. If your only acceptable alternative turns out to be unavailable, the objective changes, and it should change before you launch.

Now, the harder part, which no worksheet covers. A group has to agree, out loud, that the alternatives count as success. This is not a paperwork problem; it is a pride problem. I once helped lead a trip where we turned back at the reassessment point, correctly, in a wind that arrived four hours ahead of its forecast, and one of the paddlers spent the whole return leg in a silence that I could hear from two boat lengths away. At the takeout he said, not to me exactly, to the general area: well, that was a waste of a Saturday. He had a good roll, a good boat, and a definition of success that his own expectations had already settled without his noticing, and nothing in the trip announcement had corrected it, because the announcement had named a destination and nothing else. I should have said at the launch what the day was for. I said it on the next trip, and I felt slightly foolish doing it, standing in front of twelve adults explaining that a shorter route would still count. Nobody laughed. Two of them looked visibly relieved, and I have done it ever since.

That relief is worth noticing, because it tells you what the silence was made of. People conceal doubt when doubt looks like weakness, and they push when pushing looks like belonging. A group whose objective is a destination will contain members who are tired, cold, or frightened and who will none of them say so, because saying so would make them the reason the day failed. A group whose objective is a sound trip has removed the failure from the arithmetic. Turning back is not then a confession; it is the plan, executed at the appropriate time. The weakest paddler in that group stops being a constraint that must be dragged and becomes a person whose condition is legitimate information.

I am not arguing that every trip should be short, or that ambition is a fault. Some of my best days on the water were long, exposed, and only possible because a forecast held and a group held with it. The point is that those days were made possible by plans that would still have ended well if the forecast had broken, not by plans that required the weather to cooperate. A route that only works if everything goes right is not a plan. It is a wish with a chart reference.

Ruth's pencil note survived the day it was written for. The wind filled in at eleven, the group reached neither the island nor the first beach, and had lunch on a shingle bank I would not have chosen for a picnic, with the boats pulled up above the tide line and everyone complaining cheerfully about the sand in the sandwiches. Off the water by four. She rubbed the note out that evening, or said she did. The tide table, she told me later, still had the faint pencil shadow of that trip on it, and she had decided to leave it there, because it was the best day of the three she had run that month. The island, as far as I know, is still where it was. Decide before you launch what your day is allowed to be, and you may find, as she did, that the version you get is the one you would have written down if you'd known it was on offer.