Pasco, Washington

FAA NFDC Information Effective 56-day cycle 09/14/2017 - 11/9/2017

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks


FAA Identifier:WA24
Lat/Lng: 46.3969444444, -119.020833333
46-23-49.0000N, 119-01-15.0000W
Estimated by OWNER on 10/25/2000
Elevation: 625 feet Estimated by OWNER on 10/25/2000
Magnetic Variation: 18E, (2000), [15E (2017)]
Sectional: SEATTLE
From City: 11nm N of Pasco


Use: Private
Ownership: Privately owned
Activation: 07/2002
Control Tower: no
ARTCC: Seattle Center (ZSE)
FSS: Seattle FSS (SEA)
Wind Indicator: Unlighted
Landing Fee: no



Based Aircraft

Single Engine GA: 3
Total: 3

Annual Operations

Total: 0


Owner: Steven Pfister
2881 E. Sagemoor Rd
Pasco, Wa 99301-9792
Cell 509-531-2222
Manager: Steven Pfister
2881 E. Sagemoor Rd
Pasco, Wa 99301-9792
Cell 509-531-2222


Runways: 01/19

Runway 01/19

Length: 3400 feet
2,400 Ft Asph and 1,000 Ft Gravel
by Owner on 10/25/2000
Width: 50 feet
Surface: Asphalt / Bituminous Concrete, Gravel, Fair Condition
End 01 End 19
Objects: Powerline Road
Object Marking: Marked  
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach
Object Height: 45' AGL 20' AGL
Object Distance: 450' Along centerline 100' Along centerline



Additional Remarks

A30-01/19-Takeoffs to the North and Landings to the South.

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.