FAA NFDC Information Effective 56-day cycle 11/09/2017 - 1/4/2018
|FAA Identifier:||D63 |
Estimated by FAA-EST on 07/09/2007
|Magnetic Variation:||17E,(1985),[14E (2017)]|
|From City:||1nmE of Dinsmore|
|Use:||Open to the public|
|Airspace Analysis:||NOT ANALYZED|
Estabd Prior to 1959.
|NOTAMs and Weather:||OAKNOTAM-D service at airport|
|Pattern Altitude:||3275 MSL (900 AGL)|
TPA 3275 MSL.
|For year ending:||12/31/2016|
|Local GA (< 20 miles):||600|
1106 2Nd St
Eureka, Ca 95501
Airport Manager Located at Arcata/Eureka Airport.
3561 Boeing Ave.
Mckinleyville, Ca 95519
|Surface:||Asphalt / Bituminous Concrete, Good Condition|
|Right Hand Pattern:||Yes|| |
|Runway Markings:||Basic,Good Condition||Basic,Good Condition|
|Displaced Threshold Distance:||80'||80'|
|Gradient:||0.2 ||0.2 |
|Objects affecting Navigable Airspace (CFR part 77):||Utility runway with a visual approach||Utility runway with a visual approach|
|Object Clearance Slope:||2:1|
Approach Ratio 4:1 to Displaced Threshold.
Approach Ratio 18:1 to Displaced Threshold; Approach Ratio 6:1 Over +340' Trees 2080' from Displaced Threshold.
|Object Height:||150' AGL||15' AGL|
|Object Distance:||525' Along centerline|
|200' Along centerline|
|Other Objects:|| ||15' Road at 40' from Threshold 125' R; +5' Fence at 0' from Threshold 125' R.|
|•||Day Use only; Closed Ngts.|
|•||Mountains with High Trees in Vicinity of Airport.|
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.
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
Conditions of Use.