5TA5
Airport
Creasy
Santa Fe, Texas

FAA NFDC Information Effective 56-day cycle 09/18/2014 - 11/13/2014

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:5TA5
Lat/Lng: 29.3360694444, -95.1152066667
29-20-09.8500N, 095-06-54.7440W
Estimated
Elevation: 23 feet Estimated
Magnetic Variation: 06E, (1985), [3E (2014)]
Sectional: HOUSTON
From City: 3nm SW of Santa Fe

Operations

Use: Private
Airspace Analysis: CONDITIONAL
Provided Approach Slopes to Landing Area are Maintained Iaw Part 77 of Far.
Ownership: Privately owned
Activation: 07/1981
Attended: All year Mon-Fri 1800-0700 (local) All year Sat-Sun 24 hrs
Control Tower: no
ARTCC: Houston Center (ZHU)
FSS: Montgomery County FSS (CXO)
Wind Indicator: Unlighted
Landing Fee: no

Communications

Services

Based Aircraft

Single Engine GA: 2
Total: 2

Annual Operations

Total: 0

Ownership

Owner: William K. Creasy
13222 Vacek Rd
Santa Fe, Tx 77510
409-925-6498
Manager: William K. Creasy
13222 Vacek Rd
Santa Fe, Tx 77510
409-925-6498

Runways

Runways: 12/30

Runway 12/30

Length: 2600 feet
Width: 150 feet
Surface: Grass / Sod
End 12 End 30
Right Hand Pattern: Yes  
Objects:   Powerline
Object Marking:   Marked
Object Height:   30' AGL
Object Distance:   0' 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.