# Fleet View for One-to-Many Operations: Direct Launch, Smart Visibility, and Performance at Scale {% embed url="" %} One-to-many drone operations, where a single operator flies multiple drones at the same time, is one of the most demanding workflows in autonomous drone software. Every second the operator spends managing the dashboard is a second pulled away from situational awareness and tactical decision-making. At ten or twenty active drones, the cost of routine interface work adds up into real operational risk. This update positions FlytBase Fleet View as a purpose-built one-to-many operations dashboard. Four capability areas work together to keep operators focused on what's happening in the field rather than on managing the interface: direct launch controls, automated visibility management, pin rotation, and a performance mode for high feed counts. ### Direct Launch Controls Mission launch, Go-to-Location, and alarm response are now available directly from the Fleet View table. Operators can select drones in the dashboard and dispatch them without leaving the multi-drone overview. #### Launch Missions on Selected Drones Select one or more drones from the Fleet View table and assign a mission. The mission selector and pre-flight confirmations open in-place against the live dashboard, not as a full-page transition. The fleet table stays visible throughout, so operators retain situational awareness over all active drones while configuring the launch.
#### Send Drones to a Location Issue a Go-to-Location command to selected drones directly from Fleet View. Pick the destination on the map, confirm, and the drones are dispatched to that point. No context switch needed.
#### Respond to Alarms The alarm panel is available alongside the fleet table. Operators can assign an unconfigured alarm to a drone and dispatch that drone via mission or Go-to-Location, all without leaving Fleet View. The multi-drone overview stays on screen throughout alarm triage, so operators never lose visibility of the rest of the fleet while responding to an event. For one-to-many operators, this is the difference between staying with their fleet during a launch decision and losing context every time a drone needs to be sent somewhere.
#### What Fleet View Supports for Each Device Type Fleet View displays both docked drones and non-docked drones. The operations available for each device type reflect platform-level capabilities, not anything specific to Fleet View. | Capability | Docked Drones | Non-Docked Drones | | ---------------------------------------- | ------------- | ----------------- | | View in Fleet table, map, and video grid | ✅ | ✅ | | Mission launch | ✅ | ❌ | | Go-to-Location | ✅ | ❌ | | Alarm response | ✅ | ❌ | | Safety actions (Stop, RTH, RTSL) | ✅ | ❌ | Non-docked drones do not support mission launch, Go-to-Location, alarm response, or safety actions anywhere in FlytBase. In Fleet View, these controls are disabled when a non-docked drone is selected. The Fleet View experience for non-docked drones is full visibility: telemetry, video feeds, and map position. ### Automated Visibility: Auto-Rotation Between Sections The Fleet View table has three sections: Pinned, Visible, and Hidden. The Visible section drives what's shown on the map and in the video feed grid. Drones in this section have their positions plotted and their feeds streamed. The Hidden section holds drones that aren't currently the operator's focus. For a one-to-many operator, the relevant set of drones changes constantly. A drone takes off, becomes flight-critical, lands, and falls out of attention. Manually moving rows between sections to keep the map and feeds aligned with reality is exactly the kind of interface work that pulls focus from the field. Auto-rotation handles this automatically. Two dropdowns let operators define which drones should appear in the Visible section based on their current state.
| Criterion | Behavior | | --------- | ------------------------------------------------------------------------------------------------------- | | Armed | Drone moves to Visible when it takes off (in-air state). Returns to Hidden when it lands. | | Online | Drone moves to Visible when it connects (powered and reachable). Returns to Hidden when it disconnects. | When both criteria are enabled, a drone moves to Visible if it meets either condition. The result is that the Visible section, the map view, and the video feed grid all stay aligned with what's actually happening in the field, without the operator needing to touch the table. ### Pin Rotation: Cycling Focus Across Active Drones The Pin function focuses the dashboard on a single drone. The map recenters and follows that drone, and all of its video feeds become available, including the main camera, dock camera, and auxiliary feeds. Pin rotation cycles this focus automatically across the Visible section. Set a rotation interval, and FlytBase moves each drone in the Visible section into the Pinned position for that duration before moving to the next. With five drones in the Visible section and a 30-second interval, each drone gets a focused review every two and a half minutes, without the operator clicking anything.
Intervals are selectable up to 5 minutes. Choose based on how long you need to assess each drone's state. Shorter intervals work well for active monitoring, and longer ones are better for sustained observation. Pin rotation pairs naturally with auto-rotation. The Visible section stays current with what's flying, and pin rotation cycles attention across that current set. Together they address the two hardest interface problems in one-to-many operations: keeping the dashboard focused on active devices, and giving each device sustained operator attention without manual cycling. ### Filtering and Search Filtering and search in the Fleet View table let operators narrow the table down to only the drones relevant to a specific situation. Combined with auto-rotation, filtering gives operators a precise scope of devices for the dashboard to manage and rotate through. Filters are available across the key dimensions in the Fleet View table. Applied filters persist through the session, so operators can set their scope once and stay focused on it. ### Performance Mode: Standard and Optimised One-to-many operations push the dashboard hardest on the video pipeline. Eight, twelve, or twenty live feeds at once is a real load on the front end, and at some point the trade-off between feed smoothness and overall dashboard responsiveness becomes worth thinking about.
Two performance modes are available: | Mode | Frame Rate | When to Use | | --------- | ---------- | -------------------------------------------------------------------------------------------- | | Standard | 30 FPS | Default. Best video smoothness for monitoring critical operations. | | Optimized | 15 FPS | Reduces front-end load. Use when monitoring many feeds or when the dashboard feels sluggish. | The toggle is in the video feed section of the dashboard. Optimized mode keeps every feed live at half the frame rate. For dashboards displaying many concurrent feeds, this typically means smoother table interactions, faster map updates, and reduced browser memory pressure, without losing visibility on any drone. ### Hardware Compatibility All Fleet View improvements are dashboard-side and apply across FlytBase deployments. Auto-rotation, pin rotation, filtering, and performance mode work for any device that appears in the Fleet View table, including both docked drones (Dock 1, 2, 3) and non-docked drones. Mission launch, Go-to-Location, alarm response, and safety actions apply to docked drones only. These operations are not supported for non-docked drones anywhere in FlytBase. For non-docked drones, Fleet View provides full visibility: telemetry, video feeds, and map position. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://releases.flytbase.com/april-2026/fleet-view-for-one-to-many-operations-direct-launch-smart-visibility-and-performance-at-scale.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.