Current Effective Date: 0901Z 07 Aug 2025 to 0901Z 02 Oct 2025This Class Airspace data is provided as a vector geospatial-enabled file format and depicted on Enroute charts. Class Airspace data is published every eight weeks by the U.S. Department of Transportation, Federal Aviation Administration-Aeronautical Information Services.

The Aviation Facilities dataset is updated every 28 days from the Federal Aviation Administration (FAA) and is part of the U.S. Department of Transportation (USDOT)/Bureau of Transportation Statistics (BTS) National Transportation Atlas Database (NTAD). The Aviation Facilities dataset is a geographic point database of all official and operational aerodromes in the United States and U.S. Territories. Attribute data is provided on the physical and operational characteristics of the aerodrome, current usage including enplanements and aircraft operations, congestion levels and usage categories. This geospatial data is derived from the FAA's National Airspace System Resource Aeronautical Data Product. For more information about these data, please visit: https://www.faa.gov/air_traffic/flight_info/aeronav/Aero_Data/NASR_Subscription. A data dictionary, or other source of attribute information, is accessible at https://doi.org/10.21949/1529011

The Runways dataset is updated every 28 days from the Federal Aviation Administration (FAA) and is part of the U.S. Department of Transportation (USDOT)/Bureau of Transportation Statistics (BTS) National Transportation Atlas Database (NTAD). The Runways database contains runways in the United States and US territories containing information on the physical characteristics of the runways. This data layer contains runways that have corresponding and reported runways ends, and the linear feature of the runway could be created based off these points. The runways in the dataset are associated with the airports dataset on NTAD, showing runways for all official and operational aerodromes. This geospatial data is derived from the FAA's National Airspace System Resource Aeronautical Data. A data dictionary, or other source of attribute information, is accessible at https://doi.org/10.21949/1529077

General Aviation Airports are public-use airports that do not have scheduled service or have less than 2,500 annual passenger boardings (49 USC 47102(8)). Approximately 88 percent of airports included in the NPIAS are general aviation.

http://www.faa.gov/airports/planning_capacity/passenger_allcargo_stats/categories/

© FAA This layer is a component of Airports.

Airports categorized using the FAA Classification System: http://www.faa.gov/airports/planning_capacity/passenger_allcargo_stats/categories/

© FAA, BTS, Derald Dudley

Current Effective Date: 0901Z 07 Aug 2025 to 0901Z 02 Oct 2025Military Training Routes (MTRs) are routes used by military aircraft to maintain proficiency in tactical flying. These routes are usually established below 10,000 feet MSL for operations at speeds in excess of 250 knots. MTRs data is provided as a geospatial vector file formats and depicted on Enroute charts.MTRs data information is published every eight weeks by the U.S. Department of Transportation, Federal Aviation Administration-Aeronautical Information Services.

Current Effective Date: 0901Z 07 Aug 2025 to 0901Z 02 Oct 2025This Special Use Airspace (SUA) data is provided as a vector geospatial-enabled file format and depicted on Enroute charts. Special Use Airspace data is published every eight weeks by the U.S. Department of Transportation, Federal Aviation Administration-Aeronautical Information Services.

The dataset provides noise data to facilitate the tracking of trends in transportation-related noise. This dataset includes results from simplified noise modeling methods and should not be used to evaluate noise levels in individual locations. See the documentation for a full description of methodologies and assumptions: https://doi.org/10.21949/1519111 The 2018 National Transportation Noise Map dataset utilized transportation mode input data from 2018 in a model and is current as of October 2020, published by the Bureau of Transportation Statistics (BTS), and is part of the U.S. Department of Transportation (USDOT)/Bureau of Transportation Statistics (BTS) National Transportation Atlas Database (NTAD). Please see the website https://www.bts.gov/geospatial/national-transportation-noise-map, for downloads and more information about these datasets. For web services of these data, please navigate to https://geo.dot.gov/server/rest/services/Hosted and search for service names beginning with "Noise." Data within the National Transportation Noise Map represent potential noise levels across the nation for an average annual day for the specified year. These data are intended to facilitate the tracking of trends in transportation-related noise by mode collectively over time and should not be used to evaluate noise levels in individual locations and/or at specific times. This dataset is developed using a 24-hr equivalent A-weighted sound level (denoted by LAeq) noise metric. The results represent the approximate average noise energy due to transportation noise sources over a 24-hour period at the receptor locations where noise is computed. Layers include Aviation, Passenger Rail (prototype), and Road Noise for the Lower 48 States as well as Alaska and Hawaii. The full listing can be found below. 2018 National Transportation Noise Alaska Alaska Aviation Noise Alaska Road and Aviation Noise Alaska Road Noise Lower 48 States (CONUS) Lower 48 States (CONUS) Aviation Noise Lower 48 States (CONUS) Passenger Rail Noise (prototype) Lower 48 States (CONUS) Passenger Rail, Road, and Aviation Noise (prototype) Lower 48 States (CONUS) Road and Aviation Noise Lower 48 States (CONUS) Road Noise Hawaii Hawaii Aviation Noise Hawaii Road and Aviation Noise Hawaii Road Noise

This map layer includes airports in the United States, Puerto Rico and the U.S. Virgin Islands. The data were derived from an extract of the Public-Use Airports database of the National Transportation Atlas Databases-2010 (NTAD-2010), published by the Bureau of Transportation Statistics, Department of Transportation.

The 2020 National Transportation Noise Map dataset utilized transportation mode input data from 2020 in a model and is current as of October 2022, published by the Bureau of Transportation Statistics (BTS), and is part of the U.S. Department of Transportation (USDOT)/Bureau of Transportation Statistics (BTS) National Transportation Atlas Database (NTAD). Please see the website https://www.bts.gov/geospatial/national-transportation-noise-map, for downloads and more information about these datasets. For web services of these data, please navigate to https://geo.dot.gov/server/rest/services/Hosted and search for service names beginning with "Noise." Please contact j.goworowska@dot.gov for any questions. Data within the National Transportation Noise Map represent potential noise levels across the nation for an average annual day for the specified year. These data are intended to facilitate the tracking of trends in transportation-related noise by mode collectively over time and should not be used to evaluate noise levels in individual locations and/or at specific times. This dataset is developed using a 24-hr equivalent A-weighted sound level (denoted by LAeq) noise metric. The results represent the approximate average noise energy due to transportation noise sources over a 24-hour period at the receptor locations where noise is computed. Layers include Aviation, Freight and Passenger Rail, and Road Noise for the Lower 48 States as well as Alaska and Hawaii. The full listing can be found below. 2020 National Transportation Noise

      Alaska

             Alaska Aviation Noise
             Alaska Freight and Passenger Rail Noise
             Alaska Freight and Passenger Rail, Road, and Aviation Noise
             Alaska Road and Aviation Noise
             Alaska Road Noise

      Lower 48 States (CONUS)

             Lower 48 States (CONUS) Aviation Noise
             Lower 48 States (CONUS) Freight and Passenger Rail Noise
             Lower 48 States (CONUS) Freight and Passenger Rail, Road, and Aviation Noise
             Lower 48 States (CONUS) Road and Aviation Noise
             Lower 48 States (CONUS) Road Noise

      Hawaii

             Hawaii Aviation Noise
             Hawaii Road and Aviation Noise
             Hawaii Road Noise

This dataset displays the aviation related businesses within Washington State. Industry sectors were selected that include businesses with a high propensity to rely on aviation services as part of their typical business activities. These activities include scheduled commercial service, general aviation, and air cargo. Industry types were identified by North American Industry Classification System (NAICS) code based on the findings of numerous economic impact studies conducted for state departments of transportation and individual airports across the U.S. and in close consultation with WSDOT Aviation. Information was collected from ESRI’s Community Analyst application in September 2019. This data is provided to the public as courtesy for general aviation planning purposes. The information provided should not be relied upon for navigational, engineering, legal or other site-specific uses. It may not show an airport's current capabilities or configuration. Inaccuracies in the layer may be attributed to: spatial errors in data, airport construction, or recent changes in airport capabilities. If you have any questions about the information presented here, please contact John MacArthur, john.macarthur@wsdot.wa.gov.

The “Protected Small Landscape Element” map is included in the Environment Regulation. On this are the most special, often old landscape features of the province of Utrecht. These elements are protected and should not be cut down. In 2021, this map was updated with elements in the municipality of Vijfheerenlanden and a number of new elements in the rest of the province. The Environment Regulation has been adopted but will only work after the Environment Act enters into force.Until then the map from the Interim Regulation is active.

The National Transportation Noise Map is developed using a 24-hr equivalent sound level (LEQ, denoted by LAeq) noise metric. The results are A-weighted noise levels that represent the approximate average noise energy due to transportation noise sources over the 24 hour period at the defined receptors. This map includes simplified noise modeling and is intended for the tracking of trends, it should not be used to evaluate noise levels in individual locations and/or at specific times.

This Airspace Schedule data represents the controlled airspace schedule for airspace volumes in accordance with a location’s control tower hours. The airspace schedule defines the start time and end time for which the airspace volume is active. If the airspace volume is not active, the airspace is uncontrolled. The data is provided in CSV and GeoJSON file formats. Airspace Schedule information is published every eight weeks by the U.S. Department of Transportation, Federal Aviation Administration-Aeronautical Information Services. Current Effective Date: 0901Z 30 Nov 2023 to 0901Z 25 Jan 2024.

The Airspace Boundary data is provided as a vector geospatial-enabled file format. Airspace Boundary data is published every eight weeks by the U.S. Department of Transportation, Federal Aviation Administration-Aeronautical Information Services. Current Effective Date: 0901Z 16 May 2024 to 0901Z 11 Jul 2024.

Current Effective Date: 0901Z 07 Aug 2025 to 0901Z 02 Oct 2025This Route Airspace data is provided as a vector geospatial-enabled file format and depicted on Enroute charts. Route Airspace data is published every eight weeks by the U.S. Department of Transportation, Federal Aviation Administration-Aeronautical Information Services.

The National Security UAS Flight Restrictions in this dataset are currently pending and will become effective on November 07, 2019. The FAA, pursuant to Title 14 of the Code of Federal Regulations (CFR) § 99.7, Special security instructions (SSI), has prohibited all UAS flight operations within the airspace defined under NOTAM FDC 7/7282 . Specific locations are described in the table and on the interactive map provided on this website. The TFRs extend from the surface up to 400 feet Above Ground Level (AGL), apply to all types and purposes of UAS flight operations, and remain in effect 24 hours a day, 7 days a week.

WHAT UAS FLIGHT RESTRICTIONS HAVE BEEN PUT INTO PLACE?

At the request of and pursuant to agreements with the Department of Defense and U.S. Federal security and intelligence agencies (“sponsoring Federal agencies”), the Federal Aviation Administration (FAA) has implemented Special Security Instructions for Unmanned Aircraft System (UAS), issued as temporary flight restrictions (TFR) over select national security sensitive facilities located throughout the U.S. These TFRs are established within the lateral boundaries of these facilities and extend from surface to 400 feet Above Ground Level (AGL). These TFRs apply to all UAS operations specifically including:

· Public aircraft operations conducted in accordance with a Certificate of Authorization or Waiver (COA).

· Civil aircraft operations (other than model aircraft), including those conducted in accordance with a COA and those conducted in accordance with the FAA’s small UAS Rule, 14 CFR Part 107.

· Model Aircraft operations conducted in accordance with 14 CFR Part 101, Subpart E.

UAS operators must comply with these flight restrictions in addition to all other applicable Federal Aviation Regulations, including but not limited to, requirements to secure an FAA airspace authorization and/or waiver prior to flying in the airspace where a TFR is in effect.

The information on this website complements Notice to Airmen (NOTAM) NOTAM FDC 7/7282, which generally notifies the public about these temporary flight restrictions (TFR). This website provides UAS operators with more detailed information about these TFRs, including:

· An explanation of what is restricted

· A table listing the selected facilities over which a TFR has been established

· An interactive map providing visual depictions and information about specific TFRs and geospatial (GIS) data that can be downloaded

· An explanation of which UAS operations may be able to access the airspace within a TFR, including instructions for submitting a request

· Reminders on other requirements for UAS operations

WHAT HAPPENS IF I VIOLATE A TEMPORARY FLIGHT RESTRICTION (TFR)?

The FAA classifies the airspace encompassed by these temporary flight restrictions (TFRs) as “national defense airspace” in accordance with Title 49 of the United States Code (USC) § 40103(b)(3). Violations of these TFRs may prompt the following enforcement actions:

A. The U.S. Government may pursue criminal charges, including charges under Title 49 U.S.C § 46307.

B. The FAA may take administrative action, including imposing civil penalties and the revoking FAA certificates and authorizations to operate UAS under Title 49 U.S.C. §§ 44709 and 46301.

WHAT ARE THE BASIC FLIGHT RESTRICTIONS?

The FAA, pursuant to Title 14 of the Code of Federal Regulations (CFR) § 99.7, Special security instructions (SSI), has prohibited all UAS flight operations within the airspace defined under NOTAM FDC 7/7282. Specific locations are described in the table and on the interactive map provided on this website. The TFRs extend from the surface up to 400 feet Above Ground Level (AGL), apply to all types and purposes of UAS flight operations, and remain in effect 24 hours a day, 7 days a week.

See the full text of NOTAM FDC 7/7282 here.

ARE THERE EXCEPTIONS FOR UAS OPERATIONS TO ACCESS A TFR?

The FAA has authorized UAS operations within the TFRs if those flights are in compliance with the applicable requirements listed below:

1) The UAS flight operation has been pre-approved by the designated facility contact based on criteria established by the sponsoring federal agency in coordination with the FAA. Note: UAS operators seeking approval to operate in one of the TFRs defined in this website under this provision must contact the facility’s designated point of contact identified in the table or interactive map, and secure permission to operate within the airspace prior to entry. Pre-approval from the facility or sponsoring agency does not substitute for compliance with FAA requirements. Depending on the nature of the proposed operation and Class of airspace, waiver or authorization may be needed from the FAA before flight. For more information visit our website at www.faa.gov/uas

2). The UAS flight operation is conducted in direct support of an active national defense, homeland security, law enforcement, firefighting, search and rescue, or disaster response mission, and prior notification has been provided to the designated facility contact. Note: UAS operators seeking approval to operate in one of the TFRs defined in this website under this provision must contact the facility’s designated point of contact identified in the table or interactive map, and provide notification prior to entering the airspace. These operators must make every effort to coordinate with the designated facility to deconflict the UAS flight operation with any safety or security concerns stated by the facility and/or sponsoring Federal agency.

3). The UAS flight operation is conducted in direct support of a significant and urgent governmental interest and is approved by the FAA’s System Operations Support Center (SOSC) in advance of entering the TFR. Note: UAS operators, that meet the criteria for thisprovision , may also qualify for access under provision 2 outlined above and are encouraged to coordinate directly with the facility’s designated point of contact identified in the table or interactive map, by providing notification prior to entering the airspace and taking into consideration any safety or security concerns stated by the facility and/or sponsoring Federal agency.

For urgent and time sensitive requests, contact the FAA’s SOSC at (202) 267-8276 for expedited assistance. The FAA’s SOSC will coordinate with the facility and/or sponsoring Federal agency as appropriate.

ARE THERE OTHER REQUIREMENTS TO OPERATE IN A TFR IN ADDITION TO THE EXCEPTIONS?

Separate and distinct from any of the conditions cited above used to gain access to a TFR defined by NOTAM FDC 7/7282 and described in this website, UAS operators must comply with all applicable Federal Aviation Regulations. For example:

For Model Aircraft:

· Comply with 14 CFR Part 101, Subpart E

NOTE: These provisions require model aircraft operators to notify any airport operator and air traffic control tower within 5 miles of the intended area of flight.

For All Other UAS Operators:

· Comply with a Public Aircraft Certificate of Authorization or Waiver (COA), or

· Comply with 14 CFR Part107, Small Unmanned Aircraft Systems, or

· Comply with Section 333 Exemption and a Certificate of Authorization or Waiver (COA)

NOTE: Public and civil UAS operators flying under the provisions of a COA or 14 CFR Part 107 may need to secure further airspace authorizations or waivers in order to conduct the proposed flight operation in controlled airspace, which may overlap with one of the TFRs defined by NOTAM FDC 7/7282 and this website. In those cases, these operators should follow the pre-existing procedures outlined below.

A. Non-emergency requests for UAS airspace authorizations and waivers must be submitted using the regular process as follows:

· 14 CFR Part 107 requests for airspace authorizations and waivers must be submitted to the FAA athttps://www.faa.gov/uas/request_waiver/

·
Section 333 Exemption holders may request a site specific COA at https://oeaaa.faa.gov/oeaaa/external/uas/portal.jsp

· Public aircraft operators without an existing authorization to operate must secure a public COA athttps://ioeaaa.faa.gov/oeaaa/Welcome.jsp

B. Emergency requests for UAS authorizations/waivers for missions that directly support significant and urgent governmental interests (e.g., active national defense, homeland security, law enforcement, and emergency operations missions), which cannot be supported by the FAA’s routine authorization/waiver processes should be referred to the SOSC at (202) 267-8276

ADDITIONAL QUESTIONS?

If you have any general questions regarding UAS operations, please refer to the following FAA webpage: https://www.faa.gov/uas/ , or contact the FAA by email at uashelp@faa.gov or by phone at (844) FLY-MY-UA.

If you have any additional questions regarding the TFRs defined by NOTAM FDC 7/7282 and this website, please contact the FAA SOSC at (202) 267-8276.

Disclaimers

The restrictions depicted on this site reflect temporary flight restrictions issued for national security reasons at select U.S. Federal facilities. There may be additional temporary flight restrictions that prohibit UAS and manned flight in effect in your area. Seehttp://tfr.faa.gov/tfr2/list.html for additional information on flight restrictions that may be in effect in your area before operating your UAS.

The FAA, pursuant to Title 14 of the Code of Federal Regulations (CFR) § 99.7, Special security instructions (SSI), has prohibited all UAS flight operations within the airspace defined under NOTAM FDC 7/7282 . Specific locations are described in the table and on the interactive map provided on this website. The TFRs extend from the surface up to 400 feet Above Ground Level (AGL), apply to all types and purposes of UAS flight operations, and remain in effect 24 hours a day, 7 days a week. WHAT UAS FLIGHT RESTRICTIONS HAVE BEEN PUT INTO PLACE? At the request of and pursuant to agreements with the Department of Defense and U.S. Federal security and intelligence agencies (“sponsoring Federal agencies”), the Federal Aviation Administration (FAA) has implemented Special Security Instructions for Unmanned Aircraft System (UAS), issued as temporary flight restrictions (TFR) over select national security sensitive facilities located throughout the U.S. These TFRs are established within the lateral boundaries of these facilities and extend from surface to 400 feet Above Ground Level (AGL). These TFRs apply to all UAS operations specifically including: · Public aircraft operations conducted in accordance with a Certificate of Authorization or Waiver (COA). · Civil aircraft operations (other than model aircraft), including those conducted in accordance with a COA and those conducted in accordance with the FAA’s small UAS Rule, 14 CFR Part 107. · Model Aircraft operations conducted in accordance with 14 CFR Part 101, Subpart E. UAS operators must comply with these flight restrictions in addition to all other applicable Federal Aviation Regulations, including but not limited to, requirements to secure an FAA airspace authorization and/or waiver prior to flying in the airspace where a TFR is in effect. The information on this website complements Notice to Airmen (NOTAM) NOTAM FDC 7/7282, which generally notifies the public about these temporary flight restrictions (TFR). This website provides UAS operators with more detailed information about these TFRs, including: · An explanation of what is restricted · A table listing the selected facilities over which a TFR has been established · An interactive map providing visual depictions and information about specific TFRs and geospatial (GIS) data that can be downloaded · An explanation of which UAS operations may be able to access the airspace within a TFR, including instructions for submitting a request · Reminders on other requirements for UAS operations WHAT HAPPENS IF I VIOLATE A TEMPORARY FLIGHT RESTRICTION (TFR)? The FAA classifies the airspace encompassed by these temporary flight restrictions (TFRs) as “national defense airspace” in accordance with Title 49 of the United States Code (USC) § 40103(b)(3). Violations of these TFRs may prompt the following enforcement actions: A. The U.S. Government may pursue criminal charges, including charges under Title 49 U.S.C § 46307. B. The FAA may take administrative action, including imposing civil penalties and the revoking FAA certificates and authorizations to operate UAS under Title 49 U.S.C. §§ 44709 and 46301. WHAT ARE THE BASIC FLIGHT RESTRICTIONS? The FAA, pursuant to Title 14 of the Code of Federal Regulations (CFR) § 99.7, Special security instructions (SSI), has prohibited all UAS flight operations within the airspace defined under NOTAM FDC 7/7282. Specific locations are described in the table and on the interactive map provided on this website. The TFRs extend from the surface up to 400 feet Above Ground Level (AGL), apply to all types and purposes of UAS flight operations, and remain in effect 24 hours a day, 7 days a week. See the full text of NOTAM FDC 7/7282 here. ARE THERE EXCEPTIONS FOR UAS OPERATIONS TO ACCESS A TFR? The FAA has authorized UAS operations within the TFRs if those flights are in compliance with the applicable requirements listed below: 1) The UAS flight operation has been pre-approved by the designated facility contact based on criteria established by the sponsoring federal agency in coordination with the FAA. Note: UAS operators seeking approval to operate in one of the TFRs defined in this website under this provision must contact the facility’s designated point of contact identified in the table or interactive map, and secure permission to operate within the airspace prior to entry. Pre-approval from the facility or sponsoring agency does not substitute for compliance with FAA requirements. Depending on the nature of the proposed operation and Class of airspace, waiver or authorization may be needed from the FAA before flight. For more information visit our website at www.faa.gov/uas 2). The UAS flight operation is conducted in direct support of an active national defense, homeland security, law enforcement, firefighting, search and rescue, or disaster response mission, and prior notification has been provided to the designated facility contact. Note: UAS operators seeking approval to operate in one of the TFRs defined in this website under this provision must contact the facility’s designated point of contact identified in the table or interactive map, and provide notification prior to entering the airspace. These operators must make every effort to coordinate with the designated facility to deconflict the UAS flight operation with any safety or security concerns stated by the facility and/or sponsoring Federal agency. 3). The UAS flight operation is conducted in direct support of a significant and urgent governmental interest and is approved by the FAA’s System Operations Support Center (SOSC) in advance of entering the TFR. Note: UAS operators, that meet the criteria for thisprovision , may also qualify for access under provision 2 outlined above and are encouraged to coordinate directly with the facility’s designated point of contact identified in the table or interactive map, by providing notification prior to entering the airspace and taking into consideration any safety or security concerns stated by the facility and/or sponsoring Federal agency. For urgent and time sensitive requests, contact the FAA’s SOSC at (202) 267-8276 for expedited assistance. The FAA’s SOSC will coordinate with the facility and/or sponsoring Federal agency as appropriate. ARE THERE OTHER REQUIREMENTS TO OPERATE IN A TFR IN ADDITION TO THE EXCEPTIONS? Separate and distinct from any of the conditions cited above used to gain access to a TFR defined by NOTAM FDC 7/7282 and described in this website, UAS operators must comply with all applicable Federal Aviation Regulations. For example: For Model Aircraft: · Comply with 14 CFR Part 101, Subpart E NOTE: These provisions require model aircraft operators to notify any airport operator and air traffic control tower within 5 miles of the intended area of flight. For All Other UAS Operators: · Comply with a Public Aircraft Certificate of Authorization or Waiver (COA), or · Comply with 14 CFR Part107, Small Unmanned Aircraft Systems, or · Comply with Section 333 Exemption and a Certificate of Authorization or Waiver (COA) NOTE: Public and civil UAS operators flying under the provisions of a COA or 14 CFR Part 107 may need to secure further airspace authorizations or waivers in order to conduct the proposed flight operation in controlled airspace, which may overlap with one of the TFRs defined by NOTAM FDC 7/7282 and this website. In those cases, these operators should follow the pre-existing procedures outlined below. A. Non-emergency requests for UAS airspace authorizations and waivers must be submitted using the regular process as follows: · 14 CFR Part 107 requests for airspace authorizations and waivers must be submitted to the FAA athttps://www.faa.gov/uas/request_waiver/ · Section 333 Exemption holders may request a site specific COA at https://oeaaa.faa.gov/oeaaa/external/uas/portal.jsp · Public aircraft operators without an existing authorization to operate must secure a public COA athttps://ioeaaa.faa.gov/oeaaa/Welcome.jsp B. Emergency requests for UAS authorizations/waivers for missions that directly support significant and urgent governmental interests (e.g., active national defense, homeland security, law enforcement, and emergency operations missions), which cannot be supported by the FAA’s routine authorization/waiver processes should be referred to the SOSC at (202) 267-8276 ADDITIONAL QUESTIONS? If you have any general questions regarding UAS operations, please refer to the following FAA webpage: https://www.faa.gov/uas/ , or contact the FAA by email at uashelp@faa.gov or by phone at (844) FLY-MY-UA. If you have any additional questions regarding the TFRs defined by NOTAM FDC 7/7282 and this website, please contact the FAA SOSC at (202) 267-8276. Disclaimers The restrictions depicted on this site reflect temporary flight restrictions issued for national security reasons at select U.S. Federal facilities. There may be additional temporary flight restrictions that prohibit UAS and manned flight in effect in your area. See http://tfr.faa.gov/tfr2/list.html for additional information on flight restrictions that may be in effect in your area before operating your UAS.

This map layer, utilizing data from the Federal Aviation Administration (FAA), displays all U.S. Airports and Heliports with pilot-specific information about each airfield.Airports designated as "5010 Airports" are public-use airports which have been included in an electronically generated document titled "Form 5010" by the FAA. The office of primary responsibility for this form is the Office of Airport Safety and Standards - Airport Engineering Division (AAS-100), which is responsible for airport engineering standards for configuration, design, equipment, and operations criteria at civil airports. Heliports typically are used by general aviation operators and serve very few air carrier operations. Furthermore, there are very few helicopters that can seat more than nine passengers, and fewer still are used for scheduled passenger operations. Since Congress has not given FAA the authority to certify facilities serving general aviation operations and the clear majority of operations served by heliports are by general aviation operators, certificating the few heliports that serve air carrier operations would not significantly enhance safety.5010 AirportsData Currency: October, 2017For more information: Airport Data & Contact Information.For feedback please contact: ArcGIScomNationalMaps@esri.comThumbnail image courtesy of Simon ClancyOther Federal User Community federally focused content that may interest youDepartment of TransportationFederal Aviation AdministrationOpen Data: USDOTOpen Data: FAA

ATS Route is a specified route designed for channeling the flow of traffic as necessary for the provision of air traffic services. The ATS Route data is provided in a vector geospatial file format and depicted on Enroute charts. ATS Routes information is published every eight weeks by the U.S. Department of Transportation, Federal Aviation Administration-Aeronautical Information Services. Current Effective Date: 0901Z 07 Aug 2025 to 0901Z 02 Oct 2025

Abstract: Data downloaded from the USDOT Bureau of Transportation Statistics Open Data Catalog and clipped to Volusia County plus the surrounding area. It was then saved as a local file in SPC FL E NAD83. A Coast Guard facility in Ponce Inlet and a private airport in Osteen were added as they were not included. Some attribute fields were removed, and some points were moved based on visual inspection of aerial photography.The Airports dataset includes all official and operational aerodromes as of July 16, 2020 and is part of the U.S. Department of Transportation (USDOT)/Bureau of Transportation Statistics (BTS) National Transportation Atlas Database (NTAD). The Airports database is a geographic point database of official operational aerodromes in the United States and U.S. Territories. Attribute data is provided on the physical and operational characteristics of the aerodrome, current usage including enplanements and aircraft operations, congestion levels and usage categories. This geospatial data is derived from the FAA's National Airspace System Resource Aeronautical Data Product.Copyright Text: Credit the Assistant Secretary for Research and Technology/Bureau of Transportation Statistics (BTS) National Transportation Atlas Database (NTAD). The Federal Aviation Administration (FAA) develops and maintains the textual data from which this geospatial layer was derived.