.png)
The Operator
The operator runs a mixed deep-sea and coastal commercial fishing fleet operating primarily out of Dutch Harbor, Alaska, with vessels working the Bering Sea, Gulf of Alaska, and North Pacific fishing grounds. The fleet includes combination vessels, catcher-processors, and dedicated tender vessels — ranging from 120 feet to over 200 feet — with crew rotations of 14 to 28 days.
At the time of engagement, every vessel in the fleet was running GEO VSAT through a legacy maritime communications provider. The contract was approaching renewal. The fleet manager had been watching LEO satellite performance data for 18 months and decided the transition window was open.
“We’d been on VSAT for over a decade. It was expensive, the latency made real-time communication impossible, and crew welfare was always an afterthought. The renewal was the right moment to make the move — and we wanted someone who understood fishing fleets, not just satellite hardware.”
— Fleet Manager, Pacific Northwest Commercial Fishing OperatorThe Challenge
Three operational constraints defined the engagement from the outset.
No disruption to fishing operations
Commercial fishing is seasonal and margin-sensitive. A vessel that misses fishing days due to an installation problem is a direct revenue loss. The operator required that every installation be completed at dock during scheduled port calls — with the vessel operationally ready before it returned to fishing grounds. No exceptions.
MLC compliance on day one
The operator had been operating under a compliance risk with legacy VSAT — crew internet access was inconsistent and not formally structured as an MLC 2006 obligation. With regulatory scrutiny increasing, the new platform had to deliver compliant crew welfare internet from the first day of operation, with the documentation to support it.
VMS continuity
Vessel Monitoring System position reporting is a legal obligation in US waters and across the EEZ fisheries the fleet operates in. Any gap in VMS uplink during or after the transition would trigger a compliance incident with NOAA and NMFS. The VMS uplink had to be continuous throughout the installation and transition period.
The Solution
Tidal Ops deployed a tiered package architecture across the fleet. The eight smaller coastal and tender vessels received Fleet Essentials — Starlink Maritime terminals with VMS uplink, crew welfare internet, and 8-hour NOC support. The four largest catcher-processor vessels, which run longer deep-sea trips and have larger crews with more complex operational requirements, received Platform Ops — adding constellation-agnostic routing, 5G/LTE coastal integration, fleet dashboard, and the cybersecurity managed overlay.
Starlink Maritime terminal installation on a catcher-processor vessel at Dutch Harbor. Installation completed in under 3.5 hours including network configuration and VMS verification.
Installation logistics
All 12 vessels had scheduled port calls within a 10-day window. Tidal Ops deployed two installation teams to Dutch Harbor simultaneously — one team focused on the Fleet Essentials vessels, the second handling the Platform Ops catcher-processors which required additional SD-WAN configuration and the OT traffic isolation setup.
VMS was maintained throughout the installation process via a temporary cellular uplink during the terminal swap — ensuring zero gap in position reporting during any individual installation. The NOAA VMS portal confirmed continuous uplink for all 12 vessels with no incidents logged during the transition period.
Crew welfare setup
Each vessel received a segmented Wi-Fi network — crew welfare on a dedicated SSID with a managed bandwidth allocation separate from operational traffic. The configuration was certified MLC 2006 compliant and documented for the operator’s flag state compliance records. On the day each vessel departed Dutch Harbor, the crew welfare internet was live.
“The crew on our largest vessel messaged family from the Bering Sea for the first time on the first trip after installation. That matters. It affects how long good crew stay with you.”
— Operations Director, Pacific Northwest Commercial Fishing OperatorThe Results
Post-transition performance data collected across the first three months of full-fleet operation:
| Metric | Legacy VSAT | Tidal Ops LEO |
|---|---|---|
| Average latency | 580ms | 36ms |
| Connectivity uptime (fleet average) | 97.8% | 99.7% |
| VMS compliance incidents | 3 in prior 12 months | 0 post-transition |
| MLC crew welfare compliance | Informal / unverified | Certified · Day 1 |
| Average throughput (deep-sea) | 4–8 Mbps shared | 80–140 Mbps |
| NOC support response | 24–48hr provider response | 8hr guaranteed SLA |
| Weather routing data availability | Delayed / limited | Real-time · All vessels |
What Changed Operationally
Beyond the connectivity metrics, the fleet manager identified three operational changes that were not anticipated at the outset of the engagement.
Real-time catch pricing negotiation
With reliable, low-latency connectivity from fishing grounds, the operations team was able to begin real-time communication with buyers and processors while vessels were still at sea. The ability to negotiate offloading schedules and catch pricing before reaching port — rather than accepting dock prices on arrival — was described by the fleet manager as an unexpected commercial benefit that partially offset the subscription cost in the first season.
Electronic logbook submission
The operator had been submitting paper catch logs on return to port. With continuous LEO connectivity, the vessels transitioned to direct electronic logbook submission to NOAA during the voyage — reducing port processing time and eliminating the administrative backlog that built up across a 12-vessel fleet during heavy fishing periods.
Crew retention signal
Three months post-transition, the operator reported that crew retention conversations had qualitatively changed. Multiple crew members specifically referenced the welfare internet access when renewing contracts. No quantitative retention data was available at time of publication, but the operator flagged it as a notable shift in crew feedback.
Conclusion
This engagement demonstrated that a full fleet LEO transition — across 12 vessels, multiple vessel types, and two package tiers — is executable within a single port rotation window without operational disruption, compliance gaps, or fishing season impact. The constraints that often delay maritime connectivity transitions (installation logistics, VMS continuity, crew welfare certification) are all solvable with the right managed services partner and the right pre-engagement planning.
The operator has subsequently initiated a fleet assessment for two additional vessels acquired after the initial transition. Full fleet is now under Tidal Ops managed services.