ArcGIS Desktop

  • ArcGIS Pro
  • ArcMap

  • My Profile
  • Help
  • Sign Out
ArcGIS Desktop

ArcGIS Online

The mapping platform for your organization

ArcGIS Desktop

A complete professional GIS

ArcGIS Enterprise

GIS in your enterprise

ArcGIS Developers

Tools to build location-aware apps

ArcGIS Solutions

Free template maps and apps for your industry

ArcGIS Marketplace

Get apps and data for your organization

  • Documentation
  • Support
Esri
  • Sign In
user
  • My Profile
  • Sign Out

ArcMap

  • Home
  • Get Started
  • Map
  • Analyze
  • Manage Data
  • Tools
  • Extensions

Creating Unified Facilities Criteria (UFC) surfaces for runways and helipads

Available with Aviation Airports license.

Available with Aviation Charting license.

  • Generating UFC surfaces

Unified Facilities Criteria (UFC) are imaginary surfaces that are defined in the document UFC 3-260-01 for the purpose of planning and designing airfields and helipads for United States military use. Each UFC surface contains several parts that vary depending on the branch of the United States Armed Forces and Runway Class. The Unified Facilities Criteria (UFC) Surfaces tool allows you to generate the surfaces based on the military branch as well as wing type (rotary or fixed), runway class (Class A or Class B), and flight rules (Instrument or Visual).

Generating UFC surfaces

The Unified Facilities Criteria (UFC) Surfaces tool requires an existing output polygon or multipatch feature class.

The ObstructionIdSurface polygon feature class is found within the Airspace feature dataset, in the Airports 18B schema, and may be used as the output polygon feature class. However, other z-enabled polygon or multipatch feature classes may be used. The feature class must match the projected coordinate system and spatial domain of the source runway centerline feature class and should contain the fields listed in the following table.

Note:

The containing Airspace feature dataset must match the projected coordinate system and spatial domain of the input runway feature class. This dataset should be z enabled and match the projected coordinate system and spatial domain of the source runway centerline feature class.

Field nameAliasData typeLength

DESCRIP

Description

Text

255

NAME

Name

Text

50

OISSURTY

OIS Surface Type

Text

16

SLOPE

Slope

Double

-

  1. Start ArcMap.
  2. On the main menu, click Customize > Toolbars > Aviation Airports.
  3. Click the Unified Facilities Criteria (UFC) Surfaces button Unified Facilities Criteria Surfaces on the Aviation Airports toolbar.

    The UFC Surface dialog box appears.

    UFC Surface window
  4. On the General Input tab, click the Wing Type drop-down arrow and choose a type.
    • Fixed Wing
    • Rotary Wing
  5. Click the Service Type drop-down arrow and choose an option.
    • Airforce
    • Army
    • Navy
    • Marine Corps
  6. Click the Runway Class drop-down arrow and choose an option.
    • Class A
    • Class B
  7. Click the Flight Rules drop-down arrow and choose an option.
    • Instrument
    • Visual
  8. Click the Runway drop-down arrow and choose the input features. Optionally, other line feature classes or shapefiles may be used, as long as the data is in a projected coordinate system and z enabled.

    These are the features on which the UFC is based, and are typically runway centerlines from either the Airports or the AIS data models. The tool will accept input features from the following feature classes:

    Data modelGeometry typeFeature class Attributes used

    18B

    Line

    RunwayCenterline

    RWYDESG

    18C

    Line

    RunwayCenterline

    RUNWAYDESIGNATORIDENTIFIER

    AIS

    Line

    ADHPSurfaceLine

    SUBTYPE_CODE, DESIGNATOR_TXT

    Note:

    If the line input does not contain Airports or AIS attribution, a warning message will display; however, the UFC will still be generated.

  9. Click the Type drop-down arrow and choose the output type.

    This is the file type in which the UFC is created. You can choose from two formats:

    • Polygon or multipatch shapefiles
    • Polygon or multipatch features
  10. Click the Path drop-down arrow and select the output layer.

    This must be a polygon layer that is present in the TOC where the output will be appended to. This file type must match the selected output type.

  11. Provide a value in the Length Of High Runway End Clearway text box.

    This is the length at the high end of the runway.

    Most of the specifications also require the airport reference elevation to be defined and runway classifications to be selected. For specifications that require a high-end runway classification, the high end of the runway has a name between 19 and 36, and the low end of the runway has a name between 01 and 18.

  12. Provide a value in the Length Of Low Runway End Clearway text box.

    This is the length at the low end of the runway.

    For specifications that require a low-end runway classification, the low end of the runway has a name between 01 and 18.

  13. Provide a value in the Airport Reference Elevation text box.

    Most of the specifications require the airport reference elevation to be defined and runway classifications to be selected.

  14. If necessary, click the Advanced tab on the UFC Surface dialog box.
    UFC Surface dialog box Advanced tab

    The properties are grouped based on the surface generated. There are default values for each parameter, but they can be modified.

  15. Optionally change the unit of measure for surface lengths and widths in the Linear Units section.
    • Meters—Runway length is in meters.
    • Feet—Runway length is in feet. This is the default.
  16. If necessary, change the angular units for slope surfaces in the Angular Units section.
    • Percent Rise—Slope angle is expressed as a grade (inclination) in percent.
    • Degree—Slope angle is expressed in degrees.
    • Slope—Slope angle is expressed as x units of run per 1 vertical unit. This is the default.
  17. Optionally uncheck the Limited Use check box.

    This check box only applies to U.S. Army and U.S. Air Force surfaces, and will change the parameters of several surfaces for helipads and runway surfaces. By default, it is not checked.

    Below is a listing of which surfaces are generated based on the Runway Class and Flight Rules options.

    SurfaceDescriptionClass AClass B

    Primary Surface

    An imaginary surface longitudinally centered on a runway

    Surface createdSurface created

    Clear Zone Surface

    A surface that begins at the runway end and is symmetrical to the extended runway centerline

    Surface createdSurface created

    Accident Potential Zone Surface

    An area beyond the clear zone with a significant potential for accidents

    Surface createdSurface created

    Approach Surface

    A surface that extends outward and upward from each end of the primary surface

    Surface createdSurface created

    Transitional Surface

    A surface that connects the primary and approach or departure surface that also meets with the inner horizontal

    Surface createdSurface created

    Inner Horizontal

    An imaginary surface connecting the approach or departure surface and the transitional surface

    Instrument Only

    Surface created

    Conical

    An imaginary surface that extends from the periphery of the inner horizontal surface outward and upward at a slope

    Instrument Only

    Surface created

    Outer Horizontal

    An imaginary surface extending horizontally outward from the conical surface

    Instrument Only

    Surface created

  18. You can check or uncheck the Generate check box as necessary to create or omit surface types.

    For each surface type, the properties are grouped based on the surface generated. There are default values for each parameter, but they can be modified.

  19. Optionally click the arrow next to each surface type to reveal the parameters available for the surface.
  20. Click Generate.

ArcGIS Desktop

  • Home
  • Documentation
  • Support

ArcGIS

  • ArcGIS Online
  • ArcGIS Desktop
  • ArcGIS Enterprise
  • ArcGIS
  • ArcGIS Developer
  • ArcGIS Solutions
  • ArcGIS Marketplace

About Esri

  • About Us
  • Careers
  • Esri Blog
  • User Conference
  • Developer Summit
Esri
Tell us what you think.
Copyright © 2022 Esri. | Privacy | Legal