63CN
Airport
Meadowlark Field
Livermore, California

FAA NFDC Information Effective 56-day cycle 09/18/2014 - 11/13/2014

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:63CN
Lat/Lng: 37.6613194444, -121.693561944
37-39-40.7500N, 121-41-36.8230W
Estimated
Elevation: 730 feet Estimated
Magnetic Variation: 16E, (1985), [14E (2014)]
Sectional: SAN FRANCISCO
From City: 4nm SE of Livermore

Operations

Use: Private
Ownership: Privately owned
Activation: 05/1962
Attended: All year Every day 0800-1800 (local)
Control Tower: no
ARTCC: Oakland Center (ZOA)
FSS: Oakland FSS (OAK)
Wind Indicator: Unlighted
Segmented Circle: yes
Landing Fee: no

Communications

Services

Airframe Repair: None
Powerplant Repair: None

Based Aircraft

Single Engine GA: 5
Ultralights: 1
Total: 6

Annual Operations

Total: 0

Ownership

Owner: Mark Mullen
4300 Greenville Rd
Livermore, Ca 94550
925-606-1536
Manager: Kate Mullen
4300 Greenville Road
Livermore, Ca 94550
925-606-1536

Runways

Runways: 07/25

Runway 07/25

Length: 1860 feet
Width: 25 feet
Surface: Gravel, Trtd
End 07 End 25
Right Hand Pattern: Yes  
Objects: Powerline Tree
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach

Procedures

NOTAMs

Additional Remarks


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.