WY33
Airport
Antelope Run Ranch
Daniel, Wyoming

FAA NFDC Information Effective 56-day cycle 07/24/2014 - 9/18/2014

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:WY33
Lat/Lng: 42.8169444444, -110.278333333
42-49-01.0000N, 110-16-42.0000W
Estimated by OWNER on 10/07/2003
Elevation: 7470 feet Estimated by OWNER on 10/07/2003
Magnetic Variation: [11E (2014)]
Sectional: SALT LAKE CITY
From City: 10nm SW of Daniel

Operations

Use: Private
Airspace Analysis: CONDITIONAL
Provided Users of Airport Remain Clear of Airway Victor 328 Located 0.88 NM to the Northeast.
Ownership: Privately owned
Activation: 07/2004
Control Tower: no
ARTCC: Salt Lake City Center (ZLC)
FSS: Casper FSS (CPR)
Wind Indicator: Lighted
Lights: Activate MIRL Runway 07/25 - 122.9.
Landing Fee: no

Communications

Services

Based Aircraft

Total: 0

Annual Operations

Total: 0

Ownership

Owner: Frank Krejci
1506 N 203
Elkhorn, NE 68022
402-493-6165
Manager: Johnny Schmidt
Po Box 184
Daniel, Wy 83115
307-859-8644

Runways

Runways: 07/25

Runway 07/25

Length: 7500 feet
by Owner on 10/07/2003
Width: 75 feet
Surface: Asphalt / Bituminous Concrete
Runway Lights Edge Intensity: Med Intensity
End 07 End 25
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.