AvPlot/Reference/Articles
FAA Standards · Land Use

Runway Protection Zones: Land Use Compatibility and Dimensions

The Runway Protection Zone (RPZ) is one of the most misread features on an Airport Layout Plan. It is not a clear zone you simply keep empty — its entire purpose, per AC 150/5300-13B §3.13, is to control land use off the runway end so that people and property on the ground are protected. The most common question planners type into a search bar — “what can be in an RPZ?” — has a real, citable answer. This is that answer, with the geometry, the full dimension table, and the FAA’s compatibility guidance.

What the RPZ is for

The RPZ is a trapezoidal area on the ground centered on the extended runway centerline, off the runway end. Its function under §3.13 is to enhance the protection of people and property on the ground by controlling the land uses within it. That framing matters: the RPZ is fundamentally a land-use control mechanism, not merely an airspace surface or an obstacle-free patch of pavement. The FAA’s strong preference is that the RPZ be free of incompatible land uses, and ideally that the airport own the underlying land in fee simple or hold avigation easements that let it control development there.

Source: AC 150/5300-13B (Airport Design), Change 1, §3.13, Runway Protection Zone. Function: control of land use to protect people and property on the ground.

The geometry: a trapezoid in three numbers

Every RPZ is fully defined by three dimensions:

  • Length — the dimension measured along the extended runway centerline.
  • Inner width — the width at the end nearest the runway (the “start” width).
  • Outer width — the wider far end of the trapezoid.

The RPZ does not begin at the runway end itself; it starts a set distance away, and that distance — along with which set of dimensions applies — depends on whether it is an approach or a departure RPZ.

Approach RPZ vs. departure RPZ

There are two kinds of RPZ, and a single runway end can have both:

  • Approach RPZ — protects arriving aircraft. It begins 200 ft before the landing threshold and uses the approach dimensions.
  • Departure RPZ — protects departing aircraft. It anchors to the departure (takeoff-run / TORA) end and uses the departure dimensions, which can differ from the approach RPZ for the same runway end.

Because the two are anchored to different points and can carry different dimensions, they are evaluated separately. AvPlot renders approach RPZs in cyan and departure RPZs in amber precisely so the two are never confused on a drawing.

Geometry note: Approach RPZ begins 200 ft prior to the threshold; departure RPZ anchors to the TORA end (not ASDA). Per AC 150/5300-13B §3.13 and Appendix G.

Two functional sub-areas

Within the trapezoid, the FAA distinguishes two zones for land-use purposes:

  • The Central Portion of the RPZ — centered on the extended runway centerline. This is the most restrictive area, and the FAA’s expectation is that it stays clear of structures and concentrations of people.
  • The Controlled Activity Area — the remainder of the RPZ outside the central portion, where certain uses may be acceptable subject to coordination.

RPZ dimensions by approach category and visibility

The controlling dimensions are selected by two inputs: the aircraft approach category (AAC) and the approach visibility minimums. The RPZ grows as aircraft get faster and as visibility minimums get lower — the largest RPZ belongs to runway ends serving the fastest aircraft at the lowest minimums. Read the controlling row from the table below.

RPZ dimensions — length × inner width × outer width (AC 150/5300-13B Appendix G)
Approach category / visibility Length (ft) Inner width (ft) Outer width (ft) Area (ac)
Visual & ≥1 SM — small aircraft 1,000 250 450 8.035
Visual & ≥1 SM — AAC A & B 1,000 500 700 13.774
Visual & ≥1 SM — AAC C & D 1,700 500 1,010 29.465
Not lower than 3/4 SM — all categories 1,700 1,000 1,510 48.978
Lower than 3/4 SM — all categories 2,500 1,000 1,750 78.914

The “small aircraft” row applies where the runway serves small aircraft exclusively (approach speed under 50 kt and small-aircraft design). Note the jump in footprint from the visual rows to the instrument rows: lower minimums roughly double the protected acreage.

Source: AC 150/5300-13B Appendix G, Change 1. (“Table 2-4” is legacy 13A numbering — 13B carries RPZ dimensions in Appendix G.) Areas computed from the trapezoid dimensions.

Land use compatibility: what can be in an RPZ

This is where most RPZ work actually lives. The governing answer comes from §3.13 together with the FAA’s Interim Guidance on Land Uses Within a Runway Protection Zone, dated September 27, 2012. The default posture is that the RPZ should be free of incompatible land uses, with the central portion held to the strictest standard.

Incompatible / discouraged uses

The following are considered incompatible — especially within the central portion — because they concentrate people, create hazards to flight, or both:

  • Residences of any kind.
  • Places of public assembly — churches, schools, hospitals, office buildings, shopping centers, and stadiums.
  • Fuel storage facilities and hazardous material storage.
  • Anything that creates glare or smoke, or that attracts wildlife.
  • Any use that concentrates people within the RPZ.

Uses that trigger FAA coordination

The 2012 interim guidance specifically calls for FAA coordination and evaluation whenever a new or modified land use is introduced into the RPZ. The examples it lists as triggering review include:

  • Buildings and structures.
  • Recreational land use — golf courses, sports fields.
  • Transportation facilities — roads, rail, and transit.
  • Fuel storage facilities.
  • Above-ground utility infrastructure.
  • Wastewater and water-treatment facilities.

Generally acceptable uses

Some uses are generally acceptable, provided people are not concentrated and the central portion stays clear:

  • Agriculture — crops (but not livestock concentrations, which can attract wildlife).
  • Open space.
  • Airport service roads with controlled access.
Source: FAA Interim Guidance on Land Uses Within a Runway Protection Zone, Sept 27, 2012, together with AC 150/5300-13B §3.13. New or modified uses require FAA coordination and an alternatives/cost evaluation.

What this means on the ALP

In practice, a planner must depict the RPZ on the Airport Layout Plan, show the land use within it, and coordinate any proposed change with the FAA before it is introduced. Where existing incompatible uses already sit inside the RPZ, they should be a documented mitigation or acquisition priority — the FAA expects a deliberate path toward removing or controlling them over time, typically through fee acquisition or avigation easements.

The practical takeaway: the RPZ is selected by the controlling AAC and visibility minimums, drawn as a trapezoid anchored 200 ft before the threshold (approach) or at the TORA end (departure), and then defended as a land-use boundary.

Try it in AvPlot
Generate the exact RPZ for an AAC + visibility combination
The RPZ Dimensions tool pulls the controlling length, inner width, and outer width from the design-standards data — never hardcoded — and renders approach in cyan, departure in amber.
Open RPZ Dimensions →

This article is a reference summary for planning use, not a substitute for the governing FAA text. Citations refer to AC 150/5300-13B (Airport Design) §3.13 and Appendix G, Change 1, and to the FAA Interim Guidance on Land Uses Within a Runway Protection Zone, dated September 27, 2012. Always verify dimensional values and land-use determinations against the current FAA guidance before issuing a design product. See the full airport planning glossary or the AvPlot toolkit.