89TA
Gliderport
Soaring Club Of Houston
Waller, Texas

FAA NFDC Information Effective 56-day cycle 02/22/2024 - 4/18/2024

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:89TA
Lat/Lng:30.1927138889, -95.9632888889
30-11-33.7700N, 095-57-47.8400W
Estimated
Elevation:308 feet Estimated
Magnetic Variation:05E,(1995), [2E (2024)]
Sectional:HOUSTON
From City:12nm SW of Waller

Operations

Use:Private
Airspace Analysis:CONDITIONAL
Provided All Traffic Pattern Operations are Rstrd to West Side of Runway.
Ownership:Privately owned
Activation:11/1996
Attended:All year Sat-Sun 1000-1700 (local)
Control Tower:no
ARTCC:Houston(ZHU)Houston Center
FSS:Montgomery County FSS(CXO)
Wind Indicator:Unlighted
Landing Fee:no

Communications

UNICOM:Frequency 123.3 Used at Airport.

Services

Based Aircraft

Single Engine GA:4
Gliders:33
Total:37

Annual Operations

Total:0

Ownership

Owner:Soaring Club of Houston
4403 Verone
Bellaire, Tx 77401
713-218-6767
Manager:Ken Sorenson
30368 Waller Gladish Rd
Waller, Tx 77484
979-826-8776

Runways

Runways:17/35

Runway 17/35

Length:3200 feet
Width:500 feet
Surface:Grass / Sod
Surface Treatment:NONE
End 17 End 35
Objects: Trees
Objects affecting Navigable Airspace (CFR part 77):Utility runway with a visual approachUtility runway with a visual approach
Object Height: 50' AGL
Object Distance: 0' Along centerline

Procedures

NOTAMs

Additional Remarks

for Cd Contact Houston ARTCC at 281-230-5622.

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.