34TS
Airport
Canyon Lake
Canyon Lake, 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:34TS
Lat/Lng: 29.9157722222, -98.2475138889
29-54-56.7800N, 098-14-51.0500W
Estimated by NACO on 07/07/2003
Elevation: 940 feet Surveyed by NACO on 07/07/2003
Magnetic Variation: 08E, (1980), [4E (2014)]
Sectional: SAN ANTONIO
From City: 2nm NE of Canyon Lake

Operations

Use: Private
Ownership: Privately owned
Activation: 11/1986
Control Tower: no
ARTCC: Houston Center (ZHU)
FSS: San Angelo FSS (SJT)
Wind Indicator: Unlighted
Landing Fee: yes

Communications

Services

Based Aircraft

Single Engine GA: 7
Total: 7

Annual Operations

Total: 0

Ownership

Owner: Canyon Lake Ap Council of Co-Owners
18382 from 306 Suite 103
Fischer, Tx 78133
830-935-2556
Manager: Blake Kilpatrick
18382 from 306 Suite 103
Canyon Lake, Tx 78133
830-935-2556

Runways

Runways: 01/19

Runway 01/19

Length: 2600 feet
Width: 45 feet
Surface: Asphalt / Bituminous Concrete
End 01 End 19
Right Hand Pattern: Yes  
Objects: Hill  
Object Marking: Lighted  
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach
Object Height: 150' AGL  
Object Distance: 3300' Along centerline  

Procedures

NOTAMs

Additional Remarks

Deer on Runway.

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.