23CT
Heliport
Blanchette
Burlington, Connecticut

FAA NFDC Information Effective 56-day cycle 04/03/2014 - 5/29/2014

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

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: [-14W (2014)]
Sectional: NEW YORK
From City: 2nm W of Burlington

Operations

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 Center (ZBW)
FSS: Bridgeport FSS (BDR)
Wind Indicator: Lighted
Landing Fee: no

Communications

Services

Based Aircraft

Total: 0

Annual Operations

For year ending: 09/01/2003
Total: 0

Ownership

Owner: Paul J. Blanchette
12 Ventres Way
Burlington, Ct 06013
860-673-2173
Manager: Paul J. Blanchette
69 Daniel Trace
Burlington, Ct 06013
860-582-8961

Runways

Runways: H1

Runway 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.

Procedures

NOTAMs

Additional Remarks


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.