Routing Software for Long Distance

In a multi-day offshore regatta, the outcome is not decided by sailing speed alone – what matters is which route gets the boat to the finish fastest under the given wind, current and sea state conditions. Routing software calculates exactly that: it combines weather forecast data, boat polar diagrams and nautical charts into optimised course suggestions. For navigators and tacticians on long-distance regattas from the Fastnet Race and Rolex Middle Sea Race to transatlantic events, it is no longer a luxury but standard equipment – provided you understand its limits and do not use it blindly.

What Routing Software Does

Routing software simulates the optimal path between start and finish while taking current and forecast conditions into account. At its core it works with three input sources:

1. Polar diagram (Polar) – Describes how fast a particular boat can sail at a given wind angle and wind strength. Each boat class has its own polar; for ORC or IRC racers, individual polars are stored from trial runs or rating data.
2. Weather data (GRIB) – Numerical forecast models deliver wind, pressure, waves and sometimes current at regular intervals. More on this in GRIB Files and Models.
3. Nautical chart and restrictions – Land masses, deep-water zones, traffic separation schemes, regatta area boundaries and optionally tidal currents are included in the calculation.

The result is not a single course but a routing line – a chain of waypoints that can shift with every new weather update. The navigator compares this line with the actual position and decides whether to intercept, hold or sail a tactical diversion.

Typical Software Solutions in Regatta Sailing

Several established programs are available on the market, differing in price, usability and integration. The following overview summarises common options for long-distance regattas:

Routing Software Categories Compared

The Routing Workflow on Long Distance

A structured process prevents valuable weather updates from going unused or wrong course decisions being made under time pressure.

Step 1: Preparation Before the Start

Before the lines are cast off, the software must be configured correctly:

• Verify polar – Does the stored polar match the actual boat and current sail configuration? With new sails or unusual ballast, the polar can deviate by several percent.
• Update nautical chart – Enter ENC charts, regatta area limits and exclusion zones. Details on Regatta Areas and Limits.
• Define GRIB sources – Which models (GFS, ECMWF, ICON) are used? Offshore requires longer forecast horizons than inshore racing.
• Plan redundancy – Second laptop, tablet or satellite communication for weather downloads underway.

Step 2: Routing During the Regatta

During an offshore regatta, the routing cycle runs continuously:

1. Load GRIB update – Typically every 6 to 12 hours, more often when fronts are approaching.
2. Calculate new routing line – Compare with previous route: where does the optimum diverge?
3. Tactical evaluation – Consider competitor positions, current and offshore weather windows.
4. Team decision – Skipper, navigator and tactician agree on the course to implement.
5. Transfer waypoints to plotter – Integration with GPS and Plotter.
6. Logbook entry – Document the rationale for the course choice for later analysis.

Understanding and Maintaining Polar Diagrams

The polar is the heart of every routing calculation. It indicates which boat speed is achievable at which wind angle and wind strength.

Structure of a Polar

A typical polar is organised as a table or diagram:

• Rows: Wind strengths (e.g. 8, 12, 16, 20 knots)
• Columns: Wind angle relative to the boat (0° = close-hauled, 90° = beam reach, 180° = running)
• Values: Boat speed in knots

Routing software interpolates between table values and calculates the expected passage time for each point on the route.

Maintaining and Calibrating the Polar

An outdated polar leads to systematic errors:

• After sail changes or hull repairs, review the polar
• During the regatta, compare actual SOG values (Speed Over Ground) with polar specifications
• If deviations exceed 5–8%, adjust the polar or store an alternative polar for heavy conditions

Integrating GRIB Data Correctly

Routing is only as good as the weather data. Long distance has special requirements:

Model Selection

More on interpretation and wind fields: Meteograms and Wind Fields.

Current and Tides

For many offshore routes, current is decisive. Modern routing tools can integrate ocean current GRIBs (e.g. RTOFS, Mercator). In coastal sections, tidal tables should additionally be checked manually – see Planning Ebb and Flood.

Tactical Decisions Beyond the Software

Routing software delivers the mathematically optimal result – regatta reality is more complex.

When to Deviate from Routing?

• Competitive situation – If all rivals go north, a southern split can be tactically worthwhile even with worse VMG.
• Weather uncertainty – With conflicting models, the conservative course is often better than the optimal routing line of a single model.
• Crew fitness – A course with frequent sail changes and night manoeuvres stresses a small crew more than a calmer, slightly longer route.
• Safety – Heavy weather, traffic or restricted visibility require course adjustments regardless of routing.

Routing and Night Navigation

At night, the ability to recognise visual weather signs decreases. Routing updates then become the primary decision tool – but only in combination with AIS and Collision Avoidance and the watch system. The navigator on the night watch should know the next two routing turning points and which weather update is expected next.

Night Routing Decision – Workflow

Checklist: Routing Software for Long Distance

Before the start and during the regatta, the following points should be completed:

• Polar for current boat configuration loaded and tested
• At least two GRIB sources configured (primary + comparison model)
• Nautical chart with regatta area, land and exclusion zones up to date
• Current data activated for critical passages
• Redundant hardware (laptop, power, satellite communication) checked
• Routing update rhythm defined (e.g. every 6 h for GRIB, every 12 h full routing)
• Decision rules agreed in the team: who may deviate from routing?
• Logbook template for course decisions prepared
• Plotter waypoints synchronised with routing software
• Fallback without software: paper chart and manual VMG estimation practised

Avoiding Common Mistakes

1. Outdated polar – Leads to unrealistic ETA and wrong tactical comparisons with competitors.
2. Only one weather model – Individual models can shift fronts by 12–24 hours; comparison is essential.
3. Routing without current – On Atlantic and Channel routes, currents can mean several hours gained or lost.
4. No documentation – Without a logbook, wrong decisions cannot be analysed after the regatta.
5. Software instead of sailing – Too much time at the laptop costs attention for trim, weather observation and night and offshore navigation overall.

Frequently Asked Questions

Do I need expensive pro software?

For club offshore, PredictWind or qtVlm is often enough; pro tools pay off with regular ORC/IRC racing.

How often to update GRIB?

At least every 12 hours, every 6 hours when fronts are approaching.

Can routing handle current?

Yes, with additional GRIB layers; check manually in tidal zones.

Routing vs. organiser weather routing?

Organiser routing is for orientation; your own routing takes your polar and tactics into account.

What if satellite download fails?

Download GRIBs for 48–72 h in advance; fallback to HF weather fax and visual observation.

Practical Example: Fastnet Race

In the Fastnet Race from Cowes via the Fastnet Rock to Plymouth, a typical routing scenario goes through the following phases:

1. Before start (Solent) – Include tidal current and local wind shifts from coastal and island effects in routing.
2. Celtic Sea – Transition to larger swell; activate polar for rough conditions.
3. Fastnet Rock – Narrowest part of the route; compare routing line and actual position every 15 minutes.
4. Irish Sea / St. George's Channel – Current and front decision: north or south of the route?
5. Plymouth finish – Align tidal window for entry with routing and tidal table.

Routing Updates Fastnet Race – Timeline

Conclusion

Routing software for long distance is a powerful tool that combines weather, boat performance and nautical chart into a shared tactical foundation. It replaces neither experience nor team communication – but those who maintain polars, compare GRIB models and critically evaluate routing results make better course decisions on offshore regattas and save valuable sea miles. Invest time in training before the regatta: a routing dry run with historical GRIB data from a past Fastnet or Middle Sea Race is worth more than any additional sail.

Related Topics

• Night and Offshore Navigation
• GRIB Files and Models
• GPS, Plotter and Classic Navigation
• AIS and Collision Avoidance
• Offshore and Long-Distance Regattas

Last updated: 4 July 2026