> ## Documentation Index > Fetch the complete documentation index at: https://docs.valar.space/llms.txt > Use this file to discover all available pages before exploring further. # Managing Maneuvers > Create, inspect, edit, delete, import, and export stored spacecraft maneuver records. > For the complete documentation index, see [llms.txt](/llms.txt). The **Maneuvers** page manages stored burn records for your spacecraft. Each record has an editable name, optional purpose, a required reference frame (attitude mode), and one or more burn segments. You can create records manually or import them from OCM files, then read, edit, export, or delete them. Stored records do not certify execution, even when their epochs are in the past. Mission-forecast history therefore shows execution counts and consumed propellant as unavailable when only these generic records exist; forecast estimates and dated state-vector inventory remain separate. **Route:** `/maneuvers/burn-plan` ## Find a record Use the spacecraft and time-range filters to find maneuvers. Grouping by spacecraft keeps records together; the ungrouped view shows a flat list. Select a row to open its details. Checkboxes select records for bulk export or deletion. Rows show the maneuver name, identity/display identifier, spacecraft, timing, and available derived values. A conflict indicator marks overlapping records. A record outside the selected time range may still conflict with a visible one. ## Review records in Flight Plan When Flight Plan is available for your account, open a spacecraft's **Flight plan** and choose **Burn timeline**. Set the UTC period and optionally filter by phase or unassociated records. Imported records remain visible without a source plan. Select a burn to inspect the same complete record and permitted actions here. A linked burn also shows its source plan and saved phase revision. The phase's **Maneuver plans** and **Burns** sections let you review successive proposals and related records without leaving Flight Plan. Return controls keep that context; a burn link can open a record outside the timeline's current period. Use the standalone Maneuvers page for manual creation, import and bulk export or deletion. Presence in a timeline, plan approval or a past epoch does not confirm execution. In Flight Plan, **Execution & analysis** shows matching retained Orbit Determination (OD) estimates when you have orbit read permission. Each estimate names its producing OD result, epoch, production date and convergence. Use **Load more OD results** to inspect older history; a failed read can be retried without discarding loaded results. Different producing results remain separate, and editing the stored maneuver does not update historical estimates. Missing estimates stay unavailable. OD estimates alone do not confirm execution or measured propellant consumption. ## Create a record 1. Click **Create maneuver** in the toolbar. 2. Choose the spacecraft. The selected spacecraft is fixed once the record is created. 3. Enter a name. On creation, this becomes both the stable identity and initial display name. The exact identities `.` and `..` are not permitted because URL routing normalizes them. 4. Choose a **Record frame** and, optionally, a purpose of at most 63 characters. 5. Add at least one burn segment and supply its epoch, duration, thrust vector, ISP, and reference frame. Use **Add segment** or remove a segment as needed. 6. Click **Create maneuver** to save. If validation fails, correct the indicated fields and retry. Segment epochs use ISO-8601 timestamps. Durations and ISP use seconds and thrust uses newtons. Every segment needs a positive finite duration, nonzero finite thrust, and ISP between 50 and 10,000 seconds. Use physical values appropriate to your spacecraft and burn. Reference frames are explicit, with supported examples including `TNW`, `RTN`, `QSW`, and `RSW_ROTATING`; no frame is inferred. Acceleration, delta-V, and delta mass are read-only projections in the detail view and can be unavailable. The record and every segment must use equivalent frames, including their rotation convention. **Use record frame** copies your selected frame to that segment only; it does not transform thrust components. `RTN`, `QSW`, and `RSW_ROTATING` are equivalent here; `TNW` is a different frame. Select the correct frame for the values you are entering. See [supported frames](/file-formats/ocm#supported-reference-frames). A duplicate identity for the same spacecraft is rejected. Creation never updates a record that already exists. Creating a stored maneuver does not send a command to the spacecraft. ## Read complete details Select a record to see its current name, stable **Identity**, **Display ID**, **Spacecraft**, **Purpose**, **Reference frame**, and full burn-segment composition. The details panel retrieves the complete record, so edits start from the stored segments rather than a list summary. **Summary** shows total delta-V, signed delta mass, total burn duration, creation date, and start/end epochs. Burn duration excludes gaps between segments; the start-to-end span includes those gaps. **Performance** shows available recorded performance deviation, normalized performance, pointing azimuth/elevation, and estimated total delta-V. Normalized performance is relative to 100% nominal thrust; performance deviation is relative to 0% nominal deviation. Missing values are labelled **Unavailable**, including when the physical context needed for a projection is absent. A reported zero remains zero; a missing segment value is not treated as zero to produce a total. These values and past epochs do not establish that a stored maneuver was executed. | Action | Result | | - | - | | **Edit** | Open the record's name, metadata, and segment editor | | **Export** | Download an OCM file | | **Delete** | Open a confirmation before removing the record | Create, edit, and import controls require write permission. Deletion requires delete permission; reading and exporting require read permission. Contact your administrator if an action is missing. ## Edit a record 1. Open the record and click **Edit**. 2. Change its name, purpose, attitude mode, or burn segments. 3. Review the complete segment list, including any added or removed segments. 4. Click **Save changes**. The identity and spacecraft are shown as fixed fields. Renaming changes the display name only: links, API requests, and OCM `MAN_ID` still refer to the original identity. Start and end times derive from the segment epochs and durations. To change timing, edit those segment fields directly and review the resulting burn definition. Frames use selectors. A stored token outside the common suggestions remains visible as **retained** until explicitly changed. Saving still applies current frame validation. Changing the record frame does not automatically change segment frames or transform their thrust. Add/remove actions move keyboard focus to the new or remaining segment, and failed saves retain your entries with the error. ## Resolve conflicts New and edited records must not overlap another record on the same spacecraft. The check uses the entire enclosing interval from the maneuver's start to end, including gaps between segments. One record can end exactly when the next begins. Records for different spacecraft are independent. If saving fails, read the error and inspect the conflicting identities. Choose which record to edit or delete, then try again. VALAR does not automatically change other records to make room. Unsaved editor values remain available when a save fails. ### Inspect overlapping records List indicators and record details identify overlaps. Use the **Open** links in details to inspect conflicting records, including records outside the list's current time window. You can read, export, and delete these records. Every save must make the edited record non-overlapping, even when changing only its name or metadata. Resolve the conflict through an explicit segment edit or delete. Computation results retain their captured maneuver information; new computations use the current records. ## Delete records Click **Delete** in a record's details and confirm. To delete several records, select their checkboxes and use the bulk **Delete** action. Check the reported outcome for each action. Deletion removes live maneuver data and cannot be undone. Bulk deletion reports successful and failed counts separately. Successfully deleted records are removed from the selection; failed records stay selected with their error explanations so you can resolve the cause and retry those records. ## Import and export * **Import** adds records from `.ocm` or `.txt` CCSDS OCM files. Each file is atomic; duplicate identities and overlaps are rejected. See [Importing Maneuvers](/features/maneuver-import). * **Export** in a record's details downloads that record; toolbar export selects a spacecraft and date range. The bulk toolbar exports checked records. See [Exporting Maneuvers](/features/maneuver-export). * Programmatic clients use the [Maneuver API](/api-reference/maneuvers) for OCM import, OCM export and deletion. To correct a record, explicitly delete it and import the corrected OCM; these are separate operations, so a failed import leaves the record deleted. Historical records without a usable burn epoch show unavailable timing and remain inspectable by identity. They are not positioned at the current time or their creation date on a timeline. A mixed-frame historical export downloads as a preservation `.zip` rather than `.ocm`; preservation archives are not import requests. ## Timeline View A horizontal Gantt-style visualization of every burn for the selected spacecraft, with orbital events overlaid as bands and markers to give thruster timing the right context. **Route:** `/maneuvers/burn-plan/timeline` The timeline is anchored to a UTC time axis along the top. Each spacecraft row holds the stored burns within the current window, drawn as Gantt-style segments. Orbital events are overlaid above the burn rows as either shaded bands (entry-to-exit duration) or instantaneous markers (single-epoch events). ### Zoom Toggle Two zoom levels control how densely time is packed onto the horizontal axis. | Mode | Description | | - | - | | **Wide** | More pixels per hour, useful for inspecting individual burns and short-duration events | | **Compact** | Fewer pixels per hour, useful for scanning multi-day windows and long-arc revisit patterns | A **Now** button to the right of the zoom toggle scrolls the timeline to the current UTC instant. ### Orbital Events Four orbital event types overlay onto the timeline. Each renders either as a shaded band (covering an entry-to-exit interval) or as an instantaneous marker (a single-epoch crossing). | Event | Display | Description | | - | - | - | | **Eclipses** | Band | Shadow events. Distinguished into **Umbra** (full shadow) and **Penumbra** (partial shadow); each subtype renders as a band spanning entry-to-exit duration | | **South Atlantic Anomaly (SAA)** | Band | Geographic region of elevated radiation; band spans entry-to-exit duration | | **Apsis** | Marker | Periapsis and apoapsis crossings; rendered as instantaneous vertical markers | | **Nodes** | Marker | Ascending and descending node crossings; rendered as instantaneous vertical markers | ### Display Popover Click **Display** in the topbar's right-aligned controls (accessibility name **Display settings**) to open the **Orbital events** popover. Each toggle controls visibility for one event type on the timeline; flipping a toggle is reflected immediately on the visible bands and markers. | Toggle | State | Effect | | - | - | - | | **Eclipses** | On (default) | Show or hide umbra and penumbra bands | | **Apsis** | On (default) | Show or hide periapsis and apoapsis markers | | **Nodes** | On (default) | Show or hide ascending and descending node markers | | **SAA** | On (default) | Show or hide South Atlantic Anomaly bands | ### Schedule Export Dialog Click **Export** in the timeline topbar's right-aligned controls to open the **Export Schedule** dialog. The dialog generates a Spacecraft Schedule File ([`.ssf`](/file-formats/ssf)) listing every selected event over a chosen window. The same dialog is also accessible from the passes timeline at `/passes/timeline`. Export Schedule dialog #### Spacecraft A single-select dropdown listing every spacecraft in your tenant. The dialog defaults to the spacecraft already selected on the timeline. #### Date Range | Element | Description | | - | - | | **Start Date** | Calendar picker; selectable range covers 7 days before today through 7 days after today | | **End Date** | Calendar picker; cannot be earlier than **Start Date** and cannot exceed 7 days after **Start Date** | | **Time inputs** | `HH:MM` format, **UTC** for both Start and End | | **Maximum window** | 7 days | #### Include Five checkboxes determine what the exported `.ssf` file contains. All five are checked by default. With every checkbox unchecked the **Download** button is disabled and the dialog displays the validation message **Select at least one event type**. | Checkbox | State | What it includes | | - | - | - | | **Eclipses** | Checked (default) | Umbra and penumbra entry/exit events | | **Apsis** | Checked (default) | Periapsis and apoapsis crossings | | **Nodes** | Checked (default) | Ascending and descending node crossings | | **Ground Station Passes** | Checked (default) | Visibility windows for selected ground stations | | **South Atlantic Anomaly (SAA)** | Checked (default) | SAA entry/exit events | #### Ground Stations The **Ground Stations** card appears only when **Ground Station Passes** is checked. Use it to restrict the exported passes to specific ground stations. * Click the trigger button to open the picker. * Check the stations to include; leave the selection empty to include all configured stations. * The trigger label reads **All ground stations** when no stations are selected, or **N selected** when one or more are picked. The card's helper text reads **Select specific ground stations or leave empty to include all**. #### Footer | Button | Description | | - | - | | **Cancel** | Close the dialog without exporting | | **Download** | Generate and download the `.ssf` file. While the export is in flight, the button label changes to **Exporting...** | When you export a spacecraft that is running on the fallback (see [Orbit age](/features/orbit-age#degraded-level)), the generated `.ssf` includes that spacecraft's fallback orbital events and carries an in-file `COMMENT Orbital events derived from public TLE - indicative timing` note, so a downstream reader treats their exact timing as indicative. When no fresh orbit is available and the fallback cannot rescue the craft, the file retains the `COMMENT Orbital events unavailable - no fresh state vector` note it carries today. ## Related pages * [Maneuver Planner](/features/planner) — separate plan evaluation and approval workflows * [Importing Maneuvers](/features/maneuver-import) — add records from OCM files * [Exporting Maneuvers](/features/maneuver-export) — share stored records as OCM * [Maneuver API](/api-reference/maneuvers) — authentication, OCM import/export, deletion, and correction examples This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.