Underwater glider mission planning turns an ocean-observation objective into a route, dive pattern, sampling schedule and recovery plan that a slow, buoyancy-driven vehicle can carry out. The central constraint is that moving through the water does not guarantee progress toward a waypoint: currents, available energy and access to the surface all affect whether the glider can collect useful data and return to a recoverable location.
Start with the observations you need, then test whether the proposed vehicle and operating area can deliver them. A mission is incomplete if its track looks feasible but its sensor schedule, communications or recovery arrangements do not.
On This Page
- Connect the science objective to the vehicle
- Plan a route through a moving water column
- Budget energy around the complete mission
- Define what crosses each interface
- Build data quality into the dive schedule
- Prepare for faults and recovery
- Make the mission ready for handover
Connect the science objective to the vehicle
A conventional underwater glider changes its buoyancy to descend or ascend. Wings convert that motion into forward travel, producing repeated sloping profiles through the water column. The pump-driven Slocum illustrated in NOAA's glider overview demonstrates this mechanism. Hybrid vehicles can add propulsion; their operating assumptions need separate treatment.
The planning boundary includes the buoyancy and attitude-control mechanisms, onboard flight control, science sensors and logging, batteries, surface communications, shore software and recovery crew. OceanGliders describes periodic surfacing for satellite data transfer and new instructions. Between contacts, the vehicle must execute its onboard mission within configured limits.
Define the desired measurement before choosing waypoints. Specify the variable, depth range, geographic coverage, revisit need and acceptable delivery delay. Temperature sections, oxygen observations and acoustic recordings impose different sampling and processing demands. A sensor name alone does not establish that a mission will produce the required scientific result.
Three applications illustrate the distinction:
- Repeated ocean sections: prioritize comparable profiles across a defined region, allowing for the time required to traverse it.
- Hurricane-season observing: position gliders to monitor relevant ocean features in advance. NOAA IOOS explicitly distinguishes this sustained sampling from chasing storms, which their slow horizontal motion does not suit.
- Acoustic observations: NOAA describes recording fish-spawning sounds with an acoustic receiver. The mission therefore needs a recording and retrieval plan as well as a geographic track; a temperature profile alone cannot answer that question.
Plan a route through a moving water column
The glider's motion over ground combines its movement relative to the water with the current carrying it. A direct heading toward the next waypoint can therefore be a poor route. Examine current direction and strength over the intended dive depths and times, rather than relying on a surface map alone.
EMODnet's mission-planning case study explains why operators combine historical observations, forecasts and remote sensing. Density structure also matters: the vehicle must be ballasted for the water it will encounter, within its buoyancy engine's adjustment range. A freshwater surface layer can change that problem materially.
Use this information to compare corridors, deployment timing and recovery approaches. Keep bathymetry and its uncertainty visible throughout the route review. Keep pressure-depth limits separate from bottom clearance. Review the shallowest plausible seabed along the corridor, position uncertainty and the vehicle's configured response to approaching the bottom.
At a surface contact, a GPS position can be compared with modeled underwater motion to estimate the current experienced during the preceding cycle. The OceanGNS research uses this information alongside ocean forecasts to support route changes. The estimate depends on the vehicle model and summarizes a completed interval. Changes with depth, tides and forecast error can make the next dive different.
For the wider positioning architecture, see AUV navigation without GPS. Confirm the navigation instruments actually fitted to the glider instead of assuming that every AUV navigation aid is present.
Treat the planned corridor as a revisable hypothesis. Before deployment, decide what would justify a new waypoint, a shorter submerged interval, a different sampling area or an early return. The responsible pilot needs alternatives that still meet the observation objective when the original track becomes impractical.
Budget energy around the complete mission
Build an energy budget for transit, observations, communications and recovery reserve. Include the actual sensor configuration and operating schedule. The Atlantic Canada operating study identifies buoyancy pumping, payload settings and drag, and surface communications as important endurance variables.
Deeper profiles can reduce the frequency of buoyancy reversals, while pumping at greater pressure can require more energy. The OceanGNS paper models this tradeoff for a particular glider. Do not turn that result into a rule that the deepest possible dive is always preferable: science coverage, seabed clearance and the installed vehicle configuration still control the choice.
Ask for a mission-specific budget with these separate entries:
- Expected consumption on the outward and return routes.
- Consumption for the proposed sampling and transmission schedule.
- Allowance for changed currents, extra contacts and an alternate recovery approach.
- A recovery reserve with a stated basis and an identified person authorized to end sampling.
Do not infer remaining mission duration from a battery percentage alone. Relate the available energy estimate to the work still required, and revisit it when the route or payload schedule changes. The distinction between battery telemetry and mission decisions is developed in battery management systems for unmanned vehicles.
Define what crosses each interface
Mission planning involves more than sending a waypoint list. Specify the information each subsystem accepts and returns, and how the operating team knows a change took effect.
The following interface checklist is an engineering synthesis of the OceanGliders operating model and data-format guidance. It is a set of questions for the installed system, not a claim that every glider uses one command protocol.
| Interface | Define before deployment | Confirm during operation |
|---|---|---|
| Shore planning to flight control | Waypoints, coordinate conventions, dive limits, contact rules and mission version | Acknowledged mission and actual behavior agree |
| Flight control to science payload | Enabled sensors, sampling phases and available configuration commands | Expected measurements appear with usable timestamps |
| Vehicle to shore | Priority health telemetry, science subset, transfer limits and failed-contact behavior | Latest vehicle state is distinguishable from an old report |
| Shore processing to data users | Units, calibration records, positions, quality flags and delivery mode | Users can identify what is provisional and what has been reviewed |
For conventional surface satellite operation, the next contact is an opportunity to update the mission. It should not be assumed that an urgent change can reach a submerged vehicle immediately. An optional acoustic link introduces different integration questions, covered in acoustic communications for underwater vehicles; its presence and supported commands must be confirmed for the actual system.
OceanGliders' OG1.0 format organizes mission data as NetCDF trajectories and distinguishes near-real-time, recovery and delayed-mode products. This helps data exchange. It does not make different manufacturers' flight commands interchangeable.
Build data quality into the dive schedule
Collecting more profiles is useful only if the measurements can answer the question. Reserve time and supporting observations for calibration and comparison before deciding that every available hour should be spent on the main transect.
The OceanGliders Salinity SOP recommends flight-model calibration dives and comparison with an independent conductivity, temperature and depth instrument, commonly called a CTD, near deployment and recovery. Paired ascending and descending profiles help investigate sensor response effects. Those activities influence the route and vessel schedule, not just later processing.
For oxygen, the OceanGliders Oxygen SOP explains that reference sampling should follow stable glider flight and account for sensor conditioning. Coordinate the pilot and deployment team so that the comparison occurs near the glider's relevant position. A sample collected at a convenient but unrepresentative location may not resolve the measurement question.
Agree which records will travel with the observations: sensor identifiers, applicable calibrations, time and position information, processing methods and quality flags. Preserve the original data alongside derived products. Under the OG1.0 convention, data can be updated after recovery and later quality control, so an early transmission should not silently stand in for the final scientific dataset.
Prepare for faults and recovery
The Atlantic Canada study emphasizes trained piloting coverage, diagnostic checks and practical recovery arrangements. Its lessons include watching leak indications, flight behavior, battery use and science acquisition. An autonomous mission still needs an operating team able to interpret those signals and act.
Use the following decision table to prepare the team's response. These are planning questions based on the mechanisms above; actual alarm limits and emergency commands must come from the vehicle's approved operating procedures.
| Observation or failure | Question to resolve | Plan to have ready |
|---|---|---|
| Little progress toward a waypoint | Has the current changed, or has vehicle behavior changed? | Alternate corridor and criteria for abandoning the leg |
| Abnormal dive or climb | Do diagnostics indicate a control, buoyancy or vehicle-integrity problem? | Escalation to the qualified pilot and applicable recovery procedure |
| Missed contact | Is the expected contact overdue, and what onboard behavior follows? | Contact escalation, last known state and search coordination |
| Missing or suspect science data | Is acquisition failing, or does the measurement need correction? | Diagnostic data request and a decision on continuing the mission |
Choose the recovery area while the launch is being planned. Confirm vessel access, handling equipment, crew communication and an alternative if conditions change. The authors recommend retaining the ability to recover immediately after launch; the crew should set weather and handling limits for its vessel and equipment. Neither a forecast recovery date nor a remaining-energy estimate guarantees that a suitable vessel will be available.
Make the mission ready for handover
A useful final review connects each objective to a decision the team can make at sea. The table below consolidates the route, sensor and interface questions into a mission handover checklist; it does not prescribe numerical limits for an unspecified glider.
| Planning item | Handover record | Decision it enables |
|---|---|---|
| Observation objective | Variables, region, depth coverage and delivery need | Which sampling can change without losing the purpose |
| Vehicle and environment | Configuration, density assumptions, route alternatives and seabed constraints | Whether the proposed dives and transit remain feasible |
| Energy and contacts | Consumption basis, reserve rationale and contact schedule | When to reduce work, change route or recover |
| Measurement quality | Calibration activities, reference samples and data-processing responsibilities | Whether observations are scientifically usable |
| Operational response | Duty coverage, fault procedures, vessels and recovery alternatives | Who acts when the original plan no longer works |
For each response in the handover record, name the decision owner and the contact route they will monitor during the mission. Record who takes over when a shift ends or that person cannot be reached. Walk through the transfer using the current mission configuration, so the relief pilot can distinguish an approved change from an older route or contact schedule.
Before release, ask the pilot, science lead and recovery team to walk through one missed contact, one unfavorable-current leg and one early-recovery request. Any answer that depends on an unspecified capability, unavailable person or unarranged vessel identifies work still needed. The mission is ready when its observations, vehicle behavior and recovery decisions form one workable plan.
Sources
- NOAA: What is an ocean glider?. Government overview of buoyancy-driven travel, sensors and an acoustic observation example.
- OceanGliders: Gliders. Observing-program description of profiling and periodic satellite communication.
- EMODnet: Glider Mission Planning with Historical Data. Operator case study on currents, density and environmental information.
- von Oppeln-Bronikowski et al.: Overview of a new Ocean Glider Navigation System: OceanGNS. Original 2021 research on current-aware routing, navigation estimates and energy modeling.
- von Oppeln-Bronikowski et al.: Best practices for operating underwater gliders in Atlantic Canada. Peer-reviewed 2023 operational experience, with regional and vehicle-specific limits.
- OceanGliders Salinity SOP: Missions execution. Community guidance on calibration dives and independent comparisons.
- OceanGliders Oxygen SOP: Missions execution. Community guidance on sensor preparation and reference sampling.
- OceanGliders OG1.0 format. Data-format specification covering mission trajectories, metadata and data modes.
- NOAA IOOS: Hurricane Glider Coordination. Government program description of sustained ocean observations supporting forecasting.
Last checked: September 11, 2026.
