A heavy-lift acceptance test is useful only when its configuration and conditions match the contract question. Maximum payload, endurance with a stated load, takeoff weight, reserve, environment, route and mission equipment describe different boundaries. Combining the largest number from each line into one expectation creates a promise that was never documented. The buyer should convert each commercial statement into a condition-complete evidence requirement before the order is released.

Build an acceptance matrix with one row per claim or required capability. Record the contract wording, aircraft and payload configuration, measurement method, environmental limits, start and end states, reserve definition, test location, responsible witnesses, raw evidence, pass rule and discrepancy route. Unknown tolerances and procedures remain negotiation items; they are not filled by the test team on delivery day.

Separate the Contract Claims First

List payload capacity, mission endurance, takeoff weight, route performance, launch and recovery, payload operation, communications, data handoff, transportability, training and documentation as separate acceptance topics. A single demonstration flight may contribute evidence to several rows, but it should not cause one successful outcome to stand in for an unrelated requirement.

For every statement, ask what conditions are attached and what conditions are absent. Payload may refer to capacity, installed mission load or delivered cargo. Endurance may be no-load, with a stated load, under a particular profile or before a reserve. If the contract is ambiguous, close the ambiguity before the acceptance procedure is approved.

Create a Configuration Baseline for the Test

Identify the aircraft, propulsion configuration, software and firmware where relevant, payload, mounting, ground station, antennas, batteries or fuel state, telemetry, environmental instruments and support equipment. Photograph the agreed state and preserve the release record. A later component or setting change should trigger an applicability decision rather than silently becoming part of the test.

The baseline should also name what is excluded. Optional equipment, temporary ballast, development telemetry or substitute ground gear can change interpretation. Record who owns each item and whether it will be delivered with the production configuration. Acceptance evidence should represent what the buyer will operate, not an undocumented test-only arrangement.

Use UG82 Facts Without Combining Their Conditions

The UG82 Heavy-Lift VTOL Fixed-Wing Drone controlled record lists a 50 kg payload capacity and a maximum takeoff weight of 220 kg. It separately lists 12 hours of endurance with an 8 kg payload. The endurance condition must remain attached; it must not be presented as a 12-hour result at the 50 kg payload capacity.

The record describes hybrid electric VTOL and EFI fixed-wing cruise. That identity is relevant to the test baseline, logistics and support discussion, but it does not supply a universal acceptance procedure. Lead time, warranty obligations, test tolerances and delivery performance are not approved facts in the controlled record. Put those commercial terms in the contract if they matter.

Define the Payload Evidence Chain

Describe the payload object, actual mass, center-of-gravity evidence, mounting arrangement, power and data interfaces, restraint, release authority and intended mission function. The buyer's qualified personnel and applicable documentation determine the technical procedure. The acceptance record should show that the tested payload is the contracted payload configuration, not merely that an equivalent mass was available.

If ballast is used for a limited airframe demonstration, label that scope clearly. Ballast may help answer a mass-related question but cannot prove payload operation, electromagnetic compatibility, data quality, thermal behavior or mission workflow. Create separate rows for those outcomes and decide which must be closed before shipment, before field deployment or during integration.

Define Endurance Start, End and Reserve

Write when the endurance clock starts, when it stops, which mission phases are included and how reserve is treated. Record initial energy or fuel state, payload condition, route profile, altitude basis, environmental window, operator actions and any hold or interruption. Without these details, two accurate time measurements may answer different questions.

Do not make the pass rule a simple comparison with a marketing maximum. Tie it to the contract condition and measurement uncertainty. Decide how incomplete data, a safety stop, a weather change or a configuration discrepancy affects the result. A stop taken for safety should preserve evidence and trigger a controlled review, not create pressure to continue for the sake of a number.

Plan Instrument and Time Evidence

Identify which instruments support payload mass, environmental conditions, time, position, energy or fuel state and other agreed parameters. Record identity, applicability, status and data custody. The acceptance plan should specify which evidence is authoritative when a handwritten note, telemetry record and external instrument disagree.

Synchronize time sources or document the offset before the test. Preserve raw evidence and create a read-only package for review. Do not rely only on screenshots or a summary spreadsheet. A reviewer should be able to reconstruct the start, key events, end state and any interruption without asking the test pilot to remember what happened.

Use Witness Roles Instead of a Crowd

Name the test director, flight authority, instrumentation owner, configuration owner, buyer witness, supplier witness, safety stop authority and acceptance decision maker. One person may hold more than one role, but the decision boundaries should remain explicit. Observers without a task can distract the team and create conflicting informal interpretations.

Before the test, review what each witness must see and sign. Some evidence may be verified from records after the event; other evidence may require direct observation. Define how a remote witness receives live or recorded evidence and how questions are captured without interrupting safe operation.

Handle Discrepancies by Scope

A discrepancy record should identify the affected acceptance row, configuration, evidence, immediate action, technical owner, commercial owner and closure requirement. Do not label the entire aircraft failed when the issue is an unreadable instrument record, and do not label the aircraft accepted when an affected requirement remains open. Scope supports proportionate recovery.

When corrective action changes hardware, software, configuration or procedure, determine which evidence must be repeated. Preserve the original result and link the retest. Repeating only the shortest convenient demonstration can leave dependent requirements unsupported. The acceptance authority should approve the retest scope before work begins.

Hold a Test-Readiness Review

Before equipment is committed, verify that the approved procedure, safe location, permits, weather window, configuration release, payload evidence, instruments, witnesses, data storage and stop authority are available. Mark each item ready, conditionally ready or blocked and require an owner for every condition. A calendar invitation is not evidence that the test can begin.

Use the review to identify buyer-furnished items and dependencies that could invalidate the result. If the specified payload, instrument or witness is unavailable, decide whether the event is postponed or formally changed. Do not let travel cost or delivery pressure turn a different demonstration into an acceptance test with the original label.

Distinguish Demonstration From Acceptance

A demonstration can introduce the aircraft, train observers and reduce uncertainty without closing a contractual requirement. Label its purpose, configuration and limitations before it begins. Evidence may later support acceptance only if the approved authority confirms that the conditions and method are applicable.

Keep demonstration notes in the project record, but prevent them from being copied into the completed acceptance matrix without review. This distinction allows useful learning while protecting the contract from optimistic reinterpretation.

Connect Acceptance to Delivery Documents

The final package should include configuration identity, agreed procedure, completed matrix, raw evidence locations, instrument records, witness signatures, discrepancies, concessions, retest links, training status, delivered-item register and open actions. Separate a commercial concession from technical evidence. Accepting an open item under a business agreement does not make the missing evidence appear.

Use the UNITED UAV contact page to request configuration-specific product and support details. Share the payload object, intended mission, required endurance condition, reserve rule, site constraints and the buyer's proposed evidence package. This lets the discussion focus on reproducible conditions rather than on a maximum figure without context.

Keep Regulatory Approval Separate

The EASA specific-category page provides official risk-based context for applicable civil-drone operations within that framework. It does not define the UG82 commercial acceptance test or authorize a mission. Operational approval, airworthiness or maintenance decisions, contract acceptance and customer deliverable acceptance must remain separate evidence chains.

Link Heavy-Lift Acceptance to Adjacent Controls

Strong acceptance evidence depends on configuration ownership and maintainable staffing. Continue with Heavy-Sensor VTOL Acceptance and Hybrid VTOL Fleet Readiness. They help prevent a passed delivery demonstration from being mistaken for payload validation or sustainable fleet readiness.

Convert the Matrix Into Purchase Language

Attach the condition-complete matrix to the purchase agreement or statement of work. Name the evidence due before test readiness, the buyer-furnished items, permitted substitutions, stop conditions, retest responsibility, discrepancy timing, acceptance authority and required archive. Review the matrix with engineering, operations, commercial and safety owners before signatures make an ambiguity expensive.

Compare platform classes in the UNITED UAV VTOL and fixed-wing drone collection. For UG82, ask for a configuration review that preserves the difference between payload capacity and the stated endurance condition. A disciplined contract does not demand that every maximum occur together; it demands evidence for the mission condition the buyer actually needs.