Seidel Ranch
Elroy, Texas

FAA NFDC Information Effective 56-day cycle 09/14/2017 - 11/9/2017

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks


FAA Identifier:02XS (Zero-Two-Xray-Sierra)
Lat/Lng: 30.1477130556, -97.6627791667
30-08-51.7670N, 097-39-46.0050W
Elevation: 510 feet Estimated
Magnetic Variation: 07E, (1985), [4E (2017)]
Sectional: SAN ANTONIO
From City: 2nm NW of Elroy


Use: Private
Airspace Analysis: CONDITIONAL
VFR Use. Establish An Opnl Letter of Agreement with USAF, Bergstrom AFB, Tx.
Ownership: Privately owned
Activation: 06/1977
Control Tower: no
ARTCC: Houston Center (ZHU)
FSS: San Angelo FSS (SJT)
Wind Indicator: Unlighted
Landing Fee: no



Based Aircraft

Single Engine GA: 2
Multi Engine GA: 1
Total: 3

Annual Operations

Total: 0


Owner: William G Seidel
P.O. Box 207
Del Valle, Tx 78617-0207
Manager: William G Seidel
P.O. Box 207
Del Valle, Tx 78617-0207


Runways: 02/20

Runway 02/20

Length: 1500 feet
Width: 40 feet
Surface: Grass / Sod
Runway Lights Edge Intensity: Runway Lights Edge only.
End 02 End 20
Right Hand Pattern: Yes  
Objects: Fence Powerlines
Object Height: 4' AGL 25' AGL
Object Distance: 0' Along centerline 255' Along centerline

Runway 11/29

Length: 1320 feet
Width: 40 feet
Surface: Grass / Sod
End 11 End 29



Additional Remarks

Runway Soft When Wet; Livestock may be on Runway.
Removable 3' Fence Crosses Runway 11/29 at Two Locations--Approx 175' and 625' Down Runway from Approach End Runway 29.

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.