U52
Airport
|
Beaver Muni
|
Beaver, Utah
|
|
|
|
FAA NFDC Information Effective 56-day cycle 03/20/2025 - 5/15/2025
FAA Identifier: | U52 |
---|
Lat/Lng: | 38.2305833333, -112.675416667 38-13-50.1000N, 112-40-31.5000W Estimated by 3rd Party Survey on 11/04/2006 |
---|
Elevation: | 5863 feet Surveyed by 3rd Party Survey on 11/04/2006 |
---|
Magnetic Variation: | 14E,(1985), [11E (2025)] |
---|
Sectional: | LAS VEGAS |
---|
From City: | 4nm SW of Beaver |
---|
Use: | Open to the public |
---|
Ownership: | Publicly owned |
---|
Activation: | 05/1944 |
---|
Control Tower: | no |
---|
ARTCC: | Salt Lake City(ZLC)Salt Lake City Center |
---|
FSS: | Cedar City FSS(CDC) |
---|
NOTAMs and Weather: | CDCNOTAM-D service at airport |
---|
Wind Indicator: | Unlighted |
---|
Segmented Circle: | yes |
---|
Lights: | Activate REIL Runway 13 & 31; PAPI Runway 13 & 31; MIRL Runway 13/31 - CTAF. |
---|
Beacon: | Sunset-Sunrise |
---|
Landing Fee: | no |
---|
CTAF: | 122.900 |
---|
Weather: | AWOS-3PT 435-438-5829 119.925 |
---|
Fuel: | Grade 100LL Gasoline (low lead blue) L 24 Hour Self Service. |
---|
Airframe Repair: | None |
---|
Powerplant Repair: | None |
---|
Bottled Oxygen: | None |
---|
Bulk Oxygen: | None |
---|
Transient Storage: | Tie-Down |
---|
|
|
Owner: | Beaver City Po Box 271 Beaver, Ut 84713 435-438-2451 |
---|
Manager: | Jason Brown 30 West 300 North, Po Box 271 Beaver, Ut 84713 (435) 421-1008 |
---|
|
Runway 07/25
Length: | 2150 feet by 3rd Party Survey on 11/04/2006 |
---|
Width: | 50 feet |
---|
Surface: | Natural Soil, Fair Condition |
---|
Surface Treatment: | NONE |
---|
|
End 07 |
End 25 |
---|
True Alignment: | 087,(076 Magnetic) | 267,(256 Magnetic) |
---|
Runway Markings: | None,Poor Condition | None,Poor Condition |
---|
Elevation at End: | 5842.3' MSL | 5844.5' MSL |
---|
Elevation at Touchdown Zone: | 5844.5' MSL | 5844.5' MSL |
---|
Object Marking: | 2 ft Deliminators Acrs Runway 180 ft from Aer 25. | |
---|
Objects affecting Navigable Airspace (CFR part 77): | Utility runway with a visual approach | Utility runway with a visual approach |
---|
Object Clearance Slope: | 20:1 | 20:1 |
---|
Runway 13/31
Length: | 4984 feet by 3rd Party Survey on 11/04/2006 |
---|
Width: | 75 feet |
---|
Surface: | Asphalt / Bituminous Concrete, Excellent Condition |
---|
Surface Treatment: | NONE |
---|
Weight Capacity: | Single Wheel aircraft: 12,000 lbs |
---|
Runway Lights Edge Intensity: | Med Intensity |
---|
|
End 13 |
End 31 |
---|
True Alignment: | 148,(137 Magnetic) | 328,(317 Magnetic) |
---|
Runway Markings: | Nonprecision Instrument,Good Condition | Nonprecision Instrument,Good Condition |
---|
Elevation at End: | 5790.7' MSL | 5863.3' MSL |
---|
Elevation at Touchdown Zone: | 5831.4' MSL | 5863.3' MSL |
---|
Threshold Crossing Glide Path Height: | 41' AGL | 57' AGL |
---|
Visual Glide Path Angle: | 3.00° | 4.00° |
---|
Visual Glide Slope Indicator: | 2-light PAPI on left side of runway | 2-light PAPI on right side of runway PAPI Unusbl Beyond 2.7 NM from Threshold Due to Trrn Ocs Penetration at 3.2 NM. |
---|
Runway End Identifer Lights (REIL): | Yes | Yes |
---|
Objects affecting Navigable Airspace (CFR part 77): | Utility runway with a nonprecision approach | Utility runway with a nonprecision approach |
---|
Object Clearance Slope: | 34:1 | 34:1 |
---|
• | Birds on & in Vicinity of Airport. |
---|
• | for Cd Contact Salt Lake ARTCC at 801-320-2568. |
---|
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.