The immediate conclusion is that UG32 and UG39 share approved headline values for a 5 kg maximum payload, up to 240 minutes of no-load endurance and a 21 m/s cruise speed. Repeating those values cannot decide a 5 kg mission. The procurement team should move to workflow evidence: the proposed payload configuration, known and unknown fields, transport and setup, data custody, maintenance ownership, support documentation and a fair acceptance exercise.

This is not an argument that the aircraft are identical. It is a rule against inventing differences. The current records support several shared facts and some model-specific fields, but the buyer still needs configuration evidence for the intended sensor and operating case. A defensible comparison shows which questions are closed, which remain open, and which buyer requirement actually separates the candidates.

Describe the 5 kg Mission as a System

List every item included in the mission package: primary sensor, mount, vibration elements, cables, connectors, power conversion, antennas, computing or logging hardware, storage media, protective parts and any supporting equipment. State the acceptable installed mass and balance process without assuming that the maximum payload value is the target operating point. The complete integration, not a sensor brochure weight, is the object under review.

Then define the outcome. A mapping mission, corridor inspection, environmental record and patrol task may use equipment of similar mass but require different flight geometry, data checks, operator workload, handoff speed and acceptance evidence. Keep those mission classes separate. A platform can be suitable for one workflow and create unresolved dependencies in another even when the payload number fits both.

Use Shared Facts as Boundaries

The UG32 product record and UG39 product record both support the shared payload, no-load endurance and cruise-speed values. Preserve the qualifiers. No-load endurance is not evidence of endurance with the proposed 5 kg-class integration, and maximum payload does not establish approved mounting, power, data or environmental compatibility.

Do not convert cruise speed into a route-completion promise. Mission speed can be constrained by the sensor, data quality, turning geometry, terrain, regulations, site controls and reserve policy. The buyer may use the approved speed as one input to a planning model, but the output remains a buyer assumption until validated with the selected configuration and a documented mission profile.

Create a Known-Unknown Register

For each aircraft, record verified product facts, requested configuration facts and buyer-owned operating criteria. Unknown rows may include loaded endurance, interface drawings, payload power, communication details, transport configuration, environmental limits, inspection intervals, spare strategy, training, lead time or warranty terms. The exact list should reflect the mission. A blank cell must remain visible until a qualified source closes it.

Use a structured configuration request rather than a general question about which model is better. Provide the payload list, data interfaces, route type, launch environment, reserve rule, daily cycle goal, crew model and acceptance deliverable. Ask for evidence applicable to each candidate. If an answer applies only to a proposed configuration, label it as such and preserve the revision identity.

Review Mechanical and Electrical Integration

Request drawings and procedures that show mounting surfaces, approved fasteners, clearance, vibration controls, cable routing, connector retention, power conversion, protection and access for inspection. Verify how technicians confirm the installed configuration and what evidence survives removal and reinstall. An integration that works during a supplier demonstration may still be fragile if the buyer cannot reproduce it from controlled documents.

Separate compatibility from acceptance. Compatibility may mean the system can be physically connected; acceptance should prove the mission package is correctly identified, installed, powered, recorded, operated, inspected and removed. Define stop conditions for unexpected heat, vibration, data loss, interference, loose retention or undocumented deviation. Every stop condition needs an owner and a closure record.

Compare Transport and Field Setup

Observe the full movement from storage to vehicle, site, launch area and back. Record case count, lifting needs, restraint, assembly sequence, protected work area, tool control, preflight access and the space used by the crew. Do not rely on a staged photograph. A useful comparison uses the same crew standard and equipment boundary for both platforms.

Time each step for learning, not for an unsupported productivity claim. Note which tasks can run in parallel, which depend on one specialist and which create rework when interrupted. Include recovery, post-flight inspection, data copying and repacking. The workflow with the shorter first setup may not be the stronger choice if it leaves configuration or data evidence unresolved.

Test Data Custody and Acceptance

Define how raw files are associated with aircraft identity, payload identity, configuration release, mission plan, time basis, storage media and operator. Reconcile expected files before the aircraft is repacked. Record copy verification, quarantine rules and the handoff to processing or analysis. A completed flight without a complete evidence package is not a completed mission.

For visual, mapping or sensor missions, create acceptance checks that reflect the actual deliverable. State the sample, reviewer, thresholds, discrepancy path and reflight decision. Do not attribute accuracy or detection performance to the aircraft without separate evidence. The platform comparison should show how reliably the team can produce and review the required record.

Include Maintenance and Support Ownership

Ask which inspections apply before and after the intended mission class, which documents govern them, who can release the aircraft, which discrepancies require supplier involvement and how parts applicability is confirmed. Review training and backup staffing. A 5 kg mission can create long downtime if maintenance knowledge is concentrated in one person or if support boundaries are unclear.

Compare the process for configuration changes. If a cable, sensor, mount, software component or operating instruction changes, the buyer needs to know what evidence must be repeated and how affected missions are identified. Strong change control protects accepted workflows. It also prevents a successful demonstration from becoming a permanent but undocumented exception.

Run a Common Acceptance Exercise

Use the same payload definition, route, crew requirement, site controls, evidence checklist and discrepancy rules for both candidates. Capture setup, configuration checks, permitted mission execution, recovery, file reconciliation, quality review and repacking. Record conditions and deviations. Do not move the acceptance threshold to favor the aircraft that happens to be demonstrated first.

Require a repeatable evidence package rather than a single pass label. Another reviewer should be able to reconstruct what was installed, what was done, what data were produced, what failed and why the conclusion was accepted. If a critical field remains unknown, the result should state the limitation instead of implying that the exercise closed it.

Score Evidence Closure, Not Marketing Density

Build the final evaluation from mission-critical rows. Weight configuration reproducibility, field workflow, data custody, inspection access, support ownership and change control according to the buyer's operation. Keep shared facts visible but do not count them as differentiators. A candidate earns preference by closing the right evidence with acceptable risk and commercial terms.

Review the verified UG21 versus UG25 comparison for another shared-specification example, and the UG35 versus UG62 integration-scale guide for a comparison where support demands diverge more sharply. Both reinforce the same rule: facts screen candidates; workflow evidence supports selection.

Rehearse the Commercial Handoff

Before order approval, ask engineering, operations, maintenance, mapping or inspection, finance and contracting owners to review the same evidence matrix. Each should confirm which requirement it owns and whether the proposed support deliverables are priced and scheduled. A technical preference can fail in service when spare, training, document or acceptance obligations never reach the purchase scope.

Use a short tabletop scenario in which the intended sensor is replaced, a mission is interrupted and a configuration record is missing. Observe whether the team knows who can approve the change, whether prior evidence remains applicable and how customer delivery is protected. This reveals governance gaps without claiming product performance and gives both candidates the same operational challenge.

Attach the final workflow map to the acceptance plan. It should show decision points from payload receipt through installation, dispatch, data handoff, inspection and return to service. The map is not a substitute for supplier instructions. It is the buyer's method for ensuring that those instructions, records and authorities reach the correct person at the correct step.

Review the map with the people who will perform the work, not only managers. Ask them to locate the applicable configuration record, stop criterion, data handoff and escalation contact. If they cannot do so from the controlled package, the workflow is not ready regardless of which aircraft leads the scoring table. Correct the document or training gap before acceptance.

Capture their feedback as controlled corrective actions and verify closure in the next rehearsal. This connects procurement evidence with field usability instead of assuming that a signed approval automatically creates an executable workflow.

Use the UNITED UAV VTOL and fixed-wing drone collection to identify other platform classes only when the 5 kg mission definition shows that neither candidate closes a critical requirement. Record the decision, unresolved assumptions, owner and review trigger. The strongest outcome may be UG32, UG39 or a revised requirement, but it should never be a distinction invented from identical headline numbers.