HENSYNTH takeoff and landing distance screening

Field lengths as requirements, not inputs

On the Requirements page, Takeoff limit (m) and Landing limit (m) are maximum allowed distances — the longest ground roll and obstacle-clearance path your concept must fit. You do not type predicted takeoff distance here; Run screening writes predictions to the Requirements run report and compliance matrix.

Help on the form explains takeoff limit as longest ground roll allowed for takeoff and landing limit as longest ground roll allowed for landing, in metres. The run report uses richer definitions aligned with conceptual performance methods.

What takeoff distance means on the report

The takeoff distance ? modal describes distance from brake release to fifty feet above the runway: ground roll at a liftoff speed derived from weight and wing, net force near liftoff, a transition segment, and climb to the obstacle height. Total takeoff distance is the sum of those pieces at screening fidelity.

Compliance compares that total to your takeoff limit. FAIL means the current thrust, weight, and wing combination exceeds the cap in the model — not necessarily that a real runway is unusable without your own operational analysis.

What landing distance means on the report

Landing distance is approach from the obstacle height plus ground roll after touchdown, including a short free roll before braking deceleration from drag and wheel friction. The modal references a shallow approach angle for the airborne segment.

Stall speed in landing configuration feeds approach speed, which feeds landing distance. That is why stall-speed FAIL and landing-distance FAIL often show up together when wing area is tight.

Using field length in trade studies

• Increase wing area or reduce weight when takeoff FAIL persists after propulsion edits.
• Check tail and flap proxies indirectly through stall and climb rows when landing FAIL appears with otherwise acceptable cruise range.
• Re-run after synthesis only after Use this aircraft and save — field length predictions track saved geometry.

Screening, not AFM data

Airfield performance in flight manuals comes from flight test and regulation-specific corrections. HENSYNTH field lengths are handbook-style screening numbers for comparing concepts on the same requirement set. Do not publish operational runway limits from this panel alone.

In simple words: what this page is for

Takeoff limit and landing limit on Requirements map to predicted ground roll plus obstacle clearance — how HENSYNTH documents the screening formulas in help modals.

This lesson exists because aircraft teams often jump to heavy CFD before the mission is even closed. HENSYNTH takeoff and landing distance screening 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 takeoff and landing distance screening 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 takeoff and landing distance screening 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