|
IFR Enroute Charts
at skyvector.com Click on airport for details, drag to scroll around. Zoom using +/- keys. |
|
IFR Enroute Charts
at skyvector.com Click on airport for details, drag to scroll around. Zoom using +/- keys. |
|
FAA NFDC Information Effective 56-day cycle 03/21/2024 - 5/16/2024
| Ops | Comms | Services | Owner | Runways | IFR Procs | Current NOTAMs | Remarks |
| FAA Identifier: | 23CT |
|---|---|
| Lat/Lng: | 41.7859, -72.9312972222 41-47-09.2400N, 072-55-52.6700W Estimated by Owner on 09/11/2003 |
| Elevation: | 500 feet Estimated by Owner on 09/11/2003 |
| Magnetic Variation: | [-13W (2024)] |
| Sectional: | NEW YORK |
| From City: | 2nm W of Burlington |
| Use: | Private |
|---|---|
| Airspace Analysis: | CONDITIONAL Provided Resolve Ingress/Egress with Traffic Pattern for Mountain Meadow Airport (22B) & Robertson Field (4B8); Private Use only; VFR Operations; & All Users are Notified & Comply with These Conditions. |
| Ownership: | Privately owned |
| Activation: | 12/2004 |
| Control Tower: | no |
| ARTCC: | Boston(ZBW)Boston Center |
| FSS: | Bridgeport FSS(BDR) |
| Wind Indicator: | Lighted |
| Landing Fee: | no |
Based Aircraft
|
Annual Operations
|
Ownership
|
| Runways: | H1 |
|---|
| Length: | 80 feet by Owner on 09/11/2003 |
|---|---|
| Width: | 80 feet |
| Surface: | Pierced Steel Planking / Landing Mats / Membranes 16 X 16 Concrete Pad. |
| Surface Treatment: | NONE |
| • | for Cd Contact Yankee Approach at 860-386-3597 |
|---|
This information is current as of the date at the top of the page. These pages are valid for all US airports, based on information from FAA National Flight Data Center. Weather information is provided based on AvnWx Data Sources. NOTAM information is from FAA's NAIMES data portal.
As with most information on this website, this page is generated based on FAA data, with automatic translations done via computer. You can also directly read the A/FD via the green icon link at the top of the page, which is the FAA text, and sometimes provides a different translation of codes. Please email me (using link at top-right of this page) if you see information which is confusing, misleading, or wrong....Or have suggestions for additions/changes.
Comments from the user community are clearly noted as such this page, are for informational purposes only, may be wrong and/or out-of-date, and must not be used as a sole source for critical decision making. See Privacy Policy and Conditions of Use.