MS03
Airport
Christmas
Shelby, Mississippi

FAA NFDC Information Effective 56-day cycle 04/03/2014 - 5/29/2014

Ops Comms Services Owner Runways IFR Procs Current NOTAMs Remarks

Location

FAA Identifier:MS03 (Mike-Sierra-Zero-Three)
Lat/Lng: 33.9242772222, -90.787045
33-55-27.3980N, 090-47-13.3620W
Estimated
Elevation: 153 feet Surveyed
Magnetic Variation: 03E, (1985), [0W (2014)]
Sectional: MEMPHIS
From City: 2nm SW of Shelby

Operations

Use: Private
Ownership: Privately owned
Activation: 04/1972
Attended: All year Mon-Sat 0700-1800 (local)
Control Tower: no
ARTCC: Memphis Center (ZME)
FSS: Greenwood FSS (GWO)
Wind Indicator: Unlighted
Landing Fee: no

Communications

Services

Airframe Repair: None
Powerplant Repair: None

Based Aircraft

Single Engine GA: 3
Multi Engine GA: 1
Total: 4

Annual Operations

Total: 0

Ownership

Owner: Michael Christmas
Po Box 770
Shelby, Ms 38774
601-398-7136
Manager: Michael Christmas
Box 770
Shelby, Ms 38774
662-398-7136

Runways

Runways: 18/36

Runway 18/36

Length: 3900 feet
Width: 75 feet
Surface: Porland Cement Concrete, Grass / Sod
Conc Portion (1700 Ft by 22 Ft) North End of Runway.
End 18 End 36
Objects: Powerline
2 Bldgs Near Runway.
 
Object Marking: Marked  
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.