ME00
Airport
Fort Fairfield
Fort Fairfield, Maine

FAA NFDC Information Effective 56-day cycle 11/28/2024 - 1/23/2025

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:ME00 (Mike-Echo-Zero-Zero)
Lat/Lng:46.7657055556, -67.8473916667
46-45-56.5400N, 067-50-50.6100W
Estimated by Owner on 12/12/2007
Elevation:471 feet Estimated by Owner on 12/12/2007
Magnetic Variation: [-16W (2024)]
Sectional:HALIFAX
From City:1nm SW of Fort Fairfield

Operations

Use:Private
Airspace Analysis:CONDITIONAL
Provided Pvt Use only; VFR Operations only.
Ownership:Privately owned
Activation:10/2008
Control Tower:no
ARTCC:Boston(ZBW)Boston Center
FSS:Bangor FSS(BGR)
Wind Indicator:Lighted
Landing Fee:no

Communications

Services

Based Aircraft

Total:0

Annual Operations

Total:0

Ownership

Owner:Bruce E. Philbrick
P.O. Box 2072
Bangor, Me 04402
207-664-0241
Manager:Bruce E. Philbrick
P.O. Box 2072
Bangor, Me 04402
207-664-0241

Runways

Runways:08/26

Runway 08/26

Length:1800 feet
by Owner on 12/12/2007
Width:40 feet
Surface:Asphalt / Bituminous Concrete
Surface Treatment:NONE
End 08 End 26
Objects:PoleTrees
Objects affecting Navigable Airspace (CFR part 77):Utility runway with a visual approachUtility runway with a visual approach
Object Height:50' AGL50' AGL
Object Distance:500' Along centerline150' Along centerline

Procedures

NOTAMs

Additional Remarks

Runway is Closed Until Further Notice
for Cd Contact Boston ARTCC at 603-879-6859.

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.