0B4
Airport
Hartington Municipal/ Bud Becker Field
Hartington, Nebraska

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:0B4 (Zero-Bravo-Four)
Lat/Lng: 42.6030833333, -97.2535
42-36-11.1000N, 097-15-12.6000W
Estimated by 3RD PARTY SURVEY on 07/13/2008
Elevation: 1388 feet Surveyed by 3RD PARTY SURVEY on 07/13/2008
Magnetic Variation: 06E, (2000), [4E (2014)]
Sectional: OMAHA
From City: 2nm SE of Hartington

Operations

Use: Open to the public
Airspace Analysis: NOT ANALYZED
Existed Prior to 1959.
Ownership: Publicly owned
Activation: 02/1949
Attended: Continuous
Control Tower: no
ARTCC: Minneapolis Center (ZMP)
FSS: Columbus FSS (OLU)
NOTAMs and Weather: OLU NOTAM-D service at airport
Wind Indicator: Lighted
Beacon: Dusk-Dawn. Activate MIRL Runway 13/31; PAPI Runways 13 & 31 - CTAF.
Clear-Green (Lighted Land Airport)
Landing Fee: no

Communications

CTAF: 122.900

Services

Fuel: Grade 100LL Gasoline (low lead blue)
for Fuel Call (402) 254-7316 or (402) 841-0659.
Airframe Repair: Major
Powerplant Repair: Major
Bottled Oxygen: None
Bulk Oxygen: None
Transient Storage: Hanger,Tie-Down
Other Services: Crop Dusting, Pilot Instruction, Aircraft Rental

Based Aircraft

Single Engine GA: 20
Multi Engine GA: 1
Helicopter GA: 1
Total: 22

Annual Operations

For year ending: 08/15/2013
AirTaxi: 250
Local GA (< 20 miles): 5400
Non-local GA: 950
Total: 6600

Ownership

Owner: Hartington Airport Authority
Airport Authority Chairman is V.E. Rossiter, Jr.
P.O. Box 14, 302 S. Cedar Avenue
Hartington, NE 68739-0014
402-254-6873
Manager: Tom Becker
56395 881 Road
Hartington, NE 68739-4021
402-254-7317
Mobile Phone 402-841-0659 (Manager)

Runways

Runways: 03/21
13/31

Runway 03/21

Length: 2150 feet
Width: 125 feet
Surface: Grass / Sod, Good Condition
End 03 End 21
True Alignment: 041, (037 Magnetic) 221, (217 Magnetic)
Gradient: 0.5 0.5
Elevation at End: 1387.2' MSL 1374.2' MSL
Elevation at Touchdown Zone: 1387.2' MSL 1387.2' MSL
Objects: Trees Road
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach
Object Clearance Slope: 23:1 21:1
Object Height: 32' AGL 10' AGL
Object Distance: 765' Along centerline
145' Left of centerline
215' Along centerline
0B'

Runway 13/31

Length: 3950 feet
by 3Rd Party Survey on 07/13/2008
Width: 60 feet
Surface: Porland Cement Concrete, Good Condition
Runway Lights Edge Intensity: Med Intensity
End 13 End 31
True Alignment: 141, (137 Magnetic) 321, (317 Magnetic)
Runway Markings: Nonprecision Instrument, Good Condition Nonprecision Instrument, Good Condition
Displaced Threshold Distance:   400'
Gradient: 0.3 0.3
Elevation at End: 1367.1' MSL 1380.6' MSL
Elevation at Displaced Threshold:   1381.8' MSL
Elevation at Touchdown Zone: 1382.6' MSL 1382.7' MSL
Threshold Crossing Glide Path Height: 52' AGL 37' AGL
Visual Glide Path Angle: 4.00° 3.00°
Visual Glide Slope Indicator: 2-light PAPI on left side of runway 2-light PAPI on left side of runway
Objects:   Road
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a nonprecision approach Utility runway with a nonprecision approach
Object Clearance Slope: 50:1 7:1
Approach Ratio 37:1 to Displaced Threshold.
Object Height:   20' AGL
Object Distance:   350' Along centerline
0B'
Other Objects: +5' Road, 0' from Runway End, 125' Left.  

Procedures

NOTAMs

Additional Remarks

A30-03/21-not Plowed Winter Months.
Runway 03/21 not Plowed Winter Months.

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.