FL58
Airport
Johary
Belleview, Florida

FAA NFDC Information Effective 56-day cycle 09/18/2014 - 11/13/2014

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:FL58
Lat/Lng: 29.02637, -81.9878633333
29-01-34.9320N, 081-59-16.3080W
Estimated
Elevation: 72 feet Estimated
Magnetic Variation: 03W, (1985), [-6W (2014)]
Sectional: JACKSONVILLE
From City: 4nm SE of Belleview

Operations

Use: Private
Airspace Analysis: CONDITIONAL
Pvt Use VFR only
Ownership: Privately owned
Activation: 10/1965
Control Tower: no
ARTCC: Jacksonville Center (ZJX)
FSS: Gainesville FSS (GNV)
Wind Indicator: Unlighted
Beacon: Strob Red.
Landing Fee: no

Communications

Services

Airframe Repair: None
Powerplant Repair: None

Based Aircraft

Single Engine GA: 3
Multi Engine GA: 4
Total: 7

Annual Operations

Total: 0

Ownership

Owner: Johary Aviation, Inc
P O Box 916552
Longwood, Fl 32779
321-948-3368
Manager: Johary Aviation, Inc.
P. O. Box 916552
Longwood, Fl 32779
321-948-3368

Runways

Runways: 18/36

Runway 18/36

Length: 3543 feet
Width: 40 feet
Clear Width 200', Usable Width Varies 40-50'.
Surface: Grass / Sod
End 18 End 36
Runway Markings: Has Light Reflectors Every 50'.  
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach

Procedures

NOTAMs

Additional Remarks


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.