IFR Enroute Charts
at skyvector.com Click on airport for details, drag to scroll around. Zoom using +/- keys. |
|
FAA NFDC Information 28-day cycle
Ops | Comms | Services | Owner | Runways | IFR Procs | Current NOTAMs | Remarks |
FAA Identifier: | AK28 |
---|---|
Lat/Lng: | 64.81402777777778, -147.91855555555554 64-48-50.5000N, 147-55-06.8000W Estimated |
Elevation: | 427 feet Estimated by Naco on 04/20/1994 |
Magnetic Variation: | 27E,(1990), [14E (2025)] |
Sectional: | FAIRBANKS |
From City: | 5nm SW of Fairbanks |
Use: | Private |
---|---|
Airspace Analysis: | CONDITIONAL Provided All Requirements in Letter Dated 2/23/87 are Followed. |
Ownership: | Privately owned |
Activation: | 12/1991 |
Control Tower: | no |
ARTCC: | Anchorage(ZAN)Anchorage Center |
FSS: | Fairbanks FSS(FAI) |
Wind Indicator: | Unlighted |
Beacon: | None |
Landing Fee: | no |
CTAF: | 118.300 |
---|
Fuel: | Grade 100LL Gasoline (low lead blue) 24 Hour. Credit Card Pump Midfield on Runway |
---|
Owner: | Chena Marina Floatpond & Runway Assoc P O Box 83658 Fairbanks, Ak 99708 907-479-2141 |
---|---|
Manager: | Donald D Kirk P.O. Box 80702 Fairbanks, Ak 99708 907-479-2141 |
Runways: | 18/36 18W/36W |
---|
Length: | 4700 feet |
---|---|
Width: | 60 feet |
Surface: | Gravel, Good Condition |
Surface Treatment: | NONE |
End 18 | End 36 | |
---|---|---|
Right Hand Pattern: | Yes | |
Objects affecting Navigable Airspace (CFR part 77): | Utility runway with a visual approach | Utility runway with a visual approach |
Length: | 4000 feet |
---|---|
Width: | 200 feet |
Surface: | Water |
Surface Treatment: | NONE |
End 18W | End 36W | |
---|---|---|
Right Hand Pattern: | Yes | |
Objects affecting Navigable Airspace (CFR part 77): | Utility runway with a visual approach | Utility runway with a visual approach |
• | Suais - 125.3/126.3(1-800-758-8723). |
---|---|
• | Use at Own Risk. Chena Marina is in Fai Class D Airspace, All Arriving/Departing Aircraft Must Contact Fai Tower (118 .3) Prior to Operating in Their Airspace. |
• | Traffic Pattern is on the West Side of Runways, with Chena Ridge Being the Westside Boundary. TPA is 1000 ft MSL, and in No Case to be Above 1200 ft MSL, to Allow for Separation with Other Fai Traffic. |
• | Runway Closely Bordered by Trees, Aircraft, and Floatpond. Occasional Vehicles, People, and Dogs on Runway. |
• | Air Taxi Operations and at Times Heavy Traffic on Field. be Aware All Traffic may not be in Same Direction As Fai. |
• | Hard Packed Snow Maintained on Runway During Winter Months. Wheeled Aircraft Advised to Call a Local, on Site FBO, for Conditions. |
• | Flight Training with Multiple Tkofs and Landings not Allowed. No Student Pilot Solo Flights Allowed. |
• | Please Consider Other Aircraft When Doing Run-Ups, As Summer Months Very Dusty. No Designated Transient Parking Area, All Property Bordering Runway is Privately Owned. |
• | Transients Need to Contact One of the Numerous FBO'S or Property Owners for Arrangements Before Parking. |
• | Floatpond for Use by Members only. Float Pond is Unattended, All Landings at Your Own Risk. |
• | Numerous Air Taxi Operations and at Times Heavy Traffic on Floatpond. |
• | No Designated Transient Tiedown Area, All Property Bordering Floatpond is Privately Owned. Transients Need to Contact One of the Numerous FBO'S or Property Owners for Arrangements Before Tiedown/Mooring. |
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 Chart Supplment (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.
rgrep