This map provides the locations of airports, which the FAA defines as areas on land or water intended to be used either wholly or in part for the arrival, departure, and surface movement of aircraft/helicopters. Thus, places such as hospitals with helicopter pads are depicted as airports in this dataset. The data is provided as a vector geospatial-enabled file format.

Airport defines area on land or water intended to be used either wholly or in part for the arrival; departure and surface movement of aircraft/helicopters. This airport data is provided as a vector geospatial-enabled file format and depicted on Enroute charts.Airport information is published every eight weeks by the U.S. Department of Transportation, Federal Aviation Administration-Aeronautical Information Services.Current Effective Date: 0901Z 12 Jun 2025 to 0901Z 07 Aug 2025

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

Current Effective Date: 0901Z 12 Jun 2025 to 0901Z 07 Aug 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 users with information about airport locations and attributes and can be used for national and regional analysis applications.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.For more information on the coded values in this dataset, please visit: https://nfdc.faa.gov/webContent/28DaySub/extra/30_Nov_2023_APT_CSV.zip

Current Effective Date: 0901Z 12 Jun 2025 to 0901Z 07 Aug 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 UAS Facility Maps are designed to identify permissible altitudes (above ground level) at which UAS, operating under the Small UAS Rule (14 CFR 107), can be authorized to fly within the surface areas of controlled airspace. These altitude parameters, provided by the respective air traffic control facilities, are criteria used to evaluate airspace authorization requests (14 CFR 107.41), submitted via FAA.GOV/UAS. Airspace authorization requests for altitudes in excess of the predetermined map parameters will require a lengthy coordination process. This dataset will be continually updated and expanded to include UAS Facility Maps for all controlled airspace by Fall 2017. This map is not updated in real time. Neither the map nor the information provided herein is guaranteed to be current or accurate. Reliance on this map constitutes neither FAA authorization to operate nor evidence of compliance with applicable aviation regulations in or during enforcement proceedings before the National Transportation Safety Board or any other forum. Disclaimer of Liability. The United States government will not be liable to you in respect of any claim, demand, or action—irrespective of the nature or cause of the claim, demand, or action—alleging any loss, injury, or damages, direct or indirect, that may result from the use or possession of any of the information in this draft map or any loss of profit, revenue, contracts, or savings or any other direct, indirect, incidental, special, or consequential damages arising out of any use of or reliance upon any of the information in this draft map, whether in an action in contract or tort or based on a warranty, even if the FAA has been advised of the possibility of such damages. The FAA’s total aggregate liability with respect to its obligations under this agreement or otherwise with respect to the use of this draft map or any information herein will not exceed $0. Some States, Territories, and Countries do not allow certain liability exclusions or damages limitations; to the extent of such disallowance and only to that extent, the paragraph above may not apply to you. In the event that you reside in a State, Territory, or Country that does not allow certain liability exclusions or damages limitations, you assume all risks attendant to the use of any of the information in this draft map in consideration for the provision of such information. Export Control. You agree not to export from anywhere any of the information in this draft map except in compliance with, and with all licenses and approvals required under, applicable export laws, rules, and regulations. Indemnity. You agree to indemnify, defend, and hold free and harmless the United States government from and against any liability, loss, injury (including injuries resulting in death), demand, action, cost, expense, or claim of any kind or character, including but not limited to attorney’s fees, arising out of or in connection with any use or possession by you of this draft map or the information herein. Governing Law. The above terms and conditions will be governed by the laws of each and every state within the United States, without giving effect to that state’s conflict-of-laws provisions. You agree to submit to the jurisdiction of the state or territory in which the relevant use of any of the information in this draft map occurred for any and all disputes, claims, and actions arising from or in connection with this draft map or the information herein.

Geospatial data about United States Federal Aviation Administration Class Airspace. Export to CAD, GIS, PDF, CSV and access via API.

Current Effective Date: 0901Z 12 May 2025 to 0901Z 07 Jul 2025The Digital Obstacle File dataset describes all known obstacles of interest to aviation users in the United States, with limited coverage of the Pacific, the Caribbean, Canada, and Mexico. It contains only obstruction data for those man-made objects that affect domestic aeronautical charting products and does not purport to indicate the presence of all obstructions that may be encountered. The obstacles are assigned unique numerical identifiers; accuracy codes, and listed in order by state. Obstacle information is published every eight weeks by the U.S. Department of Transportation, Federal Aviation Administration-Aeronautical Information Services.

Point features of airports in Connecticut, based on Federal Aviation Administration records.

The Federal Aviation Administration (FAA) Regions dataset is as of July 12, 2023 from the Federal Aviation Administrationâ s (FAA's) Office of National Engagement and Regional Administration (ARA) and is part of the U.S. Department of Transportation (USDOT)/Bureau of Transportation Statistics (BTS) National Transportation Atlas Database (NTAD). This dataset depicts the geographical boundaries of the nine FAA regions, which fall under the FAAâ s Office of National Engagement and Regional Administration (ARA). The regional office located within each region help the FAA build relationships and collaboration on the local level for the variety of stakeholders within each boundary. More information about the FAA Regions can be found at: https://www.faa.gov/about/office_org/headquarters_offices/ara

The Runway Ends Table 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 with information on the physical characteristics of the runways. Not all runways in this dataset have geospatial locations associated with them, as this is not a required data element from the airport source. As a result, this database contains a polyline layer, a points layer and a table. The polyline layer contains runways that had corresponding runways ends. The points layer contains mostly heliports, but also non-linear landing areas. The table contains runways where geospatial information was not reported. The runways in the database 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/1529790

The UAS Facility Maps are designed to identify permissible altitudes (above ground level) at which UAS, operating under the Small UAS Rule (14 CFR 107), can be authorized to fly within the surface areas of controlled airspace. These altitude parameters, provided by the respective air traffic control facilities, are criteria used to evaluate airspace authorization requests (14 CFR 107.41), submitted via FAA.GOV/UAS. Airspace authorization requests for altitudes in excess of the predetermined map parameters will require a lengthy coordination process. This dataset will be continually updated and expanded to include UAS Facility Maps for all controlled airspace by Fall 2017. This map is not updated in real time. Neither the map nor the information provided herein is guaranteed to be current or accurate. Reliance on this map constitutes neither FAA authorization to operate nor evidence of compliance with applicable aviation regulations in or during enforcement proceedings before the National Transportation Safety Board or any other forum. Disclaimer of Liability. The United States government will not be liable to you in respect of any claim, demand, or action-irrespective of the nature or cause of the claim, demand, or action-alleging any loss, injury, or damages, direct or indirect, that may result from the use or possession of any of the information in this draft map or any loss of profit, revenue, contracts, or savings or any other direct, indirect, incidental, special, or consequential damages arising out of any use of or reliance upon any of the information in this draft map, whether in an action in contract or tort or based on a warranty, even if the FAA has been advised of the possibility of such damages. The FAA's total aggregate liability with respect to its obligations under this agreement or otherwise with respect to the use of this draft map or any information herein will not exceed $0. Some States, Territories, and Countries do not allow certain liability exclusions or damages limitations; to the extent of such disallowance and only to that extent, the paragraph above may not apply to you. In the event that you reside in a State, Territory, or Country that does not allow certain liability exclusions or damages limitations, you assume all risks attendant to the use of any of the information in this draft map in consideration for the provision of such information. Export Control. You agree not to export from anywhere any of the information in this draft map except in compliance with, and with all licenses and approvals required under, applicable export laws, rules, and regulations. Indemnity. You agree to indemnify, defend, and hold free and harmless the United States government from and against any liability, loss, injury (including injuries resulting in death), demand, action, cost, expense, or claim of any kind or character, including but not limited to attorney's fees, arising out of or in connection with any use or possession by you of this draft map or the information herein. Governing Law. The above terms and conditions will be governed by the laws of each and every state within the United States, without giving effect to that state's conflict-of-laws provisions. You agree to submit to the jurisdiction of the state or territory in which the relevant use of any of the information in this draft map occurred for any and all disputes, claims, and actions arising from or in connection with this draft map or the information herein.

This dataset represents the location of public, private and military airports and heliports in Kentucky as derived from the Federal Aviation Administration Airport Data & Contact Information online database.Data Download: https://ky.box.com/s/c0k7h4jwz8u5d5e7fwmlbzq9qgqz11lb

This is a point layer of Military Airports currently permitted by the State of California, Department of Transportation (Caltrans), Division of Transportation Planning Aeronautics Program. The attributes include the airport location, function class, ownership, and the link of Federal Aviation Administration (FAA) site. FAA website has airport detail information and master records and reports.

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 allUAS 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 FDC7/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 operationsWHAT 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 FDC7/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 FDC7/7282here.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/uas2). 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 this provision , may also qualify for access under provision 2outlined 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 FDC7/7282and 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 FDC7/7282and 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 at https://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 at https://ioeaaa.faa.gov/oeaaa/Welcome.jspB.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-8276ADDITIONAL 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.govor by phone at (844) FLY-MY-UA.If you have any additional questions regarding the TFRs defined by NOTAM FDC7/7282and this website, please contact the FAA SOSC at (202) 267-8276.DisclaimersThe 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.htmlfor additional information on flight restrictions that may be in effect in your area before operating your UAS.

Airports Polygon is a 1:24,000-scale, feature-based layer that includes all airport features depicted on all of the U.S. Geological Survey (USGS) 7.5 minute topographic quadrangle maps that cover the State of Connecticut and are listed on the Federal Aviation Administration (FAA) "Airport Data (5010) & Contact Information" June 5, 2008 report. Airports in New York, Massachusetts and Rhode Island that are near the Connecticut state boundary are included. Airports that are listed by FAA and are visible on aerial photography (Connecticut 2004 Orthophotos and Connecticut 2006 NAIP Color Orthophotos from National Agriculture Imagery Program) are included. Airports that are listed by FAA but are not visible on aerial photography are not included. All airports listed by FAA are included in a separate point feature-based layer, Airport FAA CT. The airport point locations were generated from latitude and longitude coordinates contained in the FAA report and all the attribute information in the report was included. The airport layer is based partly on information from USGS topographic quadrangle maps published between 1969 and 1984 which does not represent airports in Connecticut at any one particular point in time. The layer does depict current conditions as to airports listed by FAA and having _location identification codes and visible on aerial photography of 2004 and 2006. The layer delineates airports and heliports. It includes airport name, airport _location code, type of facility, public or private use of facility and state the airport is located in. It does not include airport elevation, flight schedule, runway capacity, or ownership information. Features are polygonal and generally depict landing strips and perimeters for large and small airports and helicopter landing pads. Attribute information allows to cartographic representation (symbolize) and labeling of these features on a map. This layer was originally published in 1994 and slightly updated in 2005.

This is a point layer of Military Airports currently permitted by the State of California, Department of Transportation (Caltrans), Division of Aeronautics. The attributes include the airport location, function class, ownership, and the link of Federal Aviation Administration (FAA) site. FAA website has airport detail information and master records and reports.This data is provided as a service for planning purposes and not intended for design, navigation purposes or airspace consideration. Such needs should include discussions with the Federal Aviation Administration, Caltrans Division of Aeronautics, and the site management/owners.The maps and data are made available to the public solely for informational purposes. Information provided in the Caltrans GIS Data Library is accurate to the best of our knowledge and is subject to change on a regular basis, without notice. While the GIS Data Management Branch makes every effort to provide useful and accurate information, we do not warrant the information to be authoritative, complete, factual, or timely. Information is provided on an "as is" and an "as available" basis. The Department of Transportation is not liable to any party for any cost or damages, including any direct, indirect, special, incidental, or consequential damages, arising out of or in connection with the access or use of, or the inability to access or use, the Site or any of the Materials or Services described herein.CalTrans Division of Aeronautics.

Current Effective Date: 0901Z 12 Jun 2025 to 0901Z 07 Aug 2025A runway is a defined rectangular area on a land airport prepared for the landing and takeoff of aircraft along its length. Runways are normally numbered in relation to their magnetic direction rounded off to the nearest 10 degrees. This geospatial vector file provides information on the airport runway and helicopter landing areas. This runway dataset is depicted on Enroute charts.Runway information is published every eight weeks by the U.S. Department of Transportation, Federal Aviation Administration-Aeronautical Information Services.

A FRIA is a defined geographic area where drones can be flown without Remote ID equipment. Both the drone and the pilot must be located within the FRIA's boundaries throughout the operation. In addition, the pilot of the drone must be able to see it at all times throughout the duration of the flight.

For further guidance on the FRIA application, read Advisory Circular 89-3.

For additional information on FRIA, read 14 CFR Part 89.

Got Questions? Contact the UAS Support Center