| 48VT
Seaplane Base
|
Cub Cove
|
|
Colchester, Vermont
|
|
|
|
FAA NFDC Information Effective 56-day cycle 05/02/2013 - 6/27/2013
| FAA Identifier: | 48VT |
| Lat/Lng: |
44.5535472222, -73.2314972222
44-33-12.7700N, 073-13-53.3900W
Estimated by OWNER on 02/13/2009
|
| Elevation: |
95 feet
Estimated
by OWNER
on 02/13/2009
|
| Magnetic Variation: |
[-15W (2013)]
|
| Sectional: |
MONTREAL
|
| From City: |
6nm
W of Colchester
|
| Use: |
Private
|
| Airspace Analysis: |
CONDITIONAL
Provided Pvt Use only and All Traffic Pattern Conflicts are Resolved with Vt57.
|
| Ownership: |
Privately owned
|
| Activation: |
04/2009
|
| Attended: |
May-Oct Every day DAWN-DUSK (local)
|
| Control Tower: |
no
|
| ARTCC: |
Boston
(ZBW)
Boston Center
(ZBW)
|
| FSS: |
Burlington FSS
(BTV)
|
| Wind Indicator: |
None
|
| Landing Fee: |
no
|
| Single Engine GA: |
1
|
| Total: |
1
|
|
| For year ending: |
02/27/2006
|
| Total: |
0
|
|
| Owner: |
Frank Shea/ Catherine Rush
48 Spaulding East Shr
Colchester, Vt 05446
802-660-2641
|
| Manager: |
Frank Shea
48 Spaulding East Shr
Colchester, Vt 05446
802-660-2641
|
|
Runway 05W/23W
| Length: |
4000 feet
|
| Width: |
300 feet
|
| Surface: |
Water
|
|
End 05W |
End 23W |
| Objects: |
200 Ft Hill 400 Ft NW of Landing Area.
|
|
| Objects affecting Navigable Airspace (CFR part 77): |
Utility runway with a visual approach
|
Utility runway with a visual approach
|
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.