| OG32
Heliport
|
Mahlon Sweet Field
|
|
Eugene, Oregon
|
|
|
|
FAA NFDC Information Effective 56-day cycle 05/02/2013 - 6/27/2013
| FAA Identifier: | OG32 (Oscar-Golf-Three-Two) |
| Lat/Lng: |
44.1265125, -123.223425556
44-07-35.4450N, 123-13-24.3320W
Estimated
|
| Elevation: |
364 feet
Estimated
|
| Magnetic Variation: |
19E,
(1985),
[16E (2013)]
|
| Sectional: |
KLAMATH FALLS
|
| From City: |
7nm
SE of Eugene
|
| Use: |
Private
|
| Ownership: |
Publicly owned
|
| Activation: |
09/1990
|
| Attended: |
Continuous
|
| Control Tower: |
no
|
| ARTCC: |
Seattle Center
(ZSE)
|
| FSS: |
Mc Minnville FSS
(MMV)
|
| Wind Indicator: |
Lighted
|
| Segmented Circle: |
yes
|
| Beacon: |
Sunset-Sunrise (local time)
Clear-Green (Lighted Land Airport)
|
| Landing Fee: |
no
|
| Fuel: |
Grade 100 Gasoline (green)
Grade 80 Gasoline (red)
Jet A - Kerosene, freeze point -40C
|
| Helicopter GA: |
2
|
| Total: |
2
|
|
|
| Owner: |
City of Eugene
28855 Lockheed Dr
Eugene, or 97402
541-682-5430
|
| Manager: |
Timothy Doll, a.a.E
28855 Lockheed Dr
Eugene, or 97402
541-682-5430
|
|
Runway H1
| Length: |
50 feet
|
| Width: |
50 feet
|
| Surface: |
Asphalt / Bituminous Concrete, Fair Condition
|
Runway H2
| Length: |
50 feet
|
| Width: |
50 feet
|
| Surface: |
Asphalt / Bituminous Concrete, Fair Condition
|
Runway H3
| Length: |
50 feet
|
| Width: |
50 feet
|
| Surface: |
Asphalt / Bituminous Concrete, Fair Condition
|
Runway H4
| Length: |
50 feet
|
| Width: |
50 feet
|
| Surface: |
Asphalt / Bituminous Concrete, Fair Condition
|
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.