58AZ
Airport
Chapman Ranch Airstrip
Young, Arizona

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:58AZ
Lat/Lng: 34.0936111111, -110.932777778
34-05-37.0000N, 110-55-58.0000W
Estimated by OWNER on 02/28/2008
Elevation: 5115 feet Estimated by OWNER on 02/28/2008
Magnetic Variation: [10E (2014)]
Sectional: PHOENIX
From City: 2nm E of Young

Operations

Use: Private
Airspace Analysis: CONDITIONAL
See Aeronautical Study 2007-Awp-469-Nra Dated 11/17/07.
Ownership: Privately owned
Activation: 02/2008
Control Tower: no
ARTCC: Albuquerque Center (ZAB)
FSS: Prescott FSS (PRC)
Wind Indicator: Unlighted
Segmented Circle: yes
Landing Fee: no

Communications

Services

Based Aircraft

Total: 0

Annual Operations

Total: 0

Ownership

Owner: Chapman Rabh, Llc
Po Box 135
Young, Az 85554
928-462-3259
Manager: Frank Chapman
Po Box 135
Young, Az 85554
928-462-3259

Runways

Runways: 01/19

Runway 01/19

Length: 3068 feet
by Owner on 02/28/2008
Width: 50 feet
Surface: Gravel
End 01 End 19
Right Hand Pattern: Yes  
Runway Markings: Runway 01/19 Marked with Berm at the Edges.  
Objects:   Ground
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach
Object Height:   821' AGL

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.