Blog / Geometry processing

Geometry processing

How to Repair Self-Intersecting Airfoil Geometry Before Aerodynamic Analysis

HENDOI · 26 October 2026

A self-intersection is a curve that crosses itself, usually a bad ordering, a spline loop or a trailing-edge fold. Delete the loop and rebuild the station. Do not scale it and hope the panel code copes.

Why a crossing is fatal

Panel and viscous methods assume a simple closed curve: one interior, panels that do not cross, a boundary layer that can walk from stagnation to trailing edge. A self-intersection gives the curve two interiors, or a panel that cuts its neighbor. The solver may still return numbers. They are not the airfoil you think you drew. The invalid-point lesson is how a bad file starts. This is the repair when the curve actually crosses itself.

Repair in a way you can check

  1. Plot the polyline at a scale where the trailing edge and the leading edge each fill the screen. Most loops hide in one of those two places.
  2. Find the two segments that cross, or the span of points that reverse. A point-in-polygon wobble or a segment-intersection test is the systematic version of looking.
  3. Delete the points on the loop, not a smooth neighborhood of innocent surface. Keep the deletion count in the log.
  4. Re-order so the surface walks upper surface from trailing edge to leading edge and lower surface back, or the other consistent convention you already chose. Do not mix them.
  5. Re-close the trailing edge with an explicit decision: sharp, or a blunt edge with a real thickness. A repair that pinches a 2% trailing edge into a spike has traded one defect for another.
  6. Run the geometry gate again. Then normalize. Then analyse. A polar computed on the broken curve cannot be rescued by deleting the loop afterward.

If the crossing came from a fit, refit with fewer degrees of freedom rather than hand-patching every time. A spline that loops once will loop on the next station. Record the original file hash and the repaired file hash. “Cleaned” is not a revision history.


Where this sits in the series

In simple words: what this page is for

A self-intersection is a curve that crosses itself, usually a bad ordering, a spline loop or a trailing-edge fold. Delete the loop and rebuild the station. Do not scale it and hope the panel code copes.

This lesson exists because section decisions fail when geometry, method labels and selection reasons are scattered. How to Repair Self-Intersecting Airfoil Geometry Before Aerodynamic Analysis 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 How to Repair Self-Intersecting Airfoil Geometry Before Aerodynamic Analysis 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 How to Repair Self-Intersecting Airfoil Geometry Before Aerodynamic Analysis 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?

These pages teach the ideas. They are not wind-tunnel data and not a certification analysis. When a number matters, compute it at a stated Reynolds number, Mach number and transition setting, and keep the method label on the result. In HENFOIL that production polar is a VIC polar — see the analysis ladder and the polar field guide.

Both products live

Use this lesson in the HENDOI workspace

This page sits in Geometry processing. 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 More

Live · 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 More

Aerospace 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

Sundarapandi Muthupandi, Founder and CEO of HENDOI

This post by

Sundarapandi Muthupandi

Founder & CEO · HENDOI

Click to visit my profile

Related articles

Call usChat with us