Danz Ranch
Johnson City, Texas

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:XA02 (Xray-Alpha-Zero-Two)
Lat/Lng: 30.2802, -98.4264111111
30-16-48.7200N, 098-25-35.0800W
Estimated by OWNER on 05/18/2003
Elevation: 1230 feet Estimated by OWNER on 05/18/2003
Magnetic Variation: [4E (2015)]
Sectional: SAN ANTONIO
From City: 1nm W of Johnson City


Use: Private
Airspace Analysis: CONDITIONAL
Provided Existing or Contemplated Traffic Patterns, Existing Airspace Structure and Projected, File with FAA.
Ownership: Privately owned
Activation: 07/2003
Control Tower: no
ARTCC: Houston Center (ZHU)
FSS: San Angelo FSS (SJT)
Wind Indicator: Unlighted
Landing Fee: no



Based Aircraft

Single Engine GA: 1
Total: 1

Annual Operations

Total: 0


Owner: Jay Roger Danz
Po Box 300
Johnson City, Tx 78636
Manager: David Jay Danz
Po Box 653
Johnson City, Tx 78636


Runways: 02/20

Runway 02/20

Length: 1200 feet
by Owner on 05/18/2003
Width: 60 feet
Surface: Grass / Sod
End 02 End 20
Right Hand Pattern:   Yes
Objects: Fence Trees
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach
Object Height: 4' AGL 25' AGL
Object Distance: 0' Along centerline 200' Along centerline



Additional Remarks

Powerlines Across Mid Field.

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.