ME22
Airport
Avery Field
Rockwood, Maine

FAA NFDC Information Effective 56-day cycle 07/24/2014 - 9/18/2014

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:ME22
Lat/Lng: 45.6711666667, -69.8067777778
45-40-16.2000N, 069-48-24.4000W
Estimated by OWNER on 11/17/2004
Elevation: 1070 feet Estimated by OWNER on 11/17/2004
Magnetic Variation: [-16W (2014)]
Sectional: MONTREAL
From City: 2nm W of Rockwood

Operations

Use: Private
Airspace Analysis: CONDITIONAL
Provided Pr Use, VFR Operations, & Satisfactory for Small Land Planes.
Ownership: Privately owned
Activation: 06/2005
Control Tower: no
ARTCC: Boston Center (ZBW)
FSS: Bangor FSS (BGR)
Wind Indicator: Lighted
Landing Fee: no

Communications

Services

Based Aircraft

Single Engine GA: 1
Total: 1

Annual Operations

Total: 0

Ownership

Owner: William Avery
303 Maynards Road
Rockwood, Me 04478
207-534-7516
Manager: William Avery
303 Maynards Road
Rockwood, Me 04478
207-534-7516

Runways

Runways: 11/29

Runway 11/29

Length: 2000 feet
by Owner on 11/17/2004
Width: 100 feet
Surface: Grass / Sod
End 11 End 29
Objects: Trees Trees
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach
Object Height: 50' AGL 50' AGL
Object Distance: 100' Along centerline 100' 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.