HENSYNTH Geometry page: wing, fuselage, and tails

The Aircraft page is your geometry source of truth

In HENSYNTH, the Aircraft page holds the configuration the screening run reads. Wing span, wing area, taper, sweep, twist, thickness-to-chord, fuselage length and cross-section limits, horizontal tail span and arm, vertical tail height, and propulsion kind and count all live here. When you press Run screening elsewhere in the project, the engine uses the saved aircraft object — not an unsaved form state.

Get in the habit of saving geometry after meaningful edits. The project workspace can save requirements automatically before a run; geometry still needs an explicit save when you change planform or tails.

Wing and planform

The wing block drives reference area, aspect ratio, and the airfoil or thickness proxy the aero build-up uses. You can start from a configuration baseline when you pick an aircraft type: the UI applies representative span, area, taper, and sweep so you are not staring at empty fields. Adjust toward your concept, then inspect the 2D section plot and planform views to confirm the numbers match what you meant.

• Span and area set aspect ratio and wing loading once weight is known.
• Taper and sweep feed stability and structural proxies in the screening model.
• Twist and t/c influence stall and drag bookkeeping at this fidelity level.

Fuselage and tails

Fuselage length and maximum width and height size wetted area and component weight groups. The horizontal tail uses span and tail arm; the vertical tail uses height and the same arm convention. Tail volume ratios feed the static margin calculation on the requirements run — if the tail is too small on paper, stability screening will say so before you invest in detail design.

Propulsion on the geometry page

Electric, piston, and jet kinds are selected with the propulsion block: motor or engine count, propeller diameter where applicable, and the architecture label the synthesis cards may reuse. Screening is not a propulsion test cell; it is a consistent mass and power bookkeeping path tied to the geometry you saved.

3D view, views, and CAD continuity

The 3D aircraft view rotates with drag when your browser exposes WebGPU; 2D views show top, side, and front projections for reviews. CAD continuity panels help you see which downstream artifacts would need refresh after a planform change — a reminder that geometry edits invalidate earlier runs until you Run screening again.

Before you leave for Requirements

With geometry saved and visually checked, move to Requirements and enter mission caps. Screening compares predictions from this aircraft to those caps. A beautiful 3D model with unsaved wing area is still the wrong aircraft to the engine.

In simple words: what this page is for

How to use the Aircraft page in HENSYNTH: planform inputs, fuselage dimensions, tail arms, propulsion, 3D view, section plots, and save-before-run discipline.

This lesson exists because aircraft teams often jump to heavy CFD before the mission is even closed. HENSYNTH Geometry page: wing, fuselage, and tails 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 Geometry page: wing, fuselage, and tails 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 Geometry page: wing, fuselage, and tails 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 workflow: dashboard to technical report
• All HENDOI blog articles
• HENSYNTH product page
• HENFOIL product page
• Pricing — Student, Professional & Team
• FAQ
• Login · Register now