K15
Airport
Grand Glaize-Osage Beach
Osage Beach, Missouri

FAA NFDC Information Effective 56-day cycle 11/13/2014 - 1/8/2015

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:K15 (Kilo-One-Five)
Lat/Lng: 38.1104444444, -92.6805555556
38-06-37.6000N, 092-40-50.0000W
Estimated by 3RD PARTY SURVEY on 11/09/2011
Elevation: 876 feet Surveyed by 3RD PARTY SURVEY on 11/09/2011
Magnetic Variation: 02E, (2000), [1E (2014)]
Sectional: KANSAS CITY
From City: 1nm SW of Osage Beach

Operations

Use: Open to the public
Ownership: Publicly owned
Activation: 10/1947
Attended: Apr-Sep Sat-Thu 0800-1800 (local) Apr-Sep Fri 0800-2000 (local) Oct-Mar Every day 0800-1800 (local)
Control Tower: no
ARTCC: Kansas City Center (ZKC)
FSS: Columbia FSS (COU)
NOTAMs and Weather: COU NOTAM-D service at airport
Wind Indicator: Lighted
Lights: Activate MIRL Runway 14/32; PAPI Runway 32 - CTAF.
Beacon: Sunset-Sunrise (local time)
Clear-Green (Lighted Land Airport)
Landing Fee: no

Communications

CTAF: 122.800
UNICOM: 122.800
Approach:
Contact 'MIZZU' Approach
124.1, 353.7
Departure:
Contact 'MIZZU' Departure
124.1, 353.7
Master Airport: SGF (SPRINGFIELD-BRANSON NATIONAL)

Services

Fuel: Grade 100LL Gasoline (low lead blue)
Bottled Oxygen: None
Bulk Oxygen: None
Transient Storage: Hanger,Tie-Down

Based Aircraft

Single Engine GA: 10
Multi Engine GA: 1
Helicopter GA: 1
Total: 12

Annual Operations

For year ending: 12/31/2012
AirTaxi: 150
Local GA (< 20 miles): 1480
Non-local GA: 5000
Military Operations: 10
Total: 6640

Ownership

Owner: City of Osage Beach
1000 City Parkway
Osage Beach, Mo 65065
573-302-2000
Manager: Budd Hyde
1000 City Parkway
Osage Beach, Mo 65065
573-348-4469

Runways

Runways: 14/32

Runway 14/32

Length: 3205 feet
by 3Rd Party Survey on 11/09/2011
Width: 60 feet
Surface: Asphalt / Bituminous Concrete, Good Condition
Surface Treatment: Rubberized Friction Seal Coat
Weight Capacity: Single Wheel aircraft: 15,000 lbs
Runway Lights Edge Intensity: Non-standard Lighting System
Incorrect Spacing of Threshold Lights at Runway 32 End.
End 14 End 32
True Alignment: 142, (141 Magnetic) 322, (321 Magnetic)
Runway Markings: Nonprecision Instrument, Good Condition Nonprecision Instrument, Good Condition
Gradient: 0.6 0.6
Elevation at End: 876.3' MSL 857.5' MSL
Elevation at Touchdown Zone: 876.3' MSL 875.4' MSL
Threshold Crossing Glide Path Height:   46' AGL
Visual Glide Path Angle:   3.50°
Visual Glide Slope Indicator:   4-light PAPI on left side of runway
Objects: Trees Trees
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a nonprecision approach Utility runway with a nonprecision approach
Object Clearance Slope: 0:1 4:1
Object Height: 30' AGL 32' AGL
Object Distance: 205' Along centerline
160' Right of centerline
330' Along centerline
250'Left and Right of centerline
Other Objects: Runway 14 1- 47 Ft Trees; 25-200 Ft from Runway End 160-250 Ft R; Aircraft Tiedown Area 0-200 Ft from Runway End, 150-250 L. Runway 32, +6-26 Ft Tree 0-130 Ft from Runway End; 50 Ft L.

Procedures

NOTAMs

Additional Remarks

A30-14/32-Restricted to Aircraft 12,500 Lbs Max Gwt or Less; Prior Permission for Aircraft Exceeding 12,500 Lbs Call Airport Manager on 573-302-2003.
Deer on and in View of Runway & Taxiways Dusk and After Dark.
Ntsd Runway Safety Area Grading Beyond Each Runway End; Large Drop Offs & Rolling Terrain.

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.