Starlink for the CT sailing calendar.

Six events define the bulk of the Connecticut sailing program. Different boats prioritize different events, but the connectivity needs are similar across all of them: weather files, tactical data, navigation, occasional video calls home, and post-race uploads.

• Off Soundings (Memorial Day weekend, Labor Day weekend).The local fleet's bread and butter. Block Island and Watch Hill courses, mostly within cellular range but with patchy coverage on the further legs. Standard kit on Mobile Priority covers it cleanly; many boats run on Roam if they're staying inshore.
• Block Island Race Week (late June, biennial).The flagship event. Hosted out of Block Island; CT fleet sails over the night before. Five days of buoy and around-the-island racing. Cellular is workable in Old Harbor but unreliable on the courses. Starlink is the answer.
• Vineyard Race (Labor Day weekend).Stamford to Vineyard Sound and back, overnight, ~210 nm. Cellular drops fast east of Block Island. Standard with Mobile Priority is the right setup; weather routing during the night becomes critical and you don't want to be reliant on intermittent SiriusXM.
• Storm Trysail Club distance events.The longer offshore series — Block Island Race, Marion-Bermuda (alternate years), various delivery legs. For dedicated offshore programs, Maritime hardware on the priority data plan is worth the upgrade. For coastal-only programs, Standard is enough.
• Cedar Point and Stamford YC IRC fleet.Wednesday night and weekend buoy racing through the season. Connectivity is mostly nice-to-have here — you're never more than a few miles from shore — but post-race tactical data review is a real workflow.
• Mystic ORR programs.The eastern CT racing scene out of Noank and Mystic. Block Island, Newport, the Vineyard. Same kit profile as the Stamford programs.

For all of these, the install spec is roughly identical. Where they differ is in how hard you push the system and how much it costs you when it fails.

The right kit for nearly every CT racing program is the same: Starlink Standard with the Flat High Performance antenna, paired with a Mobile Priority data plan. The reasoning:

1. Standard handles the conditions.Sailing-yacht heel, occasional spray, vibration from the rig — Standard's antenna is rated for it. Mini is too lightweight for racing programs where you want robustness; Maritime is overkill unless you're genuinely running offshore distance events.
2. Mobile Priority is the right plan.The $250/month Mobile Priority tier is in-motion capable without deprioritization. Roam works on a moored boat; for a boat actively racing, Mobile Priority's better. Owners running 3-month seasonal programs sometimes pause and unpause the plan around the racing window to manage cost.
3. Aft-arch mount is cleanest.Cable run is short and protected, weight is low and aft (centerline-friendly for trim), rig shadow is symmetric on port and starboard tacks. Pushpit-pole works for boats without an arch. Masthead is rarely the right call on a racing program — weight aloft and serviceability arguments both point against it.
4. Onboard router is your call.Some racing programs run a Peplink with cellular failover; some just use the Starlink router. For Block Island Race Week and offshore programs, Peplink is worth it for the dual-WAN reliability. For Off Soundings inshore racing, the Starlink router alone covers it.

Starlink is universally permitted in CT-area handicap racing. IRC and ORR don't prohibit satellite communications, and Off Soundings, Storm Trysail, Block Island Race Week, and the Vineyard Race all explicitly allow it in their NORs and SIs. The hardware is just a piece of the boat for rules purposes.

The one place rule pedants will note something: weight aloft for IRC. The Flat High Performance antenna and short cable run on an aft arch are negligible — well under the threshold that materially affects the rating. Masthead-mounted Starlink would be more meaningful, which is one more reason aft-arch is the right answer on racing programs. Your rating officer can run the calculation if you're skeptical.

For Cat 1 and Cat 2 ocean racing (Marblehead-Halifax, Bermuda Race, transatlantic events), the World Sailing Offshore Special Regulations apply and have specific communications requirements (HF radio, EPIRB, etc.). Starlink doesn't replace those; it supplements them. Read the NOR carefully for any event with offshore certification.

Two weeks of shakedown before the race start. That's the rule. Specifically:

1. 4 weeks before race:Install scheduled and complete. Helm's racing-sailboat installs are 4–6 hours scoped properly; rushing inside this window produces compromises you'll live with for the season.
2. 2 weeks before race:First weekend underway with the system. Real-conditions test — not just dock testing. Verify connection holds at speed, on tacks, at heel. Identify any cable chafe, mesh dead zones, or power-draw issues. Most failures show up here.
3. 1 week before race:Second shakedown. Confirm the fixes from the first weekend held. Pre-download weather files, tactical data, and tide tables you'd need if Starlink dropped out for an hour. Verify cellular failover (if you have it) by simulating an outage.
4. Day before start:Final verification. Speed test from anchor or slip. Confirm Mobile Priority is active. Confirm onboard chartplotters and weather services see the connection. Don't troubleshoot at the start.

For Block Island Race Week (late June), this means installing in late May or early June at the latest. For Vineyard Race (Labor Day weekend), early-to-mid August. Helm books out racing-sailboat installs 4–8 weeks in advance during the spring rush; reach out early.

Three failure modes account for nearly all the racing-program issues we get called in to fix mid-season:

1. Cable chafe at the boom or vang.The cable run was clean on the dock, then the boom swept through it once on an aggressive gybe and the jacket is now compromised. Always route cable inside the cabin or through dedicated chases — never across the deck where running rigging or sheets can find it. We design every racing-sailboat install around this constraint.
2. Connector water intrusion.Racing boats see materially more spray and green water than cruising boats, especially in close-fetched conditions. Any field-removable connector that wasn't sealed properly with dielectric grease and a strain-relieved boot will let salt water in over a week of hard sailing. Symptoms are intermittent connection loss that worsens through the regatta. Prevent it during install; fix it by replacing the connector mid-season if it surfaces.
3. Power brownouts during peak load.A racing boat running navigation instruments, autopilot, AIS, chartplotter, deck lights at night, and Starlink simultaneously can pull more amperage than the house bank or alternator can sustain. Symptoms are Starlink rebooting itself or dropping connection during heavy use. Verify house-bank capacity and Starlink power draw with a clamp meter during the shakedown weekend; if you're marginal, talk to us about wiring optimization.

For most CT racing programs, the Starlink install is the easy part. Mounting the antenna properly, routing cable cleanly, sizing the data plan to the program, and shaking down before the start — those are what separate a system that works through Block Island Race Week from one that fails halfway through Day 2.

If you're prepping a CT racing sailboat for the season, we're booking installs for May, June, and August — the windows that line up with Off Soundings, Block Island Race Week, and the Vineyard Race. Tell us about your boat and your race calendar.