Radar Vectors
Advisory Circular Cancelled Issued Sep 30, 2015 AAS-100 512 pages Copy saved Nov 18, 2026

AC 150/5300-18C Survey and Data Standards for Submission of Aeronautical Data Using Airports GIS

This AC provides the specifications and technical requirements for data collection conducted at airports in support of the FAA Airport Surveying – Geographic Information System (GIS) Program. The information furnished under these standards covers the entire spectrum of the FAA’s airport data requirements, including runway and stopway data, navigational aid data, obstruction data, and data on various airport features, including taxiways, aprons, and landmark features. This version of the AC is a major rewrite; it now conforms to the new FAA enterprise data model and process of maintaining a single authoritative source of aeronautical data.

This document is cancelled. It may have been replaced. Check the official source before relying on it.

Official source ↗ Open PDF

U.S. Department of Transportation Federal Aviation Administration

Advisory Circular

Subject: Survey and Data Standards for Submission of Aeronautical Data Using Airports GIS

Date: 9/30/2015 Initiated By: AAS-100

AC No: 150/5300-18C

Purpose. 1 This Advisory Circular (AC) provides the specifications for the collection of airport data through field and office methodologies in support of the Federal Aviation Administration (FAA). It also explains how to submit data to the FAA, for independent verification and validation. The primary purpose of these general guidelines and specifications is to list the technical requirements for data collection conducted at airports in support of the FAA Airport Surveying – Geographic Information System (GIS) Program. The FAA’s Office of Airport Safety and Standards (AAS-1) administers this program. The standards covered in this document provide critical information for the operation and safety of the National Airspace System (NAS). The information furnished under these standards covers the entire spectrum of the FAA’s airport data requirements, including but not limited to runway and stopway data, navigational aid data, obstruction data, and data on various airport features, including taxiways, aprons, and landmark features. Most of this information is sourced data, acquired by field survey and/or remote sensing methods.

Cancellation. 2 This AC cancels 150/5300-18B, General Guidance and Specifications for Submission of Aeronautical Surveys to NGS: Field Data Collection and Geographic Information System (GIS) Standards, Consolidated Change 1, dated February 24, 2014.

Application. 3 The FAA recommends the guidelines and standards in this AC for the collection of geospatial airport and aeronautical data. In general, this AC is not mandatory. However, use of these guidelines is mandatory for the collection of geospatial airport and aeronautical data funded under federal grant assistance programs. It also provides one, but not the only, acceptable means of meeting the requirements of 14 CFR part 139, Certification of Airports, for the collection of geospatial airport and aeronautical data. Mandatory terms such as "will" and "must" used herein apply only to those who purchase the collection of geospatial airport and aeronautical data using Airport Improvement

Program (AIP) or Passenger Facility Charge Program (PFC) funds, or those who seek to demonstrate compliance by use of the specific method described by this AC.

Principal Changes. 4 This version of the AC is a major rewrite. Users should review the entire document to ensure they understand the requirements and specifications in the document. The principal reason for this AC change is to conform to the new FAA enterprise data model and process of maintaining a single authoritative source of aeronautical data. To conform to this new enterprise data model some features had to be renamed, all features incorporated temporality by adding start and end dates, and a few additions were made to enable printing of an airport layout plan from Airports GIS data. The AC also incorporates the following principal changes:

1. Removed the requirement for submission of survey plans in portable document format. Airports GIS now supports these functions through online forms.

2. Added information and clarification regarding 14 CFR part 77, Objects Affecting Navigable Airspace, analyses and Airport Layout Plan data collection to the AC.

3. Updated ESRI shapefile naming conventions and included these in an appendix.

4. Added additional detail and guidance on temporality of features.

5. Updated Table 2-1, Survey Requirements Matrix.

6. Added temporality attributes to all features allowing for the management of data using time. Eliminated the alternative (previous temporality method) from all features.

7. Added Geometric Constraints defining the relationship of certain features to other features (such as a runway centerline must be contained within a runway) to ensure the topological integrity is maintained between the associated features.

8. Added Feature attribution constraint information describing the minimum required attribution for each feature required by the system.

9. Added ESRI Geodatabases as an acceptable format for input of data to Airports GIS.

10. Significant changes aligned Chapter 5 of this AC with the FAA National Airspace System (NAS) Enterprise Architecture Base Infrastructure:

• Identified attributes common to each feature in a single paragraph rather than repeating them in each feature description. • Removed the Information Assurance Level description from each feature description. • Updated or provided clarification of data capture rules. • Changed the feature name of Movement Area to Airport Movement Area. • Deleted Obstacle feature and replaced with Object Area, Object Line, and Object Point features.

• Updated the Airport Sign feature including defining a methodology for inputting the sign inscription in a standardized manner. • Changed the feature name of Runway End to Runway Direction. • Deleted Lease Zone feature. • Renamed Runway Safety Area Boundary feature to Runway Safety Area. • Deleted Taxiway Intersection as a separate feature and required the taxiway element feature to have the intersection attribute if it is an intersection. • Deleted Runway Label feature and added it as an attribute to the Marking Area feature. • Deleted Runway Protect Area and combined attributes and types into Runway Helipad Design Surface. • Deleted Obstruction Area and replaced by the use of the Object Area feature. • Deleted County feature; the system now generates this information from official government sources. • Deleted Municipality; the system now generates this information from official government sources. • Deleted State feature; the system now generates this information from official government sources. • Deleted FAA Region Area; the system now generates this information from an

official FAA source. • Deleted Landmark Segment; replaced with Landmark Area, Landmark Line and Landmark Point, providing greater detail in representing landmark features. • Changed the feature name of Shoreline to Natural Water Body, providing a more appropriate name for the feature. • Deleted Building, Fence, Gate, and Tower features and replaced with Structure Line, Structure Point, and Structure Polygon. • Added the use of the CodeLandUseType to the following features providing additional standardized descriptions for these features: Object Area, Object Line, Object Point, Noise Contour, Structure Line, Structure Point, Structure Polygon, Sidewalk Segment, Tunnel, Tank Site, Utility Line, Utility Point, Utility Polygon. • Combined NAVAID Equipment features into a single feature entry, reducing the redundancy in the standard. • Deleted Airport Control Point and replaced with Position feature.

Combined all (airport Control Point entries) into a single entry to reduce redundancy in the standard. • Added a feature for Vegetation to clarify difference between ground cover and low lying vegetation from Forest Stand Area. • Added feature Dimension to support airport layout plan (ALP) and electronic airport layout plan (eALP) initiatives of the agency; added to new General group. • Added feature Label Point to support ALP and eALP initiatives of the agency; added to new General group.

 Added Runway Declared Distance feature to allowing more flexibility in

defining these critical elements.  Added Final Approach and Takeoff Area as a separate feature and removed it

from the runway helipad design surface.  Added Runway Protection Zone feature (removed from runway helipad

design surface) to provide for additional attribution and flexibility in visualization.  Easements and Right of Ways is now Right and Interest aligned with other

FAA standards.  Moved the Restricted Access Boundary feature from Airfield group to

Security group.  Moved all National computer-aided design and drafting (CADD) standard

mapping information to an appendix.  Moved FAA Std-002, Standard Engineering Drawing Preparation and

Support, mapping information to an appendix.  Updated and refined enumerations used in the standard.  Moved Coordinate Zone information from within Chapter 5 to an appendix.  Updated the information to help map features to the other related standards of

Spatial Data Standards for Facilities, Infrastructure, and Environment (SDSFIE), Aeronautical Information Exchange Model (AIXM), and DO-272, User Requirements for Aerodrome Mapping Information.

11. Provided general editorial and clarifications throughout the document.

12. Updated and expanded criteria in Chapters 1, 2 and 3 to meet the needs of the government for the data this AC defines.

13. Added hyperlinks (allowing the reader to access documents located on the internet and to maneuver within this document) throughout this document and identified them with underlined text. When navigating within this document, return to the previously viewed page by pressing the “ALT” and “←” keys simultaneously.

Feedback on this AC. 5 If you have suggestions for improving this AC, you may use the

Advisory Circular Feedback form at the end of this AC.

Michael J. O’Donnell Director of Airport Safety and Standards

CONTENTS

Paragraph Page

v

General Guidance and Specifications … 1-1 Chapter 1.

1.1 Introduction … 1-1

1.2 Administration … 1-1

1.2.1 Specifications … 1-1 1.2.2 Conventions … 1-1

1.3 Data Provider Requirements … 1-2

1.3.1 Maintenance and Calibration of Equipment … 1-2 1.3.2 Original Data … 1-2 1.3.3 Corrections or Revisions to Data … 1-3 1.3.4 Unusual Circumstances … 1-3 1.3.5 Specification Review and Familiarity … 1-3

1.4 Data Collection Planning and Reporting … 1-3

1.4.1 Types of Plans … 1-3 1.4.2 Pre-Survey Preparation Activities … 1-6

1.5 Data Accuracy … 1-8

1.5.1 Geodetic and Ground Control Data … 1-9 1.5.2 Remote Sensing … 1-9 1.5.3 Raster Imagery … 1-9

1.6 Final Reporting … 1-10

1.6.1 Project Summary … 1-10 1.6.2 Survey Data Conclusions … 1-10 1.6.3 Control Network Survey Results/Conclusions … 1-11 1.6.4 Field Survey Data Collection Conclusions … 1-11 1.6.5 Data Processing/Adjustment Conclusions … 1-11 1.6.6 Recommendations/Additional Comments … 1-11

1.7 Independent Data Validation and Verification … 1-11

1.7.1 Verification … 1-12 1.7.2 Validation … 1-12

Survey Specifications and Standards … 2-1 Chapter 2.

2.1 Introduction … 2-1

2.2 Geodetic and Ground Control … 2-1

2.2.1 Horizontal Control … 2-1 2.2.2 Vertical Control … 2-1 2.2.3 Geoid Model … 2-2 2.2.4 Airports Requiring Geodetic Control Monumentation … 2-2

CONTENTS (CONTINUED)

Paragraph Page

vi

2.2.5 Geodetic and Ground Control Data Format … 2-2 2.2.6 Verification of Existing Survey Marks … 2-3

2.3 Field Survey Operations … 2-3

2.3.1 Preparation … 2-3 2.3.2 Data … 2-4

2.4 Data Collection Supporting Documentation Requirements … 2-4

2.4.1 Digital Images from Hand-held Cameras … 2-4 2.4.2 Documents or Sketches … 2-7 2.4.3 Field Note Information and Data … 2-8

2.5 Determining the Survey Requirements … 2-10

2.6 Types of Surveys … 2-17

2.6.1 Airport Geodetic Control … 2-17 2.6.2 Runways … 2-17

2.7 Navigational Aid (NAVAID) Surveys … 2-27

2.7.1 Navigational Aids … 2-27 2.7.2 Determining the NAVAID Horizontal and Vertical Survey Position … 2-30 2.7.3 Electronic Navigational Aids … 2-30 2.7.4 Visual Navigational Aids … 2-30 2.7.5 Reference Measurements … 2-31 2.7.6 Navigational Aid Screening and Interference Reference Measurements. ... 2-31

2.8 Airport Airspace Analysis … 2-32

2.8.1 14 CFR Part 77 Analysis … 2-32 2.8.2 Airport Airspace Analysis Surveys … 2-33 2.8.3 Determining the Type of Analysis … 2-34

2.9 Surface Definition and Analysis … 2-34

2.9.1 Runways with Vertical Guidance … 2-34 2.9.2 Runways without Vertical Guidance … 2-44 2.9.3 Airport Airspace Analysis Special Cases and Exemptions … 2-49

2.10 Airport Layout Plan Surveys … 2-53

2.10.1 Electronic Airport Layout Plans … 2-54

2.11 Topographic Surveying … 2-54

2.11.1 Category II and III Operation Area Topographic Survey … 2-56

2.12 Airport Mapping Database (AMBD) Surveys … 2-58

2.13 Engineering (Construction) Surveys … 2-62

2.14 Airport Pavement … 2-63

CONTENTS (CONTINUED)

Paragraph Page

vii

2.14.1 Construction/Roughness … 2-63 2.14.2 Airport Pavement Inventory … 2-64

2.15 Sub-Surface Utilities Engineering (SUE) … 2-64

2.15.1 Utility Research … 2-66 2.15.2 Utility Designation … 2-66 2.15.3 Utility Field Collection … 2-67

2.16 Boundary Surveying/Land Use … 2-68

2.16.1 Research and Investigation … 2-68 2.16.2 Monumentation … 2-68 2.16.3 Measurement Specifications … 2-69 2.16.4 Plat of Survey … 2-69

Geographic Information System (GIS) Specifications and Standards 3-1 Chapter 3.

3.1 Overview … 3-1

3.2 Advantages of Data Compliance … 3-1

3.3 Relationship of GIS Features to Computer Aided Drafting and Design (CADD) Layers.3-1

3.3.1 Layering of Feature Types … 3-1 3.3.2 Feature Type Layering in GIS Software … 3-3 3.3.3 Relationship of GIS and CADD Layers … 3-3 3.3.4 Feature Type Layering in CADD Software … 3-3

3.4 Acceptable Data Formats for Airports GIS … 3-5

3.5 ESRI Shapefile Nuances for Dealing With FAA Attribute Names … 3-5

3.6 Geometric Requirements … 3-5

3.6.1 Feature Types … 3-5 3.6.2 Geometry … 3-6 3.6.3 Topological Integrity … 3-7

3.7 Attributes … 3-11

3.7.1 Enumeration Values … 3-11

3.8 Metadata … 3-12

3.8.1 Temporal Relevance … 3-13 3.8.2 Accuracy … 3-13

3.9 Coordinate Systems … 3-14

3.9.1 Acceptable Coordinate Systems … 3-14 3.9.2 Acceptable Datum … 3-14

3.10 Temporality … 3-15

CONTENTS (CONTINUED)

Paragraph Page

viii

3.10.1 Overview … 3-15 3.10.2 Properties of Temporality … 3-15 3.10.3 Temporality Models … 3-16 3.10.4 Connecting Temporal Data … 3-17 3.10.5 Data Context … 3-18 3.10.6 Temporary Feature Changes … 3-18 3.10.7 Temp Delta … 3-19 3.10.8 Snapshot … 3-19 3.10.9 Temporality within Airports GIS … 3-20 3.10.10 Temporality Date/Time Reference … 3-21

3.11 Geometric Constraints … 3-21

3.12 Feature Attribution Constraints … 3-22

Data Translation and Use of Existing Data … 4-1 Chapter 4.

4.1 Use of Existing Data … 4-1

4.1.1 Verifying the Quality of Existing Data … 4-2

4.2 Maintenance of Data … 4-3

4.3 Safety Critical Data … 4-4

4.4 Preparing Your Data for Submission to the FAA … 4-4

Airport Data Features … 5-1 Chapter 5.

5.1 Feature Specifications … 5-1

5.1.1 Common Feature Attributes … 5-1

5.2 Group: AIRFIELD … 5-2

5.2.1 Air Operations Area … 5-2 5.2.2 Aircraft Gate Stand … 5-3 5.2.3 Airfield Light … 5-5 5.2.4 Airport Movement Area … 5-6 5.2.5 Airport Sign … 5-7 5.2.6 Apron … 5-10 5.2.7 Arresting Gear … 5-11 5.2.8 Deicing Area … 5-13 5.2.9 Displaced Threshold … 5-14 5.2.10 Final Approach and Takeoff Area (FATO) … 5-25 5.2.11 Frequency Area … 5-28 5.2.12 Marking Area … 5-29 5.2.13 Marking Line … 5-31 5.2.14 Passenger Loading Bridge … 5-34 5.2.15 Runway … 5-35

CONTENTS (CONTINUED)

Paragraph Page

ix

5.2.16 Runway Arresting Area … 5-37 5.2.17 Runway Blast Pad … 5-39 5.2.18 Runway Centerline … 5-40 5.2.19 Runway Declared Distance … 5-42 5.2.20 Runway Direction … 5-46 5.2.21 Runway Element … 5-57 5.2.22 Runway Helipad Design Surface … 5-59 5.2.23 Runway Intersection … 5-61 5.2.24 Runway LAHSO … 5-63 5.2.25 Runway Protection Zone … 5-64 5.2.26 Runway Safety Area … 5-67 5.2.27 Shoulder … 5-69 5.2.28 Stopway … 5-72 5.2.29 Taxiway Element … 5-78 5.2.30 Taxiway Holding Position … 5-80 5.2.31 Touchdown Liftoff Area … 5-82

5.3 Group: AIRSPACE … 5-85

5.3.1 Landmark Area … 5-85 5.3.2 Landmark Line … 5-87 5.3.3 Landmark Point … 5-88 5.3.4 Object Area … 5-89 5.3.5 Object Identification Surface … 5-95 5.3.6 Object Line … 5-96 5.3.7 Object Point … 5-101

5.4 Group: CADASTRAL … 5-106

5.4.1 Airport Boundary … 5-106 5.4.2 Airport Parcel … 5-107 5.4.3 Land Use … 5-109 5.4.4 Lease Area … 5-110 5.4.5 Parcel … 5-111 5.4.6 Right and Interest … 5-112 5.4.7 Zoning … 5-114

5.5 Group: ENVIRONMENT … 5-114

5.5.1 Environmental Contamination Area … 5-114 5.5.2 Fauna Hazard Area … 5-115 5.5.3 Flood Zone … 5-116 5.5.4 Flora Species Site … 5-117 5.5.5 Forest Stand Area … 5-118 5.5.6 Hazardous Material Storage Site … 5-119 5.5.7 Natural Water Body … 5-120 5.5.8 Noise Contour … 5-121

CONTENTS (CONTINUED)

Paragraph Page

x

5.5.9 Noise Incident … 5-121 5.5.10 Noise Monitoring Point … 5-122 5.5.11 Sample Collection Point … 5-123 5.5.12 Vegetation Area … 5-123 5.5.13 Wetland … 5-124

5.6 Group: GENERAL … 5-125

5.6.1 Dimension … 5-125 5.6.2 Label Point … 5-126

5.7 Group: GEOSPATIAL … 5-126

5.7.1 Elevation Contour … 5-126 5.7.2 Position … 5-128

5.8 Group: MANMADE STRUCTURES … 5-131

5.8.1 Construction Area … 5-131 5.8.2 Roof … 5-132 5.8.3 Structure Line … 5-133 5.8.4 Structure Point … 5-135 5.8.5 Structure Polygon … 5-136

5.9 Group: NAVIGATIONAL AIDS … 5-139

5.9.1 NAVAID Critical Area … 5-139 5.9.2 NAVAID Equipment … 5-143 5.9.3 NAVAID Site … 5-159

5.10 Group: SEAPLANE … 5-160

5.10.1 Anchorage Area … 5-160 5.10.2 Docking Area … 5-161 5.10.3 Navigation Buoy … 5-164 5.10.4 Seaplane Ramp Centerline … 5-165 5.10.5 Seaplane Ramp Site … 5-165 5.10.6 Taxi Channel … 5-166 5.10.7 Turning Basin … 5-168 5.10.8 Water Lane End … 5-169 5.10.9 Water Operating Area … 5-171

5.11 Group: SECURITY … 5-174

5.11.1 Restricted Access Boundary … 5-174 5.11.2 Security Area … 5-175 5.11.3 Security Identification Display Area … 5-176 5.11.4 Security Perimeter Line … 5-177 5.11.5 Sterile Area … 5-178

5.12 Group: SURFACE TRANSPORTATION … 5-179

CONTENTS (CONTINUED)

Paragraph Page

xi

5.12.1 Bridge … 5-179 5.12.2 Driveway Area … 5-180 5.12.3 Driveway Centerline … 5-181 5.12.4 Parking Lot … 5-182 5.12.5 Railroad Centerline … 5-184 5.12.6 Railroad Yard … 5-186 5.12.7 Road Centerline … 5-187 5.12.8 Road Point … 5-189 5.12.9 Road Segment … 5-190 5.12.10 Sidewalk Segment … 5-192 5.12.11 Tunnel … 5-193

5.13 Group: UTILITIES … 5-194

5.13.1 Tank Site … 5-194 5.13.2 Utility Line … 5-196 5.13.3 Utility Point … 5-198 5.13.4 Utility Polygon … 5-200

5.14 Attribute Enumerations … 5-202

5.14.1 CodeAcquisitionType … 5-202 5.14.2 CodeAirportFacilityType … 5-202 5.14.3 CodeApproachCategory … 5-203 5.14.4 CodeApproachGuidance … 5-203 5.14.5 CodeApronType … 5-203 5.14.6 CodeArrestingSystem … 5-204 5.14.7 CodeBridgeType … 5-205 5.14.8 CodeBuoyType … 5-205 5.14.9 CodeColor … 5-205 5.14.10 CodeCompassDirection … 5-206 5.14.11 CodeConstructionAreaType … 5-207 5.14.12 CodeCoordinatedUseType … 5-207 5.14.13 CodeDeclaredDistance … 5-207 5.14.14 CodeDeicingArea … 5-207 5.14.15 CodeDesignGroup … 5-207 5.14.16 CodeDesignSurfaceType … 5-207 5.14.17 CodeDimensionType … 5-208 5.14.18 CodeDirectionality … 5-208 5.14.19 CodeDirectionLocation … 5-209 5.14.20 CodeDisposition … 5-209 5.14.21 CodeEasementType … 5-209 5.14.22 CodeElevated … 5-209 5.14.23 CodeEncumbranceType … 5-209 5.14.24 CodeEnvironmentalAreaType … 5-210 5.14.25 CodeFloodZoneClassificationType … 5-210

CONTENTS (CONTINUED)

Paragraph Page

xii

5.14.26 CodeFloraType … 5-210 5.14.27 CodeForestStandAreaType … 5-210 5.14.28 CodeFuel … 5-214 5.14.29 CodeGateStandType … 5-215 5.14.30 CodeHazardCategory … 5-215 5.14.31 CodeHowAcquired … 5-217 5.14.32 CodeLabelType … 5-217 5.14.33 CodeLandmarkType … 5-218 5.14.34 CodeLandUseLocation … 5-219 5.14.35 CodeLandUseType … 5-219 5.14.36 CodeLightingConfigurationType … 5-222 5.14.37 CodeLowVisibilityCategory … 5-224 5.14.38 CodeMarkerRole … 5-225 5.14.39 CodeMarkingCondition … 5-225 5.14.40 CodeMarkingFeatureType … 5-225 5.14.41 CodeMonumentType … 5-227 5.14.42 CodeNaturalWaterBody … 5-227 5.14.43 CodeNavaidEquipmentType … 5-228 5.14.44 CodeNavaidSystemType … 5-229 5.14.45 CodeNoiseSourceType … 5-229 5.14.46 CodeObjectGroup … 5-230 5.14.47 CodeObjectSource … 5-230 5.14.48 CodeObjectType … 5-230 5.14.49 CodeOffsetDirection … 5-233 5.14.50 CodeOisSurfaceCondition … 5-233 5.14.51 CodeOisSurfaceType … 5-233 5.14.52 CodeOperationsType … 5-234 5.14.53 CodeOwner … 5-234 5.14.54 CodeParcelAreaType … 5-235 5.14.55 CodePassengerLoadingBridgeType … 5-235 5.14.56 CodePlantPurpose … 5-235 5.14.57 CodePollutionCause … 5-235 5.14.58 CodePositionRoleCode … 5-235 5.14.59 CodeProjectStatus … 5-236 5.14.60 CodeRecoveredCondition … 5-237 5.14.61 CodeRemediationUrgency … 5-237 5.14.62 CodeRightAndInterest … 5-237 5.14.63 CodeRightEstate … 5-237 5.14.64 CodeRightOrInterest … 5-237 5.14.65 CodeRouteType … 5-238 5.14.66 CodeRpzArea … 5-239 5.14.67 CodeRpzType … 5-239 5.14.68 CodeRunwayDirectionDesignator … 5-239

CONTENTS (CONTINUED)

Paragraph Page

xiii

5.14.69 CodeRunwayMarkingType … 5-239 5.14.70 CodeSampleCollectionPointLocation … 5-240 5.14.71 CodeSegmentType … 5-240 5.14.72 CodeShoulderType … 5-240 5.14.73 CodeSignPurpose … 5-240 5.14.74 CodeSignType … 5-241 5.14.75 CodeStatus … 5-242 5.14.76 CodeStructureType … 5-242 5.14.77 CodeSurfaceCondition … 5-244 5.14.78 CodeSurfaceMaterial … 5-245 5.14.79 CodeSurfaceType … 5-246 5.14.80 CodeTaxiwayDesignGroup … 5-246 5.14.81 CodeTaxiwayType … 5-246 5.14.82 CodeThresholdType … 5-247 5.14.83 CodeUseCode … 5-247 5.14.84 CodeUnitOfMeasurement … 5-247 5.14.85 CodeUtilityConfidence … 5-247 5.14.86 CodeVegetationAreaType … 5-247 5.14.87 CodeVerticalStructureMaterial … 5-248 5.14.88 CodeWaterLaneType … 5-249 5.14.89 CodeWildlifeHazardType … 5-249 5.14.90 CodeZoningClass … 5-249

Appendix A. Additional References, Glossary and Acronyms … A-1

Appendix B. Airport Reference Point Computation … B-1

Appendix C. Runway, Stopway and Displaced Threshold End Identification and Monumentation … C-1

Appendix D. Truncated Attribute Values to be used with ESRI® Shapefiles … D-1

Appendix E. CADD Standard Layers … E-1

Appendix F. The FAA Standard 002 Compliance Tables … F-1

Appendix G. Coordinate … G-1

CONTENTS (CONTINUED)

xiv

FIGURES

Number Page

Figure 1-1. Example of Raster Imagery … 1-10 Figure 2-1. Photograph Type 1 … 2-5 Figure 2-2. Photograph Type 2 … 2-6 Figure 2-3. Photograph Type 3 … 2-6 Figure 2-4. Illustrates Documentation of a Glideslope Antenna from Different Perspectives. ... 2-6 Figure 2-5. Photograph Highlights How Ground Evidence and Painted Marking Supporting

Figure 1-1: picture of page 14Figure 1-1 · page 14
Picture of the page from the copy saved here

Features may not be Consistent … 2-18 Figure 2-6. Depicts Some of the Required Points and Elements of a Runway or Stopway … 2-20 Figure 2-7. An Example of the Proper Marking for a Blast Pad or Stopway … 2-21 Figure 2-8. Illustrates the Proper Marking of a Displaced Threshold … 2-23 Figure 2-9. Illustrates the Use of Day Markers to Define the End of a Runway … 2-24 Figure 2-10. Typical Communications, Navigation, Surveillance and Weather (CNSW) … 2-28 Figure 2-11. Shows the Required Measurements for a Navigational Aid … 2-29 Figure 2-12. Isometric View of Part 77 Precision Surfaces … 2-33 Figure 2-13. Illustrates the Areas, Dimensions, and Slopes of the VGAS and Analysis

Specification Required to Support Instrument Procedure Development … 2-36 Figure 2-14. Illustrates the Dimensional Criteria Associated with the VGATS and the

Figure 2-6: picture of page 14Figure 2-6 · page 14
Picture of the page from the copy saved here

Connection to the VGPCS … 2-37 Figure 2-15. Object Representation in the VGRPS Area … 2-38 Figure 2-16. SAWS, AWOS and ASOS Station Installations … 2-39 Figure 2-17. Illustrates the VGRPS and VGPCS Object Representations … 2-40 Figure 2-18. The Area Outlined in Blue Illustrates the Limits of the VGAS … 2-41 Figure 2-19. Illustrates the VGATS Divided into Four (4) Sections for Analysis … 2-42 Figure 2-20. Illustrates Dividing the VGHS into Quadrants through the ARP … 2-43 Figure 2-21. NVGPS, NVGAS, and NVGTS Types 1/2/3 for Non-Vertically Guided (NVG)

Airport Surfaces … 2-46 Figure 2-22. Horizontal Surface (NVGHS) for Non-Vertically Guided (NVG) Airport Surfaces.

… 2-47 Figure 2-23. Object Representation in the Non-Vertically Guided Operations Primary Surface

Figure 2-15: picture of page 14Figure 2-15 · page 14
Picture of the page from the copy saved here

Area … 2-48 Figure 2-24. Reporting Highest Object(s) within Object Area Limits … 2-50 Figure 2-25. This Picture Illustrates the Importance of Appropriately Identifying Catenaries. 2-50 Figure 2-26. Illustrates the Collection of Penetrating Vessel and Mobile Object Areas … 2-52 Figure 2-27. Terrain Data Collection Surface, Area 4, CAT II and III Operations Area … 2-57 Figure 2-28. Paper Chart … 2-58 Figure 2-29. The Development of Highly Accurate Digital Representations of the Airport

Environment Will Enhance the Operational Safety Systems at the Airport … 2-59 Figure 2-30. Highly Accurate Digital Representations of the Airport Environment … 2-59 Figure 2-31. Areas of Collection for Vertical Objects Surrounding the Movement Areas … 2-61

CONTENTS (CONTINUED)

xv

Figure 2-32. Airport Mapping Database Collection of Vertical Objects Meeting the

Figure 2-24: picture of page 14Figure 2-24 · page 14
Picture of the page from the copy saved here

Requirements of ICAO Area 3 … 2-61 Figure 2-33. Uniform Color Codes … 2-67 Figure 3-1. Portrays the Layering of Feature Types to Form a Map or Drawing … 3-2 Figure 3-2. Format of CADD Layer Names … 3-3 Figure 3-3. Typical Depiction of a Series of Points … 3-6 Figure 3-4. Illustrates Examples of a Line … 3-6 Figure 3-5. Depicts Some Typical Polygon Examples … 3-7 Figure 3-6. Depicts the Topology Rules for Line Segments … 3-8 Figure 3-7. Depicting the Placement of Vertices along a Curve … 3-8 Figure 3-8. Illustrates the Shared Edges and Shared Vertices Topological Rule … 3-9 Figure 3-9. Depicts an Example of the Placement of Vertices of Adjacent Polygons with

Misplaced Vertices … 3-9 Figure 3-10. Illustrates the Topological Rule of Overlapping Polygons of the Same Feature Type.

Figure 2-33: picture of page 15Figure 2-33 · page 15
Picture of the page from the copy saved here

… 3-10 Figure 3-11. Illustrates the Difference between Closed and Unclosed Polygons … 3-10 Figure 3-12. Example of a Feature and its Attributes … 3-11 Figure 3-13. MetaData Elements Have Different Levels of Aggregation … 3-13 Figure 3-14. NOTAM Temp Delta Example … 3-19 Figure 3-15. NOTAM Temp Delta Example with Snapshots … 3-20 Figure 5-1. Illustrates the Collection of the Aircraft Gate Stand Feature (the Green Circles

Represent Individual Instances of the Feature) … 5-4 Figure 5-2. Illustrates the Coding for a Multiple Element Airport Sign … 5-8 Figure 5-3. Illustrates the Collection of the Arresting Gear Feature as a Line … 5-12 Figure 5-4. Deicing Area … 5-14 Figure 5-5. Survey Point Locater … 5-16 Figure 5-6. Runway End Survey Point … 5-17 Figure 5-7. Surveying Equipment … 5-18 Figure 5-8. Paved Runway and Aligned Taxiway … 5-19 Figure 5-9. Shows the Location of the Runway Direction Point 10 Feet Inside the End Markers.

Figure 3-11: picture of page 15Figure 3-11 · page 15
Picture of the page from the copy saved here

… 5-19 Figure 5-10. Paved Runway and Aligned Taxiway Details … 5-20 Figure 5-11. Paved Runway and Aligned Taxiway … 5-21 Figure 5-12. Photograph One … 5-22 Figure 5-13. Photograph Two … 5-23 Figure 5-14. Photograph Three … 5-23 Figure 5-15. Provides a Close-up of the Nail and Washer Marking the Runway Direction Feature

Location … 5-24 Figure 5-16. The Yellow Polygon in this Figure Illustrates the FATO of a Rooftop Helipad. . 5-26 Figure 5-17. The Area Depicted by the Cyan Polygon Indicates the Extents of a Frequency Area

for a Specific Area of an Airport … 5-28 Figure 5-18. The Individual Blue Polygons in this Figure Illustrate the Capture of Runway

Markings … 5-30 Figure 5-19. The Red Line in this Figure Demonstrates the Proper Way to Collect a Marking

Line Feature on the Side Away from the Area it is Protecting … 5-32

CONTENTS (CONTINUED)

xvi

Figure 5-20. Demonstrates the Appropriate Way to Collect a Taxiway Holding Position. Capture

Figure 5-10: picture of page 15Figure 5-10 · page 15
Picture of the page from the copy saved here

the Line on the Holding Side of the Marking Away from the Area Being Protected. The Blue Arrow Indicates the Direction of Travel … 5-32 Figure 5-21. Depicts the Capture of Marking Lines on the Apron around an Aircraft Parking

Stand … 5-33 Figure 5-22. Illustrates Capturing a Passenger Loading Bridge Feature with a Passenger Loading

Bridge Type Attribute Value of Passenger Loading Bridge … 5-34 Figure 5-23. Runway Collection … 5-36 Figure 5-24. Runway 4L/22R EMAS at Chicago Midway Airport. Note the collection includes

the setback value for the EMAS … 5-38 Figure 5-25. Runway Blast Pad … 5-39 Figure 5-26. Shows the Capture of Runway Centerlines Connecting Each Runway Direction

Point … 5-41 Figure 5-27. TODA Shortened to Mitigate Penetration to the Departure Surface Resulting in

Figure 5-21: picture of page 16Figure 5-21 · page 16
Picture of the page from the copy saved here

Shortened TORA … 5-43 Figure 5-28. TODA Extended by use of a Clearway, Normal TORA … 5-44 Figure 5-29. Stop End of ASDA and LDA Located to Provide Additional RSA … 5-45 Figure 5-30. Survey Point Locater … 5-47 Figure 5-31. Runway End Survey Point … 5-47 Figure 5-32. Surveying Equipment … 5-48 Figure 5-33. Paved Runway and Aligned Taxiway … 5-49 Figure 5-34. Shows the Location of the Runway Direction Point 10 Feet Inside the End Markers.

… 5-49 Figure 5-35. Paved Runway and Aligned Taxiway Details … 5-50 Figure 5-36. Paved Runway and Aligned Taxiway … 5-51 Figure 5-37. Photograph One … 5-52 Figure 5-38. Photograph Two … 5-53 Figure 5-39. Photograph Three … 5-53 Figure 5-40. Provides a Close-up of the Nail and Washer Marking the Runway Direction Feature

Location … 5-54 Figure 5-41. Illustrates the Method of Capturing Runway Elements … 5-58 Figure 5-42. Threshold Siting Based on Approach Slope … 5-60 Figure 5-43. The Blue Polygon Illustrates the Collection of a Runway Intersection Feature. The

Figure 5-28: picture of page 16Figure 5-28 · page 16
Picture of the page from the copy saved here

Yellow Circle in the Middle of the Polygon Identifies the Intersection Point of the Two Runway Centerlines … 5-62 Figure 5-44. The Green Line in this Photo Illustrates the Capture of the Runway LAHSO

Marking. The Protected Runway is to the Left of the Marking. The Aircraft are Landing Right to Left in this Instance (Green Arrow). We have Exaggerated the Line to Illustrate the Concept … 5-64 Figure 5-45. Runway Protection Zone (RPZ), Runway Object Free Area (ROFA) and Runway

Safety Area (RSA) … 5-66 Figure 5-46. Runway Safety Area (RSA) … 5-68 Figure 5-47. Shoulders … 5-70 Figure 5-48. Taxiway Shoulder Polygon … 5-71

CONTENTS (CONTINUED)

xvii

Figure 5-49. The Blue Polygon Illustrates how to Capture the Stopway. The Yellow Polygon is

Figure 5-44: picture of page 16Figure 5-44 · page 16
Picture of the page from the copy saved here

the Runway Polygon. They Share a Common Edge Ensuring They Meet the Data Geometric Constraint Rules … 5-73 Figure 5-50. Shows the Criteria for Properly Marking a Stopway … 5-74 Figure 5-51. Illustrates the Stopway Start and Ends … 5-75 Figure 5-52. Photograph Type 1 (Eye Level) … 5-76 Figure 5-53. Photograph Type 2 … 5-76 Figure 5-54. Photograph Type 3 … 5-77 Figure 5-55. Close-up View of the Nail and Washer, Properly Inscribed … 5-77 Figure 5-56. Taxiway Element … 5-79 Figure 5-57. The Blue Line in this Figure Illustrates the Proper Location for Collecting the

Holding Position Marking … 5-81 Figure 5-58. Uses a Blue Line Extracted at the Outer Edge of the ILS/MLS holding Marking to

Figure 5-50: picture of page 17Figure 5-50 · page 17
Picture of the page from the copy saved here

Illustrate the Proper Collection Method … 5-81 Figure 5-59. The Red Square Illustrates Capturing the TLOF of a Ground Level Helipad … 5-83 Figure 5-60. Depicts the Landmark Segment Features being Extracted from Imagery … 5-86 Figure 5-61. Object Area … 5-90 Figure 5-62. Illustrates Areas Where the Airport has Right and Interest Data … 5-113 Figure 5-63. Elevation Contour … 5-127 Figure 5-64. Illustrates the Collection of an Airport Construction Area … 5-131 Figure 5-65. Sloped Roof … 5-133 Figure 5-66. Flat Roof … 5-133 Figure 5-67. Illustrates the Collection of Airport Buildings … 5-137 Figure 5-68. NAVAID Critical Areas … 5-140 Figure 5-69. NAVAID Critical Area Polygon … 5-141 Figure 5-70. NAVAID Critical Area Example … 5-142 Figure 5-71. Illustrates the Different Measurements Required for Navigational Aids … 5-145 Figure 5-72. Docking Area … 5-162 Figure 5-73. Taxi Channel … 5-167 Figure 5-74. Water Lane End … 5-170 Figure 5-75. Water Operating Area … 5-172 Figure 5-76. Illustrates the Capture of a Restricted Access Boundary Protecting Restricted Areas

Figure 5-59: picture of page 17Figure 5-59 · page 17
Picture of the page from the copy saved here

of an Airport … 5-174 Figure 5-77. Security Area … 5-176 Figure 5-78. Bridge … 5-179 Figure 5-79. Parking Lot … 5-183 Figure 5-80. Railroad Centerline … 5-185 Figure 5-81. Railroad Yard … 5-187 Figure 5-82. Shows the Collection of Road Centerlines … 5-188 Figure 5-83. Uses Orange Circles to Represent Road Point Locations Where Roads Intersect the

Object Identification Surface … 5-190 Figure B-1. Airport Reference Point (ARP) Computation … B-3 Figure C-1. Depicts the Proper Marking of a Threshold Bar … C-4

CONTENTS (CONTINUED)

xviii

Figure C-3. Typical Elevated Runway or Taxiway Edge Light with the Blue Taxiway Lens

Installed … C-6 Figure C-4. Typical Installation of the Runway End Identification Light (REIL) With the

Horizontal and VSPs Identified … C-7 Figure C-5. Illustrates the Proper Location of a GPS Setup to Locate the HSP of a Precision

Approach Path Indicator (PAPI) light System. The PAPI is One Type of VGSI. . C-8 Figure C-6. Typical Glideslope Installation … C-9

TABLES

Number Page

Figure 5-77: picture of page 17Figure 5-77 · page 17
Picture of the page from the copy saved here

Table 2-1. Survey Requirements Matrix … 2-11 Table 2-2. List of Typical Electronic NAVAIDs Associated with an Airport … 2-30 Table 2-3. List of Typical Visual Navigational Aids on an Airport … 2-31 Table 2-4. Topographic Survey Accuracy Requirements (Sample) … 2-55 Table 2-5. Sample Federal Geodetic Data Committee Spatial Data Accuracy Standards (ASPRS

Class II Mapping Accuracy for Large-Scale Maps) … 2-56 Table 2-6. CAT II and III Operation Area Accuracy Requirements … 2-58 Table 4-1. Required Field Validation Points based on Annual Aircraft Operations and Airport

Area … 4-2 Table 4-2. Examples of Field Verification Points Required of Various Airports … 4-3 Table 5-1. NAVAID Equipment Documentation and Submission Requirements … 5-146

Chapter 1. GENERAL GUIDANCE AND SPECIFICATIONS › 1.2 Administration.

GENERAL GUIDANCE AND SPECIFICATIONS Chapter 1.

1.1 Introduction. In developing the guidance in this Advisory Circular (AC), the Federal Aviation Administration (FAA) is striving to maximize the level of data collected while trying to minimize the cost to airports. However, verifying the appropriate collection and safety implications of the prescribed data against defined, repeatable and verifiable standards far outweighs the potential costs. The collection and maintenance of the data regarding airports is a shared responsibility of the FAA and the Airport Authority or proponent. The uses of the information collected according to these standards and specifications are in part to complete the following tasks:

• Provide geodetic control for engineering projects.

• Assist in airport planning and land use studies, and for other miscellaneous activities.

• Certify airports for certain types of operations.

• Develop instrument approach and departure procedures.

• Determine maximum takeoff weights.

• Update aeronautical publications.

• Plan for and site navigational aids supporting the airport.

1.2 Administration.

1.2.1 Specifications. This document provides general specifications, standards, and guidelines for collecting and maintaining airport and related aeronautical data. These specifications provide the technical requirements for capturing the data used in all phases of airport development from planning to construction, and publication in selected U.S. Government aeronautical data and related products. These specifications are designed to provide information regarding the different types of data collection tasks on airports. A Statement of Work (SOW) should detail the specific survey information for the individual airport. However, the requirements for reporting deviations, unusual circumstances, etc., described in the following paragraphs apply to both the General Specifications and to the SOW.

1.2.2 Conventions. The following conventions provide specific usage of words in this specification:

• The verbs “will” and “must” mean the action is mandatory.

• The verb “should” means the action is strongly recommended but not required.

• The contraction “N/A” means not applicable.

• The term “position” means horizontal position (latitude and longitude) unless specified otherwise.

• The term “elevation” means the distance of a point above a specified datum, measured along the vertical direction of gravity.

Chapter 1. GENERAL GUIDANCE AND SPECIFICATIONS › 1.3 Data Provider Requirements.

• The term “vertical” refers to the direction in which the force of gravity acts.

• The term “height” means the distance, measured along a perpendicular, between a point and a datum.

• The term “observation” means the survey observations resulting in a position and/or elevation for the survey mark in question, whether it is pre-existing or newly set.

• The term “set” means physically constructed.

• Use the U.S. Survey Foot (3.28083333333333 feet = 1 meter) for any length conversions. If required by state law to use another value, identify this requirement in the project plan.

• “Airport Authority” refers to the administrators at an airport awarding the contract or their designated representatives.

1.3 Data Provider Requirements. The data provider will provide all labor, equipment, supplies, material, and transportation to produce and deliver data and related products as required under this guidance. The data provider will be responsible for ensuring all employees (including sub-contractors) meet airport security requirements and follow any other Airport Authority requirements, including making arrangements for escorts, radios, and training.

1.3.1 Maintenance and Calibration of Equipment. Provide records of instrument calibrations or certification for all surveying equipment used in the data collection process. These records can include maintenance logs showing routine preventive maintenance and repairs or independent certifications of calibration. Data providers will upload these records as part of the data submission using the Airports GIS web site (https://airports-gis.faa.gov) as supporting materials of the data collection effort. Additionally, data providers will complete the online instrumentation and software sections of the web site to identify the equipment model and serial numbers, and versions of software used in collecting the data. If a hand–held electronic distance meter instrument (EDMI) is used, compare its distance measuring accuracy to a distance measured with a calibrated EDMI and upload this information as an equipment certification.

1.3.2 Original Data. Original observation logs, electronic files, and other records prepared or obtained under the terms of the contract, are instruments of service and remain the property of the consultant and Airport Authority unless agreed to by both parties. Provide reproducible copies of drawings and copies of other pertinent data to the Airport Authority. Submit the

Chapter 1. GENERAL GUIDANCE AND SPECIFICATIONS › 1.4 Data Collection Planning and Reporting.

data required by the FAA under these specifications to the FAA Airport Surveying– Geographic Information System (GIS) Program at https://airports-gis.faa.gov. Ensure original logs and records are legible, neat, clear, accurate, and completed in indelible black ink. Complete all available entries on the recording forms, or indicate as N/A. Use blue ink when checking or verifying field notes and for any required signatures. Clearly write "original" (in blue ink) on the originals of all forms, notes, and computation sheets used. Save original data unmodified whether in handwritten or computer recorded form.

1.3.3 Corrections or Revisions to Data. In the original records (paper or digital), nothing is to be erased or obliterated. If a mistake is made on a form, draw a single line through the mistake and write the correction above or to the side. If space is too limited to permit a field correction, restart with a new log sheet; however, do not recopy the form in the office in order to make a “clean” copy. An explanatory note should be made for all corrections to the original recorded figures. All editing of computer-recorded data must be done on a copy of the original with all changes initialed.

1.3.4 Unusual Circumstances. The data provider will notify the Airport Authority and the responsible FAA Regional/District Airport Office of any unusual circumstances occurring during the data collection according to these specifications. The FAA Airports Regional/District Office will then consult with the appropriate government technical representatives to determine an appropriate course of action and advise the data provider.

1.3.5 Specification Review and Familiarity. It is the responsibility of the data provider to ensure all personnel (including any subcontractors) involved in collecting, processing, or formatting the data are thoroughly familiar with the information in this guidance and in cited associated supporting materials these specifications reference.

1.4 Data Collection Planning and Reporting. Data collection at airports is a complex activity requiring proper planning. Data providers must use the Airports GIS web site to properly plan and document how they will complete the data collection. Airports GIS provides a series of web forms for data providers to use in planning and documenting the project. Data providers are no longer required to submit portable document format (PDF) versions of their plans; instead, they must use the functionality Airports GIS provides for planning and documenting projects.

1.4.1 Types of Plans. Airport data collection generally requires planning in four areas; geodetic control, ground control, remote sensing and field operations. In addition, data providers must complete information regarding the quality control processes they will use in planning and executing the data collection activity.

1.4.1.1 Geodetic and Ground Control Planning. This plan covers not only geodetic control (Primary Airport Control Station (PACS) and Secondary Airport Control Station (SACS)) but also other ground control supporting the collection of data, such as imagery control stations and checkpoints. AC 150/5300-16, General Guidance and Specifications for Aeronautical Surveys: Establishment of Geodetic Control and Submission to the National Geodetic Survey, specifies data providers complete survey planning before any mark setting or Global Positioning System (GPS) observations begin for review by the Airport Authority and the National Geodetic Survey (NGS). After reconnaissance, data providers must complete and submit their Geodetic and Ground Control planning through Airports GIS. NGS will review this plan and respond with an approval or comment via the Airports GIS web application as soon as possible, normally within five working days. Field work may start after the data provider receives notification via the web site of the approval.

1.4.1.2 Remote Sensing Planning. This plan identifies how the data providers will utilize remote sensing technologies (aerial imagery or LiDAR) as part of the data collection. AC 150/5300-17, Standards for Using Remote Sensing Technologies in Airport Surveys, provides the guidance and specifications for the use of remote sensing technologies at airports. Data providers will use Airports GIS to provide the information necessary for the review and approval of remote sensing plans. Remote sensing plans should address the following areas, but are not specifically limited to these areas:

• Flight Line Planning: Submit a diagram identifying the collection methods (flight lines) and control stations used in the remote sensing process.

• Geo-referencing: Describe in detail the plan for using geo-referenced (aero-triangulated) imagery identifying the flight lines and control stations used in the remote sensing process with acceptable accuracies. Refer to AC 150/5300-17 for additional guidance and requirements.

• Feature Extraction: Detail methods for collecting airport features, such as airport buildings, aircraft movement areas, landmark features, and object area limits (3D), with the required horizontal and vertical accuracies as specified in Chapter 5. Identify any deviations from the data capture rules provided within this guidance and the alternative method the data provider will use.

• Object Analysis: Provide a detailed description of the remote sensing methods used to identify, locate, and observe the required objects relative to the specified object identification surfaces provided in this guidance. Describe the data collection methods and the associated horizontal and vertical accuracies expected.

• Equipment and Software Listing: Provide a complete listing of the equipment planned for use in the remote sensing process including model and serial numbers, calibration reports, and equipment maintenance reports. This will include remote sensing hardware and software.

1.4.1.3 Survey Field Work. Data providers must develop and submit survey field work plans through Airports GIS for approval before beginning any field work. The FAA designated representative will review and approve the survey field work plan. Airports GIS provides the data providers with the ability to detail the methods for data collection, the tools and software they plan to use and how they will safeguard the data to ensure it is not corrupted before submission to the government. Data providers must provide insight into how they will check all data to ensure it is complete, reliable, and accurate. Ensure you identify data safeguards used to protect this sensitive and safety critical data. Once the information is entered into Airports GIS, submit the plan for review by the government. The plans must include a description of the combinations of methods used to collect the data and must discuss the comparison of the results. The plan should detail the processes used to resolve discrepancies between the remote sensing survey and ground survey. The plan should address each of the following areas but is not limited to these areas:

• Project Observation (Execution) Plan: Detail how you expect to execute the project including how you will make GPS observations to achieve two distinct data sets to determine positional data.

• Object Analysis: Provide a detailed description of the field survey methods used to identify, locate, and observe the required objects relative to the specified object identification surfaces provided in this guidance. Describe the data collection methods and the associated horizontal and vertical accuracies expected.

• Prior Survey Data: The FAA recommends the use of prior survey data in the data collection process. Describe the procedure to use previous airport survey data if available and identify the source of the previous data. If the source of the data is not known or available, verify and document the data set as accurate using the techniques described in Chapter 4.

• Runway Data: Describe in detail the methods for the ground survey and data collection used in identifying, locating, and observing all required runway data.

• Navigational Aid Data: Describe in detail the survey techniques and procedures used to identify, locate, and observe the required navigational aids associated with the airport. Provide details if you will collect the navigational aids individually or grouped by the type of navigational aid (electronic or visual).

• Airport Feature Data: Provide a detailed description of the procedures and methods used for identifying, locating, and observing the required airport feature data associated with the airport. If you plan to use existing data, describe its source, data collection and the techniques used to merge the data sets into a single comprehensive airport data set.

• Equipment and Software Listing: Provide a complete listing of the equipment planned for use in the survey, including model and serial numbers, calibration reports, and equipment maintenance reports. This will include field survey hardware and software.

1.4.1.4 Quality Control Planning. The most important step in a data collection project is ensuring the quality and usability of the data. Data providers must detail in Airports GIS the measures they will use to ensure the collection of high quality data meeting the needs of the airport and the government. Data providers should use a checklist based quality control process with definable and repeatable standards for each element ensuring consistency of work between different personnel within an organization. The Quality Control Plan must include the quality control (including error analysis) procedures and practices followed during data collection and provide traceability and adherence to the requirements of this guidance. At a minimum, the plan will include the following:

• A summary of methods to be used to ensure high-quality data.

• A description of the quality control measures to be used to ensure all data is checked, complete, reliable, and meets the accuracy requirements in this AC.

• Evidence of the methods to be used to collect the various types of features to meet the desired accuracies.

• A description of the data backup and archive procedures and methods to be used to ensure the integrity of the original data.

• An explanation of the methods to be used to check all file formats and a summary of the file-naming convention for all electronic files.

1.4.2 Pre-Survey Preparation Activities.

1.4.2.1 Contact with Airport Authorities. Close communication with airport management is critical throughout the entire data collection process. Make appointments with airport management well in advance to ensure a qualified airport representative is available to discuss the survey. Obtain proper clearances to work in the aircraft operations areas prior to performing any work at an airport. A security and safety briefing may be required before field crews access the airfield. Follow standard safety procedures and equip all vehicles with flashing yellow lights meeting the

requirements of AC 150/5210-5, Painting, Marking and Lighting of Vehicles Used on an Airport, and radios capable of communicating on Air Traffic Control frequencies. Contact with the airport traffic control tower is mandatory during data collection at controlled airports. If vehicles are not properly equipped, an escort is required. Be sure to inquire about off-airport navigational aids and the process for accessing them. Ensure approval to work on or near these sites is received not only from the airport authorities but also the FAA maintenance personnel and any private landowners whose land is adjacent to or near the site. When approaching landowners regarding access, be sure to document their name, contact information and details about the discussions or copies of any correspondence sent or received from the landowners regarding access to their land.

1.4.2.2 Interviews. During the interviews, ask specific questions based on the interview checklists located on the FAA Airports GIS website (https://airports-gis.faa.gov). In addition, discuss with Airport Authority the runway/stopway data published in the latest editions of the Airport/Facility Directory (A/FD) and U.S. Terminal Procedures (TPP), and both U.S. Government Flight Information Publications. Data providers can access these publications free of charge at the following FAA web site https://www.faa.gov/air_traffic/flight_info/aeronav/digital_products/dtpp/. During the project, additional meetings may be required to discuss unusual circumstances, problems, or changes to published or given data. Upon completion of the survey, the airport authorities may require a final meeting. Turn in any badges, passes, or keys; discuss any significant and/or unusual findings with the data collection effort; and notify the airport authorities of your departure. Avoid discussing specific problems since the data is unverified. Especially avoid any statements about approaches being “clear,” because the requirements for the use of the data are different based on the needs of the organizations within the FAA. Smaller airports might not have personnel in all of these areas of expertise or they may not be located at the airport. Complete interviews with the following personnel if possible.

1.4.2.2.1 Airport Manager/Operations. The airport manager/operations is the key individual on the airport. It is important for the data provider to contact the airport management prior to visiting the site. This allows the data provider an opportunity to introduce themselves, their company, and their purpose before arriving at the airport. It also allows the airport manager to prepare other airport staff members and schedules for the field team visit and to gather information the field team may require during their visit. In this interview, obtain permission to enter the airfield for the survey. Use this interview to gather valuable information about recent, ongoing, and future construction, obstruction changes, clearing, and operational considerations (scheduled runway closures or special events, high-

Chapter 1. GENERAL GUIDANCE AND SPECIFICATIONS › 1.5 Data Accuracy.

security areas on the field, etc.). Include the contact information of the airport manager/operations person interviewed on the checklist.

1.4.2.2.2 Airport Engineering. This interview is generally only necessary or helpful at larger airports. The engineering department can provide specific information about runway dimensions, construction projects, and control stations. They can be helpful in scheduling runway work. Include the engineering department Point of Contact (POC) in the final project submission in case questions arise after the survey.

1.4.2.2.3 Air Traffic Control. If an Airport Traffic Control Tower (ATCT) is operational during the time of data collection, discuss the project with the Air Traffic Manager or their designated representative. This interview can provide information on operational factors and facilitate the working relationship between the data provider and the air traffic controllers. Include contact information in the final project submission.

1.4.2.2.4 FAA Technical Operations. An interview with FAA Technical Operations personnel is necessary on any airport with FAA owned and maintained navigational facilities. In some cases, the personnel who maintain the facilities for the airport may be located at another site. If necessary, complete these portions of the interviews by telephone. The first purpose of the interview is to determine all pertinent facilities and changes to navigational aids within 10 nautical miles surrounding the airport. It might also be necessary to schedule a technician to accompany the data provider personnel to certain facilities to let them through a gate or monitor an alarm while collecting data within critical areas of the site. Include the contact information for the assigned FAA Technical Operations POC in the final project submission in case questions arise after the survey.

1.5 Data Accuracy. The data about airports is critical to the operation and safety of the National Airspace System (NAS). Collect this data through a combination of remotely sensed and field survey methods. When determining the best method of collection, consider the required accuracy and efficiency of operations. Remote sensing techniques do not currently meet the accuracy requirements of some airport and aeronautical features, so it is necessary to collect them through field survey. The accuracy for geospatial vector airport features (taxiway, aprons, ramps, buildings, etc.) is typically mapping grade accuracy, usually within 3 feet horizontally and 5 feet vertically (Refer to Chapter 5 for complete accuracy requirements). The required accuracies for many airport features are not achievable using remotely sensed methods and require the use of field survey methods. Specific runway, stopway and navigational aid data accuracies are usually within 1 foot horizontally and 0.25 feet vertically. Accuracy requirements for geospatial features used for geographic

orientation (major highways and roads, lakes, rivers, coastline, and other items of landmark value) are usually 20 feet horizontally and 10 feet vertically relative to the National Spatial Reference System (NSRS). Derived elevations must be within 10 feet vertically. Refer to the appropriate section of this guidance for specific information on the different types of surveys typically performed on or near an airport. In all cases, the geographic coordinate and elevation accuracies of the data must meet or exceed the requirements in this AC and in the following guidance.

1.5.1 Geodetic and Ground Control Data. The control stations established near the airport and used in the collection of the data must meet all accuracy requirements and other criteria specified in AC 150/5300-16. These control stations and their accurate connection to the NSRS ensure accurate relativity between all surveyed points on an airport and the NAS, including navigation satellites.

1.5.2 Remote Sensing. The remote sensing technologies used in the data collection process must meet or exceed the standards, specifications, and accuracy requirements specified in AC 150/5300-17. Ensure the spatial resolution and vertex spacing provides an accurate representation of features without compromising the accuracy of the data. With respect to imagery, this document defines the word “resolution” as the smallest spacing between two display elements, expressed as dots per inch, pixels per line, or lines per millimeter. Also consider the attribute accuracy. Collecting and identifying attributes from imagery requires skill in and knowledge of interpreting airport and aeronautical features. The user must be familiar with the feature classes, attributes, and valid record entries used to identify spatial features contained within this AC.

Features extracted using remote sensing technologies must have spatial accuracies reported in ground distances at the 95-percent confidence level. Use Root-Mean-Square Error (RMSE) to estimate spatial accuracies. Testing is the preferred method of reporting accuracy. Accomplish this by computing RMSE using the square root of the average of the set of squared differences between twenty or more checkpoint coordinate values and the coordinate values from an independent source of higher accuracy. However, if fewer than twenty checkpoints are available for testing, then report the accuracy as a deductive estimate based on knowledge of errors in each production step. Indicate in the final project submission information the methods used in the deductive method including complete calibration tests, and describe assumptions about error propagation.

1.5.3 Raster Imagery. Raster data is a form of spatial data where rectangular cells, each carrying a value, are organized into rows and columns. One of the most common forms of raster data is digital imagery in which each cell or pixel of the image carries a grayscale value in the case of black-and-white photographs or red/green/blue values in the case of color photographs. Images taken from aerial or satellite platforms must be orthorectified, meaning that the cells or pixels of the image are positioned to represent their true position on the face of the earth (i.e., removing distortions caused by camera angle, terrain, etc.). Figure 1-1

Chapter 1. GENERAL GUIDANCE AND SPECIFICATIONS › 1.6 Final Reporting.

provides an example of an orthorectified raster image of an airport. Imagery requirements are specified in AC 150/5300-17.

Figure 1-1. Example of Raster Imagery.

1.6 Final Reporting. Airports GIS provides users the ability to submit data supporting their collection of the data at or for an airport. The final project submission is a compilation of documentation supporting the collection of the data and provides a standardized delivery of field notes, raw survey data and project summary to facilitate the independent verification, validation, and quality assurance of the data. The final project submission addresses each of the following areas.

1.6.1 Project Summary. Provide a written overview of the project details and conclusions. The summary describes the scope of the data collection identifying the key elements of the project (i.e., runway, object identification and analysis, mapping, and navigational aid (NAVAID) collection). Provide background information on the source(s) of existing airport geospatial data (FAA, airport engineering, etc.) used in the project. Describe any conditions affecting the survey such as any equipment failures, weather, scope of project, site accessibility, reconnaissance, and/or any other problems experienced.

1.6.2 Survey Data Conclusions. Provide your conclusions regarding the following subjects as they relate to this project.

Chapter 1. GENERAL GUIDANCE AND SPECIFICATIONS › 1.7 Independent Data Validation and Verification.

1.6.3 Control Network Survey Results/Conclusions. Provide a description of the control network used as the basis of the data collection completed. Include information on the source of the control referenced, whether it was established or verified, and comments on the recovery and status of the control monumentation. When using an existing control network, provide verification computations and results between control points. Also, provide information on the data collection methods used, and the third party software used in data reduction.

1.6.4 Field Survey Data Collection Conclusions. Provide written and, as necessary, pictorial descriptions of significant findings from the survey results to ensure the information being provided is clear to the reader. Include information on the data collection methods used, and identify the hardware/software used during the survey. Examples of typical information to report are (but not limited to):

• Output information, published data comparison for runway end, stopway, and displaced threshold positions.

• Significant objects of concern such as temporary or mobile objects.

• Comments on current or planned construction at the airport that causes concern.

• Conditions that affected the final solutions of the survey (vegetation, access, air traffic, etc.).

• Significant NAVAID situations (proposed locations, instruments/lighting removed, etc.).

• Boundary encroachments or significant misclosures.

• Utility system situations (significant utility systems found otherwise unknown, potentially hazardous situations, etc.).

1.6.5 Data Processing/Adjustment Conclusions. Provide information on the software used to reduce the data. Comment on issues or concerns discovered during the use or translation process of existing data. Also provide comments on any issues or outliers found during the reduction process considered important for the retracement of the data collection by the validation team.

1.6.6 Recommendations/Additional Comments. Provide comments on the survey project including suggestions to improve future work specifications or any information providing additional explanation and understanding of survey project and results. In this section, provide an overview of the pre-survey interviews completed as part of the project preparation.

1.7 Independent Data Validation and Verification. Due to the critical nature of some airport features, the FAA requires independent verification and validation. Typically, these features are those associated with the airport’s movement areas, navigational systems or those affecting flight, such as objects surrounding the airport. Once the independent verification, validation and quality

assurance of the data is completed, the government technical representatives will, through Airports GIS, provide the data provider with a written analysis of their findings including approval or disapproval of the data. Using the functions within Airports GIS, the government technical representatives will identify and list any discrepancies discovered relating to these specifications and decide on the usability of the data. In some cases, data providers may need to provide updates to the data prior to its acceptance by the government. If updates to the data are necessary, only the data requiring updating will require resubmission. Data previously submitted and accepted will already be within the system.

1.7.1 Verification. In this guidance, “verification” is defined as the confirmation by examination and provision of objective evidence that the requirements are fulfilled. Verification is necessary to ensure the data set accurately fulfills the specified requirements and is uncorrupted. The verification process proves the data was properly collected. The following verification techniques compose the government verification of the safety critical data.

• Comparison of a sample of the data set points with samples from an independent measurement system.

• Typically, the government uses photogrammetric analysis along with the provided ground observational data to resample the data set. The more samples checked, the higher the level of confidence in the quality of the data set.

• Comparison of the data set with other existing data sets. For this verification method, the verification must account for the vertical and horizontal reference datums for the data sets and the data sets should be independent. Typically, the government uses this technique when there is an existing good data set to compare the submitted data against.

• Reasonability checks to ensure the data set does not violate known properties (such as: objects must have positive orthometric heights).

1.7.2 Validation. In this guidance, “validation” differs from “verification” in scale. The validation process ensures the aeronautical information submission was correctly developed as an input to the system. Validation is the confirmation by examination and provision of objective evidence showing the data set meets the particular requirements of the intended use. The purpose of the validation process is to demonstrate the data set has sufficient overall integrity to satisfy the requirements for its intended application. Validation answers the questions “is the data reasonable when compared against known data” and “does it meet the identified need.” Validation does not typically compare the data against photogrammetric analysis or review of the observational data.

Chapter 2. SURVEY SPECIFICATIONS AND STANDARDS › 2.2 Geodetic and Ground Control.

SURVEY SPECIFICATIONS AND STANDARDS Chapter 2.

2.1 Introduction. Airports conduct surveys for many reasons. However, all survey types require the collection, classification and reporting of accurate data about the project. All geospatial data collection completed on the airport will provide the information outlined in Chapter 5 within the stated accuracies. The method selected to gather the information is up to the data provider’s judgment. Some features require observation through ground field methods, while others lend themselves to collection via remote sensing technologies. Since each element of the National Airspace System (NAS) ties to a single reference framework, it is important for geospatial data collection conducted on the airport to tie in some way to the National Spatial Reference System (NSRS). When the project uses an engineering grid rather than a national grid, tying the local grid to the NSRS ensures accurate relativity to other NAS elements. This chapter breaks down the different elements of typical airport surveys and provides guidance on completing those tasks. Chapter 5 provides the information on the proper collection, classification and reporting of many airport features.

2.2 Geodetic and Ground Control. Data providers must establish and maintain appropriate ties to the NSRS for all data collection supporting airports or instrument flight procedures. The geodetic and ground control stations established near the airport and their accurate connection to the NSRS ensure accurate relativity between all surveyed points on an airport and the NAS. Data providers must ensure this connectivity by referencing all data to appropriate ground control at the airport. Refer to AC 150/5300-16 for guidance on establishing geodetic control and the NSRS.

2.2.1 Horizontal Control. The data provider will provide horizontal control on the airport referenced to the North American Datum of 1983 (NAD 83) for all data collection activities. Data providers must ensure they are using the most current adjustment of NAD 83. The year of adjustment for all NSRS control stations is on the NGS data sheet next to the latitude and longitude of the station. Data providers must establish and use either permanent or temporary control stations to connect to the NSRS. Establish geodetic and ground control stations according to the standards and specifications of AC 150/5300-16 and NGS. Data providers must identify in the survey plans section of Airports GIS all control stations they plan to use in collecting the data.

2.2.2 Vertical Control. Data providers will provide on airport vertical control referenced to the North American Vertical Datum of 1988 (NAVD 88). Data providers establish and use permanent or temporary control station on the airport to ensure appropriate vertical ties to the NSRS. Data providers can find further information regarding NAVD 88 in AC 150/5300-16 and at the following internet location.

(http://www.ngs.noaa.gov/PUBS_LIB/NAVD88/navd88report.htm). Data providers will reference all ellipsoid heights to NAD 83 (GRS-80) realization.

2.2.3 Geoid Model. The data provider must use the NGS geoid model current at the time of data collection. For further information regarding geoid models refer to the following website: http://www.ngs.noaa.gov.

2.2.4 Airports Requiring Geodetic Control Monumentation. AC 150/5300-16 provides guidance and specifications for data providers in the establishment and submission of geodetic control data. Many airports have existing permanent geodetic control in place. However, if the airport does not, the following information is provided for reference.

2.2.4.1 Permanent Control. FAA Regional Airports Divisions will determine which airports require permanent geodetic control monumentation in the form of PACS or SACS based on the activity (operational or proposed construction) at the airport. However, for all airports in the National Plan of Integrated Airport Systems (NPIAS), we strongly recommend that at least the PACS be established.

2.2.4.2 Temporary Control. Where it is not reasonable from a cost perspective to establish permanent control at the airport, the FAA Regional Airports Division may allow temporary airport control to be established and tied to the NSRS through the use of the NGS Online User Positioning System (OPUS). Data providers should observe the following practices when using the OPUS to establish temporary airport control:

• Establish at least two independent but intervisible marks on an airport as a conformity check and providing for redundant observations.

• Observe each mark in two continuous and independent sessions of at least four hours and submit these observations to the NGS OPUS site at http://www.ngs.noaa.gov/OPUS/.

• Review and follow all other NGS requirements outlined for use of the OPUS.

• Include results of the OPUS sessions in the final project submission information in Airports GIS.

2.2.5 Geodetic and Ground Control Data Format. When submitting newly established permanent ground control data to NGS for inclusion into the NSRS, format this data to meet NGS blue book standards as required by AC 150/5300-16.

Chapter 2. SURVEY SPECIFICATIONS AND STANDARDS › 2.3 Field Survey Operations.

2.2.6 Verification of Existing Survey Marks. Where practical and available, data providers should plan to use existing geodetic and ground control stations. Before use, verify the unmoved position and elevation of the PACS and SACS. The verification of each control station includes:

• Physically visiting each control station to determine its usability and checking its identity;

• Ascertaining its unmoved position;

• Determining its condition, stability, visibility; and

• The submission of recovery information to NGS.

To verify the unmoved position and elevation of an existing control station data providers should make two independent GPS observations, each at least 10 minutes long, with a 5second collection interval, between the PACS and each SACS, or measure the distance between the PACS and each SACS using calibrated electronic distance meter instrument (EDMI), and compare the results to a computed inverse distance. Compute the inverse using either the NGS program INVERS3D (available on the NGS website at http://www.ngs.noaa.gov/TOOLS/) or a comparable commercial product. Compare the newly measured distances or inverse distances (from new observations) against the distances determined from the published positions. Provide the results or the comparisons as part of the observational data in the final project submission information. Obtain elevation checks either from GPS observations or from spirit levels. The distances must agree within 3 cm; the difference in ellipsoidal height must agree to ± 4 cm, and the difference in orthometric height must agree to ± 5 cm or the data must be recollected.

Once the data provider verifies the position and elevation, they should submit a recovery report for the PACS and SACS to the NGS at the following web site: http://www.ngs.noaa.gov/cgi-bin/recvy_entry_www.prl. Verification is not required if the data provider performing the survey also established the monuments by satisfying the requirements of AC 150/5300-16 for the same airport as part of the same project.

2.3 Field Survey Operations.

2.3.1 Preparation. Carefully evaluate the requirements in the statement of work from the Airport Authority or proponent. A careful review of all available data enables the team to begin the survey work in an efficient way and to conduct all necessary preparations and communications. The specific sourced data requirements of each survey require the team to identify potential sources, research the necessary data, and review the requirements of the survey thoroughly. The following list provides information the survey team should review to prepare for the survey. Generally, addressing each item listed below will prepare the survey team to begin the survey:

• Ensure a thorough understanding of the specifications and requirements for the type of survey required. If you are unsure of a requirement, ask the Airport Authority.

Chapter 2. SURVEY SPECIFICATIONS AND STANDARDS › 2.4 Data Collection Supporting Documentation Requirements.

• Review imagery and United States Geological Survey (USGS) quadrangles of the airport (a terrain analysis tool).

• Prepare an imagery acquisition plan that ensures sufficient coverage of the entire survey area.

• Determine areas of private or government property and arrange for access.

• Prepare a list of questions to discuss with the Airport Authority or proponent about the survey.

• Review the descriptions for control stations identified for use in the project.

• Acquire and review an accurate airport diagram for use on the airport.

• Obtain and review all data available from the FAA or the airport for its applicability to the project.

• Coordinate with airport authorities.

• Provide the appropriate planning information through the Airports GIS web site for review and approval.

2.3.2 Data. Airport data collection projects will include identifying and observing accurate positions and elevations for many different airport features. Be sure you understand the requirements of this AC for each type of feature you may encounter during the project. Table 2-1, Survey Requirements Matrix, is a good starting point for determining the data collection requirements for different types of projects. For airport airspace analysis surveys, specific points along runways, runway vertical profiles, positions and elevations of navigational aids, positions and elevations of objects within the Object Identification Surface, and positions and elevations of certain non-obstructing objects are required. For other survey types, data portraying aircraft movement and apron areas, prominent airport buildings, selected roads and other traverse ways, cultural and natural features of landmark value, topography, other miscellaneous features, and special request items could be required. The accuracy of this data must meet the standards published in this guidance.

2.4 Data Collection Supporting Documentation Requirements.

2.4.1 Digital Images from Hand-held Cameras. Provide digital photographs taken during daylight hours to document monuments used or data collected. These photos assist in retracing the data provider’s steps by providing the evaluators with a picture of what the data is describing. Take sufficient photographs to document the conditions encountered. These images should illustrate the appearance, condition, and location of the points of interest, including visibility obstructions, roads, runways, taxiways, or other dangers and any special setup requirements. Use the JPEG (Joint Photographic Experts Group) format for digital images taken with a hand-held digital camera. This includes the required images of photo control points. A photograph

is acceptable if it meets the requirements of this AC and is clear, in focus, and adequately represents the information. Use the highest resolution possible to ensure good clarity and detail definition.

2.4.1.1 Types of Photos. Provide at least one of the following three types of photos to document a position or object. Provide a digital caption and file name as specified in paragraph 2.4.1.2.

• Photograph Type 1 is an extreme close-up of the object as shown in Figure 2-1. Typically, this type of photograph is only used to document control monuments or other defined points such as runway end or displaced threshold locations.

• Photograph Type 2 (Figure 2-2) is taken at eye-level with the station or object 5 to 6 feet in the distance and provides general information about the area immediately surrounding the station or point.

• Photograph Type 3 is taken horizontally with the station approximately 10 to 30 feet in the distance (Figure 2-3). Photograph Type 3 provides general orientation information to the user with a caption including the cardinal direction the camera is pointing in.

Figure 2-1: picture of page 35Figure 2-1 · page 35
Picture of the page from the copy saved here

When documenting navigational aids surveyed, as in Figure 2-4, take two photographs from different cardinal directions. Take the photograph, using a tripod, over the horizontal and vertical (if practical) survey point or electronically add arrows to the photograph showing the point(s) surveyed. The independent verification and validation team uses these photos to confirm the correct point was surveyed based on the type of navigational aid.

Figure 2-1. Photograph Type 1.

Figure 2-2. Photograph Type 2.

Figure 2-3. Photograph Type 3.

Figure 2-4. Illustrates Documentation of a Glideslope Antenna from Different Perspectives.

Location used to define object as an OBSTACLE

Horizontal Survey Point

Vertical Survey Point

Figure 2-4: picture of page 36Figure 2-4 · page 36
Picture of the page from the copy saved here

2.4.1.2 Digital Image File Naming Convention. Use the following file naming convention for photograph filenames. The filename is composed of the airport location identifier assigned by the FAA, runway end designator, photo number, and date, followed by the file type extension, as in the example below. Separate each section of the file name with an underscore —except precede the photo number with a dash. For example, the filename for a runway endpoint at Los Angeles International Airport (LAX) would be LAX_CL_END_RWY_12R-3_04MAY2001.jpg. Decoding the example, “LAX” provides the airport location identifier, “CL_END_RWY_12R” identifies the position photographed such as the centerline end of runway designator [CL=centerline, END=end, RWY= runway, 12=runway number, and R=right (or C=center, or L=left)], dash, “3”= photo number, and date. FAA approved location identifiers are located at the FAA web site http://www.faa.gov/airports_airtraffic/air_traffic/publications/.

2.4.1.3 Digital Image Electronic Caption. For each digital image, provide an electronic caption. The caption should include the following information separated by commas or dashes:

• Airport location identifier assigned by the FAA.

• Runway end designator.

• Photo type number.

• Date the photo was taken.

For example, “LAX, 12R, 3, 23 Aug 2004”. In addition, the caption for photograph types 2 and 3 include the direction (N, NE, E, SE, etc.) the camera is pointing. An example is LAX, 12R, 3NE, 23 Aug 2004.

2.4.2 Documents or Sketches. Provide reports and diagrams, such as Runway End sketches, GPS Visibility Diagrams, Field note sketches, etc., in a non-editable format such as the Adobe Portable Document Format™ (PDF). Obtain these forms from the FAA Airports GIS website (https://airports-gis.faa.gov). The FAA requires field sketches as documentation of the following features as a minimum:

• The selected runway end.

• The location of any displaced threshold.

• The stopway or blastpad associated with a runway.

• New taxiways, ramp (parking) area(s), runways or other construction areas that were not available or completed when the imagery was collected, including sketches or photographs of photo reference points in the imagery. Include a mark or identifying feature available in the imagery relating the construction and the field collection together.

• All NAVAIDS located off the airport (digital photographs are sufficient).

2.4.3 Field Note Information and Data.

2.4.3.1 Geodetic Control Data. Provide the raw-data files containing the observational data used for establishment or verification of the geodetic and ground control, including any data used to plot temporary points occupied. Typically, these files include the original raw GPS data files (in both the manufacturer’s download format and in RINEX II format), binary files containing ionosphere modeling information and vector reduction and adjustment files. If the project required the establishment of new PACS or SACS, this information is already available and does not require duplication here. Provide digital photographs, sketches, and scans of the field book or log sheets supporting the geodetic control survey (including temporary points occupied) as outlined in AC 150/5300-16.

2.4.3.2 Survey Information and Data. Providing the observational data collected during the survey allows the independent verification and validation team to analyze the data. Provide the instrument or data collector raw measurement data files used to compute final positional data. Provide the independent verification and validation team the same information you provide for office computation and compilation. The internal and external quality assurance teams use this information to verify and validate the survey. Provide digital photographs taken during the survey to document or provide clarification of the survey data submitted. These photographs will provide supporting information for follow-on work at the airport, and may include photos of stations occupied, obstructions to visibility or any other information you wish to convey to the FAA and the independent verification and validation team regarding the survey. Scan and include all pages of the log sheets or sketches completed during the survey.

2.4.3.3 Project Execution Guidelines. The tasks completed during the data collection process require careful planning and execution to ensure the geospatial data generated complies with the specifications in this AC. Provided below is a checklist identifying specific items to assist in ensuring proper planning and execution of a successful data collection project. The FAA provides a checklist for the deliverables on the program website at https://airports-gis.faa.gov.

• Complete the necessary planning and ensure you receive the appropriate approvals. If the work deviates from the plan, identify the differences in the final project submission.

• Complete and document the Pre-Survey Preparation Activities outlined in Chapter 1 of this AC.

• Read and fully understand the standards and specifications in this AC. If something is unclear, direct questions to the responsible Airport

District or Regional Office. Having a complete understanding of the requirements and completing them appropriately will reduce the time it takes to validate and verify the data. It will also reduce the amount of rework you may need to complete.

• Get the deliverables checklist from the Airports GIS web site and use it to ensure you are providing all of the required data and supporting documentation.

• Digital Files to be delivered:

o Provide the documentation required for each feature as defined by

the descriptions in Chapter 5. Documentation types include data such as digital photographs, scans of field notes (log sheets, field sketches, field book pages, etc.), and field/office and quality assurance checklists used.

o Provide the raw observational data collected from terrestrial and/or

photogrammetric survey operations in formats identified in these specifications. Providing this data for all surveys allows the independent verification and validation team to retrace the survey. The types of data files to be delivered include, but not limited to:

 Data collector files

 GPS receiver files

 Continuously Operating Reference Station (CORS) data

downloaded

 Photogrammetric observation files

 Other field measurement devices’ digital raw data (range

finder, scanner, etc.)

 Final processing, adjustment or reduction files used to produce

the final data. This includes the results of independent software files produced during the reduction of the final data. The intent is to provide the data necessary to recreate the data delivered if required.

 Airport point of contact list for use by the independent

verification and validation team in the final project submission information.

 Copies of any correspondence and transmittal letters for all

deliveries provided to the Airport Authority or FAA.

• Manage the project to completion including completing the Final Project submission information documenting the data collection project.

Chapter 2. SURVEY SPECIFICATIONS AND STANDARDS › 2.5 Determining the Survey Requirements.

2.5 Determining the Survey Requirements. The following matrix identifies the high level requirements for the different survey types typically encountered at an airport. The matrix is meant as a starting point to help users scope the project appropriately. Airport operators should consult with their local Airports Regional or District Office when scoping a data collection project.

Table 2-1. Survey Requirements Matrix

Row Intended End Use of the Data  AC Reference Category

II or III Operations

Navigational Aid Siting Airport Layout Plan

(ALP)

Construction Instrument

Procedure Development

Pavement

Design, Construction, Rehabilitation or

Roughness

Airport Mapping Database Required Tasks 

Non- Precision

Precision Visual Airside Landside

1 Provide Geodetic Control Plan 150/5300-16 • • • • • • • • • •

2 Provide remote sensing plan 150/5300-17 •

3 Provide a Survey Field Work Plan 150/5300-18 •

4 Provide Quality Control Plan 150/5300-16/17/18 •

5 Establish or validate Airport Geodetic Control 150/5300-16 • • • • • • • •

6 Perform, document and report the tie to National Spatial Reference System (NSRS)

150/5300-16 • • • • • • •

7 Survey runway end(s)/threshold(s) 150/5300-18 • • • • •1 • • •

8 Monument runway end(s)/threshold(s) 150/5300-18 • • • • •1 • •

9 Document runway end(s)/threshold location(s) 150/5300-18 • • • • •1 •1 •1

10 Identify and survey any displaced threshold(s) 150/5300-18 • • • • •1 • • •

11 Monument displaced threshold(s) 150/5300-18 • • • •1 •1 •

12 Document displaced threshold(s) location 150/5300-18 • • • • •1 • • •

13 Determine or validate runway length 150/5300-18 • • •1 • • •

14 Determine or validate runway width 150/5300-18 • • •1 • • •

15 Determine runway profile using 50 foot stations 150/5300-18 • • •1 • •

16 Determine runway profile using 10 foot stations and 10 foot offsets at Part 139 airports

150/5300-18 • • • •1 • • •

17 Determine the touchdown zone elevation (TDZE) 150/5300-18 • • • • •

18 Determine and document the intersection point of all specially prepared hard surface (SPHS) runways

150/5300-18 • • •

19 Determine and document the horizontal extents of any Stopways

150/5300-18 • • • •

20 Determine any Stopway profiles 150/5300-18 • • • •

1 Only when runway construction is involved.

Row Intended End Use of the Data  AC Reference Category

II or III Operations

Navigational Aid Siting Airport Layout Plan

(ALP)

Construction Instrument

Procedure Development

Pavement

Design, Construction, Rehabilitation or

Roughness

Airport Mapping Database Required Tasks 

Non- Precision

Precision Visual Airside Landside

21 Determine if the runway has an associated clearway 150/5300-18 • •

22 Survey clearway to determine objects penetrating the slope

150/5300-18 • • • •

23 Determine and document the taxiway intersection to threshold distance

150/5300-18 •

24 Determine runway true bearing 150/5300-18 • • • • •

25 Determine or validate and document the position of navigational aids

150/5300-18 • • • • • •

26 Determine or validate and document the position of runway abeam points of navigational aids

150/5300-18 • • • •

27 Determine potential navigational aid screening objects 150/5300-18 • • •

28 Identify, classify and provide navigational aid critical areas

AC 150/5300-13,

FAA Order

6750.16

• • • •

29 Collect and document VOR receiver checkpoint location and associated data

150/5300-18 • •

30 Perform or validate and document an airport airspace analysis

150/5300-18 • • • • • •1 •

31 Collect and document helicopter touchdown lift off area (TLOF)

150/5300-18 • • • • • •

32 Collect and document helicopter final approach and takeoff area (FATO)

150/5300-18 • • • • • •

33 Collect or validate and document airport planimetric data 2

150/5300-18 • • • •

34 Determine or validate the elevation of the Air Traffic Control Tower Cab Floor (if one is on the airport)

150/5300-18 • • • • •

35 Perform or validate a topographic survey 150/5300-18 •3 • • • • • •4

36 Collect and document runway and taxiway lighting 150/5300-18 • • •

2 In this guidance, planimetric data is defined as representing airport features that are works of man or natural features within the boundaries of the airport. 3 Only required for the identified Category II and III special topographic survey. 4 For CAT II and III radar altimeter area or if specifically requested.

Row Intended End Use of the Data  AC Reference Category

II or III Operations

Navigational Aid Siting Airport Layout Plan

(ALP)

Construction Instrument

Procedure Development

Pavement

Design, Construction, Rehabilitation or

Roughness

Airport Mapping Database Required Tasks 

Non- Precision

Precision Visual Airside Landside

37 Collect and document parking stand coordinates 150/5300-18 •

38 Collect cultural and natural features of landmark value 150/5300-18 • •

39 Determine elevation of roadways at the intersecting point of the Runway Protection Zone (RPZ)

150/5300-18 • •

40 Determine elevation of roadways at the intersecting point of the 14 CFR part 77, Approach Surfaces, and the runway centerline extended

150/5300-18 •

41 Determine all Land Use to 65 DNL contour 150/5300-18 •

42 Document features requiring digital photographs 150/5300-18 • • • • • • •

43 Document features requiring sketches 150/5300-18 • • • • • • • •

44 Collect position and type of runway markings 150/5300-18 • • •

45 Collect position and type taxiway markings 150/5300-18 • •

46 Locate, collect, and document photo ID points 150/5300-17 • •

47 Identify collect, and document wetlands or environmentally sensitive areas

150/5300-18 •

48 Collect imagery 150/5300-17 • • • •

49 Determine and provide required dimensions 150/5300-18 •

50 Determine and provide required labels for all surfaces 150/5300-18 •

51 Develop, analyze and provide 14 CFR part 77 surfaces 150/5300-18 •

52 Identify and provide water and sewage facilities within lateral limits of 14 CFR part 77 surfaces

150/5300-18 •

53 Develop, analyze, and provide Airport Design Surfaces 150/5300-18 •

54 Identify, classify, and provide the Airport Boundary (existing and future) with easements (fee and simple)

150/5300-18 •

55 Identify, classify, and provide on and off Airport Parcels including easements (existing, future, and ultimate)

150/5300-18 •

56 Identify, classify, and provide all roads and railroads within the lateral limits of the 14 CFR part 77 surfaces

150/5300-18 •

Row Intended End Use of the Data  AC Reference Category

II or III Operations

Navigational Aid Siting Airport Layout Plan

(ALP)

Construction Instrument

Procedure Development

Pavement

Design, Construction, Rehabilitation or

Roughness

Airport Mapping Database Required Tasks 

Non- Precision

Precision Visual Airside Landside

57 Identify, classify and provide all air carrier gate locations

150/5300-18 •

58 Identify, classify and provide all fueling facilities 150/5300-18 •

59 Identify, classify and report all major airport drainage ditches or storm sewers

150/5300-18 •

60 Identify, classify and provide all vehicle parking areas associated with the airport

150/5300-18 •

61 Identify, classify, and provide all special use areas (e.g., agricultural spraying, deicing, or containment, etc.)

150/5300-18 •

62 Identify, classify and provide building restriction line 150/5300-18 •

63 Identify, classify, and provide all security and general purpose fencing and gates (including height AGL). Provide existing and future

150/5300-18 •

64 Identify, classify and provide the Runway Visibility Zone

150/5300-18 •

65 Identify, classify, and provide general aviation development areas

150/5300-18 •

66 Identify, classify, and provide Declared Distances 150/5300-18 • •

67 Identify, classify and provide ground elevation contours and spot elevations

150/5300-18 • •

68 Identify, classify and provide aircraft tie down locations

150/5300-18 •

69 Identify, classify and provide existing and ultimate data as appropriate

150/5300-18 •

70 Identify, classify and provide any objects of landmark value within the approach surfaces e.g., bluffs, rivers, roads, schools, churches, libraries towers, etc.)

150/5300-18 •

71 Identify, classify and provide 50 foot elevation contours on all 14 CFR part 77 sloping surfaces

150/5300-18 •

72 Identify, classify and provide the top elevation (MSL) and height (AGL) for all penetrating objects and representative objects

150/5300-18 • •

Row Intended End Use of the Data  AC Reference Category

II or III Operations

Navigational Aid Siting Airport Layout Plan

(ALP)

Construction Instrument

Procedure Development

Pavement

Design, Construction, Rehabilitation or

Roughness

Airport Mapping Database Required Tasks 

Non- Precision

Precision Visual Airside Landside

73 Identify, classify and provide all representative and penetrating obstacles

150/5300-18 • •

74 Identify, classify and provide all on airport building and include building numbers

150/5300-18 •

75 Airport overlay zoning or zoning restrictions 150/5300-18 •

76 Identify, classify and report all public use facilities (schools, churches, libraries, hospitals, parks, etc.) within the limits of the 14 CFR part 77 surfaces

150/5300-18 •

77 Identify, classify and provide TERPS surfaces evaluated (existing and future)

150/5300-18 •

78 Provide a final project submission information 150/5300-16/18 • • • • • • • • • •

This page intentionally left blank.

2.6 Types of Surveys.

2.6.1 Airport Geodetic Control. Recover (if existing) the Primary Airport Control Station (PACS) and the associated Secondary Airport Control Stations (SACS) at the airport. These marks are typically set at commercial service airports and some high activity general aviation airports. A listing of airports with PACS and SACS and the dates of observation is available from the following National Geodetic Survey (NGS) website http://www.ngs.noaa.gov/cgibin/airports.prl?TYPE=PACSAC. PACS are set to meet high stability standards and positioned to meet high-accuracy standards. SACS have slightly less stringent stability and positioning specifications. Refer to AC 150/5300-16 for full PACS and SACS requirements. Use the established PACS and SACS as starting control for all airside surveys at the airport. When a local control grid is established for engineering purposes, make direct ties to existing control stations with published NSRS coordinates. Existing control should consist of monumented points such as the PACS, SACS, runway ends, displaced thresholds, other published NSRS monuments, etc. Incorporate at least three existing recoverable control stations into the local control network to maintain the airport relative to the NAS. If the PACS and/or either of the SACS are not found, are destroyed, are damaged, or are not usable for some other reason, advise the airport and the responsible FAA Airports Regional or District Office for guidance. The FAA Airport Regional or District Office will review the situation and may seek the guidance or recommendations of government technical representatives before advising the Airport Authority on a path forward.

Chapter 2. SURVEY SPECIFICATIONS AND STANDARDS › 2.6 Types of Surveys.

2.6.2 Runways. This section provides data providers with guidelines for properly identifying the precise survey point for runway ends, displaced thresholds, and stopway ends. It highlights the importance of resolving runway/stopway discrepancies with airport authorities and official U.S. government aeronautical publications. Accurate runway data is critical to aircraft safety. Inaccurate data can result in unnecessary operational limitations or dangerous misassumptions. The positions and elevations of runway/stopway/displaced threshold points are elements used to determine airport design and operation information such as runway length, Accelerate Stop Distance Available (ASDA), Takeoff Distance Available (TODA), Takeoff Run Available (TORA), Landing Distance Available (LDA), runway gradient, and runway bearing, among other data elements. In many cases, the locations of these points are not obvious and the precise survey point selection may not be consistent among surveyors. Figure 2-5 highlights how the placement of survey equipment can result in incorrect data collection. The incorrectly placed survey equipment is located over an outdated or incorrect survey mark and is not placed directly above the actual endpoint of the runway. The correctly placed survey equipment is located within acceptable parameters of the runway end.

Figure 2-5: picture of page 48Figure 2-5 · page 48
Picture of the page from the copy saved here

Figure 2-5. Photograph Highlights How Ground Evidence and Painted Marking

Supporting Features may not be Consistent.

The FAA has issued a series of advisory circulars establishing standards for construction, markings (painting), lighting, signage, and other items pertaining to runways/stopways. Airports certificated under 14 CFR part 139 and Federally obligated airports must comply with the published standards. However, complicating this are situations where the repainting of markings based on runway/stopway changes is delayed, leaving inappropriate painting in place at the time of the data collection. Other situations occur when the airport intends to comply with the AC, but the marking standard is misinterpreted or applied incorrectly. An example of misinterpreted criteria is where the threshold bar is painted on a blast pad adjacent to a runway end rather than on the runway. These guidelines should help data providers correctly identify runway/stopway survey points, not only when standard markings exist, but also in the many cases where a nonstandard situation is encountered.

2.6.2.1 Runway and Stopway Points. The location and orientation of the runway(s) are paramount to the safety, efficiency, economics, and environmental impact of the airport. This section provides guidance on the collection of data regarding the specific features and attributes about the runway, stopway, clearway and displaced threshold (if any). See Figure 2-6. Additionally, it provides guidance on the accurate collection of profile points along the runway. These points support many different areas of airport planning and design as well as other initiatives within the FAA such as instrument flight procedure design. Typically, the runway end, stopway, and displaced threshold positions are collected using GPS or ground-based methods. Since the points are fairly high accuracy points and are used to establish the approach and departure characteristics for the runway, collection using remote sensing technologies is not acceptable.

Provide the runway/stopway data required for a runways and stopways using the Runway, Runway Direction, Stopway, Displaced Threshold and Position (for stopway ends) features in Chapter 5 for all runways and stopways with a specially prepared hard surface (SPHS) existing at the time of the field survey. Use the same features to provide the data for non-specially prepared hard surface (non-SPHS) runways and stopways existing at the time of the field survey and depicted in the current version of the U.S. Government flight information publication U.S. Terminal Procedures. Provide Stopway data and Clearway data using the feature if it is requested by appropriate authorities (FAA, Airport Authority, State Aviation authority). Data providers should refer to and document runways using the number painted on the runway at the time of the field survey. Use the runway number published in U.S. Terminal Procedures (version current at the time of the field survey) if a number is not painted on the runway. Use the FAA Runway Data Sheet to document published data and collected data. Download the form from the FAA Airports GIS website at https://airports-gis.faa.gov.

Figure 2-6. Depicts Some of the Required Points and Elements of a Runway or Stopway.

In order to be a stopway, the area must be officially designated, appropriately marked, and approved as a stopway by the Airport Authority and the FAA. The following points about stopways are important for the data provider to keep in mind:

• A stopway is an area beyond the runway, with sufficient strength to support a decelerating aircraft in all weather conditions. It is not a runway safety area.

• A stopway must be designated as such. This means the airport owner/operator determines that a stopway exists and commits to maintaining the area as a stopway, including the appropriate marking

AIRPORT ELEVATION RUNWAY HIGH POINT

RUNWAY END

RUNWAY END

STOPWAY END

POINT ABEAM OF AN OFFSET NAVAID

SUPPLEMENTAL PROFILE POINT

SUPPLEMENTAL PROFILE POINT RUNWAY LOW POINT

INTERSECTION OF SPECIALLY PREPARED HARD SURFACED RUNWAYS

DISPLACED THRESHOLD

236.3

236.0

235.8

233.1

235.2

237.4

231.2

236.3

234.1

OFFSET NAVAID

PROVIDE POSITIONS AND/OR ELEVATIONS

and lighting (see Figure 2-7). Unless otherwise stated, capture all runway, stopway, and clearway points on the centerline of the runway, stopway, or clearway (as appropriate) being represented.

Figure 2-7. An Example of the Proper Marking for a Blast Pad or Stopway.

NOTES:

50 FOOT [15M] SPACING MAY BE USED WHEN LENGTH OF AREA IS LESS THAN 250 FEET [75M] IN WHICH

CHEVRONS ARE YELLOW AND AT AN ANGLE OF 45° TO THE RUNWAY CENTERLINE.

DIMENSIONS ARE IN: FEET [METERS].

CHEVRON SPACING MAY BE DOUBLED IF LENGTH OF AREA EXCEEDS 1000 FEET [300M]

PAVEMENT EDGE RUNWAY EDGE IS AT OUT BOARD EDGE

OF THRESHOLD BAR

CASE THE FIRST FULL CHEVRON STARTS AT THE INDEX POINT (INTERSECTION OF RUNWAY CENTERLINE AND RUNWAY THRESHOLD).

5 [1.5] MAX

5 [1.5] MAX 100 [30]

100 [30]

50 [15]

50 [15]

STANDARD RUNWAY MARKINGS

3 [0.9] MIN

1.

2.

4.

3.

Figure 2-7: picture of page 51Figure 2-7 · page 51
Picture of the page from the copy saved here

2.6.2.2 Determining the Runway Length and Width. The runway length does not include blast pads or stopway surfaces located at one or both ends of a runway; however, the length of the pavement before a displaced threshold (if there is one) is included in the physical length of the runway. Determine runway lengths from the positions of the runway ends. Determine the runway end positions using the guidance provided in the data capture rules for the Runway Direction feature in Chapter 5.

The runway width is the width extending over the entire length of the rectangle defining the runway surface, or the area within the runway side stripes if the full pavement width is not available as a runway. Determine the width of the runway by measuring the width as a line perpendicular to the defined runway centerline. Where the runway has painted runway edge markings measure the width to the outer edge (shoulder side) of the markings. If the runway does not have painted runway edge markings, measure from pavement edge to pavement edge at multiple places and report the narrowest dimension. Measure and record runway widths to the nearest whole foot and include the dimension on the runway end sketch. If the runway width is less than 100 feet, report the value to the nearest 5 foot increment. If the runway width is greater than 100 feet, report the width to the nearest 10 foot increment. If the determined dimensions of the runway, displaced threshold, stopway, or blast pad dimensions do not agree with the information published for the airport, discuss the discrepancies with the airport manager or designated representative and attempt to resolve any discrepancies before departing the site. If the discrepancy cannot be resolved, note the discrepancy and document the discussions with the airport officials in the final project submission information for review by the independent data validation and verification team and resolution by the FAA with the Airport Authority.

Determine and provide the runway bearing from true North to the nearest thousandth (0.001) of a degree between the physical runway ends. Compute the runway true bearing inverse using either the NGS program INVERS3D (available on the NGS website at http://www.ngs.noaa.gov/TOOLS/), the Geographic Calculator available through Airports GIS or a comparable commercial product. Document the runway true bearing in the appropriate attribute in the Runway Direction feature. Determine and report the true bearing for each runway direction.

2.6.2.3 Displaced Thresholds. On some runways, the threshold is displaced due to objects in the approach area penetrating the threshold siting surface, for example, or to meet runway safety area length requirements where the airport is constrained. When a displaced threshold is encountered it must be identified (see Figure 2-8), classified, and documented (see Supporting Documentation information in the data capture rules in Chapter 5 for documentation requirements) similarly to a runway end. In FAA Airports GIS, a displaced threshold is modeled using the

Figure 2-8: picture of page 53Figure 2-8 · page 53
Picture of the page from the copy saved here

Displaced Threshold feature with a value in the POSITIONROLECODE of Displaced Threshold.

Figure 2-8. Illustrates the Proper Marking of a Displaced Threshold.

100 [30]

120 [36]

80 [24M] 20 [6M]

STD RUNWAY MKG

5 [1.5M]

10 [3M] WIDE WHITE THRESHOLD BAR

RUNWAY THRESHOLD

200 [65M]

3 [1M] EDGE TO EDGE

5 [1.5M]

45 [13.5M]

15 [4.5M]

3 [1M]

5 [1.5M]

TAIL

HEAD

80 [24M]

NOTES:

RUNWAY SIDE STRIPES,

RUNWAY MARKINGS

DIMENSIONS ARE IN:

WIDTH

100 [30M]

100 [30M]

60 [32M]

1.

2.

3.

ARROWHEADS

4

3

2

ARROWHEADS

W/4

W/3

W/2

RUNWAY EDGE

W/8

W/6

W/4

RUNWAY NUMBER OF SPACING BETWEEN SPACING TO

(W = RUNWAY WIDTH)

FEET [METERS]

ARE WHITE. DISPLACED THRESHOLD INCLUDING THOSE IN THE

(EXCEPT HOLDING

POSITION MARKINGS)

THE DISPLACED AREA.

WHEN USED ON THE

RUNWAY, EXTEND INTO

2.6.2.4 Establishing the Runway Endpoint. Use existing FAA or airport provided runway endpoint data to assist in locating the points identifying the threshold (physical or displaced) of the runway. The data capture rules for the Runway Direction feature provides detailed identification descriptions; additionally, Appendix B provides clarifying guidance. Recover, verify or establish and document the following points (see Figure 2-6) using the appropriate feature from Chapter 5.

• Runway endpoints – using the Runway Direction feature

• Displaced threshold points – using the Displaced Threshold feature

• Clearway endpoints – using the Position feature

• Stopway endpoints – using the Position and Stopway features

• Runway High and Low points – using the Position feature

• Touchdown Zone Elevation – using the Position feature

• Intersection of two runway centerlines – using the Position feature

• Points abeam offset navigational aids – using the Position feature

Figure 2-9. Illustrates the Use of Day Markers to Define the End of a Runway.

Figure 2-9: picture of page 54Figure 2-9 · page 54
Picture of the page from the copy saved here

2.6.2.5 Location of Specific Survey Points. The locations of the following runway and stopway survey points are defined by the intersection of the runway or stopway centerline and one of the indicated survey point locators as detailed in the data capture rules for the feature in Chapter 5. When the survey point is determined, the selection of the point is solidified through the use of various supporting features. Occasionally, a supporting feature will conflict with the selected survey point or another supporting feature. If this occurs, resolve the conflicts before leaving the airport. For example, a runway number may be located near the end of the pavement, but threshold lights and a threshold bar are located down

the runway at an apparent displaced threshold. Discuss the conflict with airport authorities and, if necessary, contact the appropriate FAA Airports Regional or District Office for assistance. In the feature descriptions (see Chapter 5), reference is made to inboard or outboard threshold and runway end lights. These terms are defined in Appendix A. If light units or day markers are used to construct the trim line defining a survey point, as in the case of a runway end with an aligned taxiway, use the two units nearest to the runway (one light on each side of the runway). Always define the trim line perpendicular to the runway centerline. If a line connecting the lights (or markers if the runway is unlighted) is not perpendicular to the runway centerline, then the trim line must be best fit to the defining lights or markers.

2.6.2.6 Runway and Stopway Profiles. The runway profile provides information about the runway gradient, establishes the airport elevation, runway high and low points, the touchdown zone elevation(s), and supports runway pavement roughness studies. Collect runway profile data along the runway centerline at 50-foot stations. Additionally, at airports certificated under 14 CFR part 139 collect runway centerline profiles at 10-foot stations and two additional profiles offset 10 feet on both sides of the centerline. Collect the runway or stopway profiles beginning and ending on the runway ends. Each point collected in the profile should be accurate to within 0.5 inches relative to its adjacent points and modeled using the Position feature in Chapter 5. Identify the points in the Point Role Code attribute as centerline_point.

Continue reading ↓ 120 of 913 passages shown