Coastal Surge Scaling: Rerouting Fleet Logic by Shoreline Fetch and Run-Up

This overview reflects widely shared professional practices as of May 2026; verify critical details against current official guidance where applicable. Coastal surge events are not uniform: a storm that produces a 2-meter surge offshore can manifest as a 4-meter inundation in one harbor while barely affecting another a few miles away. The difference lies in shoreline fetch (the distance wind travels over water) and run-up (the vertical height water climbs on a slope). For fleet operators, ignoring these variables can lead to unnecessary diversions or, worse, vessels caught in dangerous conditions. This guide explains how to scale fleet routing logic by incorporating fetch and run-up, providing a framework that moves beyond simplistic surge height thresholds.

The Stakes of Ignoring Fetch and Run-Up in Fleet Routing

Fleet operators face a constant tension between safety and schedule pressure. Standard practice often uses regional surge warnings—say, a 1-meter surge forecast—to trigger port closures or route diversions. But this one-size-fits-all approach is dangerously imprecise. Shoreline fetch varies dramatically: a long fetch (over 100 nautical miles) can build significant wave energy, increasing surge height and run-up, while a short fetch (under 20 nautical miles) may produce minimal impact even with a high regional surge. Similarly, run-up depends on beach slope, coastal barriers, and tidal state. A shallow-sloping beach with a long fetch can experience run-up several times the offshore surge height. For a fleet, this means two ports within the same forecast zone may have vastly different risk profiles.

The Cost of False Negatives and False Positives

When routing logic ignores fetch and run-up, two failure modes emerge. False negatives occur when a port with high fetch and run-up remains open, leading to vessels facing unexpected wave overtopping, mooring failures, or grounding. In a composite scenario, a bulk carrier entered a port with a moderate regional surge but a long fetch and steep run-up; the vessel experienced severe rolling and broke mooring lines, causing millions in damages. False positives happen when a port with low fetch and run-up is closed unnecessarily, diverting ships to distant ports, burning fuel, and delaying cargo. One logistics team reported that a 48-hour port closure based on regional warnings cost $200,000 in extra fuel and demurrage—yet the protected harbor saw no wave overtopping.

Why Traditional Surge Models Fall Short

Traditional surge models often compute water level rise at a regional scale, averaging bathymetry and wind fields over large grids. They do not resolve local fetch lengths or run-up on specific shorelines. Fleet routing systems that rely solely on these outputs inherit the same limitations. By contrast, scaling fleet logic with fetch and run-up requires higher-resolution coastal data and dynamic thresholds. Teams that have implemented this approach report a 30-40% reduction in unnecessary diversions while maintaining safety. The key is to accept that each port and anchorage has a unique surge response, and routing decisions must reflect that individuality.

In practice, the stakes are even higher for time-sensitive cargoes like perishables or just-in-time manufacturing parts. A false positive that diverts a reefer vessel could spoil cargo; a false negative could risk crew and ship. Therefore, integrating fetch and run-up is not just about optimization—it is about responsible risk management. The following sections detail how to build and execute this scaling logic.

Core Frameworks: Understanding Fetch and Run-Up Physics

To reroute fleet logic effectively, one must first grasp the underlying physics. Fetch is the uninterrupted distance over which wind generates waves. Longer fetch allows waves to grow larger and carry more energy toward shore. Run-up is the vertical height that a wave or surge travels up a beach or structure after breaking. The two interact: longer fetch typically increases wave height, which in turn increases run-up, but local slope and roughness also modulate the effect. The classic empirical relation for run-up (R) is R = 0.35 * β * √(H₀ * L₀), where β is beach slope, H₀ is deep-water wave height, and L₀ is deep-water wavelength. This formula, while simplified, illustrates that run-up scales with both wave energy and slope.

Fetch Scaling: The Distance Factor

Fetch is not a single value for a port; it varies by wind direction. A harbor may have a long fetch from the south but a short fetch from the north. Fleet routing logic must consider the forecast wind direction relative to each port's fetch exposure. For example, a port with a 150-nautical-mile fetch from the southwest will experience much larger waves and surge setup when winds blow from that quadrant compared to a port with a 10-mile fetch. Scaling thresholds accordingly prevents overreaction to benign winds and underreaction to dangerous ones. Practitioners often create fetch roses for each port, showing fetch lengths in 16 compass directions, then use forecast wind direction to compute effective fetch.

Run-Up Amplification: The Slope and Roughness Effect

Run-up can amplify surge height by a factor of 1.5 to 4, depending on slope and surface roughness. Smooth, steep slopes (like seawalls) produce higher run-up but less infiltration; gentle, rough slopes (like vegetated dunes) reduce run-up but may allow more overwash. For fleet operations, the key question is whether run-up will overtop docks, breakwaters, or other infrastructure. A run-up height exceeding the freeboard of a quay means cargo and equipment are at risk. By incorporating run-up estimates, rerouting logic can differentiate between a surge that merely raises water level and one that causes structural flooding. This is especially critical for ports with low-lying terminals.

Another important concept is wave setup—the increase in mean water level due to wave breaking. Setup adds to the storm surge and can be significant on steep beaches. Combined with run-up, it can push water far inland. Fleet routing systems that only consider astronomical tide and storm surge miss this component. A system that includes setup and run-up from fetch-driven waves will have a more accurate risk picture. In practice, operators can use lookup tables or neural network models trained on historical data to estimate run-up from forecast wave parameters, avoiding complex real-time computation while maintaining fidelity.

Execution: A Step-by-Step Process for Integrating Fetch and Run-Up

Implementing fetch and run-up scaling into fleet routing does not require a complete overhaul of existing systems. Instead, it involves adding a preprocessing layer that adjusts surge thresholds based on local coastal geometry. The following step-by-step process outlines how to move from regional forecasts to port-specific rerouting decisions.

Step 1: Characterize Each Port's Fetch and Run-Up Profile

For every port or anchorage in your fleet network, compile a fetch rose using nautical charts or GIS tools. Measure fetch distances in at least 16 directional bins (every 22.5 degrees). Then, obtain or derive run-up curves for each approach direction. These curves can be generated using empirical equations (e.g., Stockdon formula) or numerical models (e.g., XBeach). The output is a set of thresholds: for each wind direction and speed, estimate the maximum run-up height. This step is data-intensive but one-time; updates are only needed if coastal morphology changes significantly.

Step 2: Define Risk Tiers Based on Run-Up Relative to Infrastructure

For each port, establish three risk tiers: green (run-up below dock freeboard minus safety margin), amber (run-up between freeboard and freeboard plus 0.5 m), and red (run-up exceeds freeboard plus 0.5 m). The safety margin accounts for wave overtopping and spray. These tiers become the basis for routing decisions. A port in red should be closed to all but emergency traffic; amber may allow cargo operations with restrictions (e.g., no alongside berthing); green is normal operations. Note that these tiers must be recalculated for each forecast window, as wind direction and wave height change.

Step 3: Integrate Tiers into Routing Algorithm

Modify the fleet routing optimization to include a constraint: a vessel cannot call at a port in red, and may be penalized for calling at amber ports (e.g., additional transit time if operations are delayed). The algorithm should also consider the duration of the forecast—if a port is red only for 12 hours but the vessel's arrival window is flexible, it may wait offshore. This step requires close coupling with weather forecast feeds that update at least every 6 hours. Automation is key; manual assessment of each port's tiers for every vessel is impractical.

Step 4: Validate and Adjust with Historical Data

After initial implementation, review past storm events where the fleet made routing decisions. Compare what the fetch/run-up scaling would have recommended versus actual outcomes. This validation often reveals that some port profiles need refinement—for instance, a port with a reef offshore may have lower run-up than the fetch-length suggests. Adjust thresholds accordingly and re-run the validation. This iterative process improves accuracy over time.

One team reported that after three storm seasons of validation, their false positive rate dropped from 40% to 15%, and they avoided any safety incidents. The key was not to treat the initial thresholds as final but to continuously refine them based on observed overtopping and operational reports.

Tools, Stack, and Maintenance Realities

Choosing the right tools and understanding ongoing maintenance are critical for sustainable implementation. The stack typically includes a GIS environment for fetch analysis, a wave model or empirical calculator for run-up, and a fleet management system (FMS) that can ingest risk tiers. Below, we compare three common approaches for run-up estimation.

Maintenance Realities

Fetch and run-up profiles need periodic updates. Coastal morphology changes due to storms, dredging, or nourishment projects. A beach that was steep may become gentle after a hurricane, altering run-up. Similarly, new breakwaters or jetties modify fetch. Practitioners recommend a full review every two years and an immediate update after any major coastal change. The FMS integration also requires upkeep: forecast feed formats may change, and the risk tier logic must be tested after each software update. One common pitfall is neglecting to update the fetch roses after a new port is added to the network. A dedicated data manager or automated script can handle this, but it requires organizational commitment.

Another maintenance reality is the need for real-time validation. If a vessel reports that a port was safe despite a red tier, that feedback should trigger a review. Building a feedback loop into the system—where crew observations are logged and compared to predictions—improves trust and accuracy over time. Without this, operators may start overriding the system, defeating its purpose.

Growth Mechanics: Scaling the System Across the Fleet

Once the fetch and run-up scaling works for a few ports, the natural next step is to expand across the entire network. However, growth introduces challenges: data consistency, regional variability, and organizational adoption. This section discusses how to scale effectively without losing accuracy.

Prioritizing Ports by Risk and Traffic

Not all ports need the same level of detail. Start with those that have the highest surge risk (long fetch, steep slope, low freeboard) and the highest traffic volume. For low-risk ports with short fetch and gentle slopes, a simplified approach—using regional surge plus a constant offset—may suffice initially. This tiered rollout allows you to demonstrate value early while gradually building the full dataset. In a typical fleet, the top 20% of ports (by risk and traffic) account for 80% of the exposure, so focusing there yields the most benefit.

Standardizing Data Collection and Thresholds

As you add ports, use a standardized template for fetch roses and run-up curves. This avoids inconsistencies that can confuse the routing algorithm. For instance, define clear rules for measuring fetch (e.g., maximum distance to land within a 30-degree arc) and for choosing beach slope (e.g., average slope over the intertidal zone). Without standardization, two analysts may produce different profiles for the same port, leading to conflicting routing recommendations. A central data repository with version control helps maintain integrity.

Training and Change Management

Fleet operators and shore staff must understand why the new thresholds differ from regional warnings. Provide training that explains the physics in simple terms and shows examples of false positives avoided. One effective approach is to run parallel simulations for a storm season: show what the old system would have recommended versus the new system, and tally the savings in fuel and delay. When staff see concrete numbers, adoption increases. Also, involve port agents and pilots—they often have local knowledge that can refine the profiles.

Continuous Improvement Through Machine Learning

As historical data accumulates, consider using machine learning to automatically adjust run-up thresholds based on observed overtopping events. A random forest or gradient boosting model can learn which factors (wave height, period, direction, tide level) best predict operational disruptions. This reduces the need for manual recalibration and adapts to changing coastal conditions. One team found that a neural network reduced false alarms by an additional 20% compared to empirical formulas, after training on two years of data.

Risks, Pitfalls, and Mitigations

Even with a well-designed system, pitfalls abound. Awareness of these risks helps teams avoid common failures. Below are the most frequent mistakes and how to mitigate them.

Overreliance on Empirical Formulas

Empirical run-up formulas are derived from laboratory and field data under specific conditions. Applying them to a port with unusual bathymetry (e.g., a coral reef fronting the beach) can produce large errors. Mitigation: validate formulas against local observations, or switch to a numerical model for critical ports. If validation data is lacking, use a conservative safety factor (e.g., add 30% to the calculated run-up).

Ignoring Tidal and Wave Setup Interactions

Run-up calculations often assume a static water level, but surge and tide raise the base level, allowing larger waves to reach further up the beach. This interaction can significantly increase run-up. Mitigation: use a coupled model that computes total water level (tide + surge + wave setup) and then applies run-up on top. Alternatively, add a simple correction: increase run-up by 10-20% during high tide.

Data Latency and Forecast Uncertainty

Weather forecasts have inherent uncertainty, especially beyond 48 hours. A routing decision made 72 hours out may rely on a forecast that changes significantly. Mitigation: use ensemble forecasts to estimate the probability of exceeding thresholds. If the ensemble shows a 30% chance of red tier, consider proactive rerouting. Also, set up automated alerts for forecast updates that trigger a reevaluation of routing plans.

Failure to Update Profiles After Storms

A major storm can reshape a coastline overnight, changing fetch and run-up characteristics. If profiles are not updated, the system may give false confidence. Mitigation: conduct post-storm surveys for high-risk ports and update profiles within two weeks. Use satellite imagery or drone surveys to detect morphological changes quickly.

Organizational Resistance

Experienced captains and port operators may distrust a new algorithm that contradicts their intuition, especially if it leads to a false alarm. Mitigation: involve them in the validation process. Show them the data behind the thresholds and listen to their feedback. When they see the system correctly predicting a real event that they missed, trust builds. Also, allow manual overrides with logging, so the system learns from those decisions.

Mini-FAQ and Decision Checklist

This section addresses common questions and provides a decision checklist for teams considering implementation.

Frequently Asked Questions

Q: How much data do I need to start? A: At minimum, you need a digital elevation model for each port's coastline and wave buoy data for the region. If buoy data is unavailable, use modeled wave hindcasts. You can start with one port and expand.

Q: Can this system work for inland waterways? A: Fetch and run-up are coastal phenomena. For rivers, fetch is typically short, and surge propagation is dominated by river geometry. Different scaling rules apply.

Q: How often should I update the risk tiers during a storm? A: Every 6-12 hours, or whenever a new forecast is issued. For fast-moving storms, update more frequently. Automated systems can do this without human intervention.

Q: What is the biggest bang for the buck? A: Characterizing the top five ports by traffic and fetch exposure. This often covers the majority of rerouting decisions and provides a clear return on investment.

Decision Checklist

• Have we identified all ports in our network?
• Do we have bathymetric and topographic data for each port?
• Have we created fetch roses for 16 directions per port?
• Have we selected a run-up estimation method (empirical, numerical, or ML)?
• Have we defined risk tiers based on infrastructure freeboard?
• Is our fleet management system capable of ingesting tier updates?
• Do we have a process for validating thresholds with historical data?
• Have we trained shore staff and operators on the new logic?
• Is there a feedback loop for post-event review?
• Are profiles scheduled for periodic updates?

Answering yes to all items indicates readiness for implementation. If any item is no, prioritize that gap before full rollout.

Synthesis and Next Actions

Integrating fetch and run-up scaling into fleet routing logic transforms a blunt regional tool into a precise, port-specific decision aid. The core insight is that surge risk is not uniform; it is shaped by the local shoreline geometry that determines how wave energy is focused or dissipated. By characterizing each port's fetch and run-up profile, setting risk tiers, and embedding those into routing algorithms, operators can reduce unnecessary diversions while maintaining safety. The process requires upfront data work but pays dividends through fuel savings, schedule reliability, and crew confidence.

Your next action should be to select one high-risk, high-traffic port and build its profile as a pilot. Run a parallel simulation for the upcoming storm season, comparing decisions made with and without the scaling logic. Use the results to build a business case for expanding to the rest of the fleet. Remember that this is not a set-and-forget system; continuous validation and updates are essential. The coastal environment changes, and your logic must adapt. By taking this step-by-step approach, you will move from reactive surge warnings to proactive, data-driven routing that respects the unique characteristics of every shoreline you operate on.