Mat Su Valley CTAF Frequencies Change on May 29th

Heads up for pilots who fly in the Matanuska-Susitna Valley. On May 29, 2014 a significant change takes place to the Common Traffic Advisory Frequencies (CTAFs) assigned north and west of Anchorage.  If you aren’t religious about buying new flight charts, or updating your GPS databases, plan to do so with this charting cycle, as approximately 78 airport CTAFs will change on that date.  In addition, 36 airports will have CTAFs assigned for the first time.  In total, FAA is sending letters to 178 airport owners notifying them of the CTAF assignment changes.  Goose Bay, Wolf Lake and Anderson Lake are just three of the airports whose CTAFs will change.  The new frequencies will be found on flight charts, in individual airport listings in the Alaska Supplement, along with a map in the Notices section that shows the “big picture” change taking place.

Background
In the summer of 2011, a number of mid-air collisions occurred in the Mat Su Valley, one with fatal results.  During the subsequent NTSB investigation, it appeared that both pilots involved in that accident had been using what they believed was the correct frequency for the location they were flying—but they were not communicating on the same frequency.  A working group with representation from industry and government was established that fall to look at the published guidance regarding CTAF usage.  Over the past two and a half years, the group methodically examined CTAF assignments, civil and military flight patterns, ATC infrastructure and the results of an AOPA pilot survey.  After agreeing that changes needed to be made, different scenarios for creating “area CTAFs” were evaluated and reviewed by seasoned pilots, commercial operators, flight instructors and pilots based at different area airports.  Like all good Alaska discussions, not everyone agreed with everything, but there was widespread support to reduce the complexity—and overlap—between CTAFs used at different airports and landing areas.  Last fall a set of recommendations was made to the FAA, elements of which will go into effect at the end of May.

New CTAF Areas defined
To eliminate the overlap from adjacent airport frequencies, the FAA is designating new “CTAF Areas” within which, all the airports will be on the same frequency. This concept is not new in Alaska, as the airspace over Denali National Park has had designated “mountain traffic advisory frequencies” for many years.  Cook Inlet and the Knik Glacier areas also have established CTAFs.  On May 29th, there will be four new CTAF area frequencies identified, to let pilots know what frequency to use, if they are not in contact with ATC or a Flight Service Station.  There are corresponding changes to the north boundary of the Cook Inlet CTAF area that become effective at this time.  A diagram showing these areas will be on page 399 of the Notices Section of the Alaska Supplement, however the information is also listed on the FAA’s website  www.faa.gov/go/flyalaska.

Depiction of the Mat Su CTAF Areas that go into effect May 29. Notice that the adjacent Cook Inlet CTAF Area to the sound also has a change in boundary

Depiction of the Mat Su CTAF Areas that go into effect May 29. Notice that the adjacent Cook Inlet CTAF Area, west of Anchorage, also has a change in boundary

How were boundaries selected?
The Mat Su Valley is a highly aviation oriented place. In addition to over 200 private and public airports in the FAA’s database, there are other landing areas (lakes, gravel bars and rivers) that are heavily used either seasonally or on a year-around basis.  The boundaries were designed, as much as possible, to avoid areas where traffic concentrated—along major rivers, at area airports, etc.  Consequently, the boundaries were offset from rivers and coast lines, recognizing that they are often used for navigation when weather is down.  Flight patterns in and out of area airports were also considered, and verified with ATC radar data. During the review process, numerous boundary revisions were made to minimize conflicts with existing flows of traffic along commonly used routes to popular locations.  Ultimately, the beauty of the airplane is that it can go anywhere—weather permitting—so no set of boundaries will meet everyone’s needs.  Hopefully assigning advisory frequencies to different areas will reduce some of the ambiguity experienced previously.

Hi Traffic areas are also depicted within the Mat Su CTAF Areas.  While some are popular airports, others are not shown on flight charts.

High Traffic areas are also depicted within the Mat Su CTAF Areas. While some are popular airports, others are not shown on flight charts.

High Traffic Locations
The working group also identified “high traffic” locations in the Mat Su Valley.  Many of these are airports that already appear on the charts, familiar to us all.  Others are popular lakes, rivers and gravel bars used during fishing season or to access recreational cabins.  These are also depicted on the CTAF Area diagram, along with their names, to let pilots know which CTAF frequency to use when operating to or near these locations.  We hope those locations not charted as airports will eventually become VFR waypoints that may be depicted on FAA flight charts.

Feedback Needed
Any significant change of this magnitude has the potential to solve some problems, and may cause others.  As a result, the working group set up a feedback mechanism to report problems or concerns.  A feedback form has been established on the Alaska Aviation Safety Foundation’s website so that pilots may report problems or ask questions, regarding this change of CTAF architecture.  www.aasfonline.org/feedback  Please let us know if you encounter problems that need to be addressed.  The working group will continue to address other areas, such as the Glenn Highway corridor between Anchorage and Palmer, to consider further refinements in the future.

What can I do?
This is a significant change, a long time in the making.  Please make sure to pick up the May 29th issues of flight charts, the Alaska Supplement, and update GPS databases.  Make it a point to check the CTAF of the place you are flying from and to-especially if you have gone there a hundred times before.  Talk about these changes with your friends and neighbors, to make sure they know about it.

This only works if we truly are all on the same frequency!

May 23rd Update:
Here are two additional documents to help “navigate” the changes to the Mat Su CTAFs.

Mat Su single-sided transition map This document is a single-sided map of the Mat Su CTAF Areas, which also has the high traffic areas combined.  The document size is 11 x 17 inches, in Adobe  PDF format, but may also be printed on 81/2 x 11 inch letter size paper.

 

MatSuValley Airports CTAF Listing  This document lists Mat Su Valley airports, seaplane bases and helipads, their identifiers and assigned CTAF frequency as of May 29, 2014.

Mat Su Traffic Working Group makes Recommendations

For the past two years a working group of industry and government stakeholders have looked at ways to reduce the risk of mid-air collisions in the Mat Su Valley. Initially the group listened to briefings from CFI’s, charter pilots, military users, Air Traffic Control, FAA Airports Division, Flight Service and others.  During the summer of 2012, AOPA conducted an online survey, which gathered feedback from over 500 pilots who fly in this airspace.  Communications ranked highest among the factors that pilots said contributed to unsafe situations when flying over the Mat Su.  Based on this information, the working group started work on a plan to simplify radio frequency usage in the area.  By April, 2013 two different scenarios were proposed, and taken back to the aviation community for review.  Starting with the Airmen’s Trade Show in May, numerous meetings were held with individual pilots, flight schools, air taxi operators as well as the government participants in the group.  Air Traffic Control staff members produced a set of radar tracks, showing traffic patterns that lead to modification of some of the initial boundaries.  At a meeting near the end of October, the working group selected a single alternative, and finalized an initial set of recommendations that will go to different parts of the FAA requesting changes in the guidance regarding CTAF frequency usage in this area.

 

Recommended "Area Frequency" zones for consideration by the FAA to simplify radio communication when not in contact with ATC.

Recommended “Area Frequency” zones for consideration by the FAA to simplify radio communication when not in contact with ATC.

Initial Recommendations
The group crafted four “Area Frequency” zones, where a single discrete VHF radio frequency would be recommended, when not in contact with ATC.  The accompanying image map shows the proposed frequency zones.  Within each area, individual airport CTAF frequencies would be changed to match, to eliminate conflicting guidance for aircraft flying in this airspace. The working group suggested making changes to some of the existing “area frequency” zones in Cook Inlet and around the Knik Glacier, to conform to the newly proposed zones.  Outside the defined zones, pilots would use the CTAF frequencies assigned to an individual airport, or the “default” 122.9 MHz frequency used for airports or landing areas without an assigned frequency.

Another recommendation is to create VFR reporting points for a number of “high traffic” areas identified by the working group, and confirmed by the 2012 user survey.  This would allow pilots not familiar with these sites to understand their proximity to areas that are heavily used (in some cases on a seasonal basis) but that aren’t charted as airports.

An additional recommendation is to clarify the language in the Aeronautical Information Manual (AIM), to recognize Area Frequency zones.  Pilots need to understand how they differ from conventional CTAF areas, which today the AIM defines as a 10 mile zone around an individual airport or landing area.

More work to come
With this initial set of recommendations completed, different parts of the FAA will have to go through their own internal process to change aeronautical charts, airport CTAF assignments, and guidance in other documents such as the Alaska Supplement.  Meanwhile the working group will continue to address other issues that need attention, such as the corridor along the Glenn Highway between Palmer and Anchorage, extending to the Kenai Peninsula.  Further work is needed to review and possibly revise the guidance to pilots on best operating practices in that area.

It will take months for the changes described above to be implemented by the FAA.  At this time these are only recommendations that are not in effect today.  The industry and government members of this team also agreed that a significant educational campaign will be needed when changes are made. Stay tuned as guidance is revised for more details in the months ahead. Meanwhile, keep your head on a swivel and be vigilant as you fly!

This update by Tom George, AOPA Alaska Regional Manager and Adam White, Government Affairs, Alaska Airmen’s Association

Mat Su Area Traffic Frequencies: Your input needed

A group of industry and government stakeholders is working to reduce the risk of mid-air collisions in the Mat Su Valley, but they need your help to reach that objective.  Over the past five months, the working group has taken the results of last summer’s AOPA pilot survey and inputs from pilots who fly in and through the area.  The goal is to clarify the use of radio frequencies used to maintain situational awareness when operating in this busy airspace.

Home to over two hundred private and public use airports, airstrips, lakes and landing areas, the Mat Su experiences a wide range of aviation uses.  The airspace in the valley sees everything from private pilots heading to cabins or hunting and fishing areas, to commercial operators hauling visitors, groceries and supplies to remote lodges and mines. It is also used for military training flights at low-level by helicopters and C-17s, and student flight training from Anchorage and valley airports. Add to the list, those of us that fly through the Mat Su headed to more distant destinations.  One of the tools we use to share the airspace is reporting our location and listening for nearby aircraft, but on what frequency?

Rex Gray's map showing overlapping CTAF frequencies.

Rex Gray’s map showing overlapping CTAF frequencies.

During the “inventory” phase of this project, it became apparent there was a lack of agreement even among seasoned professionals on what radio frequency to use for situational awareness in different parts of this airspace.  Rex Gray, a valley resident who also serves as the President of the Alaska Airmen’s Association, took the time to sit down with the Anchorage Sectional and the Alaska Supplement and map out overlaps in CTAF coverage in the valley.  According to the AIM, a Common Traffic Advisory Frequency serves an area 10 miles around its assigned airport.  This map, coupled with other area frequency guidance in different publications highlighted the problem. Pilots who consciously used the CTAF for the airport they were headed to were often sharing airspace with aircraft on other frequencies enroute to adjacent landing areas.  A priority was identified within the working group to reduce this confusion, and promote the use of defined area frequencies, as has been done on a case by case basis in other parts of the state.

Developing a plan that would address the diversity of users is a challenge.  Over the past two months, using Google Earth as a tool, the group developed a number of scenarios to identify areas that might share a common frequency.  Subsequently, these were reduced to two scenarios which are still in need of refinement before focusing on a final course of action.

Scenario which assigns frequencies to different zones in the Mat Su Valley.

Scenario which assigns frequencies to different zones in the Mat Su Valley.

Area Frequency Scenario: This option would assign the frequency 122.9 to the zone west of the Susitna River, to the flanks of the Alaska Range. It also cuts across the lower valley, to accommodate traffic that departs Anchorage headed northwest.  A second zone, running along the Parks Highway toward Talkeetna under this scenario would use 122.8.  The zones around Palmer and Talkeetna, with part time Flight Service Stations, would use the FSS Advisory Frequency, 123.6.  These proposed zones would connect to other areas, such as the Cook Inlet Area Frequency to the west and the Knik Glacier advisory frequency, both of which use 122.7.  Northwest of Talkeetna, a Mountain Traffic Frequency of 123.65 has been in use for years to accommodate the aircraft hauling climbers and flightseeing visitors between Talkeetna and the Alaska Range.

Scenario that provides a discrete frequency above 2,000 ft to reduce congestion on 122.8.

Scenario that provides a discrete frequency above 2,000 ft to reduce congestion on 122.8.

Vertical Area Frequency Scenario:  In the second case, the zones to the west and around Palmer and Talkeetna (described above), would remain the same. The frequency 122.8 would still serve the area along the Parks Highway, but aircraft operating between 2,000 and 5,000 feet MSL would have the option to use a discrete frequency, we’ll call it 122.XX, to reduce the frequency congestion from the traffic flying in airport traffic patterns and at lower altitudes in the zone.

What happens after I leave a zone?  Several people have raised the question of what happens once you leave one of these zones. At that point, pilots would resort to the standard rules involving CTAF’s.  Chapter Four in the AIM addresses this topic. Section 4-1-9 defines the protocol for traffic advisory practices for airports without facilities:  Within 10 miles of the airport or landing area, monitor and communicate on the designated CTAF.  Section 4-1-11 indicates that an airport with no tower, FSS or Unicom should use the multi-com frequency 122.9.  Table 4-1-2 indicates that for air-to-air communication, the FCC has authorized the use of 122.75, which helps keep the chatter down on the other frequencies in congested airspace. Checking the Alaska Supplement Notices Section is a good idea, as a number of areas around the state have had special area frequencies assigned.

These scenarios are still taking shape. AOPA would like to hear your thoughts on these approaches to reducing the confusion on radio frequency usage in the Mat Su Valley. Please email your comments to: airtrafficservices@aopa.org.  If you attend the Alaska Airmen’s Great Alaskan Aviation Gathering this weekend in Anchorage, stop by the AOPA booth and look at these scenarios in more detail.  While this work continues, fly with your lights on, keep your eyes out of the cockpit and fly safe!

Pilot Survey focuses on Mat Su Mid-Air Collision Concerns

A little over a year ago an Alaskan industry/government working group was established to look at the rash of mid-air collisions that occurred in 2011.  To support that effort, AOPA fielded an online survey to hear directly from pilots concerning this topic.  The goal of the survey was to discover what methods pilots used to avoid mi-air collisions, and to find out how often they encountered unsafe conditions while flying in the Mat Su Valley.

The survey was emailed directly to a sample of 2,942 AOPA members who live in Alaska. In addition the Alaska Airmen’s Association, FAA and other aviation groups broadcast the link to the survey through their communication networks.  Over 600 people took the time to respond.  This will help the industry working group focus its efforts as it considers recommending ways to minimize the potential for mid-air collisions.  While that process goes forward over the months ahead, I wanted to share the summary of the survey so that you could see what the cumulative results tell us about how we operate—and what the respondents of this survey had to say regarding this topic. A summary of the survey is available here:   2012_04 Mat Su Valley Collision Avoidance Survey Final Report.    Look for more information in the months ahead as the working group starts to develop recommendations.