| TA45
Heliport
|
Eckels
|
|
Houston, Texas
|
|
|
|
FAA NFDC Information Effective 56-day cycle 05/02/2013 - 6/27/2013
| FAA Identifier: | TA45 |
|---|
| Lat/Lng: |
29.8316158333, -95.6552236111
29-49-53.8170N, 095-39-18.8050W
Estimated
|
|---|
| Elevation: |
110 feet
Estimated
|
|---|
| Magnetic Variation: |
06E,
(1985),
[3E (2013)]
|
|---|
| Sectional: |
HOUSTON
|
|---|
| From City: |
in Houston
|
|---|
| Use: |
Private
|
|---|
| Airspace Analysis: |
CONDITIONAL
E111 Provided Heli Rmns Pvt Use. Caution Heli Near Lakeside Airport & Lies Bnth Lakeside Airport Traffic Pattern; Contact Lakeside Unicom (122.8) for Traffic ADZY.
|
|---|
| Ownership: |
Privately owned
|
|---|
| Activation: |
11/1979
|
|---|
| Attended: |
All year Mon-Fri 0800-1700 (local)
|
|---|
| Control Tower: |
no
|
|---|
| ARTCC: |
Houston Center
(ZHU)
|
|---|
| FSS: |
Montgomery County FSS
(CXO)
|
|---|
| Wind Indicator: |
Unlighted
|
|---|
| Segmented Circle: |
yes
|
|---|
| Landing Fee: |
no
|
|---|
| Helicopter GA: |
1
|
|---|
| Total: |
1
|
|---|
|
|
| Owner: |
R. Y. Eckels
4035 Trey Drive
Houston, Tx 77084
409-885-4564
|
|---|
| Manager: |
Bob Eckels
712 Bartlett
Sealy, Tx 77474
409-885-4564
|
|---|
|
Runway H1
| Length: |
100 feet
|
|---|
| Width: |
100 feet
|
|---|
| Surface: |
Asphalt / Bituminous Concrete
|
|---|
| • | (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.
