Plan return to service before a fuel-powered VTOL enters seasonal storage. The team should know which instructions control preservation, what evidence will be recorded, who monitors the stored condition, what changes trigger review and what must be verified before the next campaign. Storage without an exit plan converts known aircraft state into future uncertainty.

This article does not prescribe maintenance intervals, fuel handling or engine procedures. Those details must come from the applicable manufacturer documentation and qualified personnel for the exact configuration. The procurement and operations task is to make the evidence, ownership and campaign decisions visible so technical instructions are actually followed.

Define the Storage State

Record the aircraft identity, configuration, total condition known at shutdown, open discrepancies, installed payload, removed equipment, software or record versions, location, environmental controls and custody owner. A photograph of an aircraft in a hangar is not a storage record. The goal is to let a future reviewer understand what entered storage and why.

Separate serviceable, deferred, quarantined and unresolved conditions. Do not use storage as a place to hide work that missed the end of a campaign. If a discrepancy will be addressed later, record the required evidence, owner and due decision. Otherwise the next team may mistake an untouched aircraft for a ready one.

Use Manufacturer Instructions as the Technical Baseline

Identify the documents and revisions that apply to the airframe, propulsion system, power sources, payload, ground equipment and storage environment. Assign a qualified owner to interpret them. The storage plan can schedule and document the work, but it should not rewrite technical instructions or create a generic procedure from experience with another model.

When an instruction is unavailable or applicability is uncertain, stop and obtain a configuration-specific answer. Record the question and response with the aircraft file. An informal note may help a conversation, but a return-to-service decision requires controlled evidence that the intended team can retrieve.

How the UG73 Relates to the Planning Case

The UG73 Fuel-Powered Fixed Wing VTOL Drone for Surveying, Property Mapping and Route Inspection is a fuel-powered compound-wing platform using a B2G390 engine in the approved product description. The record lists a 50 kg maximum effective payload and a 185 kg maximum take-off weight.

It also lists a 32 m/s cruise speed. These facts identify the product class and support a procurement discussion; they do not provide storage intervals, preservation actions or return-to-service instructions. The controlled product data contains no approved lead-time or warranty value, and this article does not manufacture either one.

Use the product page for current identity and approved public information. Ask UNITED UAV for configuration details and applicable documentation needed by the intended aircraft and campaign. Keep the response with the storage and acceptance records.

Create a Preservation Evidence Map

For each controlled condition, record the applicable instruction, work owner, date, aircraft state before work, evidence produced, independent check where required and the future verification it enables. Examples of evidence categories include identity, condition photographs, inspection results, removed-item custody, environmental records and discrepancy status. The actual technical actions remain document-controlled.

The map should answer a future question: if a reading or condition is abnormal at return to service, can the team compare it with the known storage baseline? Without that link, the crew may know that something changed but not when, why or who can approve the next action.

Manage the Storage Environment and Access

Name the person responsible for the storage location and the person responsible for aircraft technical status. Record environmental limits from the applicable instructions, monitoring method, inspection cadence and response when the condition leaves the permitted band. Do not invent universal values. A limit without a monitoring and response owner is not a control.

Control access and movement. If equipment is removed, transferred or temporarily installed elsewhere, update the configuration and custody record. If another team performs facility work near the aircraft, record any inspection required afterward. Seasonal storage often fails through ordinary handling rather than a dramatic event.

Maintain a Storage Exception Ledger

Log every departure from the planned state: environmental excursion, loss of monitoring, movement, opened packaging, removed equipment, facility work, inspection finding or document change. Record when it began, how it was detected, the aircraft or component affected, immediate protection, technical owner and required return-to-service review. The ledger should not diagnose beyond the available evidence.

Review exceptions while storage is ongoing rather than waiting for the campaign deadline. Some events may require prompt action under the applicable instructions; others may only add a verification item. The responsible technical person decides. The operations team should understand the schedule effect without converting it into unauthorized maintenance guidance.

Sequence Campaign Readiness Backward

Work backward from the first customer access date. Reserve time for document review, configuration reconciliation, approved technical work, independent checks, functional verification, controlled test activity, crew currency, payload preparation, permissions, logistics and corrective action. A single return-to-service date hides these dependencies and encourages every team to assume the aircraft becomes ready at once.

Give each gate a latest safe decision date and a consequence if it is missed. The commercial plan may reduce scope, move the first mission, assign another aircraft or stop the campaign. Making those choices early protects the technical team from pressure to compress verification. It also gives the customer a more honest schedule than a promise based on an unopened storage file.

Review Support and Material Availability

Before committing the campaign, verify which support questions remain open, which mission-stopping items are on hand, what configuration evidence is needed for replacements and who can approve field actions. Do not publish or rely on an unsupported supplier lead time. If availability is uncertain, the campaign risk should remain visible until a current configuration-specific answer is obtained.

Inspect the deployment kit as part of return-to-service readiness, not as a separate warehouse task. An aircraft can pass its technical gate while a required cable, tool, payload accessory or controlled record remains missing. Reconcile the kit against the actual mission and name the person who accepts any reduced-scope plan.

Plan the Return-to-Service Gate

Build the gate around evidence categories: complete storage record, resolved discrepancies, applicable document revisions, configuration reconciliation, required inspections and servicing, ground verification, controlled functional checks, approved test activity, mission-equipment verification and a named release decision. The exact actions and sequence must come from the applicable instructions.

Avoid combining technical release with campaign readiness. An aircraft can be technically serviceable while the crew, payload, permissions, customer deliverable or support plan remains unready. Use separate sign-offs so a commercial deadline cannot turn one completed checklist into proof for unrelated gates.

Rehearse the First Campaign Without Flying

Run a tabletop review using the planned crew. Ask them to locate the storage record, configuration baseline, open-action list, applicable documents, support route, site plan, payload evidence and release owner. Note every missing file, ambiguous version and unofficial shortcut. Correct the system before the aircraft is placed on the first job schedule.

Include one change scenario: a payload, component, document revision or mission requirement changes during storage. Walk the change through applicability review, evidence update, additional verification and release. This reveals whether the organization can distinguish stored configuration from intended campaign configuration.

Keep Regulatory Context Separate

The EASA specific-category page provides official risk-based context for applicable civil-drone operations within that framework. It does not supply UG73 maintenance instructions or return an aircraft to service. Operational authorization, technical airworthiness decisions and commercial campaign readiness must remain separate evidence chains.

Link Storage to Spares and Dispatch Planning

A sound return-to-service plan depends on known support items and a conservative mission-release rule. Read VTOL Inspection Spares Planning: Identify Mission-Stopping Parts Before Deployment and Wide-Area VTOL Mission Reserves: Turn Best-Case Endurance Into a Dispatch Rule. These controls prevent a technically prepared aircraft from entering an operationally weak campaign.

Close the Storage Record Deliberately

When return-to-service work is complete, close the storage period with a dated reconciliation. List resolved exceptions, remaining limitations, current configuration, document revisions, verification evidence and the person who accepted technical status. Preserve the original storage baseline rather than replacing it with the final state; the comparison explains what changed while the aircraft was inactive.

Hold a short review with storage, technical, operating and project owners. Identify preventable handling, documentation or scheduling problems and test the corrective action before the next storage cycle. The review should improve the control system without creating unofficial technical procedures. Manufacturer instructions remain the baseline for the actual work.

Put Lifecycle Evidence Into Procurement

Before purchase, ask which documents apply, what the buyer must supply, how preservation and return-to-service questions are handled, which records identify the configuration, and what evidence supports acceptance after a storage period. Record gaps as open procurement items rather than assuming they will be solved during the off-season.

Compare platform classes in the UNITED UAV VTOL and fixed-wing drone collection. For a UG73 review, provide the campaign calendar, storage location, custody model, payload plan, support constraints and intended return-to-service governance so lifecycle planning is part of the buying decision. Bring the open-document list to that review.