17TS
Heliport
Big Bend Regional Med Ctr
Alpine, 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:17TS (One-Seven-Tango-Sierra)
Lat/Lng: 30.3847222222, -103.669444444
30-23-05.0000N, 103-40-10.0000W
Estimated by OWNER on 02/03/2002
Elevation: 4435 feet Estimated by OWNER on 02/03/2002
Magnetic Variation: 09E, (2000), [7E (2014)]
Sectional: EL PASO
From City: 2nm N of Alpine

Operations

Use: Private
Medical.
Airspace Analysis: CONDITIONAL
See Airspace Letter Dated 1/26/2000.
Ownership: Privately owned
Activation: 02/2002
Control Tower: no
ARTCC: Albuquerque Center (ZAB)
FSS: San Angelo FSS (SJT)
Wind Indicator: Lighted
Lights: Activate Perimeter Lights - 122.8.
Beacon: Activate Rotating Beacon - 122.8.
Clear-Green-Yellow (Heliport)
Landing Fee: no

Communications

UNICOM: 122.800

Services

Based Aircraft

Total: 0

Annual Operations

Total: 0

Ownership

Owner: Big Bend Regional Medical Ctr
2600 Hwy 118N
Alpine, Tx 79830
915-837-9668
Manager: Richard Allen
2600 Hwy 118N
Alpine, Tx 79830
915-837-6341

Runways

Runways: H1

Runway H1

Length: 50 feet
by Owner on 02/03/2002
Width: 50 feet
Surface: Porland Cement Concrete
Runway Lights Edge Intensity: Perimeter

Procedures

NOTAMs

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.