The answer-first takeaway is that the UG25 value of up to 240 minutes is explicitly a no-load flight-time condition. It is not a promise of mapping endurance with a sensor, not a range figure, not a mapped-area estimate, not a reserve policy and not a daily productivity guarantee. A buyer should preserve the qualifier and turn the number into a structured request for evidence from the exact loaded configuration.

This distinction improves both safety and commercial clarity. The approved record can screen a platform class, while the evidence request defines what must be shown before the buyer plans a project. The request should connect payload identity, installation, mission profile, environment, transitions, reserve, data quality, recovery and acceptance. Unknowns remain visible until the supplier or a controlled buyer test closes them.

Define the Deliverable Before Endurance

Write the mapping output, area, terrain, surface conditions, coordinate reference, control approach, required products, delivery deadline, quality review and acceptance owner. A flight-time discussion has little meaning until the buyer knows what data must be captured and how success will be judged. The deliverable determines sensor, overlap, speed, altitude, turns, checkpoints and possible repeats.

The ASPRS Positional Accuracy Standards provide professional context for defining and reporting geospatial accuracy. They do not certify UG25, prescribe a mission or guarantee results. The buyer must still create the survey design, reference evidence, processing record and quality review. Aircraft endurance should support that controlled workflow, not replace it.

Quote the Product Fact Exactly

The current UG25 product record lists a 2.5 kg maximum payload, up to 240 minutes of no-load flight time, a 20 m/s cruise speed and a 4800 m maximum service ceiling. Each field keeps its own meaning. The payload value does not prove sensor integration, the cruise value is not necessarily survey speed, and service ceiling is not operating authorization.

Place the approved endurance statement in the evidence request as a source fact, then add a separate row for the proposed loaded mission. Do not edit the qualifier to make the brief shorter. If a stakeholder asks for range or coverage, show the assumptions required to calculate an internal planning scenario and label the result as unvalidated until a controlled configuration exercise supports it.

Freeze the Loaded Configuration

Identify the aircraft, sensor, mount, fasteners, vibration-control elements, power conversion, cables, connectors, antennas, storage media, protective parts and software or firmware states when relevant. Assign a configuration-release identity. A supplier response that mentions only the sensor model does not close the configuration because accessories and installation details can change mass, power, drag, data and maintenance behavior.

Request the applicable installation and inspection evidence. Ask who approves the configuration, how technicians verify it before flight, what changes invalidate previous evidence and which records must accompany removal and reinstall. Loaded-endurance evidence is only reusable when the buyer can confirm that the tested configuration matches the delivered and operated configuration.

Describe the Mission Profile

Record vertical transitions, climb, planned survey speed, turns, route length, line spacing, altitude, reserve, loiter or hold assumptions, approach, recovery and contingency behavior. Include the ground sequence that affects launch timing. Do not simplify the request to one continuous cruise segment if the real mission contains repeated turns, terrain response or constrained work windows.

State whether the exercise is intended to show one route, a repeatable cycle, a reserve decision or data-quality completion. Use one primary objective and record secondary observations separately. Trying to prove every commercial claim in one demonstration usually produces ambiguous evidence and incentives to ignore deviations.

Record the Environment Without Inventing Limits

Capture site elevation, temperature, wind observations, launch-surface condition and other relevant conditions from approved instruments or sources. Do not infer environmental suitability from the endurance number. Request supplier-confirmed operating and storage instructions for the delivered configuration, and define stop conditions within the buyer's safety and authorization framework.

If the evidence will be compared across days, preserve conditions and differences. A stronger result is not automatically caused by the aircraft when payload, route, crew, weather or configuration changed. The record should allow a reviewer to decide whether two runs are comparable or whether a new exercise is required.

Build a Reserve Policy Separately

The buyer should define dispatch and recovery margins from its operating procedures, applicable authorization, site risks and approved product guidance. Do not subtract an arbitrary percentage from the no-load figure and call the result safe endurance. The evidence request should ask how the proposed configuration indicates remaining energy or fuel state as applicable and how operators make a conservative recovery decision.

Exercise the decision path. Include a shortened route, unexpected hold, data-quality repeat or site change. Verify that the team recognizes the trigger, preserves data and reaches a clear recover, pause or replan outcome. An endurance figure is operationally useful only when the crew can connect it to a controlled decision before margin is consumed.

Measure Data Completion, Not Air Time Alone

Reconcile expected files, image count, logs, timestamps and storage media after recovery. Run agreed field checks and record whether the dataset can proceed to processing. If a quality issue requires a repeat, preserve the reason and affected area. A long flight that produces incomplete or untraceable data does not prove useful mapping endurance.

Link the dataset to aircraft and payload identity, configuration release, mission plan, operator and processing handoff. The evidence package should show whether the route was completed and whether the output met the defined checks. This allows procurement to separate airborne duration from mission success.

Request Evidence in a Reviewable Format

Ask for the configuration list, mission profile, environmental record, preflight confirmation, takeoff and recovery times, reserve state or applicable indication, raw logs, data reconciliation, discrepancy record and post-flight inspection. State which files the buyer must control and which can be supplied. Avoid a summary table without underlying identities and conditions.

Submit the request through the UNITED UAV configuration inquiry with the exact sensor and project assumptions. Ask which evidence already exists, which requires a proposed configuration test and which fact remains unavailable. A responsible response may leave fields open. That is more useful than a confident but unsupported coverage estimate.

Run a Controlled Acceptance Exercise

Freeze the acceptance criteria before the exercise. Confirm configuration identity, mission plan, site controls, crew roles, start conditions, stop conditions, required data, reserve decision and post-flight inspection. Record deviations as they occur. Do not extend the mission merely to approach a headline value; test the operating case the buyer intends to approve.

Review the result with engineering, operations, mapping and commercial owners. One group may accept a data outcome while another identifies an unresolved transport, maintenance or reserve dependency. Close or explicitly accept each issue. Re-run only the evidence chain affected by a controlled change.

Turn the Result Into a Procurement Limit

The approved plan should state the exact configuration, mission assumptions, validated route or cycle, reserve decision, environmental record, support needs and review triggers. It should not generalize one result to all payloads or projects. If the sensor, mount, route, site, software, instructions or acceptance requirement changes, decide which evidence must be repeated.

Use Evidence to Set Commercial Expectations

Translate the accepted mission case into a proposal boundary. State the validated configuration and assumptions, then distinguish them from optional scenarios that still require review. Sales, project and operations teams should use the same language. This prevents a cautious engineering result from becoming an unconditional coverage promise when it reaches a customer-facing document.

Record the consequence of incomplete evidence in the schedule and price. A pending loaded-configuration exercise may require a later commitment point, a conservative route plan or an alternative platform review. Making that dependency visible is not a weakness. It gives the customer and supplier a realistic path to close the mission case before field delivery is at risk.

After acceptance, sample completed missions against the controlled configuration and data checklist. This is not a performance-marketing program; it is a way to detect drift in payload identity, records or planning assumptions. Escalate deviations through change control and avoid rewriting the original product fact to match a local observation.

Keep the exercise record with the procurement decision and customer proposal boundary. When a new project asks for more area, a different sensor or a shorter window, begin by comparing its assumptions with the accepted case. Reuse only evidence that remains applicable; route the rest through a new configuration review. This protects both operational planning and honest sales language.

Read the UG21 versus UG25 verified-fact comparison and the UG32 versus UG39 workflow-evidence guide for related procurement controls. Then compare appropriate aircraft in the VTOL and fixed-wing collection. Keep every commercial conclusion tied to an approved fact or a configuration-specific acceptance record.

The 240-minute no-load value remains useful when it is used honestly. It identifies a product-class screening fact and reveals the next question: what evidence supports the proposed loaded mapping mission? A buyer who asks that question can plan reserves, data checks and acceptance responsibly. A buyer who turns the number directly into range or productivity creates certainty that the current source does not provide.