Ash Creek
Pearce, Arizona

FAA NFDC Information Effective 56-day cycle 10/15/2015 - 12/10/2015

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks


FAA Identifier:6AZ5
Lat/Lng: 31.8574833333, -109.542316667
31-51-26.9400N, 109-32-32.3400W
Estimated by OWNER on 12/18/2007
Elevation: 4680 feet Estimated by OWNER on 12/18/2007
Magnetic Variation: [9E (2015)]
Sectional: PHOENIX
From City: 20nm SE of Pearce


Use: Private
Airspace Analysis: CONDITIONAL
Provided VFR Operations and Pvt Use only; Maintain Obstruction Free Rtes of Ingress/Egress; Use Caution When Ingress/Egress to Landing Area Due to Close Location to Military Training Area.
Ownership: Privately owned
Activation: 08/2009
Control Tower: no
ARTCC: Albuquerque (ZAB) Albuquerque Center (ZAB)
FSS: Prescott FSS (PRC)
Wind Indicator: Lighted
Landing Fee: no



Based Aircraft

Total: 0

Annual Operations

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


Owner: Wharton Properties, Llc
Po Box 15465
Phoenix, Az 85060
Manager: Wharton Properties, Llc
Po Box 15465
Phoenix, Az 85060


Runways: 08/26

Runway 08/26

Length: 3000 feet
by Owner on 12/18/2007
Width: 30 feet
Surface: Grass / Sod
End 08 End 26
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach



Additional Remarks

500' Down the Strip from the Approach End of 26 is a Barbed Wire Fence. the Fence Runs Across the Entire Width of the Strip. the Strip is Over Grown with Weeds.

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.