The answer-first conclusion is that the approved UG62 facts do not by themselves approve a 40 kg payload mission. The current 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 of no more than 135 kg, a 5000 m maximum service ceiling and fuel-powered fixed-wing cruise. The buyer still needs a complete mass statement, integration record and supplier-verified configuration evidence.

Missing values are not defects to be hidden. They are decision items. Communication details, wind information, material details for this model, configuration-specific loaded endurance, installation interfaces, environmental limits, maintenance requirements, training, lead time or warranty terms may matter to a particular mission. If the approved record does not verify a needed value, label it unknown and assign a closure path.

Define the Mission Configuration

List the payload, mount, fasteners, damping, cables, connectors, power conversion, antennas, computing, storage media, protective equipment and service tools. Add aircraft-installed options and operational equipment that affect the delivered configuration. Identify every item by a controlled name and revision where available. The mass statement must represent the actual system, not a rounded payload label.

Describe the mission outcome, route, site, transitions, reserve policy, crew, data workflow and acceptance evidence. A logistics payload, environmental sensor and emergency-supply concept can have similar mass but different installation, restraint, power, access and recovery requirements. Do not approve a generic 40 kg mission class when the buyer intends to operate a specific package.

Separate Facts From Calculations

Use the UG62 product record as the fact lock. Copy the maximum payload and recommended takeoff-weight limit exactly. Then place the buyer's itemized mass statement in a separate controlled record. Do not infer empty mass, fuel quantity, usable payload or margin from the published values when those inputs are not in the approved record.

Every calculation should show source, unit, revision, measured or declared status, uncertainty where relevant and owner. The arithmetic can be correct while the decision is wrong if an item was omitted or a value came from the wrong configuration. Add an independent reconciliation before acceptance and define what happens when a component or quantity changes.

Build the Missing-Value Register

Create one row per mission-critical unknown. State why the value matters, acceptable evidence, responsible source, due date, impact if unresolved and fallback. Avoid broad questions such as asking for all specifications. A targeted register helps the supplier respond to the proposed configuration and prevents an answer for another model or operating case from being accepted accidentally.

Use the configuration inquiry to request controlled answers. Include the payload package, site, elevation, route, ground-support concept, staffing and acceptance plan. Ask the supplier to identify applicable documents and test evidence. If an answer is not available, preserve the unknown and decide whether the mission can proceed with a conservative limitation.

Request Interface-Control Evidence

Ask for applicable mounting surfaces, fasteners, allowable arrangements, clearance, retention, cable routing, power, protection, data interfaces and inspection access. Define who approves the integration and how the installed configuration is verified. A payload that fits within the mass boundary can still be unsuitable if its interfaces, balance, structure, power or service access are unresolved.

Plan a staged review: document review, physical fit, controlled installation, ground checks, permitted mission exercise and post-test inspection. Give each stage stop conditions and an owner. Do not use a flight to compensate for missing configuration records. A successful exercise is only reusable when the buyer can confirm the delivered setup matches the tested setup.

Treat No-Load Endurance as Conditional

The 16-hour value is an up-to, no-load condition. It cannot establish loaded mission endurance, route range, reserve or productivity. Request evidence for the exact payload and mission profile. Record transitions, planned speed, route geometry, holds, reserve decision, recovery and environmental conditions. Keep buyer assumptions separate from supplier facts.

Build normal and disrupted scenarios without publishing their outputs as product claims. Include shorter weather windows, additional inspection, a delayed launch, route change and early recovery. The purpose is to identify which unknowns control the decision and what evidence the acceptance exercise must collect.

Define Propulsion-Support Responsibilities

Because the approved record identifies fuel-powered fixed-wing cruise, request the applicable supplier instructions for fuel, handling, inspection, storage, transport, documentation and maintenance. Do not invent quantities, intervals or procedures. Identify which responsibilities belong to operators, trained maintenance personnel, the supplier or another approved party.

Map the support equipment, site controls, training and records needed by the delivered configuration. Check whether the deployment location can provide them without improvised practices. A configuration can satisfy the mass statement and still fail readiness if propulsion-support ownership, safe storage or maintenance escalation is unavailable.

Review Transport and Site Readiness

Trace storage, loading, restraint, vehicle access, unloading, staging, assembly, payload installation, launch, recovery and return. Identify lifting needs, tool control, clean areas, fire and spill controls where applicable under the buyer's safety program, communications and quarantine space. Confirm requirements from approved documentation rather than generic assumptions.

Rehearse the workflow with the intended crew and equipment. Record roles, pauses, inspection access and how the team handles an uncertain component or record. Time observations can support staffing, but one rehearsal is not a guaranteed productivity claim. Its value is finding dependencies before the mission schedule depends on them.

Create Acceptance Evidence

Freeze aircraft identity, payload configuration, itemized mass statement, applicable documents, crew standard and mission profile. Verify installation, ground checks, permitted operation, data or delivery outcome, recovery, reserve decision and post-flight inspection. Capture environmental conditions and deviations. State which changes require partial or complete reacceptance.

The evidence package should let an independent reviewer reconstruct the configuration and conclusion. Include discrepancies and closures, not only successful steps. If a needed value remains unknown, document the limitation and operational consequence. Acceptance is a controlled decision, not a way to convert an absent specification into an implied fact.

Keep Authority Boundaries Separate

Product specifications, configuration approval, maintenance release, operational authorization, site safety and customer acceptance are different decisions. A fact in one record cannot grant another authority. Name the owner and evidence for each. This prevents the procurement team from treating a supplier statement as an operating permission or a completed flight as an engineering approval.

If the intended mission involves unusual risk, complex operations or third-party approvals, obtain the appropriate professional and regulatory review. Do not infer compliance from product capability. Preserve the aircraft specification review as one input to the larger authorization and safety system.

Make Unknowns Commercially Visible

Attach the missing-value register, document list, training, tooling, support, acceptance data and closure dates to the commercial scope. State the impact of late or incomplete delivery. A lower headline price or earlier aircraft date cannot compensate for a configuration that the buyer cannot approve, maintain or operate with controlled evidence.

Audit the Register at Each Milestone

Review open values at order, design review, factory acceptance, shipment and field acceptance. A row can change owner or evidence status, but it should not disappear because the schedule advanced. Record who accepted any residual uncertainty and the operating limitation attached to it. This gives management a clear view of readiness without converting unresolved questions into silent assumptions.

Check source applicability during every review. A document can be authentic yet apply to another configuration, revision or operating context. Require the reviewer to record why the source supports this row and which condition it carries. If the connection cannot be shown, return the value to unknown and reopen the supplier request.

Use the register after delivery when payloads, instructions or support arrangements change. Compare the proposed change with the accepted baseline, identify affected facts and tests, and preserve the previous state. This prevents a locally convenient modification from inheriting evidence that no longer applies.

Give unresolved rows a decision category: must close before order, before shipment, before flight, or accepted as a documented limitation. Require a named approver for the last category and state what activity is prohibited until the fact is available. This turns uncertainty into managed scope rather than allowing it to migrate unnoticed between engineering, commercial and operations teams over time.

Review category assignments with the people who carry the operational consequence. Engineering may understand the missing value, while a dispatcher, technician or customer manager sees a different failure path. Record the rationale and verify that the restriction appears in the documents used at the decision point, not only in a procurement spreadsheet for every operating shift.

Read the UG35 versus UG62 integration-scale comparison and the heavy-lift composite-support guide. Then compare appropriate classes in the VTOL and fixed-wing collection. Use the same rule for each: approved facts stay fixed, unknowns stay visible and configuration evidence supports the decision.

Approve the proposed UG62 mission only when the mass statement is complete, interfaces are controlled, conditional performance is handled honestly, support responsibilities are assigned and acceptance evidence is reviewable. If a critical field cannot be closed, reduce the requirement, select another class or record the limitation. The wrong action is to fill the gap with a plausible but unsupported number.