FAA 2C (Aviation Tools)

Summary

Generates an obstruction identification surface (OIS) for helipads based on specifications from FAA Advisory Circular 150/5390-2C.

This tool can be used to identify obstacles that may impact an aircraft's ability to take off from or land on a helipad. By creating multipatch or polygon features, you can visually identify obstructions in ArcGIS Pro.

Usage

This tool creates the OIS in an existing polygon or multipatch feature class. The OIS can also be generated in an existing polygon shapefile. If a feature class is provided for the Target OIS Features parameter, it must have a vertical spatial reference.
To create a .json file for the Custom JSON File parameter, use the CustomizeOIS.exe utility included in the Aviation Airports Product Data download available from My Esri.
If you select the Curved Surface option for the Surface Shape parameter, you must provide polyline features for the Input Flight Path Features parameter for the surface to follow.
The Input Flight Path Features parameter value must be polyline geometry and include an ObjectID field. The polyline endpoint pf the Input Flight Path Features parameter value should be created within a 100-meter search radius of the edge of the Input FATO Features parameter value.
The Input Flight Path Features parameter value can be 2D data, because the x and y-values are used to create the direction of the curve.
If the PATHID field is included in the Target OIS Features parameter value, it will be populated with the ObjectID value of its source Input Flight Path Feature. This allows Flight Path features to be related to their output curved approach surfaces. The PATHID field (long integer) must first be added to the Target OIS Features parameter value.
The Input FATO Features parameter value should be z-enabled polygon features with defined horizontal and vertical coordinate systems.

Note:

Z-values are required to determine the slope and final height of the approach surface.
The RunwayHelipadDesignSurface feature class in the Esri Airports Airfield dataset can be used for the Input FATO Features parameter value.
If the Input FATO Features parameter has values that are populated in the RWYDESG and IDARPT fields, they will also be populated in corresponding fields in the Target OIS Features parameter value.
The ObstuctionIdSurface_MP feature class in the Esri Airports Airspace dataset can be used for the Target OIS Features parameter value and contains the expected fields to be populated.
The following output attributes will be populated by the tool: DESCRIP, NAME, OISSURTY, RWYDESG, SLOPE, and IDARPT.

Label	Explanation	Data type
Input FATO Features	The input Final Approach and Takeoff (FATO) features.	Feature Layer
Target OIS Features	The target polygon or multipatch feature layer containing the OIS.	Feature Layer
Surface Classification	Specifies the classification type of the FATO surface. Non Prior Permission Required (PPR) Facilities—These are publically available helipads for general use by pilots. This is the default. Prior Permission Required (PPR) Facilities—These are heliports used exclusively by the owner and individuals authorized by the owner to use the facility.	String
Surface Shape (Optional)	Specifies the shape of the take off or approach surface. Straight Surface—The take off or approach surface is straight. This is the default. Curved Surface—The take off or approach surface is curved.	String
Approach Bearing (Optional)	The absolute bearing that an approaching aircraft will travel along the surface. A value of 0 will align the surface to true north. The default is 0.	Double
Input Flight Path Features (Optional)	The polyline flight path features that the curved surface will follow.	Feature Layer
Helipad Elevation (Optional)	The elevation of the highest point of the helipad. The value must be in the vertical coordinate system linear units of the target feature class. If no value is provided, the highest point of the Input FATO Features parameter value will be used. The default is 0.	Double
Custom JSON File (Optional)	The import configuration file, in JSON format, that will be used to create the custom OIS.	File

Derived output

Label	Explanation	Data type
Output OIS Features	The updated feature class containing the generated OIS.	Feature Layer

arcpy.aviation.FAA2C(input_fato_features, target_ois_features, surface_classification, {surface_shape}, {approach_bearing}, {in_flightpath_features}, {helipad_elevation}, {custom_json_file})

Name	Explanation	Data type
input_fato_features	The input Final Approach and Takeoff (FATO) features.	Feature Layer
target_ois_features	The target polygon or multipatch feature layer containing the OIS.	Feature Layer
surface_classification	Specifies the classification type of the FATO surface. `NON_PRIOR_PERMISSION_REQUIRED_FACILITIES`—These are publically available helipads for general use by pilots. This is the default. `PRIOR_PERMISSION_REQUIRED_FACILITIES`—These are heliports used exclusively by the owner and individuals authorized by the owner to use the facility.	String
surface_shape (Optional)	Specifies the shape of the take off or approach surface. `STRAIGHT_SURFACE`—The take off or approach surface is straight. This is the default. `CURVED_SURFACE`—The take off or approach surface is curved.	String
approach_bearing (Optional)	The absolute bearing that an approaching aircraft will travel along the surface. A value of 0 will align the surface to true north. The default is 0.	Double
in_flightpath_features (Optional)	The polyline flight path features that the curved surface will follow.	Feature Layer
helipad_elevation (Optional)	The elevation of the highest point of the helipad. The value must be in the vertical coordinate system linear units of the target feature class. If no value is provided, the highest point of the `input_fato_features` parameter value will be used. The default is 0.	Double
custom_json_file (Optional)	The import configuration file, in JSON format, that will be used to create the custom OIS.	File

Derived output

Name	Explanation	Data type
derived_outfeatureclass	The updated feature class containing the generated OIS.	Feature Layer

Code sample

FAA2C example 1 (stand-alone script)

The following Python script demonstrates how to use the FAA2C function to create straight approach and takeoff surfaces.

# Name: FAA2C_Straight_Surface_example.py
# Description: Generates a straight obstruction identification surface (OIS) for
# helipads based on specifications from FAA Advisory Circular 5390-2C.

import arcpy


# Set variables

input_fato_features = r'C:\Data\Airports.gdb\Helipads'
target_ois_features = r'C:\Data\Airports.gdb\ObstructionIdSurface_MP'
surface_classification = "NON_PRIOR_PERMISSION_REQUIRED_FACILITIES"
surface_shape = "STRAIGHT_SURFACE"
approach_bearing = 90.0
helipad_elevation = 121.0
custom_json_file = r'C:\Data\config.json'

# Run FAA 2C
arcpy.aviation.FAA2C(input_fato_features, target_ois_features, surface_classification,
                     surface_shape, approach_bearing, helipad_elevation, custom_json_file)

FAA2C example 2 (stand-alone script)

The following Python script demonstrates how to use the FAA2C function to create curved approach and takeoff surfaces.

# Name: FAA2C_Curved_Surface_example.py
# Description: Generates a straight obstruction identification surface (OIS) for
# helipads based on specifications from FAA Advisory Circular 5390-2C.

import arcpy


# Set variables
input_fato_features = r'C:\Data\Airports.gdb\Helipads'
target_ois_features = r'C:\Data\Airports.gdb\ObstructionIdSurface_MP'

surface_classification = "NON_PRIOR_PERMISSION_REQUIRED_FACILITIES"
surface_shape = "CURVED_SURFACE"
in_flightpath_features = r'C:\Data\Airports.gdb\FlightPath'
helipad_elevation = 121.0
custom_json_file = r'C:\Data\config.json'

# Run FAA 2C
arcpy.aviation.FAA2C(input_fato_features, target_ois_features, surface_classification,
                     surface_shape, in_flightpath_features, helipad_elevation, custom_json_file)

Environments

This tool does not use any geoprocessing environments.

Licensing information

Basic: No
Standard: Requires Airports or ArcGIS Aviation Charting
Advanced: Requires Airports or ArcGIS Aviation Charting

FAA 2C (Aviation Tools)

Summary

Usage

Note:

Parameters

Derived output

Environments

Licensing information

Related topics