72TS
Airport
Galaxy Ranch
Sheridan, Texas

FAA NFDC Information Effective 56-day cycle 11/13/2014 - 1/8/2015

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:72TS
Lat/Lng: 29.3608016667, -96.6224730556
29-21-38.8860N, 096-37-20.9030W
Estimated
Elevation: 178 feet Estimated
Magnetic Variation: 07E, (1985), [4E (2014)]
Sectional: HOUSTON
From City: 10nm SE of Sheridan

Operations

Use: Private
Ownership: Privately owned
Activation: 02/1987
Control Tower: no
ARTCC: Houston Center (ZHU)
FSS: Montgomery County FSS (CXO)
Wind Indicator: Unlighted
Landing Fee: no

Communications

Services

Based Aircraft

Total: 0

Annual Operations

Total: 0

Ownership

Owner: Galaxy Energies Inc
Po Box 1873
Corpus Christi, Tx 78403
512-888-6851
Ranch Telephone - 512-798-4742.
Manager: John Graefing
P.O. Box 1873
Corpus Christi, Tx 78403
409-539-9851

Runways

Runways: 17/35

Runway 17/35

Length: 3335 feet
Width: 100 feet
Surface: Gravel / Cinders / Crushed Rock / Coral/Shells / Slag
End 17 End 35
Displaced Threshold Distance:   500'
Objects:   Pole
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach
Object Height:   30' AGL
Object Distance:   60' Along centerline

Procedures

NOTAMs

Additional Remarks

(A89) for Flight Plan Filing Call Cxo FSS 1-800-833-5602.

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.