| 8XS2
Airport
|
Ayers Field
|
|
Bellevue, Texas
|
|
|
|
FAA NFDC Information Effective 56-day cycle 05/02/2013 - 6/27/2013
| FAA Identifier: | 8XS2 |
| Lat/Lng: |
33.5701666667, -98.1144666667
33-34-12.6000N, 098-06-52.0800W
Estimated by OWNER on 02/26/2009
|
| Elevation: |
1010 feet
Estimated
by OWNER
on 02/26/2009
|
| Magnetic Variation: |
[5E (2013)]
|
| Sectional: |
DALLAS-FT WORTH
|
| From City: |
7nm
SW of Bellevue
|
| Use: |
Private
|
| Airspace Analysis: |
CONDITIONAL
Provided VFR Operations and Pvt Use only.
|
| Ownership: |
Privately owned
|
| Activation: |
11/2010
|
| Control Tower: |
no
|
| ARTCC: |
Fort Worth
(ZFW)
Fort Worth Center
(ZFW)
|
| FSS: |
Fort Worth FSS
(FTW)
|
| Wind Indicator: |
Unlighted
|
| Landing Fee: |
no
|
| Single Engine GA: |
2
|
| Total: |
2
|
|
| For year ending: |
12/30/2008
|
| Total: |
0
|
|
| Owner: |
James Ayers
892 Wagon Rd
Bellevue, Tx 76228
940-476-2450
|
| Manager: |
James Ayers
892 Wagon Rd
Bellevue, Tx 76228
940-476-2450
|
|
Runway 18/36
| Length: |
2400 feet
by Owner on 02/26/2009
|
| Width: |
130 feet
|
| Surface: |
Grass / Sod
|
|
End 18 |
End 36 |
| Objects: |
Trees
|
Trees
|
| Objects affecting Navigable Airspace (CFR part 77): |
Utility runway with a visual approach
|
Utility runway with a visual approach
|
| Object Height: |
25' AGL
|
25' AGL
|
| Object Distance: |
225' Along centerline
|
225' Along centerline
|
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.