TS22
Airport
Joye Ranch
Smiley, Texas

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:TS22
Lat/Lng: 29.2416666667, -97.6297222222
29-14-30.0000N, 097-37-47.0000W
Estimated
Elevation: 280 feet Surveyed
Magnetic Variation: 07E, (1985), [4E (2014)]
Sectional: SAN ANTONIO
From City: 2nm S of Smiley

Operations

Use: Private
Ownership: Privately owned
Activation: 03/1990
Attended: All year Every day DAWN-DUSK (local)
Control Tower: no
ARTCC: Houston Center (ZHU)
FSS: San Angelo FSS (SJT)
Wind Indicator: Unlighted
Landing Fee: no

Communications

Services

Based Aircraft

Single Engine GA: 1
Total: 1

Annual Operations

For year ending: 05/11/1993
Local GA (< 20 miles): 200
Non-local GA: 100
Total: 300

Ownership

Owner: E.a. Davis
Box 326
Smiley, Tx 78159
512-587-6381
Manager: E.a. Davis
Box 326
Smiley, Tx 78159
512-587-6381

Runways

Runways: 13/31

Runway 13/31

Length: 3935 feet
Width: 80 feet
Surface: Grass / Sod, 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 Clearance Slope: 0:1 0:1
Object Height: 4' AGL 4' AGL
Object Distance: 0' Along centerline
40' Right of centerline
0' Along centerline
0B'

Procedures

NOTAMs

Additional Remarks

+4' Fences 40' Each Side of Runway Centerline Obstruct Primary Surface.

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.