Wave Impact Calculator
The formula
What the wave penalty tells you
A coaching-plateau model of wave cost: pace penalty rising with wave height, scaled by encounter angle, modulated by period’s effect on breathing.
Calculation: Pace penalty = k(H) × angle factor; k ≈ 2 + 5H s per 100 m. Enter your inputs and every substitution is shown below the result.
Reading the result
The angle column is the tactical lesson — swimmers who zig-zag at 45° pay far less than those who grind head-on.
Rules of thumb: 1 m chop ≈ +4–8 s/100 head-on; 2 m swell ≈ +12 s
Limitations and best practice
Wind-over-tide builds short steep waves that the linear model under-prices; double the penalty there.
This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.
Frequently asked questions
Do following seas help?
Do calmer lanes exist?
Source & methodology
Open-water coaching models (disclosed heuristic).
Wave Impact: what this tool answers
You are here because you need a specific number, and you want to see how it was produced before you rely on it. Searchers land on a Wave Impact page for three reasons — to plan, to compare options, and to check that somebody else’s arithmetic is honest. This tool serves all three, and everything after the calculator explains the model instead of hiding it.
The useful way to hold Wave Impact is as a ratio with a story attached: Pace penalty = k(H) × angle factor; k ≈ 2 + 5H s per 100 m says how the parts combine, and the 8.0 s/100 figure above is simply that sentence written in numbers. Everything that follows unpacks one clause of the sentence at a time.
The number itself is the easy part. What takes judgement is knowing which inputs are facts in your situation and which are guesses wearing a decimal point — a distinction this page makes explicit for every field above.
Every figure in the prose is generated by the engine rather than written beside it — the worked example resolves to pace penalty = 8.0 s/100 on the default inputs, and the sensitivity section ranks the inputs that move the result — Significant wave height first, at ≈7.5 % of the headline for a ten-percent error either way in that input. Work down the page and by the end you could re-derive the result in a spreadsheet from memory.
Inside the Wave Impact calculation: formula and every input
The engine implements a single stated model: Pace penalty = k(H) × angle factor; k ≈ 2 + 5H s per 100 m. There is no hidden coefficient and no login-gated precision — the formula printed is the formula executed, which is also what makes the result citable.
Flat-water pace /100 (s) (example value 91) is a plain measured quantity — the unit shown in the label is the unit the formula expects. Replace the example with the figure from your own records — the tool recomputes instantly and the printed steps follow your numbers.
Significant wave height (m) (example value 1) is a numeric input whose unit is fixed by the label; a wrong unit is a wrong answer wearing a plausible disguise. Small measurement errors grow here: a length that is squared or cubed in the model magnifies a one-percent slip into a three-percent answer.
Wave period (s) (example value 12) is a plain measured quantity — the unit shown in the label is the unit the formula expects. The example value is there to demonstrate the mechanics, not to describe your situation — overwrite it.
Encounter angle (example value Head-on (0°)) is a selector, not a measurement: the engine follows a different route for each option. If you are unsure what belongs in this field, look at the printed steps: the substitution shows exactly how the engine uses it.
What each “Encounter angle” choice actually does: Head-on (0°) → 8.0 s/100 · Quarter (45°) → 4.8 s/100 · Beam (90°) → 6.0 s/100 · Following (180°) → 2.8 s/100 That table is the honest answer to “does this option matter”, re-derived from the formula rather than hard-coded into page copy.
The default Wave Impact calculation, written out in full
The tool prints its own working; this is the same arithmetic on the example values, reproduced so you can follow it by hand. Starting figures: Flat-water pace /100 (s), Significant wave height (m), Wave period (s), Encounter angle. Run to the end, the pace penalty resolves to 8.0 s/100 — In 1.2 m head-on chop the penalty is 8 s per 100 m — pace 91 → 99 s; the period of 12 s sets how much of it is breathing rhythm versus body lift on the bands this tool uses.
- Base penalty = 2 + 5×1.2 = 8.0 s/100 head-on
- × angle 1.00 = 8.0 s
- Pace now 99 s/100, 8.8% off
Adjusted pace — 99.0. This is the number experienced users quote when the headline alone would mislead.
% slower — 8.8. This is the number experienced users quote when the headline alone would mislead.
Angle factor — 1.00. If your inputs change, this is usually the first companion figure to move.
Short-period note — long ground swell is nearly free. Compare it against the main result of 8.0 s/100 before drawing conclusions.
Re-running with your own figures is instant; re-running by hand once is the best way to know the tool is telling you the truth.
Scenario table: Wave Impact at ±10 % and ±20 % of the key input
The honest version of any estimate is a corridor, and this one is cheap to produce: Wave Impact was recomputed at 5 points along the dominant input, with every other field left untouched.
| Significant wave height setting | Pace penalty |
|---|---|
| 80 % of the example value | 6.8 s/100 |
| 90 % of the example value | 7.4 s/100 |
| example inputs | 8.0 s/100 |
| 110 % of the example value | 8.6 s/100 |
| 120 % of the example value | 9.2 s/100 |
That spread — 6.8 s/100 at the low end, 9.2 s/100 at the high — is what a careful read of Wave Impact looks like: a band you can state out loud, with the reason for each edge. Reproduce it in the form above by editing Significant wave height alone; the substitution steps will follow your figures exactly.
What actually moves your Wave Impact
Nobody should have to guess which input matters. The engine was re-run once per field below — ten percent up, ten percent down, everything else frozen — and the results ranked by how far they moved the pace penalty. For Wave Impact the ranking is measured rather than guessed, and it belongs to these defaults: shift the starting point and the order can shift with it.
- Nudge Significant wave height by ±10 % and Wave Impact lands between 7.4 s/100 and 8.6 s/100 (sensitivity ≈7.5 %)
Significant wave height is the dominant lever here: ten percent either way moves the result by about 7.5 %, from 7.4 s/100 to 8.6 s/100. That is where a careless figure does the most damage, so check it against a source. The rest of the inputs earn only a rounding-error of attention, and that asymmetry is the practical payoff of measuring rather than asserting.
Is your Wave Impact good — reading the result bands
Nobody acts on a bare figure — they act on a figure with a comparison attached. The default case lands in the “In 1.2 m head-on chop the penalty is 8 s per 100 m — pace 91 → 99 s; the period of 12 s sets how much of it is breathing rhythm versus body lift” band, and bands are deliberately wide because real situations overlap. How much of that band is luck? On Significant wave height alone ten percent either way covers 7.4 s/100 to 8.6 s/100. The practical reading rules: compare against your own history before comparing against other people; treat band boundaries as zones, not walls — one point on the wrong side of a threshold rarely changes a real outcome; and when a companion output contradicts the headline, believe the pair.
Set Wave Impact beside its neighbours and it usually plays a specific role: this figure establishes the size of something, and the neighbouring tools establish whether that size is acceptable. Skipping the first step makes the second one arbitrary.
Why Wave Impact results go wrong — and how to prevent it
Wind-over-tide builds short steep waves that the linear model under-prices; double the penalty there. This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.
Chasing precision in Significant wave height (m) while Flat-water pace /100 (s) is still a guess. The sensitivity ranking above shows exactly where the accuracy budget should go.
One mistake is specific to this engine: assuming every input matters equally. The computation above shows Significant wave height dominating — a careful figure there beats false precision everywhere else.
A final trap is presentation: reporting Wave Impact to more decimal places than the inputs support. The tool prints what the arithmetic gives; you should quote only what your least precise field justifies.
Six things to confirm before acting on Wave Impact
- Recompute once with the dominant input deliberately set low, and see whether the decision changes.
- Check that every field the formula needs actually arrived from a document, not from recollection.
- Check Significant wave height before anything else: it is the measured dominant input, ≈7.5 % of Wave Impact per ten percent.
- Note the date and the inputs beside the number so the figure can be audited later.
- Verify each input against its original source document, not memory.
- Repeat the ±10 % test on the inputs that matter and see whether the decision — not just the number — still holds.
How to use the Wave Impact tool properly
The tool does the arithmetic; the routine below is what makes the arithmetic trustworthy. Five steps, a minute total — and afterwards you will know not just what the number is, but which assumption produced it.
Step 1 — one document, one pass. Open the statement, label or record that holds flat-water pace /100 (s), significant wave height (m), wave period (s), encounter angle and transcribe straight into the form. Transcription from a single source removes the mismatch errors that appear when figures are assembled from three different places. Numbers are cheap to produce and expensive to retract; the extra minute is the cheapest insurance available.
Step 2 — baseline before exploration. Get one defensible Pace penalty on screen before you start nudging numbers. Without a baseline, every variation looks interesting and none of them means anything. Compare the calculation to the rough guess you arrived with, and ask why they differ.
Step 3 — play with the inputs on purpose. Ten percent up, ten percent down, one field at a time. Within a few minutes you will know this calculation better than most people who quote its results. When in doubt, prefer the boring input: the interesting one is usually the one you misread.
Step 4 — compute a corridor, not a point. Three runs — worst, likely, best — turn Wave Impact from a snapshot into a range. Plan against the pessimistic end and treat the optimistic end as the upside story. The fastest sanity test is to guess the answer first and see how far the calculation disagrees.
Step 5 — write the one-line memo. “Pace penalty = 8.0 s/100 on this date, from these inputs.” That line is the entire deliverable; everything else on this page is how you earned the right to write it. If the answer changes your behaviour, it deserves a second run with different assumptions.
The real-world conversations Wave Impact settles
Numbers earn their keep in conversations, and Wave Impact is no exception. In Fitness & Sports discussions around Swimming, this figure decides whether an option stays on the table: it converts an opinionated debate into an arithmetic one, and arithmetic is the only referee both sides accept. Repeating a calculation with the same numbers proves only that the arithmetic is reliable — which is worth knowing.
The companion outputs — Adjusted pace and % slower — exist for the second stage of that screen: the headline sizes the prize, while the companions describe the trade-off you are accepting to get it. Precision is a promise you make about your data; make sure your inputs can keep it.
There is a personal-administration use people overlook: periodic self-checking. Wave Impact quietly drifts as life changes — rates move, bodies change, costs compound — and re-running it a few times a year catches drift while correction is still cheap. Most surprises in numbers are surprises about inputs, not about formulas.
Quick answers: what searchers ask about Wave Impact
What affects Wave Impact the most?
Measured on this engine, Significant wave height is the dominant lever: moving it ±10 % shifts the pace penalty across 7.4 s/100 to 8.6 s/100 — about 7.5 % of the headline. The ranked list in the sensitivity section is computed live, not asserted from a template.
How much does the “Encounter angle” choice change the answer?
Across every option this tool offers, the pace penalty ranges from 2.8 s/100 (Following (180°)) to 8.0 s/100 (Head-on (0°)) with all other inputs held at their example values. The per-option table is printed in the inputs section — this is a decision that genuinely moves the number, not a cosmetic dropdown.
What is a typical Wave Impact?
There is no honest universal average for Wave Impact, but there is a reference point: the defaults on this page produce 8.0 s/100 (In 1.2 m head-on chop the penalty is 8 s per 100 m — pace 91 → 99 s; the period of 12 s sets how much of it is breathing rhythm versus body lift). Replace the inputs with your own and compare — that comparison is the useful meaning of “typical”.
How do I calculate Wave Impact by hand?
Pace penalty = k(H) × angle factor; k ≈ 2 + 5H s per 100 m is the entire method. Work the inputs in that order — Base penalty = 2 + 5×1.2 = 8.0 s/100 head-on — and you will reach 8.0 s/100 on the default figures, the same number this tool prints.
What happens to Wave Impact if significant wave height changes by 10 %?
On these inputs a ±10 % change in significant wave height takes Wave Impact to 8.6 s/100 against the 8.0 s/100 example — around 7.5 % of the headline. The same test on every other field is in the sensitivity section.
Is the Wave Impact result of 8.0 s/100 good or bad?
Good and bad are comparisons, so the honest test is three questions: where does your own Wave Impact sit against the 8.0 s/100 reference above, how far would a plausible input error move it (≈7.5 % per ten percent on Significant wave height), and what does the alternative option compute to?
How do I calculate Wave Impact manually?
Write down the inputs, then follow the printed steps in order — Pace penalty = k(H) × angle factor; k ≈ 2 + 5H s per 100 m. A spreadsheet replicates it with two or three cells. The manual route is worth doing once to build intuition; after that the calculator saves time and eliminates transcription slips.
Is Wave Impact accurate?
The arithmetic is exact: Pace penalty = k(H) × angle factor; k ≈ 2 + 5H s per 100 m is evaluated with full floating-point precision and every substitution is printed in the worked example. What limits accuracy is input quality and the model’s assumptions, so treat the 8.0 s/100 result as the correct answer to the question you typed — and check the assumptions section before acting on it.
Do following seas help?
Rarely net: they push you off-course and slap the face on the recovery; the model gives them the smallest penalty, not a bonus.
Do calmer lanes exist?
The lee of a breakwater or pontoon can cut the wave penalty substantially.
Can this tool see the numbers I type?
It cannot. There is no submission step: the calculation happens in your browser and the result disappears when you close the page. Treat the fields above as a scratchpad rather than a form.
What the labels on this page mean
- Adjusted pace
- 99.0 for the Wave Impact worked case; it sits next to the main result because it carries context the headline leaves out.
- % slower
- 8.8 in the default Wave Impact calculation — one of the secondary figures an experienced reader checks before trusting the primary number.
- Angle factor
- 1.00 in the default Wave Impact calculation — one of the secondary figures an experienced reader checks before trusting the primary number.
- Pace penalty
- The primary output of this tool: 8.0 s/100 for the default inputs, computed exactly from Pace penalty = k(H) × angle factor; k ≈ 2 + 5H s per 100 m.
- Worked example
- Every substitution in order, from the example inputs to 8.0 s/100 — the audit trail for the headline figure.
- Verdict band
- The interpretation attached to a result (“In 1.2 m head-on chop the penalty is 8 s per 100 m — pace 91 → 99 s; the period of 12 s sets how much of it is breathing rhythm versus body lift” on these inputs), which turns a bare number into a position on a scale.
- Sensitivity (±10 %)
- How far the Wave Impact moves when a single input is nudged ten percent either way; the ranked list on this page is computed live from this engine.
Where the Wave Impact model comes from
Everything above runs on one stated formula, applied without hidden coefficients: Pace penalty = k(H) × angle factor; k ≈ 2 + 5H s per 100 m. Source of record: Open-water coaching models (disclosed heuristic). Specialist software layers extra coefficients on top of the same algebra; none are hidden here, and that transparency is what makes a disagreement traceable to a specific input instead of a black box.
This page is an estimation aid, not professional advice. The design rule is simple: two people entering identical figures must get identical answers. The design constraint was set by usefulness rather than by comfort: an estimate you can interrogate beats an answer you have to trust.
Next steps after the calculation
Re-run the calculation with your own figures, stress the two most sensitive inputs by ±10 %, and only then act on the result.
This page was written for people who need one trustworthy number before their next decision, and the promise is that nothing above required trust. Bookmark the tool, re-run it whenever an input moves by more than a few percent, and keep the date with the number.