Advocacy

Topic: Key operational takeaways from the recent FAA Alaska Industry Council discussion

Focus areas: AWOS/AWSS reliability, VWOS/weather camera access, ADS-B, infrastructure outages, DYAASI implementation, and industry feedback opportunities

Executive Summary

FAA Alaska Region leadership provided updates on several aviation infrastructure initiatives affecting air carriers across Alaska, including weather observation systems, ADS-B coverage, outage reporting, dashboard development, and the broader DYAASI effort. The discussion also included extensive industry feedback about the need for better transparency, faster repair timelines, improved communication, and a broader view of infrastructure reliability beyond weather systems alone.

The most important takeaway for operators is that FAA recognizes the operational impact of unreliable or unavailable weather, communications, navigation, lighting, and flight check infrastructure. FAA is working on process improvements, including better outage visibility, a centralized intake process for operator concerns, closer coordination with Technical Operations, and continued engagement through the Alaska Aviation Safety Working Group and Industry Council.

Key Items Air Carriers Should Know

1. ADS-B/SBS update: Galena and Alakanuk moving toward ATC use

The ADS-B office reported that construction is complete at Galena and Alakanuk. Those sites remain in the testing phase, so operators may see intermittent or sporadic activity while testing continues.

FAA expects the sites to be available for use by Anchorage Center in the November/December timeframe, assuming testing is successful.

Operational relevance:

Operators may begin seeing improved surveillance capability in those areas once the systems are fully tested and accepted for ATC use, but they should not assume operational availability until FAA confirms the systems are active.

2. Weather system deployment continues, but timelines remain fluid

FAA provided a 2026 weather system update, including:

• AWOS site planning and deployment work is ongoing.
• FAA has finalized the list of 50 AWOS sites.
• Weather camera and VWOS installations are also underway.
• FAA expects continued deployment work through the calendar year.
• FAA acknowledged that Alaska logistics, weather windows, parts, access, and contractor coordination continue to affect schedules.

FAA emphasized that site lists and deployment schedules can change quickly as logistics and tasking change. FAA is being cautious about publishing information before it is stable.

Operational relevance:

Carriers should expect continued movement on new weather infrastructure, but also should expect deployment timelines to shift. FAA does not want to publish site-level expectations that may change shortly afterward.

3. “Installed” does not always mean “operational”

FAA clarified an important distinction for operators: an AWOS may be physically installed but not yet considered operational for aviation use until Tech Ops has completed its checkout and acceptance process.

For AWOS systems, FAA does not consider the system operational until it has been reviewed and accepted through the appropriate technical process. VWOS and weather cameras are treated differently because Tech Ops does not certify them in the same way.

Operational relevance:

Do not rely on word-of-mouth that a system has been “installed.” Operators should verify whether the data is actually available and usable through FAA-approved or appropriate sources before incorporating it into flight planning or dispatch decisions.

4. VWOS data access is still a major education and dissemination issue

A significant discussion focused on VWOS, weather camera data, and third-party flight planning applications.

Key points raised:

• VWOS data currently appears to be available through the FAA weather camera website.
• Several participants noted that VWOS information may not appear in standard online weather briefings or third-party apps.
• Industry representatives reported that some major third-party app providers were not aware of VWOS until recently.
• FAA intends to bring the VWOS program manager to a future Industry Council meeting, likely in October, to provide more education on the program and how pilots/operators should access and use the data.

Participants emphasized that Alaska pilots increasingly rely on multiple sources for weather information, including FAA sources, third-party apps, weather cameras, and local systems. This creates a risk that pilots may not know where to find all available data or may misunderstand what data is approved or advisory.

Operational relevance:

Operators should ensure pilots and dispatchers understand where VWOS information is available, what its limitations are, and how it differs from METAR-equivalent certified weather. AACA should continue pushing for clear FAA guidance on VWOS use, dissemination, and training.

5. FAA AWOS/ASOS dashboard is available for industry feedback

View the FAA AWOS/ASOS dashboard

FYI: Stations can be filtered and viewed on the Map page.

FAA demonstrated an AWOS/ASOS dashboard that shows weather system status, including:

• In service
• Partially in service
• Out of service
• Federal vs. non-federal systems
• Equipment type
• Associated NOTAM information, where available
• Search and filtering capability, including filtering for Alaska

FAA asked industry members to test the dashboard and provide feedback.

Industry feedback during the meeting included requests for:

• Clear definitions of “partially in service” and “out of service”
• Better visibility into which component is not working
• Separate indicators for communication channel availability, such as internet, phone, VHF, or other access methods
• A way to distinguish automated weather systems from human weather observers
• A duration field showing how long a system has been in partial or full outage
• Export capability for operators or analysts
• Better integration with other dashboards or data sources
• More clarity when multiple systems exist at one location, such as AWOS, SAWRS, VWOS, or weather cameras

FAA indicated that this may be an appropriate project for the Alaska Aviation Safety Working Group to help refine requirements for a future version of the dashboard.

Operational relevance:

This dashboard could become a useful operational awareness tool, but it needs industry input to become truly useful for carriers. Operators should review it and provide specific feedback about what information is needed to support dispatch, flight following, route planning, and operational decision-making.

6. FAA is developing a better process for outage communication

FAA acknowledged that the current process for operator concerns about outages is inconsistent. Operators often email individual FAA leaders directly, which can create delays, duplicated effort, or gaps in visibility.

FAA plans to establish a central email inbox for operator questions and concerns about infrastructure outages. The intent is not to replace existing operational reporting channels, such as ATC or Flight Service, but to create a consistent intake point for questions such as:

• “This system has been out and is affecting our operation. What is the status?”
• “When is this expected to return to service?”
• “Is FAA aware of the operational impact?”
• “Is there a workaround or repair timeline?”

FAA also plans to improve internal coordination with Technical Operations so the Regional Administrator’s office has better daily awareness of new outages, long-term outages, expected return-to-service timelines, and operational impacts.

Operational relevance:

Carriers should continue reporting outages through normal operational channels first, including ATC and Flight Service. The forthcoming central inbox would be for follow-up, visibility, impact reporting, and repair-status questions.

7. FAA heard strong industry concern that weather is only one part of the infrastructure problem

Industry participants emphasized that while weather reporting is critical, operators are also affected by outages or gaps involving:

• Navigation aids
• Communications
• RCOs and RCAGs
• Localizers
• Airport lighting
• Flight checked procedures
• Long-range weather radar
• Flight Service access
• Satellite surveillance and voice capability
• Surface condition and airport infrastructure information

Several participants urged FAA not to limit the broader DYAASI effort to weather systems alone. They stressed that safe operations depend on the full aviation infrastructure system working together.

Operational relevance:

AACA should continue advocating for a broader Alaska aviation infrastructure reliability strategy that includes weather, communications, navigation, airport lighting, flight checks, and data transparency.

8. Senator Sullivan roundtable follow-up: FAA summarized industry recommendations

FAA reviewed takeaways from Senator Sullivan’s recent aviation infrastructure discussion. FAA said the consistent industry message was that infrastructure reliability is fundamental to Alaska aviation operations.

Industry recommendations summarized by FAA included:

• Reduce repair cycle times
• Stage critical spare parts in Alaska
• Consider qualified partners for minor repairs where appropriate
• Develop a real-time weather system dashboard
• Improve data sharing among FAA, Alaska DOT, operators, and industry
• Establish a task force or structured process to explore solutions

FAA generally agreed that transparency, restoration timelines, and operational impact awareness need improvement.

Operational relevance:

AACA members should continue documenting specific operational impacts from infrastructure outages, including cancelled flights, delayed medevacs, missed mail/freight, village access impacts, and avoidable risk exposure.

9. Non-federal partner repairs remain uncertain and sensitive

Operators raised the possibility of allowing qualified local or non-federal personnel to perform simple tasks, such as resets or minor troubleshooting, particularly when FAA technicians cannot reach a site quickly.

FAA’s initial response was cautious. FAA noted that certified systems require appropriate technical oversight, and Tech Ops currently expects to retain responsibility for certified systems. However, FAA leadership agreed to continue discussing whether there may be narrow circumstances where some local assistance could be considered.

Industry representatives emphasized that there is also risk in forcing aircraft, technicians, or communities to wait for a certified technician when a simple issue may be preventing restoration of critical weather data.

Operational relevance:

This remains an unresolved policy and risk-management issue. AACA may want to develop specific examples where limited local action could reduce safety risk without compromising system integrity.

10. Flight check capacity and scheduling remain a major concern

The discussion also highlighted flight check challenges in Alaska. Concerns included:

• Limited flight check availability
• Weather and smoke disrupting flight check schedules
• Lack of predictability about when flight checks will occur
• Airport sponsors not always knowing what must be ready before flight check
• New or improved infrastructure not being usable until checked and published
• Growing demand as more weather, lighting, and approach infrastructure comes online

FAA acknowledged the issue and noted that Alaska Region has been working to expand and better plan flight check windows. Industry and airport sponsors stressed that this process needs more visibility and coordination.

Operational relevance:

Carriers should expect flight check capacity to remain an important bottleneck for new or restored infrastructure. AACA should continue elevating this as a statewide operational issue.

What Member Carriers Should Do Now

AACA recommends member carriers consider the following actions:

• Continue reporting outages through standard operational channels such as ATC or Flight Service.
• Document operational impacts from outages, including cancelled flights, delays, medevac impacts, mail/freight disruptions, and safety concerns.
• Provide feedback on FAA’s AWOS/ASOS dashboard, especially what information dispatchers, pilots, and operations managers need to make decisions.
• Educate pilots and dispatchers on VWOS limitations and access, especially that VWOS may not appear in all standard briefing tools or third-party apps.
• Share specific examples with AACA where FAA infrastructure outages have affected operations, especially long-term outages or cases where repair timelines were unclear.
• Identify locations where communications, lighting, navigation, or flight check issues are creating operational constraints, not just weather reporting gaps.
• Support AACA’s continued advocacy for transparency, faster restoration, spare-parts staging, better data sharing, and practical Alaska-specific solutions.

AACA Advocacy Position Emerging from the Discussion

Based on this discussion, AACA’s continued advocacy should emphasize that Alaska needs:

• Reliable, timely, and accessible aviation weather information
• Transparent outage status and return-to-service estimates
• A broader infrastructure reliability strategy beyond AWOS alone
• Clear guidance on VWOS use and dissemination
• Aviation infrastructure dashboards that are useful to operators, not just internally useful to FAA
• Faster repair cycles and better Alaska-based logistics
• Flight check capacity that matches the pace of infrastructure deployment
• Practical pathways for industry, airport sponsors, and FAA to solve problems collaboratively
• An ongoing DYAASI process that remains a living effort, not a one-time checklist