72ME
Airport
Philbrick Mountain
Ellsworth, Maine

FAA NFDC Information Effective 56-day cycle 09/18/2014 - 11/13/2014

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:72ME
Lat/Lng: 44.6352777778, -68.6325
44-38-07.0000N, 068-37-57.0000W
Estimated by OWNER on 04/14/2009
Elevation: 667 feet Estimated by OWNER on 04/14/2009
Magnetic Variation: [-17W (2014)]
Sectional: HALIFAX
From City: 10nm NW of Ellsworth

Operations

Use: Private
Airspace Analysis: CONDITIONAL
Provided VFR Operations and Pvt Use only.
Ownership: Privately owned
Activation: 06/2009
Control Tower: no
ARTCC: Boston (ZBW) Boston Center (ZBW)
FSS: Bangor FSS (BGR)
Wind Indicator: Unlighted
Lights: Sunset-Sunrise (local time)
Landing Fee: no

Communications

Services

Based Aircraft

Total: 0

Annual Operations

For year ending: 05/01/2007
Total: 0

Ownership

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

Runways

Runways: 01/19

Runway 01/19

Length: 1200 feet
by Owner on 04/14/2009
Width: 25 feet
Surface: Asphalt / Bituminous Concrete, Good Condition
Runway Lights Edge Intensity: Med Intensity
End 01 End 19
Objects: Tower  
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach
Object Height: 800' AGL  
Object Distance: 10560' Along centerline  

Procedures

NOTAMs

Additional Remarks

Owner Desires This Airport not be Charted.

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.