| TA33
Airport
|
Meyer Field
|
|
Rosharon, Texas
|
|
|
|
FAA NFDC Information Effective 56-day cycle 05/02/2013 - 6/27/2013
| FAA Identifier: | TA33 |
|---|
| Lat/Lng: |
29.3580197222, -95.6352238889
29-21-28.8710N, 095-38-06.8060W
Estimated
|
|---|
| Elevation: |
65 feet
Estimated
|
|---|
| Magnetic Variation: |
06E,
(1985),
[3E (2013)]
|
|---|
| Sectional: |
SAN ANTONIO
|
|---|
| From City: |
9nm
W of Rosharon
|
|---|
| Use: |
Private
|
|---|
| Airspace Analysis: |
CONDITIONAL
E111: Provided Approach Slopes to Landing Area are Mntnd Iaw Part 77 of FAA Regs.
|
|---|
| Ownership: |
Privately owned
|
|---|
| Activation: |
07/1979
|
|---|
| Control Tower: |
no
|
|---|
| ARTCC: |
Houston Center
(ZHU)
|
|---|
| FSS: |
Montgomery County FSS
(CXO)
|
|---|
| Wind Indicator: |
None
|
|---|
| Landing Fee: |
no
|
|---|
| Single Engine GA: |
1
|
|---|
| Multi Engine GA: |
1
|
|---|
| Total: |
2
|
|---|
|
|
| Owner: |
Lester Meyer
22930 from 762
Needville, Tx 77461
409-553-3002
|
|---|
| Manager: |
Lester Meyer
22930 from 762
Needville, Tx 77461
409-553-3002
|
|---|
|
Runway 18/36
| Length: |
4200 feet
|
|---|
| Width: |
80 feet
|
|---|
| Surface: |
Grass / Sod
|
|---|
|
End 18 |
End 36 |
|---|
| Objects: |
|
Powerlines
|
|---|
| Object Height: |
|
40' AGL
|
|---|
| Object Distance: |
|
10' Along centerline
|
|---|
| • | (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.
