Products · Intelligent Payloads and Accessories

Choosing a Visible-Light Gimbal

A visible-light gimbal is chosen for three things: the field of view that frames your subject, the resolution you need on that subject, and the stabilisation that keeps it there.

1 of 10Method note

Overview

Work backwards from the smallest feature you must resolve, then derive the required focal length and altitude.
Zoom range is not the same as usable resolution at maximum zoom; check the effective pixel density at your working distance.
Stabilisation quality shows up in video and in long exposures, not in the specification table.
Confirm the control protocol — a gimbal you cannot command from your ground station becomes a manual task.

A gimbal is a stabilisation problem before it is a camera problem

The instinct when choosing a visible-light gimbal is to compare sensor resolution and zoom range. Those matter, but they are not what usually determines whether the footage is usable. What determines that is stabilisation: how well the payload holds the sensor's line of sight steady while the aircraft moves, vibrates and corrects for wind. A high-resolution sensor on poor stabilisation produces sharp images of the wrong thing, or images that are unusably soft because the platform was moving during the exposure.

Stabilisation quality shows up in three places. The first is residual angular motion during steady flight, which affects whether fine detail is resolvable at all. The second is response to aircraft manoeuvres — a gust correction or a turn should not produce a visible swing in the image. The third is vibration isolation, which is a mounting property as much as a gimbal property and is where a good gimbal on a poorly isolated mount still underperforms.

So evaluate the gimbal on the aircraft it will actually fly, not on a bench. Residual motion is a system property: airframe vibration, mount stiffness, gimbal control and flight conditions all contribute. A payload that performs well in a demonstration may perform differently on a different airframe, and the difference is usually traceable to the mount rather than to the gimbal.

Resolution, zoom and what you actually need to resolve

Resolution requirements should be derived from the smallest feature the mission must resolve, at the standoff distance the mission will actually use. That gives a required angular resolution, which converts into a sensor and lens requirement. Starting from the other end — buying the highest resolution available — usually buys capability nobody uses and pays for it in mass, power and data volume.

Zoom is the other specification that is frequently over-bought. Optical zoom preserves resolution and is genuinely useful for inspection work where the aircraft must keep a safe standoff. Digital zoom does not add information; it enlarges pixels. Where a specification quotes a zoom range, confirm how much of it is optical and what the resolution is at the long end, because the long end is where inspection work happens.

Low-light performance is a third axis that inspection programmes often discover late. Inspections frequently happen at dawn, at dusk, under cloud, or under structures where light is poor. Sensor size, aperture and the gimbal's ability to hold a longer exposure without motion blur together determine whether usable imagery is possible in those conditions — and this is a system property, not a sensor specification.

Interface, power and the questions that decide integration

Before selecting a gimbal, confirm four things about the platform: the mechanical mounting provisions, the available payload power, the data and control interface, and the allowable mass and centre-of-gravity envelope. If all four are documented, selection is a matching exercise. If any is not, selection becomes a development project and the schedule should reflect that.

Power deserves specific attention because gimbal draw is continuous and, at the long end of a zoom or during rapid slewing, peaky. Confirm steady and peak draw against what the aircraft can supply across the whole flight profile, including the phases where propulsion demand is highest. A gimbal that browns out during a manoeuvre is a flight-safety issue, not an inconvenience.

Control and data paths matter for the same reason. Whether the operator can control the gimbal directly, whether the video feed reaches the ground station with acceptable latency, and whether the aircraft records onboard as a backup — these determine whether the operator can actually do the job. Our payload interface and platform compatibility note covers the interface side in detail.

Matching the gimbal to the mission

Mapping and survey work wants a different gimbal from inspection work. Mapping wants a known, stable geometry, a consistent field of view, and usually a mechanical or global shutter behaviour that does not distort fast-moving imagery. Inspection wants zoom, stabilisation and low-light capability. Trying to serve both with one gimbal usually compromises the mapping geometry, which is the harder thing to fix downstream.

Public safety and observation work — aerial reconnaissance, traffic or crowd observation, scene recording — sits closer to inspection: it wants zoom, stabilisation and the ability to dwell steadily on one point. It also raises the question of what is recorded and how it is retained, which is a policy matter rather than a payload one.

Where a programme needs both mapping and inspection, the usual answer is two payloads or two sorties rather than one compromise payload. Our visible-light gimbal range and the orthophoto acquisition note together cover the two sides; where neither standard option fits, payload mount adaptation is the route.

Selecting in practice

The practical sequence is: derive the required angular resolution from the smallest feature and the standoff distance; confirm the optical zoom needed to reach it; confirm stabilisation on the actual airframe; then confirm the four interface properties. That sequence avoids the common failure of buying a capable gimbal that cannot be mounted, powered or controlled on the aircraft.

Where the mission has an unusual requirement — a specific sensor, a specific interface, or operation in conditions outside the norm — say so early. It is cheaper to adapt a payload design than to discover the mismatch after delivery, and our custom inspection systems work exists for exactly that case.

Send your platform, the smallest feature you must resolve, your standoff distance, your light conditions and your mission type to our engineering team. We will propose a payload configuration and confirm the interface requirements, and we will be explicit where a standard payload does not cover the requirement.