NY38
Airport
Mc Bride's
Gorham, New York

FAA NFDC Information Effective 56-day cycle 11/13/2014 - 1/8/2015

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:NY38
Lat/Lng: 42.8531211111, -77.1246958333
42-51-11.2360N, 077-07-28.9050W
Estimated
Elevation: 915 feet Estimated by NACO on 07/07/2004
Magnetic Variation: 11W, (1985), [-12W (2014)]
Sectional: DETROIT
From City: 4nm N of Gorham

Operations

Use: Private
Airspace Analysis: CONDITIONAL
VFR Use only;Trees East of Runway be Cleared in Accordance with Far Part 77.25
Ownership: Privately owned
Activation: 11/1988
Control Tower: no
ARTCC: Cleveland Center (ZOB)
FSS: Buffalo FSS (BUF)
Wind Indicator: Unlighted
Landing Fee: no

Communications

Services

Based Aircraft

Single Engine GA: 1
Total: 1

Annual Operations

Total: 0

Ownership

Owner: John M. Mc Bride
3629 Goose St
Stanley, Ny 14561
585-526-6366
Manager: John M. Mc Bride
3629 Goose St
Stanley, Ny 14561
585-526-6366

Runways

Runways: 01/19

Runway 01/19

Length: 1800 feet
Width: 80 feet
Surface: Grass / Sod
End 01 End 19
Objects: Trees Powerline
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach
Object Height: 20' AGL 25' AGL
Object Distance: 600' Along centerline 2600' Along centerline

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.