11OR
Airport
|
Nail Spring Ranch
|
Bonanza, Oregon
|
|
|
|
FAA NFDC Information Effective 56-day cycle 12/26/2024 - 2/20/2025
FAA Identifier: | 11OR (One-One-Oscar-Romeo) |
---|
Lat/Lng: | 42.1333464167, -121.218337444 42-08-00.0471N, 121-13-06.0148W Estimated by Ado on 07/18/2024 |
---|
Elevation: | 4249 feet Estimated by Ado on 07/18/2024 |
---|
Magnetic Variation: | [13E (2024)] |
---|
Sectional: | KLAMATH FALLS |
---|
From City: | 10nm ESE of Bonanza |
---|
Use: | Private |
---|
Ownership: | Privately owned |
---|
Activation: | 07/2024 |
---|
Control Tower: | no |
---|
ARTCC: | Seattle(ZSE)Seattle Center |
---|
FSS: | Mc Minnville FSS(MMV) |
---|
Wind Indicator: | Lighted |
---|
Landing Fee: | no |
---|
|
|
Owner: | Dennis S. Becklin 3560 Rogue River Hwy Grants Pass, or 97623 541-659-0501 |
---|
Manager: | Dennis S. Becklin Email: STERLING@BECKLIN.COM 3560 Rogue River Hwy Grants Pass, or 97527 541-659-0501 |
---|
|
Runway 17/35
Length: | 2514 feet by Ado on 07/18/2024 |
---|
Width: | 60 feet |
---|
Surface: | Grass / Sod |
---|
Surface Treatment: | NONE |
---|
|
End 17 |
End 35 |
---|
Runway Markings: | Nonstandard (Other Than Numbers Only) | Nonstandard (Other Than Numbers Only) |
---|
Elevation at End: | 4249.0' MSL | 4249.0' MSL |
---|
Objects affecting Navigable Airspace (CFR part 77): | Utility runway with a visual approach | Utility runway with a visual approach |
---|
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.