The first mistake in payload buying is treating every impressive number as equally useful. A better process removes distractions before it compares features.
- ~12 linesWhat the datasheet shrinks to
- 4 questionsThat select the priority
- 1 flightWorth more than any table
- Mission firstThen the spreadsheet
Key takeaways
- Cross out numbers that do not change the field decision — combined zoom multipliers without the optical figure, theoretical ranges against building-sized targets, palette counts.
- What remains is about a dozen lines, and those lines decide the mission.
- Ask what the team must prove. Detection, fault evidence, perimeter monitoring and recurring documentation each point to a different priority.
- A demonstration flight against your real target, at your real distances, answers more than any comparison table.
On this page
Ignore Numbers That Do Not Change the Field Decision
Four categories account for most of the noise on a thermal payload datasheet, and none of them changes whether your operator finds the person or proves the fault.
Combined digital zoom multipliers quoted without the optical figure. A “1500x hybrid” number is arithmetic, not capability — only the optical share adds detail. Hybrid zoom explained covers how to decode it.
Maximum theoretical detection ranges against building-sized targets. A large-vehicle detection figure under Johnson criteria is a real number describing a situation you will never be in. DRI ranges explained covers why the two standards in circulation differ by roughly an order of magnitude.
Palette counts. Three well-chosen palettes serve every mission; a list of twenty is a menu, not a capability — see thermal palettes compared.
Frame-rate differences beyond what your video link carries. Though note the 9 Hz tier is a genuine limitation for dynamic work — frame rate explained covers where it actually bites.
What Remains When You Cross Those Out
Cross them out and the datasheet shrinks to about a dozen lines. Those lines decide the mission.
| Line | What it decides |
|---|---|
| Sensor resolution | Pixels on target, therefore usable range |
| NETD with its f-number | Whether low-contrast findings survive the noise floor |
| Optical focal length | Range versus area coverage |
| Stabilisation accuracy | Whether zoom imagery is usable at all |
| Controllable range | Whether the payload can point where you need it |
| Ranging capability | Whether an observation becomes a coordinate |
| Control interfaces | How long integration takes |
| Stream format | Whether it fits your link and ground system |
| Weight | Flight time, and whether it flies at all |
| Voltage and peak current | Whether the electrical system holds |
| Measurement options | Whether you can quote a temperature — permanent |
| Environmental rating | Whether it survives your conditions |
Every one of those has a guide behind it, but the point of the list is its length. Twelve lines is a comparison a person can hold in their head; a full datasheet is not.
Ask What the Team Must Prove
Does the operator need to detect a person, prove an asset fault, monitor a perimeter or document a recurring anomaly? Each answer points to a different priority.
| What must be proved | Priority | Why |
|---|---|---|
| A person is present | Sensitivity, then resolution | Low-contrast targets at range |
| This asset has a fault | Radiometry | A number is what makes a finding actionable |
| Nothing crossed this perimeter | Tracking and zoom | Detect, then identify before responding |
| This anomaly is growing | Repeatability | Comparable data across surveys beats peak capability |
Then ask the integration questions that surface late and hurt most: what does it weigh, what voltage does it need at peak, which protocol does it speak, and will the mount clear the airframe through full gimbal travel. The integration checklist covers all four properly, and they are the questions that turn a good purchase into a working system.
The Right Payload Fits the Mission Before It Impresses the Spreadsheet
Procurement still needs technical detail — none of this is an argument for buying on intuition. But detail should serve a field workflow rather than a comparison document.
A demonstration flight against your real target, at your real distances, in your real conditions answers more than any comparison table. It surfaces the things no datasheet contains: how the payload behaves in your wind, whether your operator can drive the interface, whether the imagery is legible on your ground station screen in daylight.
That is the difference between a payload that looks strong in a tender document and one that becomes trusted equipment your crews argue to keep. Evaluating payload suppliers covers testing the supplier as well as the hardware, and choosing a payload without spec noise covers the positive version of this discipline.
Buy one evaluation unit before the fleet. A demonstration flight with your own aircraft, crew and targets costs one payload and settles arguments that a year of comparison tables will not.
Related reading
- How to Choose a UAV Thermal Payload Without Spec Noise
- How to Read a Thermal Payload Spec Sheet
- Hybrid Zoom on UAV Cameras
- DRI Ranges Explained
- Thermal Camera Frame Rate
- An Integrator’s Checklist for Evaluating Suppliers
- UAV Payload Integration Checklist
- What Drives the Price of a UAV Thermal Payload
- MV-2P — 640×512 thermal at 130 g
- OP-90A — zoom, thermal and ranging
- OP-125A — flagship EO/IR pod
- Thermal Drone Payloads for Search and Rescue
FAQ
Which single specification is most over-weighted by buyers?
Hybrid zoom multipliers quoted without the optical figure. A very large number costs the manufacturer nothing to produce — digital multiplication is free — and it adds no detail the optics did not already resolve. Ask for the optical factor and the sensor resolution, and the impressive figure resolves into something comparable.
Is a demonstration flight really worth arranging?
Yes, and it is usually the cheapest step in the whole process. It surfaces what no datasheet contains: behaviour in your wind, legibility on your ground station in daylight, whether your operator can drive the interface under pressure, and how the imagery looks against your actual targets at your actual distances. Buying one evaluation unit before committing to a fleet is the same principle at slightly larger scale.
What are the integration questions that hurt most?
Weight as installed, peak current draw at gimbal slew, which control protocol the payload speaks, and whether the mount clears the airframe through full gimbal travel. All four surface late — usually after purchase — and all four are answerable in an email before ordering. The installed weight in particular routinely runs 15–30% above the catalogue figure once mounts, dampers and cabling are counted.
Questions about the technology? Talk to our engineers — we reply within 2 business days.