OBSTACLE PROTECTION SURFACE · ICAO ANNEX 14 In development

A warning today, the full approach check in development

The protection surface over an approach is a plane, and the question is whether anything crosses it. The planned check flies an arc on that plane and aims along it, so any object breaking through cuts the sightline. In active development, not offered yet. Flight planning already warns of obstacles penetrating the Annex 14 approach surface.

Schematic, generic airport · time compressed · not a survey result
1
surface tested today, the Annex 14 approach surface
−0.57°
PAPI protection surface set below the glide path, Annex 14
15%
PAPI protection surface divergence, Annex 14
60 m
distance of the PAPI protection surface origin from the threshold
FROM THE FIELD

Real captures from real inspections

Every picture below comes from an inspection we flew: drone frames, field photos and app screens. The brackets mark what the analysis reads.

Real drone frame by day: the threshold end of an asphalt runway seen across grass with a tree line and hills behind
REAL FRAME · 9 SEP 2026 · APPROACH END

The approach end, in daylight

4K frame from a PAPI flight on 9 Sep 2026, downscaled to 2880 px.

Real drone frame by day: the dashed centreline and the edge line of an asphalt runway, a crew with PAPI units on the grass
REAL FRAME · 9 SEP 2026 · RUNWAY AXIS

Runway axis, dashes and edge line

4K frame from a PAPI flight on 9 Sep 2026, downscaled to 2880 px.

FIT

Who this is for

For
Aerodrome operators who have to show, after works near the approach or a season of growth, that nothing now rises into the obstacle protection surface before an inspector asks.
Airfield managers at regional and general aviation aerodromes where vegetation rather than construction is the obstacle that grows between surveys.
Aerodromes commissioning or re-aiming a PAPI, where the protection surface moves with the set angle and has to be shown clear at the new geometry.
Not for
An evaluation of every obstacle limitation surface around the aerodrome, approach, take-off climb, transitional, inner horizontal and conical, which is a larger piece of work and is in development.
Certified obstacle data for AIP or terrain and obstacle data publication under Annex 15, which needs a licensed surveyor and a formal data chain.
The decision whether the PAPI can stay in service with a penetration present, which belongs to the operator and the authority.
WHAT IS BUILT

What is built and what is in development

01 An approach surface warning in flight planning

Obstacles in the register are tested against the Annex 14 approach surface, and a penetration shows as a warning when the flight is planned. This is the approach surface, not the PAPI obstacle protection surface.

Acceptance A penetrating obstacle is flagged in the planner.
02 An obstacle register with exports

Each obstacle has a polygon, a type, a height above ground and MSL and ellipsoid (HAE) heights, entered by hand, imported from OpenAIP or seeded from the Slovak eAIP. The register exports on the airport data sheet as JSON, CSV or PDF, and flight-plan KML can include obstacles as no-fly polygons.

Acceptance The export lists the obstacles that are in the register.
03 The PAPI protection surface check, in development

A check against the PAPI's own obstacle protection surface, with a flown sightline for the objects no register contains, is in development. It is not available today.

Acceptance Not available yet.

A geometric check, then a visual one

A complete check tests the same surface twice, once against your survey data and once against what the camera sees. The first half exists today for the approach surface.

Registered obstacles labelled with their height above base

The surface is constructed, not estimated

Inspection drone operating on an airfield alongside normal aircraft movements

Then the sightline has to agree

TODAY AND IN DEVELOPMENT

What is built and what is not

Each item with the state it is in today, and the standard values a PAPI protection surface check would use.

7 parameters ICAO Annex 14 Vol I
01 Approach surface warning

Registered obstacles tested against the Annex 14 approach surface and shown as a warning in flight planning. Not a report.

Status or value Built in the software
02 Obstacle register

Per obstacle a polygon, a type, a height above ground and MSL and ellipsoid (HAE) heights, exported on the airport data sheet as JSON, CSV or PDF.

Status or value Built in the software
03 PAPI surface penetration

No object breaks through the obstacle protection surface for the runway direction, tested against the register and on a flown sightline.

Status or value In development
04 Surface slope

The plane a PAPI protection surface check is run on, taken from a published value or derived from the published glide path.

Status or value Glide path − 0.57°
05 Surface geometry

Origin offset from the threshold, inner edge width and outward divergence of the PAPI protection surface.

Status or value 60 m · 300 m · 15%
06 Horizontal sector

A flown arc would sweep the sector either side of the runway axis rather than sampling the centre line alone.

Status or value min ±15°, in development
07 Measured top heights

Not available. Object heights are the registered values and are not measured from drone imagery.

Status or value Not available
Geometry and values per ICAO Annex 14 Vol I and ICAO Doc 9157 Part 4.
HOW IT WORKS · 6 STEPS

From runway data to an approach surface warning

01 Enter the runway data

The runway ends, threshold positions, published glide path and PAPI data go into TarmacView, with the obstacle register if one exists. Output is the geometry the surfaces are built from.

02 Fill the register

Obstacles are entered by hand, imported from OpenAIP or seeded from the Slovak eAIP, each with a polygon, a type, a height above ground and MSL and ellipsoid heights.

03 Test against the approach surface

In flight planning every registered obstacle is tested against the Annex 14 approach surface. Output is a warning for each one that penetrates.

04 Export

The airport data sheet carries the register as JSON, CSV or PDF, and flight-plan KML can include obstacles as no-fly polygons.

05 PAPI protection surface test, in development

Building the PAPI obstacle protection surface from the set angle and testing the register against it is in development. It is not available today.

06 Flown sightline, in development

Flying an arc on the plane with the camera locked on a point that also lies on it, to find what no register contains, is in development. It is not available today.

Approach surface clearance warning beside the runway and the registered obstacles
PLANNING · APPROACH SURFACE CLEARANCE WARNING

Approach surface clearance warning beside the runway and the registered obstacles

EVIDENCE AND CAPABILITY

The claim worth checking is the plane

EACH WITH AN OWNER

Risks and dependencies

Owner · WEATHER Visibility and wind

A flown sightline, once available, has to be read over two kilometres of approach, so haze, precipitation and low sun on the axis would stop the capture, and wind above the drone's limit would stop the arc. This does not affect the warning in flight planning.

Owner · OPERATOR Access and the published data

The surface needs the published glide path, threshold and PAPI data, because a plane built on the wrong angle tests the wrong volume. Tower coordination and permission for land outside the aerodrome boundary also sit with the aerodrome operator.

Owner · BOTH, AT SCOPING The geometry

A clearance statement is only as good as the surface it was made against. The approach surface warning uses the Annex 14 dimensions. A PAPI protection surface check would use the aerodrome's published dimensions or slope where they exist, and say which it used.

Download as PDF

Frequently Asked Questions

Which surface is checked?
Today, the Annex 14 approach surface, as a warning in flight planning for the obstacles in the register. That is not the PAPI obstacle protection surface. The protection surface is what Annex 14 defines for the visual approach slope indicator on that runway end. It starts a short distance in front of the threshold at a set width, diverges outward on both sides at a fixed rate and climbs along the approach at an angle slightly below the glide path the PAPI is set to. A check against it is in development. Because the plane is built from the runway geometry and the set angle, it can be constructed exactly, and anything above it is by definition a penetration.
How is this different from an obstacle limitation surface survey?
In extent. A protection surface check covers the plane over one approach, which decides whether a crew following the PAPI has anything in its way. An obstacle limitation surface evaluation covers the whole set of surfaces around the aerodrome, approach, take-off climb, transitional, inner horizontal and conical, reaching kilometres out, and is what an operator owes the authority as a statement of the aerodrome's surroundings. TarmacView does not offer that full evaluation yet, and it is in development. Only the approach surface is tested today.
Why fly it if we have a surveyed obstacle register?
Because the register tells you what was surveyed on the day it was surveyed. A complete check tests every object in it against the surface as a computation, before anyone flies, and names any that penetrate. What the register cannot contain is the objects nobody surveyed, the tree that grew, the mast that was not notified, the temporary crane. A flight along the surface is what finds those. Today TarmacView does the first half for the approach surface, as a planning warning. The flown half is in development. The register alone is a statement about the past.
How does a flown arc prove the surface is clear?
The drone flies an arc out on the approach at the height the surface plane reaches at that distance, with the camera locked on a point on the extended centreline that also lies on the plane. The sightline from the camera to that point therefore lies in the surface, and anything rising through the surface between the two passes in front of the camera. The sweep either side of the runway axis covers the sector a crew uses. This is the method, and flying it for obstacles is in development and not available today.
What do we get for a penetration?
Today, a warning in flight planning that the obstacle penetrates the Annex 14 approach surface, and the obstacle's record in the register, with its polygon, type and heights. The register can be exported on the airport data sheet as JSON, CSV or PDF. It is a warning, not a report, and the heights are the registered values rather than measurements from imagery. What you do not get is the decision about whether the PAPI can stay in service in the meantime. That is the operator's and the authority's, and it usually depends on how far the penetration is from the on-slope signal.
How often should the approach be checked?
Often enough that a penetration is caught before an inspector or a pilot report catches it. A poplar can add a metre a year, and a line of them at the edge of the approach can cross a surface that slopes at a few degrees within a couple of seasons. Aerodromes with woodland under the approach tend to check annually, in winter when the canopy is at its lowest. Aerodromes with cleared surroundings check when something changes: a permit, a crane, a works handover, a re-aimed PAPI. Keep the obstacle register current between checks, because the warning in flight planning is only as good as the register.

References

icao-annex-14-v1
Annex 14 to the Convention on International Civil Aviation, Volume I: Aerodrome Design and Operations International Civil Aviation Organization
icao-doc-9157-p4
Doc 9157, Aerodrome Design Manual, Part 4: Visual Aids International Civil Aviation Organization
icao-doc-9137-p6
Doc 9137, Airport Services Manual, Part 6: Control of Obstacles International Civil Aviation Organization
Reviewed by Štefan Moravík · 2026-09-08
Keep reading

Learn more

03 PAGES
Obstacle Limitation Surface Survey by Drone
Obstacle Limitation Surface Survey by Drone
products

Obstacle Limitation Surface Survey by Drone

The OLS survey is in active development and not offered yet. The register in two height datums, data sheet exports and approach surface warning are…

SEP 04 2026 9 MIN
Non-Aeronautical Ground Lights Survey by Drone
Non-Aeronautical Ground Lights Survey by Drone
products

Non-Aeronautical Ground Lights Survey by Drone

Drone survey of non-aeronautical ground lights near an aerodrome, in active development and not offered yet. The app already plans the observation…

OCT 23 2026 10 MIN
PAPI Protection Surface Check After Works or Growth
PAPI Protection Surface Check After Works or Growth
solutions

PAPI Protection Surface Check After Works or Growth

How an aerodrome shows its PAPI approach is unobstructed after works or tree growth. TarmacView's own check is in active development and not offered…

SEP 07 2026 10 MIN
Get Started

Talk to us about the development or early access

The approach obstacle clearance check is in active development and not offered yet. If you want to follow it or try it early at your aerodrome, tell us about the aerodrome, the runway ends and whether an obstacle register exists.