MERIDIAN Ground Control Station: a concept UX prototype

Portfolio note

You are looking at a concept piece

This is a simulated ground control station for a single UAV, the companion piece to Mission Telemetry. Where that piece is about watching a whole fleet, this one is about a single operator actively controlling one vehicle. All data here is simulated for this demo. Click Next for the design thinking behind it, then a walkthrough of each panel.

Design principles

The thinking behind this

A few decisions shaped this piece specifically, distinct from the monitoring dashboard.

• Confirmation gating: any irreversible action, like Return to Base, requires a deliberate two step confirmation with a visible countdown, so a single accidental click can never trigger it.
• Zone separation: monitoring surfaces (map, sensor feed) and control surfaces (throttle, altitude, heading, RTB) are visually distinct, so an operator always knows whether they are looking or acting.
• Fixed situational awareness: signal lock, GPS lock, battery, and link quality live in a persistent bar that can never be closed or moved, because losing sight of that information is the one failure this interface cannot allow.
• Large, deliberate targets: control inputs are sized for confident interaction under stress, not for visual density.
• Restrained motion, again: every animation still exists to make a state change easier to track, never as decoration.

This is scoped to the in-flight moment only, on purpose. No pre-flight planning or post-flight review, that is the acting-on-data half of a two-piece story.

It is modeled as single-operator. Larger platforms like the Reaper split pilot and sensor operator roles across a multi-crew station. This piece intentionally models the smaller single-operator case.

Return to Base auto-cancels if nobody confirms, the opposite of how DJI's Return to Home often behaves on a timeout. Theirs is usually a lost-link fail-safe defaulting to "go home." This models an operator-initiated command during an active session, so the safer default here is to do nothing until someone confirms.

Map icons are simplified for the demo, not official NATO symbology.

1. Navigation Map

Where the vehicle is, and how it gets home

Shows the vehicle position, its route to the next waypoint, and a persistent home marker.

The home marker and route line stay visible at all times, even before any emergency, so a return path is never something the operator has to look up under pressure.

2. Sensor Feed

What the vehicle sees

A simulated live camera feed with coordinates, heading, and target lock overlaid.

This is deliberately the largest panel by default. In an actual control task, the sensor feed is what the operator is most likely watching, so it earns the most space.

3. Flight Controls

The one place you can act

Throttle, altitude, and heading controls, plus a confirmation gated Return to Base command.

This panel does not just look different. Return to Base cannot fire from a single click anywhere else in the interface. That constraint is the point, watch what happens if the signal drops.

4. Controls

Panels, tutorial, and theme

The grid icon shows or hides any panel, close one from its header and bring it back here. The question mark replays this walkthrough any time. The sun and moon icon switches between light and dark mode.

Same operator control principle as the panels themselves. No fixed layout works for every operator or every shift.

That is the tour

Feel free to explore

Drag the throttle, altitude, and heading controls, and watch the status bar. About twelve seconds in, the signal will start to degrade on its own, watch how the interface responds, and try confirming a Return to Base while it is happening. Thanks for taking the walkthrough.