AA30
Airport
Trio Estates
Houston, Alaska

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:AA30 (Alpha-Alpha-Three-Zero)
Lat/Lng: 61.6481888889, -149.870830556
61-38-53.4800N, 149-52-14.9900W
Estimated by OWNER on 02/11/2009
Elevation: 315 feet Estimated by OWNER on 02/11/2009
Magnetic Variation: [18E (2014)]
Sectional: ANCHORAGE
From City: 4nm NW of Houston

Operations

Use: Private
Airspace Analysis: CONDITIONAL
Provided Pvt Use only; All Aircraft Comply with Traffic Pattern Boundary.
Ownership: Privately owned
Activation: 03/2004
Control Tower: no
ARTCC: Anchorage Center (ZAN)
FSS: Kenai FSS (ENA)
Wind Indicator: Lighted
Landing Fee: no

Communications

CTAF: 122.800
UNICOM: 122.800

Services

Based Aircraft

Total: 0

Annual Operations

Total: 0

Ownership

Owner: Olga Rogers, Mickey Sleeper
7657 E 20Th Ave
Anchorage, Ak 99504
907-337-3304
Manager: Olga Rogers, Mickey Sleeper
7657 E 20Th Ave
Anchorage, Ak 99504
907-317-8992

Runways

Runways: 05/23

Runway 05/23

Length: 1285 feet
by Owner on 02/11/2009
Width: 60 feet
Surface: Gravel, Good Condition
End 05 End 23
Objects: Powerline  
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: 650' Along centerline  

Procedures

NOTAMs

Additional Remarks

All Operations Must Use CTAF.

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.