Y O Ranch
Mountain Home, 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:XS22
Lat/Lng: 30.2040877778, -99.6736711111
30-12-14.7160N, 099-40-25.2160W
Elevation: 2136 feet Estimated
Magnetic Variation: 08E, (1985), [5E (2017)]
Sectional: SAN ANTONIO
From City: 16nm W of Mountain Home


Use: Private
Airspace Analysis: NOT ANALYZED
may Pre Date the Act.
Ownership: Privately owned
Activation: 01/1963
Control Tower: no
ARTCC: Houston Center (ZHU)
FSS: San Angelo FSS (SJT)
Wind Indicator: Unlighted
Landing Fee: no



Based Aircraft

Total: 0

Annual Operations

Total: 0


Owner: Charles Schreiner III
Y O Ranch
Mountain Home, Tx 78058
Manager: Louis Schreiner
Ranch Manager.
Y O Ranch
Mountain Home, Tx 78058


Runways: 01/19

Runway 01/19

Length: 2110 feet
Width: 35 feet
Surface: Gravel / Cinders / Crushed Rock / Coral/Shells / Slag
End 01 End 19
Objects: Road  
Object Distance: 0' Along centerline  



Additional Remarks

Runway Condition Good.
(A17) Atndd from Ranch Headquarters.

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.