KLUM
Airport
Menomonie Muni/Score Field
Menomonie, Wisconsin

FAA NFDC Information Effective 56-day cycle 11/27/2025 - 1/22/2026

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA/ICAO Identifier:LUM / KLUM
Lat/Lng:44.8923441667, -91.8677905556
44-53-32.4390N, 091-52-04.0460W
Estimated by 3rd Party Survey on 11/28/2023
Elevation:895 feet Surveyed by 3rd Party Survey on 11/28/2023
Magnetic Variation:01E,(2000), [-1W (2025)]
Sectional:GREEN BAY
From City:3nm E of Menomonie

Operations

Use:Open to the public
Ownership:Publicly owned
Activation:06/1986
Attended:All year Mon-Fri 0800-1700 (local)
Control Tower:no
ARTCC:Minneapolis(ZMP)Minneapolis Center
FSS:Green Bay FSS(GRB)
NOTAMs and Weather:LUMNOTAM-D service at airport
Wind Indicator:Lighted
Lights:MIRL Runway 9/27 Preset to Low Ss-Sr; to Increase Intensity and Activate REIL Runways 09 & 27; PAPI Runways 09, 18, 27, & 36; MIRL Runway 09/27 & 18/36 - CTAF.
Beacon:Sunset-Sunrise
Landing Fee:no

Communications

CTAF:123.075
UNICOM:123.075
Weather:AWOS-3PT 118.025

Services

Fuel:Grade 100LL Gasoline (low lead blue)
A+
L 24 Hour Self Service Fuel Available with Credit Card; Contact Airport Manager for Asstnc.
Airframe Repair:Major
Powerplant Repair:Major
Bottled Oxygen:None
Transient Storage:Hanger,Tie-Down
Other Services:Avionics, Pilot Instruction, Aircraft Rental

Based Aircraft

Total:0

Annual Operations

Total:0

Ownership

Owner:City of Menomonie
800 Wilson Ave
Menomonie, Within 54751-2795
715-232-2187
Manager:Darrel Gibson
1400 Indianhead Dr.
Menomonie, Within 54751
715-220-6549

Runways

Runways:09/27
18/36

Runway 09/27

Length:5074 feet
by Ngs on 07/18/2006
Width:75 feet
Surface:Asphalt / Bituminous Concrete, Fair Condition
Surface Treatment:NONE
Runway Lights Edge Intensity:Med Intensity
End 09 End 27
True Alignment:089,(088 Magnetic)269,(268 Magnetic)
Runway Markings:Nonprecision Instrument,Fair ConditionNonprecision Instrument,Fair Condition
Elevation at End:892.3' MSL892.6' MSL
Elevation at Touchdown Zone:893.6' MSL893.6' MSL
Threshold Crossing Glide Path Height:36' AGL40' AGL
Visual Glide Path Angle:3.00°3.00°
Visual Glide Slope Indicator:2-light PAPI on left side of runway2-light PAPI on left side of runway
Runway End Identifer Lights (REIL):YesYes
Objects:Farm Equip.Other
Objects affecting Navigable Airspace (CFR part 77):DD
Object Clearance Slope:34:1
Ctlng Obstruction Exceeds a 45 Deg Slp.
0:1
Object Height: 15' AGL
Object Distance: 200' Along centerline
300' Left of centerline
Other Objects: 20 ft Bldg 100 ft from Runway End, 325 ft L.

Runway 18/36

Length:3470 feet
by Ngs on 07/18/2006
Width:75 feet
Surface:Asphalt / Bituminous Concrete, Fair Condition
Surface Treatment:NONE
Runway Lights Edge Intensity:Med Intensity
End 18 End 36
True Alignment:177,(176 Magnetic)357,(356 Magnetic)
Runway Markings:Nonprecision Instrument,Fair ConditionNonprecision Instrument,Fair Condition
Elevation at End:895.0' MSL892.9' MSL
Elevation at Touchdown Zone:895.0' MSL893.5' MSL
Threshold Crossing Glide Path Height:36' AGL39' AGL
Visual Glide Path Angle:3.00°3.00°
Visual Glide Slope Indicator:2-light PAPI on left side of runway2-light PAPI on right side of runway
Objects affecting Navigable Airspace (CFR part 77):Utility runway with a visual approachUtility runway with a visual approach
Object Clearance Slope:20:120:1

Procedures

NOTAMs

Additional Remarks

Seasonal Birds on & in Vicinity of Airport.
for Cd Contact Minneapolis ARTCC at 651-463-5588.
Noise Sensitive Nbrhd W of Runway 27.

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.