| OG16
Airport
|
Jim's Airstrip
|
|
Halsey, Oregon
|
|
|
|
FAA NFDC Information Effective 56-day cycle 05/02/2013 - 6/27/2013
| FAA Identifier: | OG16 (Oscar-Golf-One-Six) |
|---|
| Lat/Lng: |
44.3826222222, -123.21315
44-22-57.4400N, 123-12-47.3400W
Estimated
|
|---|
| Elevation: |
275 feet
Estimated
|
|---|
| Magnetic Variation: |
18E,
(1995),
[16E (2013)]
|
|---|
| Sectional: |
KLAMATH FALLS
|
|---|
| From City: |
5nm
W of Halsey
|
|---|
| Use: |
Private
|
|---|
| Ownership: |
Privately owned
|
|---|
| Activation: |
06/2000
|
|---|
| Control Tower: |
no
|
|---|
| ARTCC: |
Seattle Center
(ZSE)
|
|---|
| FSS: |
Mc Minnville FSS
(MMV)
|
|---|
| Wind Indicator: |
Lighted
|
|---|
| Landing Fee: |
no
|
|---|
| Single Engine GA: |
2
|
|---|
| Ultralights: |
1
|
|---|
| Total: |
3
|
|---|
|
|
| Owner: |
James Vanleeywen
27666 Peoria Road
Halsey, or 97348
541-369-2992
|
|---|
| Manager: |
James Vanleeywen
27666 Peoria Road
Halsey, or 97348
541-369-2992
|
|---|
|
Runway 16/34
| Length: |
2200 feet
|
|---|
| Width: |
50 feet
|
|---|
| Surface: |
Grass / Sod, Natural Soil
|
|---|
|
End 16 |
End 34 |
|---|
| Objects: |
Road
Runway 16 Abuts County Road, Seperation from Road Traffic Rqrd.
|
|
|---|
| Objects affecting Navigable Airspace (CFR part 77): |
Utility runway with a visual approach
|
Utility runway with a visual approach
|
|---|
| Object Height: |
20' AGL
|
|
|---|
| Object Distance: |
0' Along centerline
|
|
|---|
| • | Runway 16/34 Soft After Heavy Rain. |
|---|
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.
