Lithia, Florida

FAA NFDC Information Effective 56-day cycle 06/22/2017 - 8/17/2017

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks


FAA Identifier:0FL6 (Zero-Foxtrot-Lima-Six)
Lat/Lng: 27.8058606944, -82.1400881667
27-48-21.0985N, 082-08-24.3174W
Estimated by OWNER on 06/14/2004
Elevation: 94 feet Estimated by OWNER on 06/14/2004
Magnetic Variation: [-6W (2017)]
Sectional: MIAMI
From City: 3nm NW of Lithia


Use: Private
Airspace Analysis: CONDITIONAL
Provided VFR Operations and Pvt Use.
Ownership: Privately owned
Activation: 07/2004
Control Tower: no
ARTCC: Miami Center (ZMA)
FSS: Saint Petersburg FSS (PIE)
Wind Indicator: Lighted
Landing Fee: no



Based Aircraft

Single Engine GA: 1
Total: 1

Annual Operations

For year ending: 06/14/2004
Total: 0


Owner: Sebastian Dewhurst
2411 Valrico Forest Drive
Valrico, Fl 33594
Manager: Sebastian Dewhurst
2411 Valrico Forest Drive
Valrico, Fl 33594


Runways: 18/36

Runway 18/36

Length: 500 feet
Width: 60 feet
Surface: Grass / Sod
End 18 End 36
Right Hand Pattern:   Yes
Objects:   Trees
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach
Object Height:   70' AGL
Object Distance:   100' Along centerline



Additional Remarks

70 Ft Trees West Side of Runway 100 Ft from Runway End.
Owner Desires Apt 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.