Energy

Your asset, watched from the water

Platforms, pipelines, wind sites, licence blocks. Weeks of met-ocean and seabed data at a fraction of a vessel day.

A red offshore platform reflected on a calm sea under a pale skyOffshore

The point

A vessel day is the wrong unit

Most offshore questions are slow ones: how the current runs across a site, how a pipeline route sits on the seabed after a winter. They need weeks of data, and weeks of vessel are what nobody budgets.

A sail drone changes the unit. It runs the survey lines at walking pace, holds a met-ocean station for a season, and passes along a pipeline route every few days, with no crew to rotate and no fuel to bring out.

It works inside the safety zone of a platform because it is small, slow and quiet, and it works at a licence block nobody has visited because it does not need a port nearby.

We deliver

What comes back from the site

  1. 01

    Met-ocean dataset

    Wind, wave, current and water column at the site, hourly, for as many weeks as the design study needs.

    Hourly
  2. 02

    Inspection log

    Camera and echosounder passes along the pipeline route and around the platform legs, with time, position and the images.

    Per pass
  3. 03

    Seabed profile

    Bathymetry along the survey lines and current profiles through the water column, delivered as grids and time series.

    Grid
  4. 04

    Route watch

    Every vessel seen along the route or inside the safety zone, from AIS and camera, for the operator and for the authority.

    Daily
  5. 05

    Your format

    Data in the formats your engineers use, on your infrastructure if you want it there, with the metadata a design study requires.

    Yours

Example

A mission as it would run

A row of offshore wind turbines reflected on a calm sea

Example mission

Oristano wind site survey

A hundred days of wind, wave and current data at a floating wind site off the west coast of Sardinia, before anyone builds anything. The drone holds station at the centre of the block, profiles the water column every hour and runs a line across the site once a week. The developer receives the met-ocean dataset a design study needs, without a buoy to install or a vessel to charter.

Area
West of Sardinia, off the Gulf of Oristano
Sea days
100
Sensors
Weather station, ADCP, CTD, AIS
Delivers
Met-ocean dataset, current profiles, traffic log
For
Wind developer

Example mission, not yet flown

How it runs

From a scope to a dataset

  1. 01

    Scope

    Site, parameters, survey lines and duration, with your engineers. The output is a mission plan and a number of sea days.

    Two weeks
  2. 02

    Mobilise

    Hulls arrive by road and go in from the nearest quay. Inside a safety zone the operator's procedures apply and we follow them.

    One day
  3. 03

    Survey

    The control room runs the lines and the station. Your engineers follow the data live and can move a line or add a pass.

    Every sea day
  4. 04

    Deliver

    The dataset lands in your format at the end, with the metadata and the quality flags a design study requires.

    Two weeks

Questions

What operators ask

Can it work inside a 500 m safety zone?

Yes, with the operator's permission and procedures. It is small, slow and quiet, and it keeps a distance from the structure that the operator sets.

What accuracy does the survey reach?

Positioning to half a metre with corrections, depth to the accuracy of a single-beam echosounder. It is a reconnaissance and monitoring survey, not a multibeam charting campaign.

Does it replace a survey vessel?

For weeks of presence, yes. For a multibeam campaign or a diver, no. The two are used together: the drone tells the vessel where to go.

How is the data delivered?

Live on a dashboard during the mission, and as a dataset at the end in the formats your engineers use, on your infrastructure if you prefer.

Next step

Start from the site and the season

A block, a route or a platform, and the parameters your study needs. We come back with a mission plan and the sea days it takes.