XA64
Airport
Nash Ranch
Batesville, Texas

FAA NFDC Information Effective 56-day cycle 05/02/2013 - 6/27/2013

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:XA64
Lat/Lng: 28.9616666667, -99.3852777778
28-57-42.0000N, 099-23-07.0000W
Estimated by OWNER on 05/31/2005
Elevation: 780 feet Estimated by OWNER on 05/31/2005
Magnetic Variation: [5E (2013)]
Sectional: SAN ANTONIO
From City: 12nm E of Batesville

Operations

Use: Private
Airspace Analysis: CONDITIONAL
Provided a Clear 20:1 Visual Approach Slope.
Ownership: Privately owned
Activation: 10/2005
Control Tower: no
ARTCC: Houston Center (ZHU)
FSS: San Angelo FSS (SJT)
Wind Indicator: Unlighted
Landing Fee: no

Communications

Services

Based Aircraft

Total: 0

Annual Operations

Total: 0

Ownership

Owner: Charles Nash
Po Box 1988
Austin, Tx 78767-1988
512-444-8888
Manager: Charles Nash
Po Box 1988
Austin, Tx 78767-1988
512-444-8888

Runways

Runways: 13/31

Runway 13/31

Length: 3800 feet
by Owner on 05/31/2005
Width: 60 feet
Surface: Asphalt / Bituminous Concrete, Trtd, Good Condition
End 13 End 31
Objects: Fence Fence
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach
Object Height: 6' AGL 6' AGL
Object Distance: 200' Along centerline 200' 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.