Before Buying a Second UVH2: Calculate the Inspection Work Your First Aircraft Can Actually Deliver
By UNITED UAV Official
A flight-time specification tells an inspection operator very little about how many useful observations will reach a client before the crew leaves the site. The missing quantities are usually on the ground: how long the team takes to prepare the next sortie, how batteries move through cooling and charging, how many recorded observations survive review, and whether the analyst can keep up with collection.
For a small inspection business, these quantities can change the next purchase. A second aircraft may increase collection capacity, but additional batteries, an adequately supplied charging station, or a dedicated reviewer may remove the actual constraint at lower cost. The useful comparison is accepted inspection output per working hour, measured across the entire operation.
This article uses the UNITED UAV UVH2 complete aircraft as the product example. Its current listing describes a fixed-wing VTOL platform with a K8T-V2 visible-light and thermal gimbal, up to 60 minutes of flight time, and up to 15 km of video transmission. Those are published limits with different meanings. Mission-specific inspection duration, operating radius and daily output require their own evidence.
Every number in the worked scenarios below is a hypothetical planning input. None is a UVH2 flight-test result, charging specification, recommended reserve, or promised production rate. Replace the examples with measurements from the actual configuration and procedures before making a purchasing decision.
- Define the output that someone will accept
Start with the client's receiving task. A roof inspector might need a location, a visible context image, a thermal observation where relevant, and an explanation of whether closer examination is required. A site survey might require an agreed image dataset and a reconstruction checked against independent survey measurements. Counting both jobs as one hour of drone work conceals different processing and acceptance requirements.
Write a short acceptance definition before calculating throughput. It should identify the asset or area, required views, file format, location information, review responsibility, and the condition that makes an observation unusable. A record with an obscured subject or an uncertain asset identity should not count as completed work merely because a file exists.
Keep the output unit stable throughout the model. Use accepted assets per hour for an asset inspection, accepted route segments for a corridor task, or accepted hectares for a mapping deliverable whose accuracy requirements are already established. Avoid moving between these units halfway through a comparison. Ten minutes of useful thermal observation cannot be converted into hectares without a verified acquisition geometry and a defined deliverable.
For the UVH2, the dual-sensor arrangement makes it especially useful to distinguish a recorded view from an accepted finding. Thermal contrast may justify a follow-up observation; a bright region alone does not establish a defect. Quantitative temperature reporting requires separately documented radiometric capability and an appropriate measurement procedure. FLIR's technical guidance explains that thermal products offer different radiometric capabilities and that temperature interpretation depends on factors including emissivity, reflections, and atmosphere.
- Split a sortie into time that serves different purposes
Use a sortie worksheet with separate entries for departure and transition, outbound transit, collection, inbound transit, recovery, and the allowance required by the actual operating plan. Record the installed battery and payload configuration beside the worksheet. A duration measured with a different package should not silently become the planning value for your aircraft.
Consider an illustrative 45-minute airborne plan. Allocate four minutes to outbound transit, four to inbound transit, three to departure, transitions and recovery combined, and five to the planning allowance. This leaves 29 minutes for the collection task. The five-minute placeholder is only an arithmetic input; the real reserve and recovery criteria must come from the aircraft documentation and the approved operation.
This distinction exposes a common purchasing mistake. Applying a collection rate to all 45 minutes would overstate the available collection time by more than half relative to the 29-minute task segment. Applying that rate to the advertised 60-minute ceiling would widen the error further. A fleet calculation should show where each minute goes rather than hiding transit and recovery inside an optimistic average.
The UVH2's video-link declaration belongs in a separate worksheet. A video transmission distance does not define return energy, terrain clearance, link availability along a route, or the authority to fly that route. Obtain the conditions behind the link specification and evaluate the actual deployment. An equipment buyer should request a mission profile, not infer one from a distance on a product page.
- Measure the ground interval from landing to readiness
Suppose the example aircraft spends eight minutes between one landing and the next departure. The complete operating cycle is then 45 plus eight, or 53 minutes. That yields approximately 1.13 sorties per hour under continuous, unconstrained operation.
The eight-minute interval must have a clear definition. Does it include moving to a safe service location, inspecting the aircraft, changing the battery, verifying storage, loading the next mission, and repeating required checks? If those activities occur outside the stopwatch, the measured turnaround is incomplete. Record delays as they happen rather than removing inconvenient events from the average.
Some ground tasks can be prepared during the previous sortie by a separate, available crew member. Others require the aircraft to be landed and secured. Draw those dependencies explicitly. Do not shorten the model by assigning the same person simultaneous flying, battery handling and data-review duties. The staffing and supervision requirements of the actual operation determine which tasks may overlap.
Distinguish the median ground interval from a conservative planning interval. An operation that usually takes eight minutes but occasionally takes twenty may need enough buffer to protect a client appointment or daylight window. Preserve the reason for each delay: inspection finding, missing file, software restart, access restriction, or ordinary servicing. Different delays need different remedies.
- Apply an acceptance yield to collected work
Flight logs show aircraft activity. They do not show whether the client received usable work. Add an acceptance yield to the model, defined for the same output unit and review criteria used at the beginning.
For the hypothetical scenario, assume that review accepts 85 percent of collection time as productive equivalent work. The 29-minute collection segment becomes 24.65 accepted-equivalent minutes per sortie. Dividing by the 53-minute cycle and multiplying by 60 gives approximately 27.9 accepted-equivalent minutes per operating hour.
This time-based yield is a simplified proxy. An asset-based business should calculate accepted assets divided by attempted assets, and should also record repeat-flight time. It is possible to have a high acceptance fraction while repeatedly collecting the same easy asset. Coverage completeness, duplicate observations and unresolved assets therefore need their own counts.
Separate first-pass acceptance from final acceptance after rework. If an analyst rejects five records and the crew returns later to collect them again, the second visit consumes real travel, setup and flight time. Crediting the corrected records without charging the rework to the job makes the operation appear more productive than it is.
Also keep causes specific. Blur, missing coverage, uncertain location, glare and ambiguous thermal observations are different problems. Buying more aircraft does little to improve output if each sortie repeats the same acquisition error. A small change in collection design may be more valuable than additional airborne capacity.
- Size battery inventory from the whole battery cycle
Battery count is a queueing problem as well as an energy problem. Track when each pack is installed, removed, released for charging, finished charging, inspected, and available for the next dispatch. Follow the approved battery and charger procedures for every stage; the model does not supply charging settings or cooling limits.
For a simple illustration, keep the 45-minute flight and assume that the complete post-flight process takes another 130 minutes before that pack is ready again. A battery is unavailable for 175 minutes from dispatch to its next ready state. With departures spaced 53 minutes apart, the arithmetic lower bound is the ceiling of 175 divided by 53: four packs in rotation.
Three packs would return the first pack to the dispatch position after 159 minutes, before the assumed 175-minute readiness time. Four packs provide 212 minutes between successive uses of the same pack, leaving 37 minutes of nominal margin. This is an inventory calculation using invented values, not a recommendation to buy four UVH2 batteries.
The lower bound assumes the charging process can actually sustain the required flow. If packs wait for a charger, readiness time increases and the original calculation no longer describes the operation. It also assumes every pack remains serviceable. A sensible procurement comparison should show what happens when one pack is removed from rotation and should price the reserve separately from the minimum working inventory.
- Check charging capacity before adding more packs
More batteries can postpone a queue without solving a sustained charging bottleneck. Calculate the charger service demand per hour and compare it with the available, independently usable charging channels and power supply.
Suppose, only for illustration, that each sortie requires 70 minutes of charger-channel occupancy after the pack becomes eligible for charging. At one sortie every 53 minutes, demand is about 79 charger-minutes per hour. One channel supplies only 60 channel-minutes per hour. The queue therefore grows during sustained operation even if the team begins the day with many charged packs.
Two channels have enough nominal time capacity for that example, provided the electrical supply, equipment ratings, environmental conditions and approved procedures allow the assumed service. Nominal channel count alone is insufficient. A multi-port device may share power between ports; a field power source may not support every connected charger at full demand.
If two adequately staffed aircraft produce a combined departure every 26.5 minutes, the same hypothetical 70-minute charge service requires roughly 159 charger-minutes per hour. Three independent channels provide a nominal 180. The extra aircraft has changed the power and charging requirement, not merely the battery shopping list.
For a short job, initial charged inventory may cover the entire visit without any recharge becoming necessary. For a long shift, steady-state charging capacity matters. Model both cases. Distinguish the transient benefit of starting with charged packs from the sustainable rate after the initial inventory has circulated.
- Test whether the receiving team can keep up
Assume a reviewer needs 31 minutes to transfer, examine and classify the files from each sortie. A single reviewer can process about 1.94 sorties per hour. The example aircraft generates 1.13, so review capacity is sufficient for one aircraft if the reviewer has no competing duties.
Two independent aircraft could nominally generate 2.26 sorties per hour. The reviewer would then become the constraint. Multiplying the review capacity by the example's 24.65 accepted-equivalent minutes per sortie gives approximately 47.7 accepted-equivalent minutes per hour, below the unconstrained two-aircraft figure of about 55.8.
These calculations assume sufficient pilots and other staff for the proposed concurrent operations. They do not suggest that one person should fly two aircraft or combine duties that the operation requires to remain separate. The staffing plan is an input to the capacity model, and additional staff cost belongs in the purchase comparison.
An overnight processing backlog may be acceptable for one client and unacceptable for another. If the contract requires same-day confirmation before the crew leaves, a delayed review can cause a second site visit. Bring the receiving team's deadline into the model. The collection system and the review system must meet the same handover requirement.
- Price accepted output and keep the comparison fair
Use cost per accepted unit as the purchasing metric. Include crew time, travel allocated to the job, aircraft ownership allocation, battery replacement allowance, charging or field power, software, data review, and expected rework. State the utilization assumption behind every hourly ownership cost. An aircraft used occasionally has a different cost profile from one used throughout the working week.
As a deliberately artificial example, suppose a one-aircraft operation costs 150 accounting units per hour and completes six accepted assets per hour. Its cost is 25 units per accepted asset. A two-aircraft operation costing 230 units per hour and producing eight accepted assets costs 28.75 units per asset. Higher output has not automatically produced lower unit cost.
A different job might justify the higher cost because it avoids another mobilization or meets a deadline that the first option cannot. Keep those benefits explicit. Compare a second aircraft with a second pilot, more charging capacity, a reviewer, and a spare-aircraft availability plan using the same job requirements. Do not assign the second aircraft revenue that the customer has not actually requested.
For mapping work, accepted output also depends on the deliverable specification. PIX4D provides a ground sampling distance calculator to help plan image sampling. That is one input to a workflow that also needs suitable overlap, georeferencing and independent accuracy checks. A small pixel size or a clear-looking model does not establish that a client's positional tolerance has been achieved. Until the workflow is demonstrated, keep a measured-area production promise out of the financial model.
- Build a short field study before committing to fleet expansion
A useful evaluation records the complete operating chain across representative sorties. Capture configuration, mission start and finish, task time, ground interval, battery identifiers, charging occupancy, review duration, first-pass acceptance, rework, and the eventual client handover. Record weather and site conditions without treating a single day as a complete operating envelope.
Use the actual UVH2 package offered in the quotation. Confirm the aircraft, gimbal, controller, batteries, charger, required software and accessories individually. A specification for one component does not establish the behavior of the assembled package. Request original output files and enough configuration information for the receiving team to repeat its review.
After the study, compare at least three scenarios: the measured one-aircraft arrangement; the same aircraft with the identified ground constraint removed; and a properly staffed two-aircraft arrangement with matching charging and review capacity. Recalculate when the site has longer transit, fewer service locations, or a more demanding acceptance standard.
The second aircraft becomes a well-supported purchase when it addresses an observed constraint or a defined availability requirement. If batteries wait for charging or files wait for review, that evidence points elsewhere. The purchasing conversation becomes more productive once the team can say which resource is limiting accepted output, by how much, and under which conditions.
For a UVH2 configuration discussion, provide the route length or site layout, intended visible and thermal deliverables, required handover time, crew arrangement and field-power constraints. The current complete-aircraft listing is here:
store.uniteduav.com/products/u…
Technical context used for the imaging distinctions:
PIX4D, Ground sampling distance calculator: support.pix4d.com/hc/en-us/art…
Teledyne FLIR OEM, Choosing the Right Thermal Imager: oem.flir.com/learn/discover/ch…
For teams already operating compact VTOL aircraft: which constraint has most often reduced your accepted daily output—airborne time, battery turnaround, access to the site, or review capacity?
