| MS61
Airport
|
Ellis Field
|
|
Picayune, Mississippi
|
|
|
|
FAA NFDC Information Effective 56-day cycle 05/02/2013 - 6/27/2013
| FAA Identifier: | MS61 (Mike-Sierra-Six-One) |
| Lat/Lng: |
30.6303805556, -89.7326166667
30-37-49.3700N, 089-43-57.4200W
Estimated by OWNER on 12/16/2011
|
| Elevation: |
175 feet
Estimated
|
| Magnetic Variation: |
03E,
(1985),
[-1W (2013)]
|
| Sectional: |
NEW ORLEANS
|
| From City: |
7nm
NW of Picayune
|
| Use: |
Private
Personal Use.
|
| Airspace Analysis: |
CONDITIONAL
VFR - Personal Use only.
|
| Ownership: |
Privately owned
|
| Activation: |
11/1988
|
| Control Tower: |
no
|
| ARTCC: |
Houston Center
(ZHU)
|
| FSS: |
Greenwood FSS
(GWO)
|
| Wind Indicator: |
Lighted
|
| Landing Fee: |
no
|
| Single Engine GA: |
3
|
| Total: |
3
|
|
|
| Owner: |
T.Troy Ellis
151 Slidell Dr
Slidell, La 70460
985-960-6195
|
| Manager: |
T.Troy Ellis
151 Slidell Dr
Slidell, La 70460
985-960-6195
|
|
Runway 14/32
| Length: |
1800 feet
by Owner on 01/17/2012
|
| Width: |
100 feet
|
| Surface: |
Grass / Sod
|
|
End 14 |
End 32 |
| Right Hand Pattern: |
Yes
|
|
| Objects affecting Navigable Airspace (CFR part 77): |
Utility runway with a visual approach
|
Utility runway with a visual approach
|
Runway 17/35
| Length: |
2500 feet
by Owner on 01/17/2012
|
| Width: |
150 feet
|
| Surface: |
Grass / Sod
|
|
End 17 |
End 35 |
| Right Hand Pattern: |
Yes
|
|
| Objects affecting Navigable Airspace (CFR part 77): |
Utility runway with a visual approach
|
Utility runway with a visual approach
|
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.