| 7AR0
Airport
|
Hammer Field
|
|
Eureka Springs, Arkansas
|
|
|
|
FAA NFDC Information Effective 56-day cycle 05/02/2013 - 6/27/2013
| FAA Identifier: | 7AR0 (Seven-Alpha-Romeo-Zero) |
| Lat/Lng: |
36.4314444444, -93.6993055556
36-25-53.2000N, 093-41-57.5000W
Estimated by OWNER on 01/14/2002
|
| Elevation: |
1600 feet
Estimated
by OWNER
on 01/14/2002
|
| Magnetic Variation: |
[2E (2013)]
|
| Sectional: |
KANSAS CITY
|
| From City: |
3nm
NE of Eureka Springs
|
| Use: |
Private
|
| Ownership: |
Privately owned
|
| Activation: |
07/2003
|
| Control Tower: |
no
|
| ARTCC: |
Memphis Center
(ZME)
|
| FSS: |
Jonesboro FSS
(JBR)
|
| Wind Indicator: |
Unlighted
|
| Landing Fee: |
no
|
|
|
|
| Owner: |
Thomas M. Hammer
1911 Cr 207
Eureka Springs, Ar 72632
479-253-7273
|
| Manager: |
Tom Hammer
1911 Cr 207
Eureka Springs, Ar 72632
479-253-7273
|
|
Runway 07/25
| Length: |
2100 feet
by Owner on 01/14/2002
|
| Width: |
75 feet
|
| Surface: |
Grass / Sod
|
|
End 07 |
End 25 |
| Objects affecting Navigable Airspace (CFR part 77): |
Utility runway with a visual approach
|
Utility runway with a visual approach
|
Runway 16/34
| Length: |
2100 feet
by Owner on 01/14/2002
|
| Width: |
75 feet
|
| Surface: |
Grass / Sod
|
|
End 16 |
End 34 |
| Objects affecting Navigable Airspace (CFR part 77): |
Utility runway with a visual approach
|
Utility runway with a visual approach
|
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.