4OR3
Airport
Lambert Field
Albany, Oregon

FAA NFDC Information Effective 56-day cycle 03/21/2024 - 5/16/2024

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:4OR3 (Four-Oscar-Romeo-Three)
Lat/Lng:44.7303988889, -123.075927778
44-43-49.4360N, 123-04-33.3400W
Estimated
Elevation:195 feet Estimated
Magnetic Variation:19E,(1990), [14E (2024)]
Sectional:SEATTLE
From City:7nm N of Albany

Operations

Use:Private
Airspace Analysis:CONDITIONAL
Provide Traffic Patterns Established West Side of Runway.
Ownership:Privately owned
Activation:08/1994
Control Tower:no
ARTCC:Seattle(ZSE)Seattle Center
FSS:Mc Minnville FSS(MMV)
Wind Indicator:Unlighted
Landing Fee:no

Communications

Services

Based Aircraft

Single Engine GA:3
Total:3

Annual Operations

Total:0

Ownership

Owner:Dwight E Lambert
33111 Harnish
Albany, or 97321
541-928-0903
Manager:Dwight E Lambert
33111 Harnish
Albany, or 97321
503-928-0903

Runways

Runways:16/34

Runway 16/34

Length:1700 feet
Width:100 feet
Surface:Grass / Sod
Surface Treatment:NONE
End 16 End 34
Right Hand Pattern:Yes 
Objects:TreesPowerline
Objects affecting Navigable Airspace (CFR part 77):Utility runway with a visual approachUtility runway with a visual approach
Object Clearance Slope: Powerline & Road on S End.
Object Height:75' AGL30' AGL
Object Distance:3000' Along centerline0' Along centerline

Procedures

NOTAMs

Additional Remarks

for Cd Contact Seattle ARTCC at 253-351-3694.

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.