Krashinsky Airfield
Pelham, Tennessee

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:7TN1 (Seven-Tango-November-One)
Lat/Lng: 35.3206344444, -85.8535888889
35-19-14.2840N, 085-51-12.9200W
Elevation: 995 feet Estimated
Magnetic Variation: 01W, (1990), [-4W (2017)]
Sectional: ATLANTA
From City: 2nm NE of Pelham


Use: Private
Airspace Analysis: CONDITIONAL
Provided 20:1 Approach Slope for Each Runway; Powerline to W is Buried or Obst Marked & Runway 10 Threshold Displaced & Marked to Provide 20:1 Approach Slope; & Trees to E are Removed or Threshold be Displaced & Marked to Provide a 20:1 Approach Slope.
Ownership: Privately owned
Activation: 04/1993
Control Tower: no
ARTCC: Memphis Center (ZME)
FSS: Nashville FSS (BNA)
Wind Indicator: Lighted
Landing Fee: no



Based Aircraft

Total: 0

Annual Operations

Total: 0


Owner: Advanced Security Concepts Inc
16027 Ventura Blvd #208
Encino, Ca 91436
Manager: Oded Krashinsky
16027 Ventura Blvd #208
Encino, Ca 91436


Runways: 10/28

Runway 10/28

Length: 3400 feet
Width: 250 feet
Surface: Grass / Sod, Fair Condition
End 10 End 28
Objects: Powerline Trees
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach
Object Height: 40' AGL 50' AGL



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.