AC 150/5300-18B General Guidance and Specifications for Submission of Aeronautical Surveys to NGS: Field Data Collection and Geographic Information System (GIS) Standards
Provides the specifications for the collection of airport data for the FAA Airport Surveying – Geographic Information System (GIS) Program. Also explains how to submit data to the FAA, which will forward the safety critical data to the National Geodetic Survey (NGS) for independent verification and validation. The standards covered in this document provide critical information for the operation and safety of the National Airspace System (NAS) and are classified as critical by the International Civil Aviation Organization (ICAO). ICAO Annex 15 defines data as critical when “there is a high probability when using corrupted critical data that the continued safe flight and landing of an aircraft would be severely at risk with the potential for catastrophe.” The information furnished under these standards covers the entire spectrum of the FAA’s airport data requirements. See also Airport Data and Information Portal (ADIP). Note: We have re-activated this AC until further notice. Please see the letter cancelling AC 150/5300-18C and re-activating AC 150/5300-18B.
Advisory
Circular
U.S. Department .of Transportation
Federal Aviation Administration
Subject: General Guidance and Specifications for
Submission ofAeronautical Surveys toNGS: Field Data Collection and Geographic Information
System (GIS) Standards
Date: 2/24/2014 Initiated by: AAS-1 00
AC No: 150/5300-ISB Change: 1
1. What is the purpose of this advisory circular (AC)?
This change incorporates updated airport data collection standards and deletes outdated information. These changes clarify airport data collection and ongoing Airports GIS and other system enhancements.
2. What are the principal changes in this change?
Vertical bars in the margins ofthe attached consolidated AC indicate the text revised in this change. We have not indicated the change number or change date in the headers ofrevised pages. See the Record of Changes at the end ofthis document for a log ofthe revisions made in this Change. Principal changes include:
a. Updates to Computer-Aided Design (CAD) standard guidelines - specifically line types,
lineweights, and color defmitions - to align with the National CAD Standard and FAA-STD 002g.
b. Deletion ofData Migration Tool (DMT).
c. The addition ofFAA standard symbols as published in the Terminal Procedures Publications.
d. Values updates to maintain consistency with other aeronautical information standards such as
Aeronautical Information Exchange Model (AIXM).
e. Minor editorial corrections.
f. The Record ofChanges at the end ofthis consolidated AC. This record lists and describes each
change by paragraph or item number.
g.
Michael • O'Donnell Director ofAirport Safety and Standards
AC 150/5300-18B CHG1 2/24/2014
ii
Intentionally left blank.
U.S. Department of Transportation Federal Aviation Administration
Advisory Circular
Consolidated AC includes Change 1
Subject: General Guidance and Specifications for Submission of Aeronautical Surveys to NGS: Field Data Collection and Geographic Information System (GIS) Standards
Date: 05/21/2009 Initiated by: AAS-100
AC No: 150/5300-18B
1. PURPOSE: 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, who will forward the safety critical data to the National Geodetic Survey (NGS) for independent verification and validation. The primary purpose of these general guidelines and specifications is to list the 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 International Civil Aviation Organization (ICAO) classifies these standards as critical. ICAO Annex 15 defines data as critical when “there is a high probability when using corrupted critical data that the continued safe flight and landing of an aircraft would be severely at risk with the potential for catastrophe.” 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 source data, acquired by field survey and/or remote sensing methods.
2. CANCELLATION: AC 150/5300-18A, General Guidance and Specifications for Submission of Aeronautical Surveys to NGS: Field Data Collection and Geographic Information System (GIS) Standards, dated 9/15/2007, is cancelled.
3. PRINCIPAL CHANGES. The substantial revision of this AC incorporates new standards addressing the collection of a greater spectrum of airport related data and is reformatted to provide better understanding. Users should review the entire document to familiarize themselves with the new format.
4. APPLICATION: 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 Title 14 Code of Federal Regulations (CFR) Part 139, Certification of Airports for the collection of geospatial airport and aeronautical data. Mandatory terms such as "shall" or "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.
ii
5. COMMENTS OR SUGGESTIONS for improvements to this AC should be sent to:
Manager, Airport Engineering Division Federal Aviation Administration ATTN: AAS-100 800 Independence Avenue, S.W. Washington, DC 20591
6. COPIES OF THIS AC. This and other FAA ACs are available online at http://www.faa.gov/regulations_policies/advisory_circulars/.
Michael J. O’Donnell Director of Airport Safety and Standards
iii
TABLE OF CONTENTS
CHAPTER 1. GENERAL GUIDANCE AND SPECIFICATIONS … 1
1.1. INTRODUCTION … 1 1.2. ADMINISTRATION … 1 1.2.1. Specifications … 1 1.2.2. Conventions … 1 1.3. CONTRACTOR REQUIREMENTS … 2 1.3.1. Maintenance and Calibration … 2 1.3.2. Original Data … 2 1.3.3. Corrections or Revisions to Data … 3 1.3.4. Unusual Circumstances … 3 1.3.5. Specification Review and Familiarity … 3 1.4. NATIONAL SPATIAL REFERENCE SYSTEM (NSRS) … 3 1.4.1. Horizontal Control … 3 1.4.2. Vertical Reference … 3 1.4.3. GEOID Model … 3 1.5. DATA FORMATS … 4 1.5.1. Ground Control Data … 4 1.5.2. Digital Images from Hand-Held Camera … 4 1.5.3. Documents or Sketches … 6 1.5.4. Geospatial Vector Files … 7 1.5.5. ESRI Nuances for Dealing with FAA Attribute Names … 7 1.5.6. Airport Layout Plan Data … 8 1.5.7. Raster Imagery … 8
CHAPTER 2. SURVEY SPECIFICATIONS AND STANDARDS … 9
2.1. OVERVIEW OF THE PROCESS … 9 2.2. INDEPENDENT VERIFICATION AND VALIDATION OF AIRPORT SAFETY DATA. ... 9 2.2.1. Verification … 9 2.2.2. Validation … 10 2.3. ACCURACY REQUIREMENTS … 10 2.3.1. Geodetic Control … 10 2.3.2. Imagery … 10 2.3.3. Remotely Sensed Surveys … 10 2.3.4. Feature Accuracy Requirements … 11 2.3.5. Field Surveys … 11 2.4. RESERVED … 11 2.5. FEATURE ATTRIBUTION … 11 2.6. REPORTING REQUIREMENTS … 12 2.6.1. General Reporting Requirements … 12 2.6.2. Survey and Quality Control Plan … 12 2.6.3. Project Status Report … 14 2.6.4. Final Project Report … 14 2.6.5. Field Note Information and Data … 16 2.6.6. Deliverables Checklist … 16 2.6.7. Pre-Survey Preparation Activities … 17 2.6.8. Field Survey Operations … 18 2.6.9. Determining the Survey Requirements … 19 2.6.10. Types of Airport Survey Projects … 23 2.7. AIRPORT AIRSPACE ANALYSIS SURVEYS … 34
iv
2.7.1. Airport Airspace Survey Surfaces and Analysis … 35 2.8. ONE ENGINE INOPERATIVE (OEI) ANALYSIS SURVEY REQUIREMENTS … 50 2.9. TOPOGRAPHIC SURVEYING … 51 2.9.1. Category II and III Operation Area Topographic Survey. … 53 2.10. AIRPORT MAPPING DATABASE SURVEYS … 55 2.11. ENGINEERING (CONSTRUCTION) SURVEYS … 58 2.12. AIRPORT PAVEMENTS … 59 2.12.1. Construction/Roughness … 59 2.12.2. Airport Pavement Inventory … 59 2.13. SUB-SURFACE UTILITIES ENGINEERING (SUE) … 60 2.13.1. Utility Research … 61 2.13.2. Utility Designation … 62 2.13.3. Utility Field Collection … 63 2.13.4. Optional SUE Quality Level A Testholes … 63 2.14. BOUNDARY SURVEYING/LAND USE … 63 2.14.1. Research and Investigation … 63 2.14.2. Monumentation … 64 2.14.3. Measurement specifications … 64 2.14.4. Plat of survey … 65
CHAPTER 3. GEOSPATIAL SPECIFICATIONS AND STANDARDS … 67
3.1. OVERVIEW … 67 3.2. ADVANTAGES OF DATA COMPLIANCE … 67 3.3. RELATIONSHIP OF GIS FEATURES TO CADD LAYERS … 67 3.3.1. Layering of Feature Types … 67 3.3.2. Feature Type Layering in GIS Software … 68 3.3.3. Relationship of GIS and CADD Layers … 69 3.3.4. Feature Type Layering in CADD Software … 69 3.4. GEOMETRIC REQUIREMENTS … 71 3.4.1. Feature Types … 71 3.4.2. Geometry … 71 3.4.3. Topological Integrity … 72 3.5. ATTRIBUTES … 75 3.5.1. Domain Values … 76 3.6. METADATA … 76 3.6.1. Temporal Relevance … 77 3.6.2. Accuracy … 77 3.6.3. Security Sensitivity Levels … 78 3.7. COORDINATE SYSTEMS … 79 3.7.1. Acceptable Coordinate Systems … 79 3.7.2. Acceptable Datum … 79
CHAPTER 4. DATA TRANSLATION AND USE OF EXISTING DATA … 81
4.1. USE OF EXISTING DATA … 81 4.1.1. Verifying the Quality of Existing Data … 82 4.1.2. Maintenance of Data … 83 4.1.3. Safety Critical Data … 83 4.2. PREPARING YOUR DATA FOR SUBMISSION TO THE FAA … 84
CHAPTER 5. AIRPORT DATA FEATURES … 85
5.1. FEATURE DOCUMENTATION MINIMUMS … 85
v
5.2. MULTIPLE INSTANCES OF FEATURES … 85 5.3. FEATURE CLASS DESCRIPTION LEGEND … 85 5.3.1. Paragraph Number and FeatureClassName … 85 5.4. GROUP: AIRFIELD … 86 5.4.1. Aircraft Gate Stand … 86 5.4.2. Aircraft Non Movement Area … 88 5.4.3. Air Operations Area … 89 5.4.4. Airfield Light … 90 5.4.5. ArrestingGear … 92 5.4.6. Frequency Area … 93 5.4.7. Passenger Loading Bridge … 94 5.4.8. Runway Centerline … 95 5.4.9. Runway Helipad Design Surface … 96 5.4.10. Runway Intersection … 97 5.4.11. Runway LAHSO … 99 5.4.12. Runway Element … 100 5.4.13. Stopway … 102 5.4.14. Taxiway Holding Position … 104 5.4.15. Airport Sign … 105 5.4.16. Apron … 107 5.4.17. Deicing Area … 109 5.4.18. Touch Down Lift Off … 110 5.4.19. Marking Area … 112 5.4.20. Marking Line … 113 5.4.21. Movement Area … 115 5.4.22. Runway … 116 5.4.23. Restricted Access Boundary … 117 5.4.24. Runway Arresting Area … 119 5.4.25. Runway Blast Pad … 121 5.4.26. Runway End … 122 5.4.27. Runway Label … 129 5.4.28. Runway Safety Area Boundary … 130 5.4.29. Shoulder … 131 5.4.30. Taxiway Intersection … 134 5.4.31. Taxiway Element … 135 5.5. GROUP: AIRSPACE … 137 5.5.1. Landmark Segment … 137 5.5.2. Obstacle … 138 5.5.3. Obstruction Area … 141 5.5.4. Obstruction Identification Surface … 145 5.5.5. Runway Protect Area … 146 5.6. GROUP: CADASTRAL … 147 5.6.1. Airport Boundary … 147 5.6.2. Airport Parcel … 149 5.6.3. County … 150 5.6.4. Easements And Rights of Ways … 151 5.6.5. FAA Region Area … 152 5.6.6. Land Use … 153 5.6.7. Lease Zone … 154 5.6.8. Municipality … 155 5.6.9. Parcel … 156
vi
5.6.10. State … 157 5.6.11. Zoning … 158 5.7. GROUP: ENVIRONMENTAL … 159 5.7.1. Environmental Contamination Area … 159 5.7.2. Fauna Hazard Area … 160 5.7.3. Flood Zone … 161 5.7.4. Flora Species Site … 162 5.7.5. Forest Stand Area … 163 5.7.6. Hazardous Material Storage Site … 164 5.7.7. Noise Contour … 165 5.7.8. Noise Incident … 166 5.7.9. Noise Monitoring Point … 167 5.7.10. Sample Collection Point … 168 5.7.11. Shoreline … 169 5.7.12. Wetland … 170 5.8. GROUP: GEOSPATIAL … 171 5.8.1. Airport Control Point – Runway Intersection Point … 171 5.8.2. Airport Control Point – Airport Elevation … 173 5.8.3. Airport Control Point – Centerline Perpendicular Points … 174 5.8.4. Airport Control Point – Displaced Threshold Point … 175 5.8.5. Airport Control Point – Stopway Ends … 179 5.8.6. Airport Control Point – Profile Points … 182 5.8.7. Airport Control Point – Touchdown Zone Elevation (TDZE) … 183 5.8.8. Airport Control Point – Primary and Secondary Airport Control Stations (PACS/SACS) … 185 5.8.9. Coordinate Grid Area … 186 5.8.10. Elevation Contour … 188 5.8.11. Image Area … 189 5.9.
GROUP: MAN MADE STRUCTURES … 190 5.9.1. Building … 190 5.9.2. Construction Area … 192 5.9.3. Roof … 195 5.9.4. Fence … 196 5.9.5. Gate … 197 5.9.6. Tower … 198 5.10. GROUP: NAVIGATIONAL AIDS … 199 5.10.1. NAVAID Critical Area … 200 5.10.2. Navaid Equipment – Airport Beacon (APBN) … 204 5.10.3. Navaid Equipment – Air Route Surveillance Radar (ARSR) or Airport Surveillance Radar (ASR) … 206 5.10.4. Navaid Equipment – Approach Light System (ALS) … 209 5.10.5. Navaid Equipment – Back Course Marker (BCM) … 218 5.10.6. Navaid Equipment – Distance Measuring Equipment (DME) … 220 5.10.7. Navaid Equipment –Glide Slope – End Fire (GS) … 223 5.10.8. Navaid Equipment – Fan Marker (FM) … 226 5.10.9. Navaid Equipment – Glideslope (GS) … 228 5.10.10. Navaid Equipment – Ground Controlled Approach (GCA) Touchdown Reflectors … 230 5.10.11. Navaid Equipment – Inner Marker (IM) … 233 5.10.12. Navaid Equipment – Localizer (LOC) … 236 5.10.13. Navaid Equipment – Localizer Type Directional Aid (LDA) … 239
vii
5.10.14. Navaid Equipment – Middle Marker (MM) … 241 5.10.15. Navaid Equipment – MLS Azimuth Antenna (MLSAZ) … 244 5.10.16. Navaid Equipment – MLS Elevation Antenna (MLSEZ) … 246 5.10.17. Navaid Equipment – Non-Directional Beacon (NDB) … 249 5.10.18. Navaid Equipment – Outer Marker (OM) … 252 5.10.19. Navaid Equipment – Precision Approach Path Indicator (PAPI) System … 255 5.10.20. Navaid Equipment – Precision Approach Radar (PAR) Touchdown Reflectors … 259 5.10.21. Navaid Equipment – Pulse Light Approach Slope Indicator (PLASI) System . 261 5.10.22. Navaid Equipment – Pulsating Visual Approach Slope Indicator (PVASI) … 263 5.10.23. Navaid Equipment – Runway End Identifier Lights (REIL) … 266 5.10.24. Navaid Equipment – Simplified Directional Facility (SDF) … 269 5.10.25. Navaid Equipment – Tactical Air Navigation (TACAN) … 271 5.10.26. Navaid Equipment – Tricolor Visual Approach Slope Indicator System (TRCV) … 274 5.10.27. Navaid Equipment – “T” Visual Approach Slope Indicator System (T-VASI) 276 5.10.28. Navaid Equipment – VHF Omni Directional Range (VOR) … 279 5.10.29.
Navaid Equipment – Visual Approach Slope Indicator System (VASI) … 281 5.10.30. Navaid Equipment – VOR/TACAN (VORTAC) … 284 5.10.31. NAVAID Site … 286 5.11. GROUP: SEAPLANE … 287 5.11.1. Water Operating Area … 287 5.11.2. Water Lane End … 290 5.11.3. Taxi Channel … 292 5.11.4. Turning Basin … 293 5.11.5. Navigation Buoy … 295 5.11.6. Seaplane Ramp Centerline … 296 5.11.7. Seaplane Ramp Site … 297 5.11.8. Docking Area … 298 5.11.9. Anchorage Area … 300 5.12. GROUP: SECURITY … 303 5.12.1. Security Area … 303 5.12.2. Security Identification Display Area … 304 5.12.3. Security Perimeter Line … 305 5.12.4. Sterile Area … 306 5.13. GROUP: SURFACE TRANSPORTATION … 307 5.13.1. Bridge … 307 5.13.2. Driveway Area … 308 5.13.3. Driveway Centerline … 309 5.13.4. Parking Lot … 310 5.13.5. Railroad Centerline … 311 5.13.6. Railroad Yard … 312 5.13.7. Road Centerline … 313 5.13.8. Road Point … 314 5.13.9. Road Segment … 315 5.13.10. Sidewalk … 316 5.13.11. Tunnel … 317 5.14. GROUP: UTILITIES … 319 5.14.1. Tank Site … 319 5.14.2. Utility Line … 320 5.14.3. Utility Point … 323
viii
5.14.4. Utility Polygon … 340 5.15. ATTRIBUTE ENUMERATIONS … 341 5.15.1. CodeAcqusitionType … 341 5.15.2. CodeAirportFacilityType … 341 5.15.3. CodeApproachCategory … 342 5.15.4. CodeApproachGuidance … 342 5.15.5. CodeApronType … 342 5.15.6. CodeBridgeType … 343 5.15.7. CodeBuoyType … 343 5.15.8. CodeClassAirspace … 343 5.15.9. CodeColor … 344 5.15.10. CodeCompassLocation … 345 5.15.11. CodeCoordinatedUseType … 345 5.15.12. CodeCoordinateZone … 345 5.15.13. CodeDesignGroup … 365 5.15.14. CodeDesignSurfaceType … 365 5.15.15. CodeDirectionality … 366 5.15.16. CodeFaaRegion … 366 5.15.17. CodeFuel … 366 5.15.18. CodeGateStandType … 367 5.15.19. CodeGridType … 367 5.15.20. CodeHazardCategory … 368 5.15.21. CodeHazardType … 370 5.15.22. CodeHowAcquired … 370 5.15.23. CodeLandmarkType … 370 5.15.24. CodeLandUseType … 371 5.15.25. CodeLightingConfigurationType … 374 5.15.26. CodeLoadingBridgeType … 376 5.15.27. CodeLowVisibilityCategory … 376 5.15.28. CodeMarkingFeatureType … 376 5.15.29. CodeMonumentType … 378 5.15.30. CodeNavaidEquipmentType … 379 5.15.31.
CodeNavaidSystemType … 381 5.15.32. CodeObstacleSource … 381 5.15.33. CodeObstacleType … 381 5.15.34. CodeObstructionAreaType … 384 5.15.35. CodeOffsetDirection … 384 5.15.36. CodeOisSurfaceCondition … 384 5.15.37. CodeOisSurfaceType … 384 5.15.38. CodeOisZoneType … 385 5.15.39. CodeOperationsType … 385 5.15.40. CodeOwner … 385 5.15.41. CodePointType … 386 5.15.42. CodeProjectStatus … 386 5.15.43. CodeRecoveredCondition … 386 5.15.44. CodeRouteType … 387 5.15.45. CodeRunwayProtectionAreaType … 388 5.15.46. CodeSamplePointLocation … 388 5.15.47. CodeSegmentType … 388 5.15.48. CodeShorelineType … 388 5.15.49. CodeShoulderType … 389
ix
5.15.50. CodeSignTypeCode … 389 5.15.51. CodeStatus … 390 5.15.52. CodeStructureType … 391 5.15.53. CodeSurfaceCondition … 392 5.15.54. CodeSurfaceMaterial … 392 5.15.55. CodeSurfaceType … 393 5.15.56. CodeTaxiwayType … 393 5.15.57. CodeThresholdType … 394 5.15.58. CodeUseCode … 394 5.15.59. CodeUtilityType … 394 5.15.60. CodeVerticalStructureMaterial … 395 5.15.61. CodeZoneType … 397 5.15.62. CodeZoningClass … 397 5.16. COMPATIBILITY WITH FAA-STD-002 … 397
APPENDIX A. ADDITIONAL REFERENCES, GLOSSARY AND ACRONYMS … 403
A.1. REFERENCES AND PROJECT MATERIALS TO REVIEW … 403 A.1.1 APPROPRIATE PAGES FROM U.S. TERMINAL PROCEDURES … 403 A.1.2. APPROPRIATE PAGES FROM AIRPORT/FACILITY DIRECTORY … 404 A.1.3. FAA NATIONAL FLIGHT DATA DIGEST (NFDD) … 404 A.1.4. FAA FORM 5010, AIRPORT MASTER RECORD … 404 A.2. GLOSSARY … 405 A.3. ACRONYMS AND WORD PHRASES … 419
APPENDIX B. AERONAUTICAL SURVEY GUIDANCE AND SPECIFICATIONS … 431
B.1. AIRPORT REFERENCE POINT (ARP) COMPUTATION … 431
APPENDIX C. RUNWAY, STOPWAY, AND DISPLACED THRESHOLD END IDENTIFCATION AND MONUMENTATION … 435
C.1. RUNWAY, STOPWAY, AND DISPLACED THRESHOLD END IDENTIFCATION AND MONUMENTATION … 435 C.1.1. Terminology … 435 C.1.2. Features Associated With Runway/Stopway Usage and Survey Point Location … 435
APPENDIX D. TRUNCATED ATTRIBUTE VALUES TO BE USED WITH ESRI® SHAPEFILES … 443
RECORD OF CHANGES … 463
LIST OF FIGURES
Figure 1-1. Photograph type 1 … 4 Figure 1-2. Photograph type 2 … 5 Figure 1-3. Photograph type 3 … 5 Figure 1-4. Illustrates the documentation of a glideslope antenna from different perspectives … 5 Figure 1-5. Example of Raster Imagery … 8 Figure 2-1. Examples of incorrect and correct survey equipment placement … 24 Figure 2-2. Depicts some of the required points and elements of a runway or stopway … 26 Figure 2-3. An example of the proper marking for a blast pad or stopway … 27
x
Figure 1-1 · page 11Picture of the page from the copy saved here
Figure 2-4. Standards for marking of runway shoulders … 28 Figure 2-5. Illustrates the proper marking of a displaced threshold … 29 Figure 2-6. This photo illustrates how lights used at airports assist the landing pilot … 32 Figure 2-7. Illustrates the dimensional criteria associated with the VGATS and the connection to the
VGPCS … 36 Figure 2-8. Illustrates the areas, dimensions, and slopes of the Vertically Guided Approach Survey and
Analysis Specification required to support instrument procedure development … 37 Figure 2-9. Object Representation in the VGRPS Area … 38 Figure 2-10. Illustrates the VGRPS and VGPCS object representations … 39 Figure 2-11. SAWS, AWOS and ASOS Station Installations … 40 Figure 2-12. The area outlined in blue illustrates the lateral limits of the VGAS … 41 Figure 2-13. Illustrates the VGATS divided into four (4) sections for analysis … 41 Figure 2-14. Illustrates dividing the VGHS into quadrants through the ARP … 42 Figure 2-15. NVGPS, NVGAS, and NVGTS Types 1/2/3 for Non-Vertically Guided (NVG) Airport
Figure 2-4 · page 12Picture of the page from the copy saved here
Surfaces … 44 Figure 2-16. Horizontal Surface (NVGHS) for Non-Vertically Guided (NVG) Airport Surfaces … 45 Figure 2-17. Object Representation in the non-vertically guided operations primary surface area … 46 Figure 2-18. Reporting highest object(s) within ObstructionArea limits … 47 Figure 2-19. This picture illustrates the importance of appropriately identifying catenaries … 48 Figure 2-20. Illustrates the collection of penetrating vessel and mobile object areas … 49 Figure 2-21. Illustrates the OEI object evaluation area and dimensions … 51 Figure 2-22. Terrain data collection surface – Area 4 … 54 Figure 2-23. Paper chart … 55 Figure 2-24. The development of highly accurate digital representations of the airport environment will
enhance the operational safety systems at the airport … 55 Figure 2-25. Highly accurate digital representations of the airport environment … 56 Figure 2-26. Areas of collection for vertical objects surrounding the movement areas … 57 Figure 2-27. Airport Mapping Database Collection of Vertical objects meeting the requirements of ICAO
Figure 2-16 · page 12Picture of the page from the copy saved here
Area 3 … 57 Figure 2-28. Uniform Color Codes … 62 Figure 3-1. Portrays the layering of feature types to form a map or drawing … 68 Figure 3-2. Format of CADD Layer Names … 69 Figure 3-3. Typical depiction of a series of points … 71 Figure 3-4. Illustrates examples of a line … 71 Figure 3-5. Depicts some typical polygon examples … 72 Figure 3-6. Depicts the topology rules for line segments … 73 Figure 3-7. Depicting the placement of vertices along a curve … 73 Figure 3-8. Illustrates the shared edges and shared vertices topological rule … 74 Figure 3-9. Depicts an example of the placement of vertices of adjacent polygons with misplaced
Figure 2-28 · page 12Picture of the page from the copy saved here
vertices … 74 Figure 3-10. Illustrates the topological rule of overlapping polygons of the same feature type … 75 Figure 3-11. Illustrates the difference between closed and unclosed polygons … 75 Figure 3-12. Sample Attribute Table for a Feature Type … 76 Figure 3-13. MetaData elements have different levels of aggregation … 77 Figure C-1. Depicts the proper marking of a threshold bar … 437 Figure C-2. Overhead view of a threshold light, which are typically flush mounted with the runway
surface … 439 Figure C-3. Typical elevated runway or taxiway edge light with the blue taxiway lens installed … 439 Figure C-4. Typical installation of the runway end identification light (REIL) with the horizontal and
VSPs identified … 440
xi
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 … 441 Figure C-6. Typical glideslope installation … 441
LIST OF TABLES
Figure 3-10 · page 12Picture of the page from the copy saved here
Table 1-1. ESRI Attribute Name Truncation to avoid Duplication … 7 Table 2-1. Survey Requirements Matrix … 21 Table 2-2. List of typical Electronic NAVAIDs associated with an Airport … 33 Table 2-3. List of Typical Visual Navigational Aids on an Airport … 34 Table 2-4. Topographic Survey Accuracy Requirements … 52 Table 2-5. Sample Federal Geodetic Data Committee spatial data accuracy standards (ASPRS Class II
Mapping Accuracy for large-scale maps) … 53 Table 2-6. Cat II and III Operation Area Accuracy Requirements … 53 Table 4-1. Required Field Validation Points based on Annual Aircraft Operations and Airport Area … 82 Table 4-2. Examples of Field Verification Points required of various airports … 83
xii
Intentionally left blank.
CHAPTER 1. GENERAL GUIDANCE AND SPECIFICATIONS › 1.2. ADMINISTRATION
CHAPTER 1. GENERAL GUIDANCE AND SPECIFICATIONS
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, the appropriate collection and safety implications of the prescribed data against defined, repeatable and verifiable standards far outweigh the potential costs. The collection and maintenance of the data regarding airports is a shared responsibility of the FAA and the Airport sponsor 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.
The FAA developed these specifications to detail the data collection requirements and processing of airport data. Compliance with these requirements and standards without deviation is mandatory for federally obligated airports, and recommended for all other airports.
Refer all questions about the interpretation and use of these standards to the Manager, Airport Engineering Division (AAS-100), Office of Airport Safety and Standards, Federal Aviation Administration, 800 Independence Avenue, S.W., Washington, DC 20591.
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 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) in the contract agreement for each airport 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:
CHAPTER 1. GENERAL GUIDANCE AND SPECIFICATIONS › 1.3. CONTRACTOR REQUIREMENTS
• The verbs “will” and “must” mean compliance is mandatory.
• The verb “should” implies compliance 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.
• 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 (refer to paragraph 1.4 National Spatial Reference System (NSRS)).
• 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. CONTRACTOR REQUIREMENTS
The contractor will provide all labor, equipment, supplies, material, and transportation to produce and deliver data and related products as required under this guidance. The contractor 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
All surveying equipment used will have maintenance logs showing routine preventive maintenance and repairs. Include in the Final Project Report the equipment model and serial numbers, and Electronic Distance Meter Instrument (EDMI) calibrations. If a hand–held EDMI is used, compare its distancemeasuring accuracy to a distance measured with a calibrated EDMI and report the results in the Final Project Report.
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 unless agreed to by both parties. Provide reproducible copies of drawings and copies of other pertinent data to the Airport Authority. Submit the data required by the FAA under these specifications to the FAA Airport Surveying–Geographic Information System (GIS) Program at https://airports-gis.faa.gov. Original logs and records must be legible, neat, clear, accurate, and fully completed in indelible black ink. All available entries on the recording forms should be completed or indicated as N/A. Use blue ink when checking or
CHAPTER 1. GENERAL GUIDANCE AND SPECIFICATIONS › 1.4. NATIONAL SPATIAL REFERENCE SYSTEM (NSRS)
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 will be done on a copy of the original with all changes initialed.
1.3.4. Unusual Circumstances
The contractor will notify the airport sponsor/proponent, local FAA airports office and the FAA Airport Surveying–GIS Program of any unusual circumstances occurring during the data collection according to these specifications. The FAA Airport Surveying–GIS Program Manager will then consult with the government technical representatives to determine an appropriate course of action and advise the sponsor.
1.3.5. Specification Review and Familiarity
It is the responsibility of the potential contractor to ensure all personnel (including subcontractors) involved in the project are thoroughly familiar with the information in this guidance and any material covered in other cited references and publications.
1.4. NATIONAL SPATIAL REFERENCE SYSTEM (NSRS)
The FAA ties all Air Operations Area surveying and positioning to the NSRS. Refer to AC 150/5300-16, General Guidance and Specifications for Aeronautical Surveys: Establishment of Geodetic Control and Submission to the National Geodetic Survey, for guidance on establishing geodetic control and the NSRS.
1.4.1. Horizontal Control
The contractor provides horizontal control referenced to the North American Datum of 1983 and year of the latest adjustment [abbreviated NAD83 (YYYY)]. NOTE: The year of adjustment is on the NGS Data Sheet next to the latitude and longitude.
1.4.2. Vertical Reference
The contractor provides vertical control referenced to the North American Vertical Datum of 1988 (NAVD 88). Information regarding NAVD88 is located at the following website: http://www.ngs.noaa.gov/PUBS_LIB/NAVD88/navd88report.htm. Reference all Ellipsoidal Heights to NAD83 (GRS 80) realization.
1.4.3. GEOID Model
The contractor should use the NGS model current at the time of data collection. To check for changes in the GEOID; update information regarding the current GEOID model; and find information regarding the current GEOID in Alaska; refer to the following website http://www.ngs.noaa.gov.
CHAPTER 1. GENERAL GUIDANCE AND SPECIFICATIONS › 1.5. DATA FORMATS
1.5. DATA FORMATS
The contractor submits data collected to the Airport Authority and to the FAA Airports GIS website (https://airports-gis.faa.gov/). Include an inventory of all geospatial digital data in the Final Project Report and identify the physical file formats. In order to facilitate communication and exchange of information, use the following standard formats for data submissions:
1.5.1. Ground Control Data
The contractor submits 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.
1.5.2. Digital Images from Hand-Held Camera
1.5.2.1. Use digital photographs taken during daylight hours to document monuments used or data collected. These photos assist in the retracing of the surveyor’s steps by providing the evaluators with a picture of what the data is describing. Take sufficient photographs to document the conditions the surveyor encountered. They 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. A photograph is acceptable if it meets the requirements of this AC and is of good visual quality. Use the highest resolution possible to ensure good clarity and detail definition.
Use at least one (more if required) of the following three types of photos to document a position or object. All three photographs require a digital caption and correct file name as specified in paragraph 1.5.2.3.
• Photograph type 1 is an extreme close up of the object as shown in Figure 1-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.
Figure 1-1. Photograph type 1
• Photograph type 2 (Figure 1-2) is taken at eye-level with the station or object 5 to 6 feet in the distance (when practical and accessible) and provides general information about the area immediately surrounding the station or point.
Figure 1-2. Photograph type 2
• Photograph type 3 (Figure 1-3) is taken horizontally with the station approximately 10 to 30 feet in the distance (Figure 1-4). Photograph type 3 provides general orientation information to the user and should include the cardinal direction the camera is pointing in the caption.
Figure 1-3. Photograph type 3
Figure 1-4. Illustrates the documentation of a glideslope antenna from different perspectives.
Figure 1-2 · page 19Picture of the page from the copy saved here
When documenting navigational aids surveyed, as in Figure 1-4, two photographs oriented from different cardinal directions. When documenting navigational aids, take the photograph with a tripod over the horizontal and vertical (if practical) survey point or electronically add arrows showing the point(s)
Location used to define object as an OBSTACLE
Horizontal Survey Point
Vertical Survey Point
surveyed. The independent verification and validation team uses these photos to check the correct point was surveyed based on the type of navigational aid.
1.5.2.2. 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.
Figure 1-4 · page 19Picture of the page from the copy saved here
1.5.2.3. Use the following file naming convention for photograph filenames. The filename is comprised 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.
Sample filename for a runway end point:
LAX_CL_END_RWY_12R-3_04MAY2001.jpg
Decoding the example above, “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/.
1.5.2.4. Electronically add a caption to each photograph. The caption should include the following information separated by commas or dashes:
• Airport location identifier assigned by the FAA.
• Runway end designator.
• Photo 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 cardinal direction (N, NE, E, SE, etc.) the camera is pointing.
1.5.3. 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 that relates the construction and the field collection together.
• Sketches of the runway profile points (two runs - digital file) annotated with the distances of each of the points collected from the runway end.
• All NAVAIDS located off the airport (digital photographs are sufficient).
1.5.4. Geospatial Vector Files
Submit data to the FAA Airport Surveying–GIS Program in any of the following 3D geospatial vector file formats:
• Autodesk™ DWG format (version 2010 or later) with attributes defined as object data.
• MicroStation™ DGN format (version 8 or later)
• ESRI™ Shape File format with attributes and metadata elements provided as attributes within each shape file
Submit requests to use other geospatial vector file formats in writing to the FAA Airport Surveying–GIS Program Manager. All geospatial vector files must conform to the data content standard specified in Chapter 5 as defined for each feature submitted.
1.5.5. ESRI Nuances for Dealing with FAA Attribute Names
When submitting data to the FAA Airport Surveying–GIS Program using ESRI software, some of the standard naming conventions specified by the FAA need to change to accommodate ESRI file naming constraints. This limitation is described by ESRI™ in their documentation as “A field's name must be no more than 10 characters in length; additional characters will be truncated.” In most cases within the specified FAA naming structure this is not a problem until the truncation results in duplicate names. In order to solve this problem, data providers should use the following table to avoid the duplication of names in the following feature classes. In all other cases the truncation at 10 characters of attribute names should not have duplicates. A full listing of all FAA features and attributes with the truncated names, as established within the FAA Airports-GIS, is provided in Appendix D for use in quality assurance of the data before submission. Although 10 characters is the maximum field name size for shape files, feature classes in geodatabases can have more.
Table 1-1. ESRI Attribute Name Truncation to avoid Duplication
FeatureClass AttributeName Shp_Name RunwayHelipadDesignSurface Determination determinat RunwayHelipadDesignSurface determinationDate detDate RunwaySafetyAreaBoundary determinationDate detDate NavaidEquipment downWindBarElevation downWindBa NavaidEquipment downWindBarThreshold dWndBarThr Obstacle heightAboveAirport heightAbov
Obstacle heightAboveRunway hAbovRwy Obstacle heightAboveTouchdownZone hAbovTdz
1.5.6. Airport Layout Plan Data
Submit digital versions of airport data defined in this standard in one of the following formats.
• Autodesk DWG format (version 2010 or later) with attributes defined as object data.
• MicroStation DGN format (version 8 or later).
• ESRI Shape File format with attributes and metadata elements provided as attributes within each shape file.
1.5.7. 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-5 provides an example of an orthorectified raster image of an airport. Imagery requirements are specified in AC 150/5300-17, Standards for Using Remote Sensing Technologies in Airport Surveys.
Figure 1-5. Example of Raster Imagery
Figure 1-5 · page 22Picture of the page from the copy saved here
CHAPTER 2. SURVEY SPECIFICATIONS AND STANDARDS › 2.2. INDEPENDENT VERIFICATION AND VALIDATION OF AIRPORT SAFETY DATA.
CHAPTER 2. SURVEY SPECIFICATIONS AND STANDARDS
2.1. OVERVIEW OF THE PROCESS
Airports have surveys conducted for many different reasons. However, all survey types require the collection, classification and reporting of accurate data about the project. All surveying completed on the airport will provide the information outlined in Chapter 5 within the stated accuracies. The methodology selected to gather the information is up to the professional surveyor’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 every survey conducted on the airport to tie in some way to the NSRS. When the project uses an engineering grid rather than a national grid, tie the local grid to the NSRS to ensure accurate relativity to other NAS elements. In order to tie an engineering grid to the NSRS, the surveyor is required to identify and use positions common to both reference systems to ensure the project remains tied to the other elements of the NAS. 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. INDEPENDENT VERIFICATION AND VALIDATION OF AIRPORT SAFETY DATA.
Due to the critical nature of some airport features, the FAA requires their independent verification and validation by the Aeronautical Survey Program of the National Geodetic Survey or a designated representative. Typically, these features are those associated with the airport’s movement areas, navigational systems or those affecting navigable flight such as objects surrounding the airport. Once the independent verification, validation and quality assurance of the safety critical data is completed, the government technical representatives will provide a complete final written analysis of their findings including approval or disapproval of the data. They will identify and list any discrepancies discovered relating to these specifications and decide on the usability of the data.
2.2.1. Verification
In this guidance, “verification” is defined as the confirmation by examination and provision of objective evidence that the specified requirements are fulfilled. Verification is necessary to ensure the data set accurately represents the specifications and is uncorrupted. The verification process proves the data was properly collected. The following verification techniques comprise 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 available data set to compare the submitted data against.
CHAPTER 2. SURVEY SPECIFICATIONS AND STANDARDS › 2.3. ACCURACY REQUIREMENTS
• Reasonability checks to ensure the data set does not violate known properties (such as obstacles must have positive orthometric heights).
2.2.2. Validation
In this guidance, “validation” differs from “verification” in scale. The validation process identifies the aeronautical information submission was correctly developed as an input to the system. Validation is the confirmation by examination and provisions 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.
2.3. ACCURACY REQUIREMENTS
The data about airports is critical to the operation and safety of the 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 requiring their collection through field survey. Typically, linear features, some objects within the object identification surfaces, and visual navigational aids are good candidates for collection by remote sensing techniques. The geographic coordinate accuracies of this data must meet or exceed the requirements in this AC and in the following:
2.3.1. Geodetic Control
The survey monuments established in the airport vicinity must meet all accuracy requirements and other criteria specified in AC 150/5300-16. These monuments and their accurate connection to the NSRS assure accurate relativity between all surveyed points on an airport and the NAS, including navigation satellites.
2.3.2. Imagery
The geo-referenced imagery of the survey area must meet the accuracy requirements specified in AC 150/5300-17.
2.3.3. Remotely Sensed Surveys
Due to the critical nature of airport and aeronautical data, it is important to position and attribute features accurately. 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 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
CHAPTER 2. SURVEY SPECIFICATIONS AND STANDARDS › 2.5. FEATURE ATTRIBUTION
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 less 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 metadata the methods used in the deductive method including complete calibration tests and describe assumptions about error propagation.
2.3.4. Feature Accuracy Requirements
The accuracy for geospatial vector airport features (taxiway, aprons, ramps, buildings, etc.) is typically mapping grade accuracy, nominally within 3 feet horizontally and 5 feet vertically (Refer to Chapter 5 Feature Descriptions for complete accuracy requirements). Specific runway, stopway and navigational aid data accuracies are nominally within 1 foot horizontal 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 NSRS. Derived elevations must be within 10 feet vertically.
2.3.5. Field Surveys
Many airport features have accuracies greater than are achievable using remotely sensed methods and require field survey methods be used. These features, specifically the data for the runway(s) and some navigational aids, are nominally within 1 foot horizontally and 0.25 feet vertically. Chapter 5 lists the features and their required accuracies and unique requirements. Refer to the appropriate section in this chapter for specific guidance on the different types of surveys typically performed on or near an airport.
2.4. RESERVED
2.5. FEATURE ATTRIBUTION
As airports move toward a more data centric environment, more information about the objects on and around the airport is required. Each of the features in Chapter 5 has a list of attributes or information about the feature. Each of these attributes should be completed. Realizing this will be an iterative process, there are some business rules which apply to all submissions.
Generally, the surveyor or consultant hired to collect the data will gather some of this information in the field. Other values can and should be derived from the field measurements. While other values will require information from other sources such a record drawings or interviews. Each attribute for each feature should be submitted with the data. Sponsors should expect surveyors or consultants to complete these attributes based on the purpose of the survey or data collection effort. Typically, any attribute that can be measured or computed should be completed as part of the statement of work. Depending on the airport's staff ability and workload, other attributes can and should be completed by them. Base the requirement for which attributes the consultant should complete on the intent of the statement of work. If the consultant is hired is to collect data for an airport analysis survey then all attributes relating to those features should be completed.
The more complete the attribution the more complete and useful the data set will be to both the FAA and the airport sponsor in the future. Sponsors should also plan for the maintenance of this information. If a previously submitted features attribution changes, it should be updated as soon as possible. Chapter 4 provides more information on the maintenance of data.
CHAPTER 2. SURVEY SPECIFICATIONS AND STANDARDS › 2.6. REPORTING REQUIREMENTS
2.6. REPORTING REQUIREMENTS
2.6.1. General Reporting Requirements
Thorough reporting is required. Prior to beginning any fieldwork, submit a survey and quality control plan to the airport sponsor/proponent, the local FAA airports office and FAA Airport Surveying–GIS Program Manager. On project completion, provide to the airport sponsor/proponent, the local FAA airports office and the FAA Airport Surveying–GIS Program manager a final project report compliant with paragraph2.6.4. Include the prime contractor’s firm name on all reports. Submit all reports electronically to the FAA using the reporting tools provided by the Airports GIS web site https://airportsgis.faa.gov.
2.6.2. Survey and Quality Control Plan
2.6.2.1. General Requirements. Develop and submit survey work and quality control plans for airport sponsor/proponent and FAA approval before beginning any fieldwork. The FAA Airport Surveying–GIS Program manager or designated representative will review and approve the survey work and quality control plans. In these plans, detail the methodologies for data collection, data safeguarding and quality assurance. Provide insight into how you will completely check all data to ensure it is complete, reliable, and accurate. Identify data safeguards used to protect this sensitive and safety critical data. Utilize a checklist based quality control process with definable and repeatable standards for each element ensuring consistency of work between different personnel within an organization. Submit the plan in a non-editable format such as Adobe Portable Document Format (PDF) ™ using the reporting functions of the Airports GIS web site https://airports-gis.faa.gov. A sample survey and quality control plan is available on the FAA Airports GIS website (https://airports-gis.faa.gov).
2.6.2.2. Remote Sensing and Field Survey. The use of remote sensing and ground survey techniques to accomplish the survey is highly recommended. The plans must include a description on the combinations of methods used and 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 contractor will amend the original plans to identify any deviation to the Airport Authority or to the FAA Airport Surveying–GIS Program Manager immediately. The plan must address each of the following areas but is not specifically 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.
• Geo-referencing: Describe in detail the plan for utilizing geo-referenced (aero-triangulated) imagery with acceptable accuracies. Refer to AC 150/5300-16, for additional guidance and requirements.
• Feature Extraction: Detail methodologies for collecting airport features, such as airport buildings, the aircraft movement areas, landmark features, and obstructing 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.
• Obstruction Analysis: Provide a detailed description of the remote sensing and field survey methods used to identify, locate, and observe the required obstacles relative to the specified obstruction identification surfaces provided in this guidance. The contractor needs to describe the data collection methods and the associated horizontal and vertical accuracies expected.
• Prior Survey Data: 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, then the consultant should verify and document the data set as accurate using the techniques described in Chapter 4.
• Field Survey Methods: Identify the methods for data collection and processing used for observing required features. Include a description of the methods of analysis in the report.
• Geodetic Control: Describe in detail the plan for connecting to and verifying all existing airport control planned for use during the survey. Use of the established Primary Airport Control Station (PACS) and Secondary Airport Control Stations (SACS) is required.
• 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, collection data and the techniques used to merge the data sets into a single comprehensive airport data set.
• Equipment 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 and remote sensing hardware and software.
• Quality Assurance Process: Describe in detail what quality assurance methods you will use to ensure the quality and protection of the data from the time and point of collection to the time of submission.
2.6.2.3. Quality Control. The Survey and 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:
• Summarize what methods you will use to ensure high-quality data.
• Describe the quality control measures used to ensure all data is checked, complete, reliable, and meets the accuracy requirements in this AC.
• Provide evidence of the methods used to collect the various types of features to meet the desired accuracies.
• Describe the data backup and archive procedures and methods used to ensure the integrity of the original data.
• Explain the methods used to check all file formats and provide a summary of the file-naming convention for all electronic files.
2.6.3. Project Status Report
Submit a project status report via email to the airport sponsor/proponent every Monday by 2:00 P.M. Eastern Time, from the date of the task order until the work is completed. Include in the reports the percentage complete for each of the major portions of the work with the estimated completion date or completion date. Provide the status of ongoing work (with expected completion dates) and any unusual circumstances and/or deviations from this guidance. Status reports should be brief and contain the current information in the text of the email. Submit all reports using the Add Document function under the category of General on the Airport GIS website. This allows all project stakeholders access to the report in a single location tied directly to the project file. The following is an example Project Status report for an airspace analysis project:
Anyplace Field/Anywhere International Airport
AIP X-XX-XXXX-XXX-20XX
Survey progress update #1
July XX to July XX
Eagle Eye Surveying completed a second week of ground surveying. The first week verified PACS and SACS control, collected runway centerline, and primary surface topographic information.
To date we have surveyed for Runway 12-30:
Airport Control (PACS, SACS, ANY B540) 100%
Runway and Stopway Ends 100%
NAVAIDS (VOR, NDB, Airport Beacon, VASI, PAPI, and REILs) 100%
Runway and Stopway Obstructions (Primary surface, approaches, transitional surfaces) 100%
Aircraft Movement and apron areas 75%
Prominent airport buildings / potential close-in obstructions 42%
This week we will be analyzing the collected obstruction survey data relative to the object identification surfaces. We will check both the required points for each obstruction zone and the navigational aids, and generate the appropriate field documentation. We completed subcontract negotiations with aerial photography sub consultant SkyCamera, Inc. and are submitting the proposed flight map with ground reference points for review and approval before completing our final week of field surveying. This week we will be setting aerial targets and surveying in the targets and PhotoID points, and collecting final outlying obstruction data. Aerial photography is promised to us 2 to 4 days after our targets are in place.
Sincerely,
Any Surveyor, P.S.
Eagle Eye Surveying
2.6.4. Final Project Report
The Final Project Report is a compilation of documentation supporting the survey project providing a standardized delivery of field notes, raw survey data and project summary to facilitate the independent verification, validation, and quality assurance of the safety critical data. In the final project report, address each of the following areas.
2.6.4.1. Project Identification Data. List each of the following items on the first page of the document.
• Official name of airport and FAA assigned location identifier
• Airport Address (Street, City, State, Zip)
• Client Name
• Project, Contract, or Grant Number assigned
• FAA Region
• Start and end dates of project (From contract signing to delivery of data)
• Contractor point of contact (including name, company name, address, telephone number, email)
2.6.4.2. Project Summary. Provide a written overview of the project details and conclusions. In the summary, describe the scope of the survey identifying the key elements for collection (i.e. runway, obstruction, mapping, and 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.
2.6.4.3. Survey Data Conclusions. Provide your conclusions regarding the following subjects as they relate to this project.
2.6.4.3.1. Control Network Survey Results/Conclusions. Provide a description of the control network utilized as the basis of the survey 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 utilizing 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 vendor used in data reduction.
2.6.4.3.2. 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 future planned construction at the airport that causes concern.
• Note 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.).
2.6.4.3.3. 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 survey by the validation team.
2.6.4.3.4. 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.
2.6.5. Field Note Information and Data
2.6.5.1. Geodetic Control Data. Provide the raw-data files collected containing the data used for establishment or verification of the geodetic control, including any data used to plot temporary points occupied. Typically, these files include the original raw GPS data files (in both the manufacture’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.6.5.2. Survey Information and Data: Providing the survey data 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/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. This includes 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.6.6. Deliverables Checklist
The tasks completed during the survey 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 details to assist in ensuring proper planning and execution of a successful survey project. The FAA provides an appropriate checklist for the deliverables on the program website at https://airports-gis.faa.gov.
• Survey and Quality Control Plan (completed before data collection begins)
• Weekly Project Status reports provided to the sponsor
• Final Project Report (develop for all survey types)
• Digital Files to be delivered:
o Provide the documentation required for each feature as defined by the descriptions in Chapter
5, Airport Data Features. 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 paragraph 2.6.5 Field Note Information and Data. 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 (but not limited to) are:
Data collector files
GPS receiver files
CORS data downloaded
Photogrammetric observation files
Other field measurement device’s digital raw data (range finder, scanner, etc.)
o Provide the 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.
o Provide an airport point of contact list for use by the independent verification and validation
team.
o Copies of the transmittal letters for all deliveries posted to the sponsor or FAA.
2.6.7. Pre-Survey Preparation Activities
2.6.7.1. Contact with Airport Authorities. Close communication with airport management is critical throughout the entire survey 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 and radios capable of receiving Air Traffic Control ground and aircraft frequencies. Contact with the airport traffic control tower is mandatory while during surveys 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 or near the site. When approaching landowners regarding access, be sure to fully 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.
2.6.7.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
authorities the runway/stopway data published in the latest editions of the Airport/Facility Directory (A/FD) and U.S. Terminal Procedures (TPP), both U.S. Government Flight Information Publications (http://www.naco.faa.gov). During the survey, additional meetings may be required to discuss unusual circumstances, problems, or changes to published or given data. Include in the final report a summary of all such meetings. 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 persons in all of these areas of expertise or they may not be located at the airport. Complete interviews with the following personnel if possible.
2.6.7.2.1. Airport Manager/operations. The airport manager/operations is the key individual on the airport. It is important for the contractor to contact the airport management prior to visiting the site. This allows the contractor 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-security areas on the field, etc.). Include the contact information of the airport manager/operations person interviewed on the checklist.
2.6.7.2.2. Airport Engineering. This interview will only be 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 in the Final Project Report in case questions arise after the survey.
2.6.7.2.3. Air Traffic Control. If an Airport Traffic Control Tower (ATCT) is operational during the time of survey, discuss the survey with the Chief Control Tower Operator or their designated representative. This interview can provide information on operational factors and facilitate the working relationship between the contractor and the controllers. Include contact information in the final report.
2.6.7.2.4. FAA Airway Facilities. An interview with FAA Airway Facilities 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. 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 contractor to certain facilities to let them through a gate or monitor an alarm while survey personnel are within critical areas of the site. Include the contact information for the assigned FAA Airway Facilities Point of Contact (POC) in the final report in case questions arise after the survey.
2.6.8. Field Survey Operations
2.6.8.1. Data. The project will include accurate positions and elevations of points, lines, or polygons based on the type of survey required (see Table 2-1 Survey Requirements Matrix). For airport airspace analysis surveys, specific points along runways, runway vertical profiles, positions and elevations of navigational aids, positions and elevations of obstructions, analysis of obstructing areas, and positions and elevations of certain non-obstructing obstacles 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.6.8.2. Preparation. Carefully evaluate the requirements in the statement of work from the airport sponsor 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 unique source 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.
• Review imagery and 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 sponsor 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.
• Review FAA Form 5010, Airport Master Record, at http://www.gcr1.com/5010web/.
• Coordinate with airport authorities.
• Produce and deliver a Survey Plan and Quality Control Plan.
2.6.9. Determining the Survey Requirements.
The following matrix identifies the requirements for the different survey types typically encountered at an airport.
Intentionally left blank.
5/21/2009 AC 150/5300-18B
21
Table 2-1. Survey Requirements Matrix
This table is designed for use in two ways. First, it defines in a general fashion the task required to meet a specific objective. Each task listed is generalized and the process to complete it many contain many other pieces. Users should refer to the text of the referenced AC to ensure that all the required subtasks are completed. The second way to use this matrix is as a checklist to ensure all the required data is collected either before leaving the field or before submitting the data to the FAA.
Intended End Use of the Data
AC Reference Category
II or III Operations
Navigational Aid Siting Airport Layout
Plan (ALP)
Airport Obstruction
Chart
Construction Instrument
Procedure Development
Pavement Design, Construction,
Rehabilitation or
Roughness
Airport Mapping Database Required Tasks Non- Precision
Precision Visual Airside Landside
Provide a Survey and Quality Control Plan 150/5300-16/17/18 • • • • • • • • • • • Establish or validate Airport Geodetic Control 150/5300-16 • • • • • • • • • Perform, document and report the tie to National Spatial Reference System (NSRS)
150/5300-16 • • • • • • • •
Survey runway end(s)/threshold(s) 150/5300-18 • • • • • •1 • • • Monument runway end(s)/threshold(s) 150/5300-18 • • • • • •1 • • Document runway end(s)/threshold location(s) 150/5300-18 • • • • • •1 •1 •1 Identify and survey any displaced threshold(s) 150/5300-18 • • • • • •1 • • • Monument displaced threshold(s) 150/5300-18 • • • •1 •1 •1 • Document displaced threshold(s) location 150/5300-18 • • • • • •1 • • • Determine or validate runway length 150/5300-18 • • • •1 • • • Determine or validate runway width 150/5300-18 • • • •1 • • • Determine runway profile using 50 foot stations 150/5300-18 •2 •2 •2 •1 • •2 Determine runway profile using 10 foot stations 150/5300-18 • •2 •2 •2 •1 • •2 •2
Determine the touchdown zone elevation (TDZE) 150/5300-18 • • • • • • Determine and document the intersection point of all specially prepared hard surface (SPHS) runways
150/5300-18 • • • •
Determine and document the horizontal extents of any Stopways
150/5300-18 • • • • •
Determine any Stopway profiles 150/5300-18 • • • • • Determine if the runway has an associated clearway 150/5300-18 • • • Survey clearway to determine objects penetrating the slope 150/5300-18 • • • • • Determine and document the taxiway intersection to threshold distance
150/5300-18 •
Determine runway true azimuth 150/5300-18 • • • • • • Determine or validate and document the position of navigational aids
150/5300-18 • • • • • • •
Determine or validate and document the position of runway abeam points of navigational aids
150/5300-18 • • • • •
Determine potential navigational aid screening objects 150/5300-18 • • • Collect and document VOR receiver checkpoint location and associated data
150/5300-18 • •
Perform or validate and document an airport airspace analysis 150/5300-18 • • • • • • •1 • Collect and document helicopter touchdown lift off area (TLOF)
150/5300-18 • • • • • • •
Collect and document helicopter final approach and takeoff area (FATO)
150/5300-18 • • • • • • •
Collect or validate and document airport planimetric data 150/5300-18 • • • • • Determine or validate the elevation of the Air Traffic Control Tower Cab Floor (if one is on the airport)
150/5300-18 • • • • • •
1 Only when runway construction is involved. 2 All 14 CFR Part 139 airports require 10 foot stations. At all other airports the distance between stations is between 10 and 50 feet to meet local requirements
AC 150/5300-18B 5/21//2009
22
Intended End Use of the Data
AC Reference Category
II or III Operations
Navigational Aid Siting Airport Layout
Plan (ALP)
Airport Obstruction
Chart
Construction Instrument
Procedure Development
Pavement Design, Construction,
Rehabilitation or
Roughness
Airport Mapping Database Required Tasks Non- Precision
Precision Visual Airside Landside
Perform or validate a topographic survey 150/5300-18 •3 • • • • • •4 Collect and document runway and taxiway lighting 150/5300-18 • • • Collect and document parking stand coordinates 150/5300-18 • Collect cultural and natural features of landmark value 150/5300-18 • • • Determine elevation of roadways at the intersecting point of the Runway Protection Zone (RPZ) or the runway centerline extended
150/5300-18 • •
Determine all Land Use to 65 DNL contour 150/5300-18 • Document features requiring digital photographs 150/5300-18 • • • • • • • Document features requiring sketches 150/5300-18 • • • • • • • • Collect position and type of runway markings 150/5300-18 • • • Collect position and type taxiway markings 150/5300-18 • Locate, collect, and document photo ID points 150/5300-17 •
Identify collect, and document wetlands or environmentally sensitive areas
150/5300-18 •
Collect imagery 150/5300-17 • • • • • Provide a final Project Report 150/5300-16/18 • • • • • • • • • • •
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
2.6.10. Types of Airport Survey Projects
2.6.10.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 NGS website http://www.ngs.noaa.gov/cgi-bin/airports.prl?TYPE=PACSAC. PACS are set to meet highstability 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 two 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, contact the FAA Airport Surveying–GIS Program Manager immediately. The FAA Airport Surveying–GIS Program will review the situation and may advise the airport proponent, Airports District Office, or Airports Regional Office to reschedule the work at the airport.
2.6.10.2. Verification of Survey Marks. 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.
Make two independent GPS sessions, each at least 10 minutes long with a 5-second 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 report. 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.
Submit a recovery report for the PACS and SACS to the NGS at:
http://www.ngs.noaa.gov/FORMS_PROCESSING-cgi-bin/recvy_entry_www.prl
Verification is not required if the contractor 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 contract.
2.6.10.3. Runway Data. This section provides field surveyors 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 azimuth, among other data elements. In many cases, the location of these points is not intuitively obvious and the precise survey point selection may not be consistent among surveyors. Figure 2-1 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 end point of the runway. The correctly placed survey equipment is located within acceptable parameters of the runway end.
Figure 2-1 · page 38Picture of the page from the copy saved here
Examples of incorrect and correct survey equipment placement
Figure 2-1. Examples of incorrect and correct survey equipment placement
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 certified under 14 CFR 139 and those federally obligated 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 survey. 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 surveyors 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.10.4. 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-2. Additionally, it provides guidance
Figure 2-2 · page 40Picture of the page from the copy saved here
on the accurate collection of profile points along the runway, used in many different areas of airport planning and design as well as other initiatives within the FAA. Typically, the runway end, stopway, and displaced threshold positions are typically 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, RunwayEnd, Stopway, and AirportControlPoint (for displaced thresholds and 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. Provide the data for non-specially prepared hard surface (non-SPHS) runways/stopways required 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 (using the feature StopwayEnd or Stopway) and Clearway data using the RunwayProtectArea feature if it is requested by appropriate authorities (FAA, Airport sponsor, State Aviation authority).
Surveyors 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 form to document published data and collected data. Download the form from the FAA Airports GIS website at https://airports-gis.faa.gov.
In order to be a stopway, the area must be officially designated, appropriately marked, and approved as a stopway by the airport and FAA authorities. The following points about stopways are important for the surveyor 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 and lighting (see Figure 2-3). The existence of a stopway means the runway has a declared accelerate/stop distance, even though it may not be published. Unless otherwise stated, all runway, stopway, and clearway points must be on the runway, stopway, or clearway (as appropriate) centerline.
Figure 2-2. Depicts some of the required points and elements of a runway or stopway.
Depicts some of t
he require
d points a
nd elements
of a runway or stopway.
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.
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.
Figure 2-3 · page 41Picture of the page from the copy saved here
CHEVRON SPACING MAY BE DOUBLED IF LENGTH OF AREA EXCEEDS 1000 FEET [300M]
DIMENSIONS ARE IN: FEET [METERS].
Figure 2-3. An example of the proper marking for a blast pad or stopway.
2.6.10.5. 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 displaced threshold (if there is one) is included in the physical length of the runway. Runway lengths are determined from the positions of the runway ends. Determine the runway end positions using the guidance provided in the RunwayEnd feature in Chapter 5. Measure the runway width from the outer edge of the runway, excluding shoulders (see Figure 2-4) and stopways. The runway width is the physical width extending
over the entire length of the rectangle, or the area within the runway side stripes if the full pavement width is not available as a runway. Measure and record runway widths to the nearest tenth of a foot (0.1 ft) and include the dimension on the runway end sketch. 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 resolve any discrepancies in the values before departing the site. If the discrepancy cannot be resolved, note the discrepancy and document the discussions with the airport officials in the final report for review by NGS and resolution by the FAA with the airport.
Determine and provide the runway true azimuth reckoned from North to the nearest thousandth of a degree as the azimuth between the physical runway ends. The runway true azimuth is documented as an attribute in the RunwayEnd feature. Each runway end will have a different runway true azimuth specified.
Figure 2-4. Standards for marking of runway shoulders.
S]. ER ET [M ET ONS ARE IN: FE DIMENSI
NOTES:
. 1
5° 4
DER
AY
DER
UL
W
UL
HO
UN
HO
S
R
S
5° 4
9] 0 .[ 3
30] [ 00 1 30] [ 00 1
LD O SH RE H Y T A W UN R 5] 1. [ 5
30] [ 00 1
5] 1 0 [ 5
30] [ 00 1
5° 4
5° 4 5] 1. [ 5
NT I O DP Y MI A W UN R
2.6.10.5.1. Displaced Thresholds. On some runways, the threshold is displaced due to other requirements such as objects in the approach area penetrating the siting surface or where the airport is constrained to meet runway safety area length. When a displaced threshold is encountered it must be identified (see Figure 2-5), classified, and documented (see paragraphs 1.5.2 and 1.5.3 for documentation requirements) similarly to a runway end. In FAA Airports GIS, a displaced threshold is modeled using the AirportControlPoint feature in Chapter 5.
Figure 2-5. Illustrates the proper marking of a displaced threshold.
STD RUNWAY MKG
10 [3M] WIDE WHITE THRESHOLD BAR
RUNWAY THRESHOLD
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,
Figure 2-5 · page 43Picture of the page from the copy saved here
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 = RUNAY 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
200 [65M] 5 [1.5M]
20 [6M] 80 [24M]
120 [36]
100 [30]
2.6.10.5.2. Establishing the Runway End Point. Use existing FAA or airport provided runway end point data to assist in locating the points identifying the ends (physical and displaced) of the runway. Proper identification of these points is in the data standard descriptions for the RunwayEnd, and AirportControlPoint (Displaced Threshold and stopway end) features in Chapter 5 of this AC, with further clarifying guidance provided in Appendix C. Recover, verify or establish and document (see paragraphs 1.5.2 and 1.5.3 for documentation requirements) the following points using the appropriate feature in Chapter 5.
• Runway end points
• Displaced threshold points
• Clearway end points
• Stopway end points
2.6.10.5.3. Location of Specific Survey Points. The locations of the following runway/stopway survey points are defined by the intersection of the runway/stopway centerline and one of the indicated survey point locators as detailed in the feature descriptions 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 FAA Airport Surveying–GIS Program Manager 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.10.5.4. Runway and Stopway Profiles. The runway profile provides information about the runway gradient, establishes the airport elevation and 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 14 CFR 139 airports collect runway centerline profiles at 10-foot stations and two (2) additional profiles offset 10 feet on either side 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 AirportControlPoint feature in Chapter 5. Use the actual date the profile was collected as the dateRecovered attribute. Specify the monumentType attribute as spot from the enumeration table
codeMonumentType. Specify the pointType attribute as a CenterlinePoint from the enumeration table codePointType.
2.6.10.5.5. Preliminary Computations and Data Discrepancies. The runway end or displaced threshold position establish the starting and end point of the runway. Use these positions to compute the runway length, length of any threshold displacement and stopway length. Before leaving the airport, compute these safety critical distances and compare them to the known data provided by the FAA or airport authority. Determine these lengths using a three dimensional geodetic inverse computation between the end points. Using a three dimensional computation corrects for the elevation of the points and difference in elevation between points. The official runway, stopway, or displaced threshold length is the straight-line distance between end points. This line does not account for surface undulations between points.
Computed lengths seldom match published lengths exactly. Discrepancies are most likely caused by interpretation of runway/stopway survey point location, remarking of thresholds, or comparison with less accurate published data. As the magnitude of discrepancies increases, the probability also increases that physical changes have occurred to the runways/stopways or that the thresholds have been moved. Differences with published data should be considered as an alert that there may be a problem in the survey. However, published lengths are often not as accurate as the new surveyed lengths and are occasionally obsolete or otherwise grossly erroneous. Therefore, the validity of the published data must always be questioned when comparing it with the new survey data, especially if the survey points are selected correctly.
Though published data is often incorrect or obsolete, new survey data should be carefully reexamined when discrepancies between published and surveyed data occur. The reasons for small discrepancies are often difficult or impossible to identify. As discrepancies become larger, the reasons typically become more apparent. Although the source of the discrepancy may not be identified, the reexamination should be conducted to provide the highest level of confidence that accurate runway data has been provided. Fully document and report the situation in the final report for examination by the independent verification and validation team.
Stopway discrepancies pose a special problem. Before an area is officially declared a stopway and published in official U.S. Government documents, airport authorities must file the request for a stopway through appropriate FAA offices. Discrepancies in the reported value for a stopway are generally harder to determine. If the apparent stopway dimensions on the ground differ by more than 10 percent from the stopway dimensions as published by the FAA or given by the airport authority, contact the FAA Airport Surveying–GIS Program Manager for assistance. If a published stopway does not appear to meet the definition of a stopway, including the requirement to support an aircraft during an aborted takeoff, without causing structural damage to the aircraft, fully document (including taking digital photos of the area in question) for resolution by the FAA with the airport authority. If the airport authorities request an area be surveyed as a stopway but the stopway is not published in the current FAA publications or the airport authorities request a change to or do not concur with the published stopway data or data resulting from the new survey, complete the survey as requested and completely document the request and the data in the final report for resolution by the FAA.
Because of the importance of runway/stopway data, always discuss the location of runway, stopway and displaced thresholds with the appropriate airport authorities. Discrepancies occurring between the judgment of the surveyor and the opinions, understandings, or intentions of the airport authorities should be resolved. It may be necessary to revisit the field with airport personnel and explain the survey and survey point selection. If a discrepancy in the location of a position cannot be resolved, assistance should
be sought from the FAA Airport Surveying–GIS Program Manager. In some cases, final resolution may ultimately require a FAA field visit.
2.6.10.5.6. Comparison with Critical Runway Length. Runway lengths that are whole thousands of feet (5,000, 8,000, etc.) or whole thousands of feet plus 500 feet (5,500, 8,500, etc.) often have special operational significance. For purposes of this document, these lengths are called critical lengths. Many aircraft operations require a minimum runway length, which is often a critical length, and many runways are built to these lengths. If a runway is incorrectly published shorter than a critical length, certain operations could be unnecessarily restricted. In addition to imposing unnecessary operational limitations, incorrectly surveyed runways may not be retrieved during a computer search. This situation is especially likely to occur with critical length runways. In some cases, this failure could have safety implications. While all runway/stopway lengths should be accurate, even small errors in critical length could have significant and far-reaching ramifications. Runway lengths determined to be less than, but within 20 feet of, a critical length should be carefully reexamined to provide the highest level of confidence that the survey is correct. This reexamination should include an inspection of the runway end survey points to ensure the longest runway length possible was provided.
2.6.10.6. Navigational Aid (NAVAID) Surveys.
2.6.10.6.1. Navigational Aids. Navigational aids are vital elements of the NAS. The FAA Pilot/Controller Glossary defines a navigational aid as “any visual or electronic device, airborne or on the surface, providing point-to-point guidance information or position data to aircraft in flight.” The FAA operates over 4,000 ground-based electronic navigational aids, each broadcasting navigation signals within a limited area. The FAA and airports also provide a variety of approach lighting systems to assist the pilot in transitioning from instrument reference to visual reference for landing (see Figure 2-6). The navigational aid survey is the process of determining the position and/or elevation of one or more navigational aids and associated points on the airport or along the runway centerline(s) extended. Where a centerline abeam position (perpendicular to) the navigational aid is required it is detailed in Chapter 5. A navigational aid survey is normally completed as part of the total airport survey, airport layout plan update or accomplished entirely independently depending on the needs of the airport sponsor/proponent.
Figure 2-6 · page 46Picture of the page from the copy saved here
Figure 2-6. This photo illustrates how lights used at airports assist the landing pilot.
2.6.10.6.2. Determining the NAVAID Horizontal and Vertical Survey Position. Determine the horizontal survey point (HSP) by either field survey or remotely sensed means. The HSP may be the center of the navigational aid or, when the navigational aid is composed of more than one unit, the center of the array. If the DME and azimuth functions of VORTAC or VOR/DME facilities are located within 10 feet consider them collocated and report them as a single navigational aid. Be sure to include a note identifying the method used to determine the identification of collocation. Survey the navigational aid position if the navigational aid is associated with the airport surveyed. If the navigational aid penetrates a surface, also identify it in the airport airspace analysis evaluation with the associated object requirements and accuracies applying.
The data standards in Chapter 5 provide the data capture rules, horizontal and vertical survey points, accuracy requirements and necessary documentation for NAVAID observations. If you encounter a navigational aid not listed, contact the FAA Airport Surveying–GIS Program Manager for guidance.
In addition, survey Airport Surveillance Radar (ASR) and Air Route Surveillance Radar (ARSR) located within the limits of the Airport Airspace Analysis Area for the airport, but not located on a military airport.
2.6.10.6.3. Electronic Navigational Aids. Determine the position (and sometimes the elevation, depending on the navigational aid) for electronic signal generating navigational aids associated with the airport. Chapter 5 identifies the accuracy requirements for electronic navigational aids. Each navigational aid feature lists the HSP and VSP, and in many cases provides photos or sketches identifying the proper survey point, accuracy requirements, documentation and monumentation requirements and coordinate resolution for the electronic navigational aids typically found on and around airports.
Table 2-2. List of typical Electronic NAVAIDs associated with an Airport
Air Route Surveillance Radar (ARSR)
Airport Surface Detection Equipment (ASDE)
Airport Surveillance Radar (ASR)
Distance Measuring Equipment (DME)
Fan Marker (FM)
Localizer (LOC)
Glide Slope (GS)
End Fire Type (GS)
Inner Marker (IM)
Middle Marker (MM)
Outer Marker (OM)
Back Course Marker (BCM)
Localizer Type Directional Aid (LDA)
MLS Azimuth Antenna (MLSAZ)
MLS Elevation Antenna (MLSEL)
Non-directional Beacon (NDB)
Simplified Directional Facility (SDF)
Tactical Air Navigation (TACAN)
VHF Omni Directional Range (VOR)
VOR/TACAN (VORTAC)
2.6.10.6.4. Visual Navigational Aids. To enhance visual information to the pilot during the day, when visibility is poor, and at night, airports provide visual aids to pilots. These aids provide visual clues to the pilot about the aircraft’s alignment or height in relation to the airport or runway. Visual navigational aids consist of a variety of lighting and marking aids used to guide the pilot both in the air and on the ground. Determine the position of the HSP for the visual aids located on the airport. The position of the HSP may be the center of the navigational aid or, when composed of more than one unit, the HSP is typically the center of the unit array. For approach lighting systems capture and report only the first and last lights.
CHAPTER 2. SURVEY SPECIFICATIONS AND STANDARDS › 2.7. AIRPORT AIRSPACE ANALYSIS SURVEYS
The HSP, VSP, accuracy and resolution requirements for the visual navigational aids typically found on and around airports are provided with each navigational aid in Chapter 5. Chapter 5 provides sample images of most typical navigational aids depicting the horizontal and VSPs for each.
Table 2-3. List of Typical Visual Navigational Aids on an Airport
Airport Beacon (APBN) Visual Glide Slope Indicators (VGSI)
Runway End Identifier Lights (REIL) Approach Light System (ALS)
NOTE: Visual navigational aids are associated with the runway end they serve; the Airport Beacon is an exception.
2.6.10.6.5. Reference Measurements. For any navigational aid, provide reference measurements to other features, which could affect the system performance or separation from runways or taxiways. For all navigational aids provide at least two reference measurements to other prominent features (runway centerline, taxiway centerline, aircraft parking areas, detailing the navigational aid and its compound (area) and the point surveyed. Document these dimensions using the Navigational Aid Facility or Runway End Sketch form from the FAA Airports GIS website (https://airports-gis.faa.gov).
2.6.10.6.5.1. Navigational Aid Screening and Interference Reference Measurements. In addition to the reference measurements above provide the following reference measurements. All measurements are derived from the horizontal survey point. Document these measurements on the FAA Navigational Aid Screening and Interference Measurement Sketch.
• The distance and azimuth from the navigational aid to any structure located with 1,000 feet.
• The distance and azimuth from the navigational aid to any metal structure beyond 100 feet and above a 1.2° angle from the antenna base or proposed location.
• The distance and azimuth from the navigational aid to all non-metal structures greater than 1,000 feet from the navigational aid and penetrating a 2.5° plane from the antenna base or proposed location.
• The distance and azimuth to any metal fence within 500 feet of the navigational aid antenna or proposed location and any overhead powerline within 1,200 feet of the antenna or proposed location.
• The distance and azimuth to any trees within 1,000 feet of the antenna or proposed location, however, a single tree is acceptable as long as it is greater than 500 feet from the antenna or proposed location.
• The distance and azimuth to any tree(s) greater than 1,000 feet from the antenna penetrating a 2.0° plane from the antenna base or proposed location.
• The distance and azimuth to any building(s) or other objects with the potential to cause signal interference with an ASR antenna within 1,500 of the antenna and identify any other electronic equipment within 2500 feet of the ASR antenna or proposed location.
2.7. AIRPORT AIRSPACE ANALYSIS SURVEYS
When required, use the following specifications and associated figures to identify, collect, and analyze objects on, and surrounding airports. These specifications require extensive field/remote sensing
operations, providing data to support a wide range of NAS activities. This section details the requirements for completing an Airport Airspace Analysis Survey to support the planning and design activities of airports and ancillary tasks such as instrument flight procedure design. This section is complementary to other sections on the collection of runway, navigational aid, and other airport data. Complete the analysis based on the highest runway designation. For example, if one end of the runway is designated as a precision runway and the other end non-precision use the Runways with Vertical Guidance analysis criteria for both ends. When both ends of the runway are or plan to be used for nonvertically guided or visual operations complete the analysis using the Non-vertically Guided criteria.
2.7.1. Airport Airspace Survey Surfaces and Analysis
2.7.1.1. Runways with Vertical Guidance. These specifications support the airport’s planning and design activities for the development of vertically guided instrument approaches such as ILS, PAR, MLS, LPV, TLS, RNP and Baro VNAV. These surfaces assist in the identification of possible hazards to air navigation and critical approach/departure obstructions within the vicinity of the airport. All surfaces identified below must be completed for both ends of a runway. Evaluate each surface independently of other surfaces. Design all appropriate airport surfaces in reference to the runway ends and not displaced thresholds.
Continue reading ↓ 120 of 1015 passages shown