Kingsland Estates
Kingsland, 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:TS18 (Tango-Sierra-One-Eight)
Lat/Lng: 30.6543513889, -98.4786413889
30-39-15.6650N, 098-28-43.1090W
Elevation: 873 feet Estimated
Magnetic Variation: 07E, (1985), [4E (2017)]
Sectional: SAN ANTONIO
From City: 3nm W of Kingsland


Use: Private
Ownership: Privately owned
Activation: 06/1959
Control Tower: no
ARTCC: Houston Center (ZHU)
FSS: San Angelo FSS (SJT)
Wind Indicator: Unlighted
Lights: Activate LIRL Runway 18/36 - CTAF.
Landing Fee: no


UNICOM: 122.700


Based Aircraft

Single Engine GA: 14
Total: 14

Annual Operations

For year ending: 03/01/1996
Non-local GA: 300
Total: 300


Owner: Wayne Dacy
5211 River Oaks
Kingsland, Tx 78639
Manager: Wayne Dacy
5211 River Oaks
Kingsland, Tx 78639


Runways: 18/36

Runway 18/36

Length: 3233 feet
Width: 150 feet
Surface: Grass / Sod, Gravel, Good Condition
Center 30 Ft is Gravel.
Runway Lights Edge Intensity: Non-standard Lighting System
Non-Standard LIRL; One Threshold Light on Each Side of Runway is Blue; All Others are Clear.
End 18 End 36
Objects: Trees Bldg
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach
Object Clearance Slope: 5:1 6:1
Object Height: 25' AGL 20' AGL
Object Distance: 136' Along centerline
10' Left of centerline
124' Along centerline
60' Left of centerline



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.