| AL37
Airport
|
Benedick
|
|
Jack, Alabama
|
|
|
|
FAA NFDC Information Effective 56-day cycle 05/02/2013 - 6/27/2013
| FAA Identifier: | AL37 |
|---|
| Lat/Lng: |
31.5550277778, -85.9772777778
31-33-18.1000N, 085-58-38.2000W
Estimated
|
|---|
| Elevation: |
335 feet
Estimated
|
|---|
| Magnetic Variation: |
[-3W (2013)]
|
|---|
| Sectional: |
NEW ORLEANS
|
|---|
| From City: |
2nm
SE of Jack
|
|---|
| Use: |
Private
|
|---|
| Airspace Analysis: |
CONDITIONAL
Provided Pvt Use only and VFR Operations only.
|
|---|
| Ownership: |
Privately owned
|
|---|
| Activation: |
06/2008
|
|---|
| Control Tower: |
no
|
|---|
| ARTCC: |
Memphis Center
(ZME)
|
|---|
| FSS: |
Anniston FSS
(ANB)
|
|---|
| Wind Indicator: |
Unlighted
|
|---|
| Landing Fee: |
no
|
|---|
| Single Engine GA: |
1
|
|---|
| Total: |
1
|
|---|
|
|
| Owner: |
Richard J Benedick
374 County Road 205
Jack, Al 36346
334-897-0279
|
|---|
| Manager: |
Richard J Benedick
374 County Road 205
Jack, Al 36346
334-897-0279
|
|---|
|
Runway 08/26
| Length: |
1800 feet
|
|---|
| Width: |
50 feet
|
|---|
| Surface: |
Grass / Sod, Fair Condition
|
|---|
|
End 08 |
End 26 |
|---|
| Objects: |
Trees
|
|
|---|
| Objects affecting Navigable Airspace (CFR part 77): |
Utility runway with a visual approach
|
Utility runway with a visual approach
|
|---|
| Object Height: |
40' AGL
|
|
|---|
| Object Distance: |
200' 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.
