HENSYNTH electric UAV mission screening loop

A mission-shaped loop, not a sample aircraft

Electric fixed-wing UAV work in HENSYNTH follows the product loop: state the mission as numbers on Requirements, save geometry on Aircraft, Run screening, read compliance, optionally synthesize candidates. This article describes that loop for battery-powered architectures. It does not quote range or endurance for a fictional vehicle — your project's run report holds the only numbers HENSYNTH calculated for your caps.

Requirements that matter for electric UAVs

Typical electric missions lean on:

• Payload (kg) — sensor or cargo mass the empty aircraft must carry.
• Endurance (s) — loiter or transit time; often the binding cap alongside range.
• Range (m) — distance when the mission is stated as reach rather than time.
• Cruise speed (m/s) and cruise altitude (m) — define the cruise segment energy draw.
• Span max (m) — transport and launch constraints on wing span.
• Battery max (kg) — ceiling on installed battery mass.
• Reserve SOC — fraction of charge held back; reduces usable energy in screening.
• Stall, takeoff, and landing limits — field and approach constraints for small runways or catapult/ recovery concepts modeled as length caps.

Use feasibility before you invest in fairing details. HEN-AI's seeded example sentence on Requirements is a template for how to phrase a mission in natural language — still save numeric fields afterward.

Geometry choices

Pick an aircraft type baseline, set electric propulsion on the Aircraft page, save wing and tail dimensions within span cap headroom. CAD continuity reminders apply: change wing area, re-run. Section refinement may happen in HENFOIL on the same account if polars drive your camber choice; HENSYNTH screening uses the aircraft model you saved, not an unstated airfoil miracle.

Run screening and read compliance

Run screening updates MTOW, empty mass, range, endurance, stall, field lengths, climb, L/D max, and static margin when the engine has predictions. Compliance PASS/FAIL tells you which caps fail at conceptual fidelity. Download the requirements zip for a stakeholder who only reads attachments.

Synthesis when feasibility allows

Open Synthesize, run four styles, compare minimum MTOW versus maximum endurance cards for the trade your mission cares about. Use this aircraft copies the chosen candidate into the project; Run screening again before you treat compliance as final. Minimum energy and balanced cards give alternate points on the same requirement set — style searches, not flight-approved variants.

Electric UAV screening is not flight test

Battery models, propulsion efficiency, and drag build-up are handbook-level in screening. Operational wind, thermal derating, and avionics duty cycle may not be in your requirement form. HENSYNTH is live for early trades; proving the vehicle flies the mission remains your test program.

In simple words: what this page is for

Walk through a fixed-wing electric UAV in HENSYNTH: payload and endurance requirements, battery cap and reserve SOC, geometry, Run screening, synthesis, candidate apply.

This lesson exists because aircraft teams often jump to heavy CFD before the mission is even closed. HENSYNTH electric UAV mission screening loop keeps the focus on conceptual screening you can explain in review.

Why the topic matters

Engineers lose time when a title sounds clear but the page only sketches the idea. This article expands HENSYNTH electric UAV mission screening loop so you can answer three questions without jargon: what is the idea, when do you use it, and how do you check it in a HENDOI product.

Read the sections above for the core definitions. Use the steps below to move from reading into a real project trail you can share with a teammate.

How to apply this in HENDOI

In practice: open HENSYNTH after you sign in, set or confirm geometry, write mission targets on Requirements, Run screening, then read PASS / FAIL with margins. Use Mission, Performance, Trades, Optimize and Reports only after the screening snapshot exists. Numbers come from stored runs — the product does not invent missing values.

If you still need the wing section itself, finish that work in HENFOIL first, then continue the aircraft in HENSYNTH. One HENDOI account covers both. Plans stay Student USD 9, Professional USD 29 and Team USD 89.

What this page will not claim: HENSYNTH is conceptual and preliminary screening. It is not wind-tunnel data, not certification CFD, and not a compliance certificate for an authority. PASS / FAIL means requirement-versus-prediction inside the product.

Checklist before you leave this page

• Can you state the idea of HENSYNTH electric UAV mission screening loop in one sentence?
• Do you know which product owns the next action — HENSYNTH or HENFOIL?
• Will every number you keep carry a method label or a stored-run source?
• If you are new here, have you opened Register or Login?

Related reading on this site

• HENSYNTH candidate cards, Use this aircraft, and CAD
• HENSYNTH compliance matrix: PASS, FAIL, and margin
• HENSYNTH download and share technical reports
• HENSYNTH Geometry page: wing, fuselage, and tails
• All HENDOI blog articles
• HENSYNTH product page
• HENFOIL product page
• Pricing — Student, Professional & Team
• FAQ
• Login · Register now