| 0MT6
Airport
|
Hanson
|
|
Marion, Montana
|
|
|
|
FAA NFDC Information Effective 56-day cycle 05/02/2013 - 6/27/2013
| FAA Identifier: | 0MT6 (Zero-Mike-Tango-Six) |
| Lat/Lng: |
48.0405555556, -114.679444444
48-02-26.0000N, 114-40-46.0000W
Estimated
|
| Elevation: |
3900 feet
Estimated
|
| Magnetic Variation: |
17E,
(1995),
[14E (2013)]
|
| Sectional: |
GREAT FALLS
|
| From City: |
4nm
S of Marion
|
| Use: |
Private
|
| Airspace Analysis: |
CONDITIONAL
Provided Daytime VFR only.
|
| Ownership: |
Privately owned
|
| Activation: |
11/1997
|
| Attended: |
Continuous
|
| Control Tower: |
no
|
| ARTCC: |
Salt Lake City Center
(ZLC)
|
| FSS: |
Great Falls FSS
(GTF)
|
| Wind Indicator: |
Unlighted
|
| Landing Fee: |
yes
|
| Single Engine GA: |
5
|
| Total: |
5
|
|
|
| Owner: |
John G Hanson
205 Sicklers Creek Road
Marion, Mt 59925
406-844-4416
|
| Manager: |
John G Hanson
205 Sicklers Creek Road
Marion, Mt 59925
406-844-4416
|
|
Runway 08/26
| Length: |
2400 feet
|
| Width: |
50 feet
|
| Surface: |
Grass / Sod
|
|
End 08 |
End 26 |
| Objects: |
Trees
|
Terrain
|
| Objects affecting Navigable Airspace (CFR part 77): |
Utility runway with a visual approach
|
Utility runway with a visual approach
|
| Object Height: |
100' AGL
|
75' AGL
|
| Object Distance: |
200' Along centerline
|
100' Along centerline
|
| • | Road Intersects Runway Near Midpoint. |
| • | Livestock in View of Runway. |
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.