Analysis
The HENFOIL analysis ladder: when to escalate
HENDOI · 24 September 2026
Thin-airfoil → Hess–Smith panel → Thwaites–Head IBL → VIC polars — and optional Euler / IB / RANS-SA screens. Escalate only when the decision needs it.
Why a ladder exists
Early airfoil decisions do not need a RANS wall on day one. They need a clear progression: start cheap, escalate when the question demands more physics, and label every step so a later review can see what was actually run.
HENFOIL’s analysis ladder is that progression. It is not a marketing funnel. It is an engineering discipline encoded in the product.
Rung by rung
1. Thin-airfoil & classical
Fourier thin-airfoil methods give fast intuition for camber effects and lift-curve slope before you spend time on denser panels. Use this when you are still shaping ideas, not crowning a winner.
2. Hess–Smith panel + Kutta
Inviscid panel solutions on conditioned geometry. Pressure and circulation become meaningful only after the quality gate has accepted the section. Spikes and crossed trailing edges invent “physics” long before viscosity gets the blame.
3. Thwaites–Head IBL + eⁿ screen
Integral boundary-layer and transition screening envelopes. Useful for early separation / transition intuition. Still a screen — not a production transition certificate for flight clearance.
4. VIC viscous polars
The production polar engine for compare, select, envelopes and batch. Multi-point CL, CD, Cm with method IDs. A VIC polar is not a RANS polar and not wind-tunnel data.
5. Optional Euler / IB / RANS-SA
Transonic Euler, immersed-boundary pictures and gated body-fitted RANS-SA exist when the decision needs them. The UI keeps those labels visible. They inform; they do not certify.
When to escalate
Escalate when geometry is clean, the cheaper rung already points a direction, and the open question is one the next rung can actually answer. Do not escalate to burn compute on a FAIL geometry or to decorate a slide.
What travels with the answer
Method IDs, trust cards and gate status travel with the numbers. That is how selection and optimize stay auditable when someone asks six months later: what did you run, and why was that enough?
In simple words: what this page is for
Thin-airfoil → Hess–Smith panel → Thwaites–Head IBL → VIC polars — and optional Euler / IB / RANS-SA screens. Escalate only when the decision needs it.
This lesson exists because section decisions fail when geometry, method labels and selection reasons are scattered. The HENFOIL analysis ladder: when to escalate helps you keep a clean trail from shape to polar to choice.
Why the topic matters
Engineers lose time when a title sounds clear but the page only sketches the idea. This article expands The HENFOIL analysis ladder: when to escalate 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: create a HENDOI account or log in, open HENFOIL, bring a section in (create, import DAT, or digitize), pass the geometry gate, climb the analysis ladder only as far as the decision needs, then compare and archive. Every calculated number should keep its method label.
When the section choice is ready for the aircraft, continue in HENSYNTH for mission, compliance and trades. Same account. Same plans.
What this page will not claim: a teaching polar or geometry note is not a flight-Re certificate. HENFOIL labels methods so you know what you bought. Tunnel data and professional judgement still sit outside any single software run.
Checklist before you leave this page
- Can you state the idea of The HENFOIL analysis ladder: when to escalate in one sentence?
- Do you know which product owns the next action — HENFOIL or HENSYNTH?
- 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
- Airfoil selection with a documented why-#1
- Create airfoil fields: NACA, analytic and CST — what each digit means
- Digitize field-by-field: every control, why fill it, what you get
- Import and digitize airfoils into HENFOIL
- All HENDOI blog articles
- HENFOIL product page
- HENSYNTH product page
- Pricing — Student, Professional & Team
- FAQ
- Login · Register now
Both products live
Use this lesson in the HENDOI workspace
This page sits in Analysis. HENFOIL and HENSYNTH are both live on one account. These articles are screening lessons — not certification reports.
Live · section
HENFOIL
Turn this lesson into a section you can draw, check, analyse and compare. Run the polar at the Reynolds number of the vehicle. The method name stays on the result.
To Know MoreLive · aircraft
HENSYNTH
After the section is chosen, set geometry and mission requirements, run screening, read compliance, synthesize candidates and download or mail the report.
To Know MoreAerospace industry collaboration
Share thoughts and ideas — help us build better solutions
We are looking for aerospace industry collaboration. Share your thoughts, ideas and real workflow challenges so we can improve our products and deliver the best solutions for OEMs, UAV / eVTOL teams, labs and aeronautical engineering companies.
Written by

Related articles
- VIC polars in HENFOIL — what they are and are not
VIC is the production polar engine for compare and select. Deep notes on use cases, limits, envelopes and honesty labels.
- Who HENSYNTH is for: OEMs, UAV teams, labs and students
HENSYNTH targets aerospace OEMs, Tier-1 suppliers, UAV and eVTOL manufacturers, design bureaus, research labs and aeronautical students — with one honest conceptual-design product.
- HENSYNTH Reports: analyze PDF and stored runs
How to download the latest HENSYNTH analyze PDF, list stored runs, and mail a conceptual screening summary from the Reports page.