Skip to main content
For the complete documentation index, see llms.txt.
Export maneuver records from the Maneuvers page at /maneuvers/burn-plan for use in external tools. Exports contain the current stored burn data in CCSDS OCM format.

​
Export one maneuver

Select a record to open its details, then click Export to download its OCM file. The corresponding API operation is GET /operations/maneuvers/export?spacecraftIds=...&maneuverIds=.... Use the stable maneuver identity and its owning VALAR spacecraft ID.

​
Export selected records

Select records with the list checkboxes and use Export as OCM in the bulk actions toolbar. A single maneuver downloads as OCM text; multiple selected maneuvers for one spacecraft download as a ZIP of OCMs. Selections spanning spacecraft are exported separately per spacecraft. For one spacecraft, use GET /operations/maneuvers/export?spacecraftIds=...&maneuverIds=BURN-001&maneuverIds=BURN-002, with 1–100 unique maneuver IDs and no request body. Repeat maneuverIds for each identity; commas within a value are literal. URL-encode names and split large selections into smaller requests if necessary to stay within URI size limits. Omit time bounds when selecting IDs.

​
Export by date range

  1. Click Export in the maneuver list’s toolbar.
  2. Select the spacecraft and time range.
  3. Download the OCM export.
For automation, use GET /operations/maneuvers/export with spacecraftIds, startDate, and endDate. The API uses the exact ISO-8601 bounds supplied. One spacecraft produces OCM text; multiple spacecraft produce a ZIP of OCM files. See the API examples.

​
File identity and metadata

OCM MAN_ID is the stable maneuver identity, including after a name edit. Exports omit optional MAN_BASIS metadata. Records with conflicts are exportable, but an export is not a way to update them: importing an already stored identity is rejected. Use Edit to change an existing record. For supported fields and units, see OCM. Creating an export does not command the spacecraft; follow your own downstream submission and uplink procedures.

​
Missing required inputs

Export requires the actual burn intervals and the physical quantities needed by the selected output.
  • Supply authoritative phase boundaries or actual burn duration. When elapsed time is derived from firing time, supply the duty ratio as well.
  • Correct reversed, nonpositive, or out-of-range sample intervals and regenerate the plan when its saved timing cannot be reconstructed. A terminal boundary sample does not create an extra burn; valid subsecond intervals remain subsecond.
  • Where delta-V or fuel is derived, provide the required mass, thrust, Isp, and consumption data. Missing values do not become zero delta-V or fuel.
Use the error’s named field to repair the source maneuver or recompute a supported plan, then retry export. These are VALAR calculation/export requirements, not universal requirements of every CCSDS file schema.