The controller says 80 metres. The aircraft looks comfortably below the 120-metre limit. Then the ground falls away beneath it.

The number on the screen may still say 80 metres, but the legal question has changed. In the UK open category, the limit follows the closest point of the Earth’s surface. A display that measures from the take-off point does not automatically tell you that distance.

This is not a software fault. It is a reference problem: two valid measurements can answer two different questions. Understanding which one the aircraft displays is essential before flying across a ridge, valley, cliff or steeply sloping site.

What the UK rule actually measures

The current UK rule for open-category operations says an unmanned aircraft flying from a natural elevation or over terrain with natural elevations must remain within 120 metres of the closest point of the Earth’s surface. It also says the measurement must adapt to the terrain, including plains, hills and mountains. The Civil Aviation Authority’s UAS.OPEN.010 text is therefore describing a geometric relationship between the aircraft and the terrain—not simply a vertical column above the launch pad.

The CAA’s accompanying guidance makes the point explicit: this is not a “vertical height”, but the geometric distance to the closest point of the Earth’s surface. Its public Drone Code tells pilots to adjust their flight path where ground rises or falls, including around hills, mountains and cliffs.

That wording matters because “120 metres above take-off” and “within 120 metres of the closest terrain” are not interchangeable. On flat ground they can be similar. On changing terrain they can diverge quickly.

What the controller may be showing

Manufacturers choose labels and references for their telemetry, so pilots must check the manual for the actual aircraft and software version. A prominent number marked H, height or altitude is not universally an above-ground measurement.

For example, the DJI Mavic 4 Pro manual explains that the H value in DJI Fly is the vertical height from the take-off point. It also warns that this value is not the aircraft’s altitude above ground level or above mean sea level and may differ from height or altitude limits defined by law.

Skydio uses the same reference for one of its enterprise aircraft: its X10D telemetry guide says the displayed altitude indicates height above the launch point. These examples do not prove that every drone behaves the same way. They show why the reference must be verified rather than guessed.

Two slopes, two different hazards

When the terrain falls away, a take-off-relative display can understate the aircraft’s distance from the surface below. Imagine launching from a high ridge and keeping the aircraft at a displayed 80 metres while crossing a deep valley. The screen value may remain steady even as the nearest terrain becomes much farther away. A pilot who treats 80 as automatic evidence of compliance can exceed the terrain-based limit without seeing a larger number.

When the terrain rises, the reverse safety problem appears. An aircraft can remain at the same displayed height while its clearance over the ground, trees or rocks shrinks. The legal 120-metre ceiling is not the immediate concern in that direction; collision clearance and a safe route are. A single take-off-relative number cannot describe both the upper limit and the changing terrain beneath the aircraft.

Cliffs make the geometry especially easy to misunderstand. The closest point of the Earth’s surface may be beside the aircraft rather than directly below it. That is why the CAA uses geometric distance rather than a simple vertical line.

Height, altitude and AGL are not synonyms

Every measurement needs a reference. Four terms often appear in drone apps, manuals and mapping workflows:

• Height above take-off point compares the aircraft with the recorded launch reference. It is useful telemetry, but it does not follow terrain.
• Above ground level (AGL) describes separation from the local ground. In uneven terrain, it changes even if height above take-off stays constant.
• Altitude above mean sea level (AMSL) uses a sea-level reference. It can help relate a route to mapped elevations, but subtracting two uncertain values is not automatically a legal-compliance system.
• GNSS ellipsoidal height uses a mathematical Earth model. It is not the same reference as mean sea level. Converting between them requires the appropriate geoid model and datum.

Those distinctions are not academic vocabulary. If an app, survey file and controller use different references, their numbers can all be internally consistent and still disagree. The safe response is to identify the reference and uncertainty for each value—not to assume the most convenient number is “the altitude”.

Why a maximum-height setting does not solve the problem

A controller setting that prevents flight above a chosen height relative to take-off can be a useful backstop. It cannot reshape itself around every hill or valley unless the aircraft and mission system are specifically using reliable terrain data for that purpose.

Nor does a manufacturer limit grant permission to fly up to that number. The DJI manual, for example, separates its displayed take-off-relative height from legal height or altitude limits and leaves compliance with the pilot. Geographical zones may also impose a lower ceiling than the general rule; the CAA guidance says those restrictions still apply.

Automated missions deserve the same scrutiny. A waypoint file may encode a relative height, an altitude or a terrain-following instruction. Importing it into different software does not guarantee that the reference survives unchanged. The mission preview, manual and site geometry must agree before launch.

The tall-obstacle provision is narrow

UK law contains a specific provision for certain artificial obstacles, but it is not a general “fly 15 metres above any building” rule. Under UAS.OPEN.010(3), the obstacle must be taller than 105 metres, the aircraft must be within 50 metres horizontally, and the operation must be at the request of the entity responsible for the obstacle. Only then may the maximum height increase by up to 15 metres above it.

The CAA guidance also says the responsible entity must explicitly grant permission. A tower’s physical height, an app’s ceiling or a landowner’s general consent does not by itself satisfy all of those conditions.

A terrain-aware pre-flight check

1. Identify the display reference. Read the aircraft and app manuals for the exact meaning of height and altitude fields. Check whether a home-point update changes that reference.
2. Trace the entire route over terrain. Look for ridges, valleys, cliffs and steep changes—not just the launch and subject locations. Consider where the closest surface could be beside the aircraft.
3. Check current restrictions separately. A 120-metre general limit does not override a lower geographical-zone limit, temporary restriction, airfield rule or operating-authorisation condition.
4. Build a conservative vertical plan. Where ground falls, plan to descend as needed to remain within the terrain-based distance. Where it rises, maintain safe obstacle clearance without assuming that the screen’s take-off-relative height describes it.
5. Verify automated-flight references. Confirm whether waypoints are relative to launch, terrain, sea level or another datum. Do not rely on a label alone when software or file formats change.
6. Keep visual and situational awareness. A map or number is an aid, not a live survey of every tree, wire, rock face or terrain-model error.
7. Stop when the reference is uncertain. If the route cannot be shown to remain within the applicable limits and safe clearances, reduce the route, choose another launch point or do not fly.

The screen is evidence, not the whole answer

A height readout can be accurate for its own reference and still be the wrong evidence for the question a pilot is asking. Over level ground, that distinction may stay invisible. Terrain exposes it.

The practical lesson is simple: before trusting a number, ask “measured from what?” Then compare that answer with the rule, the route and the ground around the aircraft. The UK 120-metre limit follows the Earth’s surface; a take-off-relative display follows the launch point. Safe planning has to connect the two.

Scope note: This article covers the UK open category and official/manufacturer material checked on 18 October 2026. It is general safety information, not legal advice or an operating authorisation. Interfaces vary by aircraft and software version. No aircraft, controller, terrain model or mission-planning application was tested for this article.