16KS
Airport
Harmony Valley
Independence, Kansas

FAA NFDC Information Effective 56-day cycle 07/24/2014 - 9/18/2014

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:16KS (One-Six-Kilo-Sierra)
Lat/Lng: 37.2234916667, -95.5983305556
37-13-24.5700N, 095-35-53.9900W
Estimated by OWNER on 10/07/2010
Elevation: 780 feet Estimated by OWNER on 10/07/2010
Magnetic Variation: [3E (2014)]
Sectional: KANSAS CITY
From City: 6nm E of Independence

Operations

Use: Private
Airspace Analysis: CONDITIONAL
Provided Maintain Clear Approach to Each Runway for a Min 20:1 Slp; Maintain a Clear Trsnl Surface for a 7:1 Slp.
Ownership: Privately owned
Activation: 04/2012
Control Tower: no
ARTCC: Kansas City Center (ZKC)
FSS: Wichita FSS (ICT)
Wind Indicator: Unlighted
Landing Fee: no

Communications

Services

Based Aircraft

Single Engine GA: 3
Gliders: 1
Total: 4

Annual Operations

Total: 0

Ownership

Owner: Lee Mattix
5118 Hwy 160
Independence, Ks 67301
620-330-0134
Manager: Lee Mattix
5118 Hwy 160
Independence, Ks 67301
620-330-0134

Runways

Runways: 09/27

Runway 09/27

Length: 2200 feet
by Owner on 10/07/2010
Width: 60 feet
Surface: Grass / Sod
End 09 End 27
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.