IFR Enroute Charts
at skyvector.com Click on airport for details, drag to scroll around. Zoom using +/- keys. |
|
FAA NFDC Information 28-day cycle
Ops | Comms | Services | Owner | Runways | IFR Procs | Current NOTAMs | Remarks |
FAA Identifier: | 1TE1 (One-Tango-Echo-One) |
---|---|
Lat/Lng: | 28.2502725, -99.81699666666667 28-15-00.9810N, 099-49-01.1880W Estimated |
Elevation: | 650 feet Estimated |
Magnetic Variation: | 08E,(1985), [4E (2025)] |
Sectional: | SAN ANTONIO |
From City: | 12nm SW of Catarina |
Use: | Private |
---|---|
Airspace Analysis: | NOT ANALYZED Aprt Estab Prior to 1959. |
Ownership: | Privately owned |
Activation: | 05/1951 |
Control Tower: | no |
ARTCC: | Houston(ZHU)Houston Center |
FSS: | San Angelo FSS(SJT) |
Wind Indicator: | None |
Beacon: | None |
Landing Fee: | no |
Airframe Repair: | None |
---|---|
Powerplant Repair: | None |
Owner: | Briscoe Ranch P O Box 389 Uvalde, Tx 78802 830-278-9171 |
---|---|
Manager: | Chip Briscoe P O Box 389 Uvalde, Tx 78802 830-278-9171 |
Runways: | 13/31 |
---|
Length: | 4000 feet |
---|---|
Width: | 50 feet |
Surface: | Asphalt / Bituminous Concrete |
Surface Treatment: | NONE |
End 13 | End 31 | |
---|---|---|
Objects affecting Navigable Airspace (CFR part 77): | Utility runway with a visual approach | Utility runway with a visual approach |
• | 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 Chart Supplment (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.
rgrep