39XS
Heliport
Kimble Hospital
Junction, 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:39XS
Lat/Lng: 30.4983333333, -99.7811111111
30-29-54.0000N, 099-46-52.0000W
Estimated by OWNER on 10/07/2011
Elevation: 1749 feet Estimated by OWNER on 10/07/2011
Magnetic Variation: [5E (2014)]
Sectional: SAN ANTONIO
From City: 1nm E of Junction

Operations

Use: Private
Airspace Analysis: CONDITIONAL
Provided VFR Operations and Pvt Use only; Takeoff/Landing Area Marked; Loa Entered Into with Kimble County Airport (Jct).
Ownership: Privately owned
Activation: 03/2013
Control Tower: no
ARTCC: Houston Center (ZHU)
FSS: San Angelo FSS (SJT)
Wind Indicator: Unlighted
Lights: Sunset-Sunrise (local time)
Landing Fee: no

Communications

Services

Based Aircraft

Total: 0

Annual Operations

Total: 0

Ownership

Owner: Kimble County Hospital District
349 Reid Road
Junction City, Tx 76849
325-446-3321
Manager: James Murr
Other: Cecil Conner 349 Reid Road Junction City Tx 76849 325-446-3321 Cconner@Kimblehospital.Org
349 Reid Road
Junction City, Tx 76849
325-446-3321

Runways

Runways: H1

Runway H1

Length: 44 feet
by Owner on 10/07/2011
Width: 44 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.