Memorial Hermann Katy Hospital
Katy, Texas

FAA NFDC Information Effective 56-day cycle 10/15/2015 - 12/10/2015

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks


FAA Identifier:70TS (Seven-Zero-Tango-Sierra)
Lat/Lng: 29.7888888889, -95.7844444444
29-47-20.0000N, 095-47-04.0000W
Estimated by OWNER on 03/31/2009
Elevation: 131 feet Estimated by OWNER on 03/31/2009
Magnetic Variation: [3E (2015)]
Sectional: HOUSTON
From City: 5nm W of Katy


Use: Private
Airspace Analysis: CONDITIONAL
Provided Pvt Use only; All Appch/Departure Rte Heli Operations Conducted from 330 to 30 Deg Clkws and from 150 to 210 Deg Clkws; a Memorandum of Understanding with Hoffpauir Airport is Needed If Anything Other than the N-S Ingress Rtes are Used.
Ownership: Privately owned
Activation: 07/2009
Attended: Continuous
Control Tower: no
ARTCC: Houston (ZHU) Houston Center (ZHU)
FSS: Montgomery County FSS (CXO)
Wind Indicator: Unlighted
Lights: Sunset-Sunrise (local time)
Landing Fee: no



Based Aircraft

Total: 0

Annual Operations

For year ending: 12/31/2006
Total: 0


Owner: Memorial Hermann Hospital - Katy
23900 Katy Fwy
Katy, Tx 77494
Manager: Eric Herrera
23900 Katy Fwy
Katy, Tx 77494


Runways: H1

Runway H1

Length: 65 feet
by Owner on 03/31/2009
Width: 65 feet
Surface: Porland Cement Concrete
Runway Lights Edge Intensity: Perimeter



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.