The UG62 approved product record lists up to 16 hours of no-load endurance. That conditional value is not a promise of loaded endurance, daily productivity, turnaround time, uptime, or multi-day campaign availability. A buyer should treat it as the start of an evidence request. Build the availability plan around the actual aircraft and payload configuration, required inspections, replenishment, crew handoffs, spares, support, recovery conditions, operating authorization, and customer deliverable.

Availability means the aircraft and supporting system are ready for an authorized mission when the program needs them, with the required configuration, crew, evidence, and ground resources. It is not simply the percentage of a day left after subtracting a headline flight time. The plan must show what happens between missions, what can block release, who resolves discrepancies, and what evidence supports each assumption.

Define the Campaign and the Availability Decision

State the campaign duration, operating locations, expected mission types, proposed payload configurations, data or delivery objective, crew model, mobilization pattern, and decision being supported. Distinguish screening, demonstration, pilot operation, and contracted service. An early planning estimate may use open assumptions; a committed operating plan needs controlled evidence and approval.

Define available, conditionally available, unavailable, awaiting evidence, and recovery states for the buyer's workflow. Write which authority assigns each state. A technically intact aircraft may still be unavailable because the required payload, crew, documents, access, authorization, fuel or power support, data capacity, or recovery site is missing. A grounded aircraft may be correctly unavailable while a discrepancy is reviewed.

Lock the Configuration Before Using Endurance

Record the aircraft identity, payload and mount, supporting equipment, propulsion and power arrangement, software or firmware references when applicable, communications arrangement, data storage, environmental assumptions, and mission profile. Ask the supplier which documentation applies to that configuration. Do not combine the 40 kg maximum payload with the up-to 16-hour no-load endurance value to create a loaded mission claim.

Request configuration-specific evidence for the proposed use. The evidence should identify conditions, test method, configuration, observed result, limitations, and responsible source. Keep published facts, supplier configuration statements, buyer calculations, field observations, and accepted operating limits in separate fields. This avoids turning a useful product-page value into an unsupported schedule promise.

Map the Ground Cycle

List every activity between recovery and the next authorized release. Relevant questions may include safing, inspection, discrepancy review, data transfer, data validation, payload removal or change, replenishment, cleaning, configuration verification, log review, maintenance action, documentation, crew briefing, site release, and approval. The actual sequence should come from supplier documentation and the operator's approved procedures.

For each task, record trigger, qualified role, required tools or facilities, inputs, output evidence, typical planning allowance if supported, blocking defects, and release authority. Do not invent maintenance intervals or turnaround durations. If no current evidence exists, mark the duration unknown and identify the trial, supplier answer, or operating experience needed to support it.

Build a Replenishment Dependency Map

Identify consumables, fuel or power support, payload supplies, data media, cleaning materials, packaging, environmental controls, and site services relevant to the proposed campaign. This is a question framework, not a statement about UG62 requirements. Ask which items are approved, how they are stored and handled, who controls them, what quality or traceability record is needed, and what happens when the normal source is unavailable.

Link replenishment to logistics lead time, site access, safe storage, transport, and responsible personnel. Avoid assuming that a remote site can replicate a factory or main-base process. If the campaign depends on a specialized resource, make that dependency visible in the availability model and define the decision point for resupply, substitution review, relocation, or stand-down.

Create a Spares Strategy From Failure Consequence

Do not copy a generic spare-parts list. Ask the supplier and maintenance authority which items are replaceable at the campaign site, which require a higher maintenance level, what tools and skills are needed, how configuration is controlled, and what evidence closes the action. Rank candidate spares by mission consequence, expected sourcing difficulty, storage constraints, shelf or service considerations when documented, and ability to install lawfully and safely.

Separate aircraft spares, payload spares, ground-equipment spares, communications components, power or propulsion support items, tools, and documentation. Record quantity basis, location, custody, reorder trigger, approved substitute policy, and shipment route. An unverified spare that cannot be traced or installed by qualified personnel should not be counted as recovered availability.

Define the Support Escalation Path

Ask for the support channel, service hours, language, evidence needed to open a case, response target if offered, diagnostic boundaries, escalation path, parts decision, remote-access conditions, and responsibility for shipping or site access. Distinguish a contractual commitment from an operating target. Record which aircraft and configuration the support applies to and when the support period begins.

Prepare a reproducible support packet with configuration identity, issue description, first observed condition, relevant logs or files, actions already taken, current state, requested decision, and safety or schedule effect. Do not ask a field team to guess a root cause. Do not treat informal advice as authorization for technical work. Supplier documentation, qualified personnel, operator procedures, and local requirements control the action.

Plan Recovery Without Promising Uptime

For each blocking condition, define detect, contain, document, escalate, decide, act, verify, and release steps. State who may return the aircraft or supporting system to service. Define what can be resolved at the operating site, what requires another location, and what evidence closes the recovery. Keep aircraft recovery, payload recovery, data recovery, and schedule recovery as separate concepts.

The availability model should allow an honest unavailable state. Pressure to protect a percentage can cause teams to shorten inspection, accept an uncertain configuration, or hide an open discrepancy. A controlled stand-down with a clear owner and recovery plan is better evidence than an attractive utilization number built on undocumented risk.

Use UG62 Product Facts With Boundaries

The current UG62 product page describes a hybrid VTOL drone for heavy-payload, long-endurance missions. The approved record lists a 40 kg maximum payload, up to 16 hours of no-load endurance, a recommended maximum takeoff weight of no more than 135 kg, and fuel-powered fixed-wing cruise. Each qualifier and condition matters.

Those facts do not establish loaded endurance, fuel consumption, maintenance intervals, battery configuration, inspection schedule, turnaround time, support response, spares requirement, uptime, or availability percentage. Keep those fields open until current supplier evidence, qualified review, or representative operating data supports them.

Run a Representative Availability Trial

• Freeze the proposed aircraft and payload configuration.
• Define mission and ground-cycle objectives.
• Brief stop and recovery conditions.
• Time only tasks performed under controlled conditions.
• Record delays, queues, defects, and missing resources.
• Preserve the evidence packet and configuration identity.
• Separate observed results from future estimates.
• Review what remains untested before scaling the model.

A trial should be conservative and allowed to fail safely. It should not chase the published maximum. Repeat only when the reason and changed condition are recorded. Use the result to improve questions and planning ranges, not to guarantee every future site or payload.

Connect Availability to Procurement and Release

Use the same-day UG25 procurement quote review to make spares and support scope explicit before purchase. Use the same-day UG82 payload release record to ensure a campaign schedule never overrides load identity, mass evidence, configuration, or sortie authority.

Close the availability plan with supported assumptions, ranges where appropriate, unknowns, owners, evidence references, and review triggers. Reopen it when payload, configuration, location, crew, mission profile, supplier documentation, support terms, or recovery resources change. Buyers can browse the VTOL and fixed-wing drone collection for current public product paths. Use the UNITED UAV contact page for configuration-specific evidence and quotation questions, keeping published facts, proposals, tests, and unknowns clearly separated.

Use Scenarios Instead of One Availability Percentage

Build a conservative base scenario, a disrupted scenario, and a recovery scenario from documented assumptions. Show configuration, mission demand, site resources, crew pattern, ground tasks, support dependency, spare position, and unresolved evidence. Do not attach a probability or availability percentage unless current data and the buyer's method support it. The scenarios are decision aids, not promises.

Ask what happens when data transfer takes longer, a payload discrepancy remains open, replenishment is delayed, the qualified technician is unavailable, or the normal support channel cannot respond. Record the decision owner and recovery option for each case. This exposes single points of dependence before the campaign rather than after the aircraft is waiting on the ground.

Review Availability After Every Operating Block

At the end of a controlled block, reconcile planned missions, authorized missions, completed captures, accepted deliverables, ground-cycle evidence, discrepancies, unavailable periods, spares use, and support cases. Explain the reason for each state without forcing every delay into an aircraft category. Update planning assumptions only when the record supports the change, and preserve the earlier version so improvement or deterioration can be understood.

Assign Ownership to Every Planning Unknown

An availability model should never hide unknown inputs inside a default value. List each missing duration, interval, resource, response, compatibility, or recovery assumption; identify the evidence source needed, owner, due date, and decision affected. If the answer does not arrive, state what conservative plan or stop condition applies. This turns uncertainty into managed work and prevents a convenient estimate from becoming an operating promise.