TT06
Heliport
|
Frio Canon
|
Leakey, Texas
|
|
|
|
FAA NFDC Information Effective 56-day cycle 04/18/2024 - 6/13/2024
FAA Identifier: | TT06 (Tango-Tango-Zero-Six) |
---|
Lat/Lng: | 29.7903333333, -99.7018527778 29-47-25.2000N, 099-42-06.6700W Estimated by Owner on 01/16/2018 |
---|
Elevation: | 1706 feet Estimated by Owner on 01/16/2018 |
---|
Magnetic Variation: | [4E (2024)] |
---|
Sectional: | SAN ANTONIO |
---|
From City: | 5nm NE of Leakey |
---|
Use: | Private |
---|
Airspace Analysis: | CONDITIONAL Wind Sock to be Placed in a Position to Give Reliable Indication, Wind Sock to be Lighted, Helipad Will be Painted with Company Logo to be Read in Predominate Landing Direction, Correct Lat Long Coordinates to be Recorded on the 5010, Weight Limit to be Evaluated and Published, Pad Identifier to be Requested, and Pad Lighting Will be Composed of Portable Bag Lighting to be Placed in Proper Location for Night Landings. |
---|
Ownership: | Privately owned |
---|
Activation: | 06/2018 |
---|
Control Tower: | no |
---|
ARTCC: | Houston(ZHU)Houston Center |
---|
FSS: | San Angelo FSS(SJT) |
---|
Wind Indicator: | None |
---|
Landing Fee: | no |
---|
|
|
Owner: | David Dalgleish 298 Frio Canon Trail Leakey, Tx 78873 512-490-6211 |
---|
Manager: | David Dalgleish 4019 Spicewood Springs Leakey, Tx 78873 512-490-6211 Shawn@Dalgleish.Net |
---|
|
Runway H1
Length: | 25 feet by Owner on 01/16/2018 |
---|
Width: | 25 feet |
---|
Surface: | Asphalt / Bituminous Concrete |
---|
Surface Treatment: | NONE |
---|
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.