2CD6
Airport
Yukon
Elizabeth, Colorado

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:2CD6
Lat/Lng: 39.39485, -104.547033333
39-23-41.4600N, 104-32-49.3200W
Estimated by OWNER on 01/24/2006
Elevation: 6510 feet Estimated by OWNER on 01/24/2006
Magnetic Variation: [8E (2014)]
Sectional: DENVER
From City: 4nm SW of Elizabeth

Operations

Use: Private
Airspace Analysis: CONDITIONAL
Provided Pilot & Aircraft Meet Requirements of Mode C Veil.
Ownership: Privately owned
Activation: 11/2007
Control Tower: no
ARTCC: Denver Center (ZDV)
FSS: Denver FSS (DEN)
Wind Indicator: Lighted
Landing Fee: no

Communications

Services

Based Aircraft

Single Engine GA: 1
Total: 1

Annual Operations

Total: 0

Ownership

Owner: Steven and Cathy Pitt
36410 Paradise Circle
Elizabeth, Co 80107
719-232-7899
Manager: Steven and Cathy Pitt
36410 Paradise Circle
Elizabeth, Co 80107
719-232-7899

Runways

Runways: 06/24

Runway 06/24

Length: 500 feet
by Owner on 01/24/2006
Width: 30 feet
Surface: Grass / Sod
End 06 End 24
Objects: Tree  
Objects affecting Navigable Airspace (CFR part 77): Utility runway with a visual approach Utility runway with a visual approach
Object Height: 40' AGL  
Object Distance: 200' Along centerline  

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.