| 59AS
Airport
|
Becker Field
|
|
Battle Ground, Washington
|
|
|
|
FAA NFDC Information Effective 56-day cycle 04/18/2024 - 6/13/2024
| FAA Identifier: | 59AS |
|---|
| Lat/Lng: | 45.8506694444, -122.544513889
45-51-02.4100N, 122-32-40.2500W
Estimated |
|---|
| Elevation: | 1720 feet Surveyed |
|---|
| Magnetic Variation: | [15E (2024)] |
|---|
| Sectional: | SEATTLE |
|---|
| From City: | 5nm N of Battle Ground |
|---|
| Use: | Private |
|---|
| Ownership: | Privately owned |
|---|
| Activation: | 03/2006 |
|---|
| Control Tower: | no |
|---|
| ARTCC: | Seattle(ZSE)Seattle Center |
|---|
| FSS: | Seattle FSS(SEA) |
|---|
| Wind Indicator: | Lighted |
|---|
| Landing Fee: | no |
|---|
| Single Engine GA: | 2 |
|---|
| Total: | 2 |
|---|
|
|
| Owner: | Becker Family Llc
31415 NE 122 Ave
Battle Ground, Wa 98604
360-576-9069 |
|---|
| Manager: | Marcus Becker
31415 NE 122 Ave
Battle Ground, Wa 98604
360-576-9069 |
|---|
|
Runway 09/27
| Length: | 1350 feet |
|---|
| Width: | 50 feet |
|---|
| Surface: | Grass / Sod |
|---|
| Surface Treatment: | NONE |
|---|
|
End 09 |
End 27 |
|---|
| Objects: | Trees | |
|---|
| Objects affecting Navigable Airspace (CFR part 77): | Utility runway with a visual approach | Utility runway with a visual approach |
|---|
| Object Height: | 60' AGL | |
|---|
| Object Distance: | 200' Along centerline | |
|---|
| • | Tkf to the East only and Land to the West only. |
|---|
| • | for Cd Contact Portland Approach at 503-493-7545. |
|---|
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.
