Peasley Field
Otis, Maine

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:0ME4 (Zero-Mike-Echo-Four)
Lat/Lng: 44.7424694444, -68.4744027778
44-44-32.8900N, 068-28-27.8500W
Estimated by OWNER on 09/27/2008
Elevation: 271 feet Estimated by OWNER on 09/27/2008
Magnetic Variation: [-16W (2017)]
Sectional: HALIFAX
From City: 5nm N of Otis


Use: Private
Airspace Analysis: CONDITIONAL
Provided VFR Operations & Pvt Use only; Daytime Operations only; Windsock Installed Prior to Beginning Operations.
Ownership: Privately owned
Activation: 06/2009
Control Tower: no
ARTCC: Boston (ZBW) Boston Center (ZBW)
FSS: Bangor FSS (BGR)
Wind Indicator: Unlighted
Landing Fee: no



Based Aircraft

Single Engine GA: 3
Total: 3

Annual Operations

For year ending: 09/30/2007
Total: 0


Owner: Robert Peasley
4 Channel Rock Rd
Otis, Me 04605
Manager: Robert Peasley
4 Channel Rock Rd
Otis, Me 04605


Runways: 16/34

Runway 16/34

Length: 2000 feet
by Owner on 09/27/2008
Width: 110 feet
Surface: Grass / Sod
End 16 End 34
Objects: Trees Trees
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach
Object Height: 60' AGL 60' AGL
Object Distance: 200' Along centerline 200' Along centerline



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.