CA03
Airport
Flying M
Planada, California

FAA NFDC Information Effective 56-day cycle 04/18/2024 - 6/13/2024

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:CA03 (Charlie-Alpha-Zero-Three)
Lat/Lng:37.3499402778, -120.2940725
37-20-59.7850N, 120-17-38.6610W
Estimated
Elevation:280 feet Estimated
Magnetic Variation:15E,(1985), [12E (2024)]
Sectional:SAN FRANCISCO
From City:4nm NE of Planada

Operations

Use:Private
Ownership:Privately owned
Activation:05/1975
Control Tower:no
ARTCC:Oakland(ZOA)Oakland Center
FSS:Rancho Murieta FSS(RIU)
Wind Indicator:Unlighted
Landing Fee:no

Communications

Services

Based Aircraft

Single Engine GA:2
Multi Engine GA:2
Total:4

Annual Operations

Total:0

Ownership

Owner:Myers Irrev. Flying M Ranch Trust
23679 Calabasas Rd., #152
Calabasas, Ca 91302
(818) 963-5884
Manager:Wes Myers
23679 Calabasas Rd., #152
Calabasas, Ca 91302
(818) 963-5884

Runways

Runways:02/20

Runway 02/20

Length:3000 feet
Width:30 feet
Surface:Asphalt / Bituminous Concrete
Surface Treatment:NONE
End 02 End 20
Objects:Other
Powerlines
Bldg
Objects affecting Navigable Airspace (CFR part 77):Utility runway with a visual approachUtility runway with a visual approach

Procedures

NOTAMs

Additional Remarks

for Landing Info Contact Mgr - Prior Permission for Landing.
for Cd Contact Norcal Approach at 916-361-0516.
Runway 02/20 Barbed Wire Fence at Both Runway Ends.
Aiming Point Mkrs are 700 ft from Runway Ends.

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.