| 0CT1
Heliport
|
Bristol-Myers Squibb Company
|
|
Wallingford, Connecticut
|
|
|
|
FAA NFDC Information Effective 56-day cycle 05/02/2013 - 6/27/2013
| FAA Identifier: | 0CT1 (Zero-Charlie-Tango-One) |
| Lat/Lng: |
41.4848197222, -72.7562083333
41-29-05.3510N, 072-45-22.3500W
Estimated
|
| Elevation: |
350 feet
Estimated
|
| Magnetic Variation: |
14W,
(1985),
[-14W (2013)]
|
| Sectional: |
NEW YORK
|
| From City: |
3nm
NE of Wallingford
|
| Use: |
Private
|
| Airspace Analysis: |
CONDITIONAL
Provided VFR only.
|
| Ownership: |
Privately owned
|
| Activation: |
04/1987
|
| Attended: |
Continuous
Prior Permission from Bristol-Myers Director of Aviation, 212-546-5131 or 914-761-8179.
|
| Control Tower: |
no
|
| ARTCC: |
Boston Center
(ZBW)
|
| FSS: |
Bridgeport FSS
(BDR)
|
| Wind Indicator: |
Unlighted
|
| Lights: |
Prior Permission for Perimeter Lights; Call Bristol-Myers Squibb Security 203-284-6100.
|
| Landing Fee: |
no
|
|
|
|
| Owner: |
Bristol-Myers Squibb Company
5 Research Parkway
Wallingford, Ct 06492
203-284-6100
|
| Manager: |
Thomas Ewing
5 Research Parkway
Wallingford, Ct 06492
203-284-6248
Home Phone 203-635-6582.
|
|
Runway H1
| Length: |
50 feet
|
| Width: |
50 feet
|
| Surface: |
Asphalt / Bituminous Concrete
|
| Runway Lights Edge Intensity: |
Perimeter Lights.
|
| Remarks: |
Helipad is Circular.
|
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.