The answer-first takeaway is simple: the approved UG21 and UG25 records share a 2.5 kg maximum payload, up to 240 minutes of no-load endurance, a 20 m/s cruise speed and a 4800 m maximum service ceiling. Those shared values do not prove equal results, and they do not identify a universal winner. A mapping buyer should preserve every condition attached to the numbers, mark unverified fields as unknown, and compare the evidence required by the actual workflow.

That approach avoids two common procurement mistakes. The first is inventing a distinction when the approved records do not support one. The second is treating the absence of a published value as proof that two aircraft are identical. A disciplined comparison keeps three columns: verified facts, configuration-specific evidence to request, and buyer-owned operating criteria. Only the first column can be filled directly from the current product records.

Start With the Mapping Deliverable

Define the customer output before discussing airframes. Record the mapped area, terrain, surface characteristics, required products, coordinate reference, control strategy, delivery deadline, review method and acceptance owner. A platform comparison becomes useful when it explains how each candidate will support that evidence chain. Without a defined deliverable, endurance and payload figures remain disconnected from the decision the customer needs to make.

For geospatial work, the ASPRS Positional Accuracy Standards provide professional context for defining and reporting positional accuracy. They do not certify either aircraft, specify a project design or guarantee a result. The buyer still owns the survey plan, reference evidence, sensor choice, processing method and quality review. Keep this deliverable standard separate from the aircraft fact sheet.

Build a Verified-Fact Matrix

Enter the current UG21 product record and the UG25 product record side by side. Copy each approved value with its unit, qualifier and source date. For both products, the endurance value is explicitly an up-to, no-load condition. It must not be rewritten as a loaded mission time, route range, reserve policy, mapped area or daily production promise.

The same discipline applies to payload and speed. A maximum payload value does not establish the mass, balance, interface, power, cooling, data or calibration suitability of a proposed mapping sensor. Cruise speed is not automatically the survey speed a project will use. Service ceiling is not operating authorization and does not establish performance at a specific field elevation. Each number is a screening input with defined boundaries.

Keep Unknown Fields Visible

Create explicit rows for any fact needed by the mission but not approved in the current record. Examples may include configuration-specific loaded endurance, interface drawings, payload power, communication details, transport dimensions, storage requirements, permitted environmental limits, maintenance intervals, documentation scope, training and warranty terms. Do not fill a blank by copying a value from another model, a memory, a reseller page or a generated summary.

Send the unresolved rows through a controlled configuration inquiry. State the intended sensor, accessories, site elevation, route, reserve rule, launch cycles, data workflow and acceptance test. Ask the supplier to identify which answer is a published product fact, which is a configuration proposal and which requires a test. A useful response preserves that classification instead of collapsing every statement into marketing copy.

Compare Payload Integration Evidence

Request a configuration list for the exact sensor package. It should identify the sensor, mount, fasteners, vibration-control elements, cables, connectors, power conversion, storage media, antennas, protective parts, firmware or software dependencies when relevant, and the controlled installation record. Ask who approves the integration and who owns corrective action if the delivered configuration differs from the accepted list.

Then define an integration review that can fail safely. Verify identity, mounting, clearance, cable routing, power behavior, data recording, calibration applicability and removal or reinstall procedures. The test should produce evidence that another technician can interpret. A photo of the aircraft with a sensor attached is not a substitute for configuration control, and a successful short flight does not close the entire mapping workflow.

Model the Mission Without Turning Conditions Into Promises

Build a buyer-owned mission model from route geometry, planned speed, turns, climb and descent, vertical transitions, setup, reserve, contingencies and expected loaded configuration. Label every assumption and keep the supplier's approved values separate from the buyer's calculation. The model should reveal which evidence changes the decision most. It should not advertise a predicted range or coverage figure before a controlled field validation supports it.

Use scenarios rather than one optimistic total. Include a normal mission, a shorter weather window, an additional recovery margin, a delayed launch and a data-quality repeat. Check how the plan responds when one assumption is less favorable. The stronger candidate is the one whose documented configuration and support process allow the buyer to close critical assumptions, not necessarily the one that produces the largest spreadsheet total.

Inspect Field Workflow Fit

Observe transport, case handling, assembly, preflight access, sensor installation, launch-area footprint, recovery, post-flight inspection and data offload. Record crew roles and elapsed time without turning one demonstration into a universal productivity claim. A mapping organization may value repeatable setup, technician access or evidence quality more than a small difference in an unsupported headline measure.

Ask what happens after an interrupted mission. The comparison should cover data custody, partial coverage, configuration changes, battery or fuel records as applicable, inspection triggers, maintenance escalation and the process for deciding whether to resume. This recovery path often exposes operational differences that are invisible in a simple payload-endurance table.

Define a Fair Acceptance Exercise

Use the same deliverable, site controls, payload identity, crew standard, mission assumptions and evidence requirements for both candidates. Record deviations before interpreting results. The exercise should verify setup, configuration identity, mission execution, data capture, processing handoff, quality review and recovery. Do not change acceptance criteria after seeing which aircraft completed a step more comfortably.

A pass decision needs traceable evidence: aircraft and payload identities, approved configuration, environmental record, mission plan version, raw files, processing record, quality checks, discrepancies and closure. If the supplier provides a demonstration, state which evidence the buyer independently controls. The comparison is only as credible as the chain connecting the field activity to the accepted deliverable.

Compare Support and Change Control

Request the applicable manuals, installation guidance, maintenance responsibilities, training scope, parts process, release authority and escalation path for each proposed configuration. Ask how updates are communicated and how the buyer can determine whether a change affects an accepted mapping setup. A platform can fit the mission technically yet create avoidable risk if documents, ownership or change notices are ambiguous.

Include these support items in the commercial evaluation with due dates and acceptance owners. Do not convert an unpriced promise into an assumed deliverable. Identify which documents must arrive before order, factory acceptance, shipment, field acceptance and routine operations. This makes the comparison auditable and prevents a late support gap from being hidden by shared performance numbers.

Make the Decision From Closed Evidence

Review the broader UNITED UAV VTOL and fixed-wing drone collection only after the mission evidence matrix is stable. A different platform class may be justified if the mapping sensor, workflow or support obligations exceed what the current comparison can verify. Expansion should follow the same fact-lock method rather than restart a marketing-led model search.

Continue with the UG32 versus UG39 workflow-evidence comparison and the no-load endurance evidence guide. Together they show how shared specifications and conditional endurance values should be converted into supplier questions, acceptance records and buyer-owned decisions.

Set Review Triggers Before Contract Close

Define which events force the comparison to be reopened: a sensor change, revised deliverable, new site condition, altered reserve rule, product-record update, support-document revision or acceptance discrepancy. Name the owner who assesses the change and the evidence that must be repeated. A decision matrix is only valid for the configuration and mission assumptions it records. Review triggers keep a sensible initial choice from becoming an unsupported permanent conclusion.

Archive the rejected alternatives and reasons as carefully as the selected platform. Future staff should be able to see whether a candidate failed a hard requirement, lacked timely evidence or simply scored lower under the original priorities. That record prevents teams from repeating the same research and allows a previously rejected aircraft to be reconsidered fairly when the mission or evidence changes.

Finally, verify that the approved comparison is reflected in the request for quotation, acceptance checklist and operating brief. Conflicting versions can reintroduce the unsupported claims the matrix was designed to remove. Give the record a controlled owner, revision and distribution list, and require acknowledgement from teams that will plan, sell, configure or operate the selected system.

Retire superseded copies so an old comparison cannot guide a new configuration in active use.

Approve a platform only when the critical rows are closed or deliberately accepted as limitations. Record why the selected configuration fits the deliverable, which assumptions remain, who owns them and what would trigger a review. That decision may select UG21, UG25 or neither. The important outcome is not a manufactured winner; it is a defensible mapping procurement record that another reviewer can reconstruct.