| XA12
Airport
|
Mcfarlin Ranch
|
|
Bertram, Texas
|
|
|
|
FAA NFDC Information Effective 56-day cycle 05/02/2013 - 6/27/2013
| FAA Identifier: | XA12 (Xray-Alpha-One-Two) |
| Lat/Lng: |
30.6947222222, -98.0327777778
30-41-41.0000N, 098-01-58.0000W
Estimated by OWNER on 05/19/2003
|
| Elevation: |
1200 feet
Estimated
by NGS-CALCULATED
on 05/19/2003
|
| Magnetic Variation: |
[4E (2013)]
|
| Sectional: |
SAN ANTONIO
|
| From City: |
3nm
SE of Bertram
|
| Use: |
Private
|
| Airspace Analysis: |
CONDITIONAL
See Airspace Ltr Dated 4/11/03 Fro Conditions.
|
| Ownership: |
Privately owned
|
| Activation: |
01/2004
|
| Control Tower: |
no
|
| ARTCC: |
Houston Center
(ZHU)
|
| FSS: |
San Angelo FSS
(SJT)
|
| Wind Indicator: |
Unlighted
|
| Landing Fee: |
no
|
|
|
|
| Owner: |
W D Mcfarlin
1434 Crownhill Dr
Arlington, Tx 76012
817-991-5054
|
| Manager: |
W D Mcfarlin
1434 Crownhill Dr
Arlington, Tx 76012
817-991-5054
|
|
Runway 18/36
| Length: |
2000 feet
by Owner on 05/19/2003
|
| Width: |
60 feet
|
| Surface: |
Grass / Sod
|
|
End 18 |
End 36 |
| Right Hand Pattern: |
Yes
|
|
| Objects: |
Trees
|
Trees
|
| Objects affecting Navigable Airspace (CFR part 77): |
Utility runway with a visual approach
|
Utility runway with a visual approach
|
| Object Height: |
30' AGL
|
40' AGL
|
| Object Distance: |
500' Along centerline
|
800' Along centerline
|
| • | Owner Desires Airport not be Charted. |
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.