The practical answer is that UG35 and UG62 belong to different integration scales. The approved UG35 record lists up to 10 kg maximum payload, 190 minutes of no-load endurance, a 21 m/s cruise speed, 35 kg maximum takeoff weight and a 4200 m maximum service ceiling. The approved UG62 record lists a 40 kg maximum payload, up to 16 hours of no-load endurance, a 30 m/s cruise speed, a recommended maximum takeoff weight no more than 135 kg, a 5000 m maximum service ceiling and fuel-powered fixed-wing cruise. None of those values alone chooses the mission.

A heavier class can support different payload concepts, but it also expands transport, installation, propulsion, maintenance, staffing, site and acceptance obligations. A lighter class can simplify some workflows but may not close the intended payload requirement. The buyer should compare complete mission systems, preserve every condition attached to the facts, and require configuration evidence before ranking either platform.

Define the Payload Package, Not Just Its Mass

List the payload body, mount, fasteners, damping, cables, connectors, power conversion, computing, antennas, storage, protective hardware and service tools. Record dimensions, interfaces and operating dependencies from approved sources. The total installed package is the object being integrated. A nominal sensor mass does not establish balance, structure, power, cooling, access, data quality or maintainability.

Describe the deliverable and mission geometry that justify the package. A heavy mapping sensor, communications relay, inspection system or logistics load creates different acceptance evidence. Keep those purposes distinct. A platform that can carry the mass still needs an approved way to install, operate, inspect and recover the actual configuration.

Preserve the Approved Conditions

The UG35 product record and UG62 product record support different controlled specifications. The endurance values are no-load conditions. They must not be presented as loaded mission times or route promises. Maximum payload and maximum takeoff-weight values are boundaries, not proof that a proposed installation has been accepted.

Service ceiling and cruise speed also require care. They do not establish performance for a specific payload, elevation, temperature, route or reserve policy. A procurement brief should quote the approved values with their labels and then state the evidence needed for the operating case. If a communication, environmental, material, maintenance or warranty field is not verified, keep it unknown.

Scale the Integration Evidence

For either candidate, require an interface-control package that identifies mounting surfaces, allowable loads where documented, clearances, fasteners, routing, power, protection, data interfaces, configuration identity and inspection access. The package should show who approves the design and how deviations are handled. A heavier installation usually creates more dependencies, but the buyer should document the actual configuration rather than assume complexity from class alone.

Plan evidence reviews in stages: concept fit, detailed interface review, bench or ground checks, controlled installation, permitted mission exercise and post-test inspection. Define the acceptance owner and stop conditions for each stage. Do not let a late flight demonstration replace missing drawings, configuration records or support responsibilities.

Compare Propulsion-Support Boundaries

The UG62 record identifies fuel-powered fixed-wing cruise, so its proposed operating system must include supplier-confirmed fuel, handling, inspection, storage, documentation and maintenance requirements. Do not invent quantities, intervals or procedures. The buyer should ask which tasks are operator-level, which require trained maintenance personnel and which remain supplier-controlled.

UG35 support planning also needs verified energy, charging, storage and turnaround instructions for the delivered configuration, but the workflow should not assume that one propulsion class is automatically simpler or safer. Compare the actual manuals, equipment, site rules, technician qualifications, spares and escalation paths. The decision is about supported operations, not a generic electric-versus-fuel slogan.

Model Transport and Ground Handling

Trace each aircraft and payload from storage through loading, restraint, vehicle access, unloading, staging, assembly, launch area, recovery and return. Identify lifting needs, case count, clean work area, tool control and weather protection. Use actual configuration evidence. A heavy-lift purchase can fail operationally when transport or site access was treated as an afterthought.

Run a ground-handling rehearsal with the proposed crew and equipment. Record task ownership, safe pauses, communication, inspection access and the process for quarantining a damaged or uncertain item. Time can be observed, but a single rehearsal should not be advertised as guaranteed setup productivity. Its purpose is to expose dependencies and training needs.

Assign Maintenance and Release Authority

Create a responsibility matrix for scheduled inspections, post-event inspections, discrepancy evaluation, configuration release, propulsion support, payload maintenance, software or firmware control when applicable, record custody and return to service. Name primary and backup personnel. If an authority boundary is unclear, treat it as a contract question rather than an informal local practice.

Review spare parts and support evidence without guessing failure rates. Ask how applicability is confirmed, which identifiers must be recorded, what documentation accompanies replacements and how an installed change affects the accepted configuration. The larger mission class may justify additional on-site support, but that decision should follow the disruption consequence and supplier process, not payload mass alone.

Build a Configuration-Specific Mission Model

Use route geometry, transitions, loaded configuration, planned speed, reserve, weather windows, ground time, inspections and data handling to construct scenarios. Label supplier facts and buyer assumptions separately. Do not multiply no-load endurance by cruise speed to claim range. Validate the chosen planning case through an accepted exercise within applicable operating authority.

Include disrupted cases: delayed launch, payload discrepancy, incomplete data, maintenance hold, fuel or charging constraint, limited site access and transport delay. Compare how each system reaches a safe decision and how evidence is preserved. Resilience comes from explicit roles and recovery paths, not only from carrying capacity.

Design Acceptance Around the Delivered System

Freeze the aircraft, payload, interfaces, support equipment, documents, software state where relevant and crew standard before acceptance. Record identity, installation, mass statement, ground checks, permitted mission profile, data evidence, recovery, inspection and discrepancies. State what must be repeated after a change. A supplier demonstration is not automatically acceptance of the buyer's configuration.

For UG35, the exercise may focus on a sensor-integration workflow. For UG62, it may include broader propulsion, transport and heavy-payload support evidence. The exact scope must come from the intended mission and delivered configuration. Use comparable decision criteria while allowing the evidence packages to reflect different system scales.

Put Support Deliverables in the Contract

List drawings, configuration records, operating and maintenance documents, training, tooling, ground-support requirements, parts process, escalation, change notices and acceptance data with delivery dates. Mark which items are required before order, factory review, shipment and field acceptance. A general promise of support cannot replace a named deliverable and responsible owner.

Use a detailed configuration inquiry to close unknowns. Provide the payload package, mission, route, site, transport, staffing and acceptance concept. Ask for configuration-specific evidence and explicitly request that unsupported values remain unknown. This prevents a comparison table from creating apparent certainty where the current records do not provide it.

Choose the Smallest Supported Mission System

The preferred class is the one that closes the mission with acceptable margin, evidence and support—not automatically the platform with the higher payload figure. If UG35 supports the validated integration, a larger system may add unnecessary obligations. If the complete mission requires UG62-class capability, the buyer must also fund and accept the larger support system.

Review Fleet Consequences

A platform decision affects more than the first aircraft. Compare how a second unit would change storage, transport, tooling, technician coverage, propulsion support, configuration control and spare strategy. Do not assume that fleet scale simply doubles the first-aircraft plan. Shared equipment may reduce some needs, while simultaneous missions and maintenance holds can expose new capacity limits.

Define the minimum operational availability the project requires and the evidence used to release each aircraft. Avoid inventing reliability percentages. Instead, test whether the support model can handle a representative inspection, a configuration change and one unavailable specialist without losing record control. These scenarios show whether the organization is buying a supported capability or only an airframe.

Include disposal, long-term storage, transport after damage and supplier-return responsibilities where they matter to the buyer. These lifecycle questions may differ between platform classes and can affect facility and contract planning. If current evidence cannot close them, place them in the commercial register rather than assigning optimistic assumptions.

At the approval meeting, separate mandatory mission requirements from desirable future options. A larger platform should not win because it supports a hypothetical payload that has no funded mission, and a smaller platform should not win because its current support footprint is familiar. Score the validated operating case, then record a separate expansion path with its own evidence and budget gate.

Require the decision chair to state which mission, configuration and support baseline the approval covers. Publish no broader capability claim from that meeting. A future payload or operating site must enter change control with its own affected evidence.

Compare the other controlled procurement patterns in the UG62 missing-values review and the heavy-lift composite-support guide. Then review relevant classes in the VTOL and fixed-wing collection. Keep the final decision tied to a documented configuration, closed evidence, named owners and a review trigger.