Lynden, Washington

FAA NFDC Information Effective 56-day cycle 10/15/2015 - 12/10/2015

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks


FAA Identifier:38W
Lat/Lng: 48.9558961111, -122.458118333
48-57-21.2260N, 122-27-29.2260W
Estimated by STATE on 08/15/2002
Elevation: 106 feet Estimated by STATE on 07/28/2005
Magnetic Variation: 21E, (1985), [16E (2015)]
Sectional: SEATTLE
From City: 1nm N of Lynden


Use: Open to the public
Airspace Analysis: NOT ANALYZED
Estabd Prior to 15 may 1959.
Ownership: Publicly owned
Activation: 02/1961
Control Tower: no
ARTCC: Vancouver (ZVR) Seattle Center (ZSE)
FSS: Seattle FSS (SEA)
NOTAMs and Weather: SEA NOTAM-D service at airport
Wind Indicator: Lighted
Segmented Circle: yes
Lights: Use 3 Clicks to Activate MIRL Runway 07/25 - CTAF.
Beacon: Use 3 Clicks to Activate Rotating Beacon- CTAF.
Clear-Green (Lighted Land Airport)
Landing Fee: no


CTAF: 122.900
UNICOM: Use 3 Clicks to Activate Automated Unicom.


Fuel: Grade 100LL Gasoline (low lead blue)
Automated Credit Card System for Fuel.
Airframe Repair: None
Powerplant Repair: None
Bottled Oxygen: None
Bulk Oxygen: None
Transient Storage: Tie-Down

Based Aircraft

Single Engine GA: 20
Multi Engine GA: 1
Helicopter GA: 1
Ultralights: 4
Total: 26

Annual Operations

For year ending: 12/31/2014
AirTaxi: 50
Local GA (< 20 miles): 4000
Non-local GA: 3000
Total: 7050


Owner: City of Lynden
City Hall, 300 4Th Street, 323 Front Street
Lynden, Wa 98264
Manager: Steve Banham
Alternate Contact: Laura Burford - Public Works Office Manager
300 4Th Street, 323 Front Street
Airport Physical Address: 8635 Depot Road, Lynden, Wa 98264
Lynden, Wa 98264


Runways: 07/25

Runway 07/25

Length: 2425 feet
by State on 08/15/2002
Width: 40 feet
Surface: Asphalt / Bituminous Concrete, Good Condition
Weight Capacity: Single Wheel aircraft: 12,000 lbs
Runway Lights Edge Intensity: Non-standard Lighting System
No White/Red Lights Past Displaced Threshold.
End 07 End 25
Runway Markings: Basic, Good Condition Basic, Good Condition
Displaced Threshold Distance: 262' 433'
Gradient: 0.2 0.2
Threshold Crossing Glide Path Height: 15' AGL 15' AGL
Visual Glide Path Angle: 3.00° 6.00°
Visual Glide Slope Indicator: 2-light PAPI on left side of runway 2-light PAPI on right side of runway
Objects: Fence Road
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach
Object Clearance Slope: 18:1
Runway 07 Approach Slope 16:1 to +17 Ft Road at 272 Ft from Displaced Threshold.
Runway 25 Approach Slope 18:1 to Displaced Threshold; 84 Ft Trees 1116 Ft 0B.
Object Height: 5' AGL 16' AGL
Object Distance: 292' Along centerline
62' Left of centerline
202' Along centerline
Other Objects: Road at 23' Road at 50 Ft Trees at 200 Ft; 80 Ft Trees at 0 Ft 84 Ft L; +7 Ft Bushes at 0 Ft Lt.



Additional Remarks

Report on Downwind on 122.9
1850' Between Threshold Lights; Runway 07 Threshold Lights Located 134' Prior to Displaced Threshold.
Avoid Night Ldngs to Runway 25 - Night Ldngs Should be Performed on Runway 07 - Winds Permitting.
Threshold Relctd 155 Ft for Night Operations; Runway 25 Threshold Relctd 434 Ft for Night Operations; 1871 Ft Lgtd at Night.
Exposed Ditch Runway 07/25.
Fly PAPI on All Aproaches to Runway 07
Runway 07 Threshold Displaced 262 Ft, Landing Distance Available 2163 Ft
Runway 25 Threshold Displaced 433 Ft, Landing Distance Available 1992 Ft
Runway 25 Departures Use Full Length of Available Runway Toda 2425 Ft
Run-Ups not Permitted on Runway 25 Turn Around Taxiway

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.