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: | 26XS |
---|---|
Lat/Lng: | 30.11409638888889, -98.46141111111112 30-06-50.7470N, 098-27-41.0800W Estimated |
Elevation: | 1420 feet Estimated |
Magnetic Variation: | 07E,(1985), [3E (2025)] |
Sectional: | SAN ANTONIO |
From City: | 2nm W of Blanco |
Use: | Private |
---|---|
Airspace Analysis: | CONDITIONAL VFR Operations only. |
Ownership: | Privately owned |
Control Tower: | no |
ARTCC: | Houston(ZHU)Houston Center |
FSS: | San Angelo FSS(SJT) |
Wind Indicator: | Unlighted |
Beacon: | None |
Landing Fee: | no |
Owner: | Charles E Tatum Jr Rt 1 Box 219 Blanco, Tx 78006 210-833-4888 |
---|---|
Manager: | Charles E Tatum Jr Rt 1 Box 219 Blanco, Tx 78006 210-833-4888 |
Runways: | 01/19 |
---|
Length: | 2000 feet |
---|---|
Width: | 150 feet |
Surface: | Grass / Sod |
Surface Treatment: | NONE |
End 01 | End 19 | |
---|---|---|
Objects: | Powerlines-M | |
Objects affecting Navigable Airspace (CFR part 77): | Utility runway with a visual approach | Utility runway with a visual approach |
Object Height: | 30' AGL | |
Object Distance: | 250' Along centerline |
• | for Cd Contact San Antonio Approach at 210-805-5516. |
---|
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