Products · VTOL Fixed-Wing

VTOL Launch and Landing Site Requirements

Launch and recovery is where VTOL projects fail in practice, and it is a site problem rather than an aircraft problem.

10 of 10Method note

Overview

Measure the actual clear area on site. Published figures assume ideal surfaces and no obstacles.
Identify the approach and departure sectors and check for wires, masts and moving vehicles.
Define the abort case: a go-around needs its own clear volume, not the same footprint as a landing.
Wind at ground level can be more turbulent than at flight altitude, especially near buildings and tree lines.

VTOL removes the runway, not the site requirement

The most persistent misunderstanding about vertical take-off and landing aircraft is that they can operate anywhere. They cannot. What VTOL removes is the requirement for a prepared runway of meaningful length; what it retains is a requirement for a clear volume during the vertical phase, a surface that will not damage the aircraft or be damaged by it, and a safety separation from people, vehicles and property that is larger than most teams initially assume.

The vertical phase is the part that needs the clearance, and it is also the part where the aircraft has the least margin. During transition the aircraft is moving between two fundamentally different flight regimes, with changing control authority and, in most configurations, less energy margin than in steady cruise or steady hover. A site that looks adequate on a map can be inadequate in practice because of a single obstruction in the transition volume.

So treat site selection as a survey task with a written outcome, not as something the crew improvises on arrival. Each site should be recorded: dimensions, surface, obstructions, access, and the approach and departure paths that will actually be flown. That record is what makes a repeatable programme possible, and it is what allows a different crew to use the same site safely months later.

What to measure at a candidate site

The first measurement is the clear volume. Not the footprint — the volume. Consider the height of the obstruction that matters: a single tree, a mast, a power line or a building edge at the boundary can invalidate a site that is otherwise generously sized. Assess the volume in three dimensions, and remember that the aircraft needs clearance on departure and arrival paths, not only directly overhead the launch point.

The second is the surface. Loose material is the primary hazard: sand, gravel, dry soil and crop residue are all ingested into rotors and into intakes, and they damage optics and bearings. A surface that is firm and clean is worth more than one that is merely flat. Where the only available surface is loose, a mat or a portable pad is a cheap and effective mitigation, and it should be part of the kit rather than an improvisation.

The third is separation. Define a radius within which no uninvolved person or vehicle is present during launch and recovery, and hold it. This is the requirement most often relaxed under schedule pressure, and it is the one whose failure has consequences beyond the aircraft. The radius should be written, briefed, and physically marked where the site is used repeatedly.

Wind, obstacles and the approach path

Wind direction determines the usable orientation of a site, and a site that works in one wind may not work in another. Choose launch and recovery points with an orientation that allows operating into wind, and have a documented alternative for the prevailing wind direction at that site. On coastal and ridge sites, where wind is strongly directional and variable, this deserves particular attention.

Obstacle assessment should include the things that appear only in certain conditions: wires that are invisible against a bright sky, trees that leaf out, crops that grow, and vehicles that park. A site survey done in one season may not describe the site in another. Re-survey sites that will be used across seasons, and record the date and conditions of the survey.

The approach and departure path deserves its own assessment, because it is where most site-related incidents occur. The path should be clear at the altitude the aircraft will actually use, free of the obstacles above, and oriented so that a problem during the vertical phase leaves the aircraft with somewhere to go that is not towards people or property.

Turning site requirements into a repeatable routine

For programmes that use the same sites repeatedly, the highest-return investment is a site card: one page per site, with dimensions, surface, obstructions, wind orientation, approach and departure paths, access, and any seasonal caveats. It takes minutes to produce and it removes the most common source of site-related error, which is relying on someone's memory of a site visited months earlier.

For programmes that use new sites continuously — long corridors, for instance — the equivalent is a site selection rule that any crew member can apply without a surveyor: minimum dimensions, surface criteria, obstruction clearance and separation, stated as pass or fail. That rule should be short enough to be applied in the field and strict enough that its answer is trusted.

Either way, brief before every launch, even at a known site. Conditions change between sorties, and the brief is where a change — a vehicle parked, a person walking, a wind shift — gets caught. The brief should be short, and it should name the abort criteria and who has authority to call them.

Where this becomes engineering scope

Standard site requirements are part of operating any VTOL platform and should be met by procedure. Where they cannot be — a site that is genuinely constrained, a surface that cannot be improved, an approach path that must cross an obstruction — the answer is not to accept the risk but to change the plan: a different site, a different launch orientation, or a different platform class.

Where a programme has unusual operating constraints across many sites, it is worth formalising them into an operating envelope and a training package rather than handling each site ad hoc. Our operating environment requirements work covers that, and delivery, training and documentation covers turning it into something a crew can be trained against.

Send your site dimensions, surface types, typical wind and obstruction context to our engineering team. We will tell you whether a standard VTOL configuration works on your sites, and if it does not, we will say so and propose the alternative rather than letting you discover it in the field. For the platform-class question that often sits behind a constrained site, see the VTOL versus multirotor comparison.