Long Pond Landing
Pelham, New Hampshire

FAA NFDC Information Effective 56-day cycle 09/14/2017 - 11/9/2017

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks


FAA Identifier:36NH
Lat/Lng: 42.7008333333, -71.3711111111
42-42-03.0000N, 071-22-16.0000W
Estimated by OWNER on 08/06/2004
Elevation: 185 feet Estimated by OWNER on 08/06/2004
Magnetic Variation: [-15W (2017)]
From City: 2nm SE of Pelham


Use: Private
Airspace Analysis: CONDITIONAL
Provided Ingress at 355 Degs & Egress at 175 Degs; Resolve Any Traffic Pattern Conflicts with Merrimack Valley Spb; Install Wind Indicator; Daylight VFR Operations only; Private Use; and All Users are Notified of These Conditons.
Ownership: Privately owned
Activation: 08/2004
Control Tower: no
ARTCC: Boston Center (ZBW)
FSS: Burlington FSS (BTV)
Wind Indicator: Lighted
Landing Fee: no



Based Aircraft

Total: 0

Annual Operations

For year ending: 08/06/2004
Total: 0


Owner: Richard & Brenda Lannan
11 Mcgrath Rd
Pelham, Nh 03076
Manager: Steven R. Rancourt
7 Mcgrath Road
Pelham, Nh 03076


Runways: H1

Runway H1

Length: 87 feet
Width: 40 feet
Surface: Asphalt / Bituminous Concrete



Additional Remarks

Owner Does not Want Heliport Charted.
800 Ft Towers with Wires 2.1 NM North of Pad.
Prior Permission from Owners or Manager for Any Landing.

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.