73TA
Airport
Reynolds Ranch
Bayview, Texas

FAA NFDC Information Effective 56-day cycle 04/18/2024 - 6/13/2024

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:73TA
Lat/Lng:26.158425, -97.3886888889
26-09-30.3300N, 097-23-19.2800W
Estimated by Owner on 12/09/2016
Elevation:24 feet Estimated by Owner on 12/09/2016
Magnetic Variation: [3E (2024)]
Sectional:BROWNSVILLE
From City:2nm NNE of Bayview

Operations

Use:Private
Airspace Analysis:CONDITIONAL
Ownership:Privately owned
Activation:01/2017
Control Tower:no
ARTCC:Houston(ZHU)Houston Center
FSS:San Angelo FSS(SJT)
Wind Indicator:Lighted
Landing Fee:no

Communications

Services

Based Aircraft

Single Engine GA:1
Total:1

Annual Operations

Total:0

Ownership

Owner:Stephen Reynolds
27677 Loop Road
Bayview, Tx 78566
956-330-3082
ECHOHOTEL@AOL.COM
Manager:Stephen Reynolds
27677 Loop Road
Bayview, Tx 78566
956-330-3082

Runways

Runways:02/20

Runway 02/20

Length:2000 feet
by Faa Oe/Aaa on 05/16/2018
Width:50 feet
Surface:Grass / Sod
Surface Treatment:NONE
End 02 End 20
True Alignment:022,(019 Magnetic)202,(199 Magnetic)
Elevation at End:23.0' MSL24.0' MSL
Objects affecting Navigable Airspace (CFR part 77):Utility runway with a visual approachUtility runway with a visual approach

Procedures

NOTAMs

Additional Remarks

for Cd Contact Houston ARTCC at 281-230-5622.

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.