Regulations & Safety
FAA Retires Century-Old FSS Radio Networks for Digital Shift
The FAA phases out legacy aviation radio systems as digital tools replace 99% of voice requests, with Alaska exempted due to operational demands.

The End of an Era: FAA’s Plan to Retire FSS Radio Networks
For over a century, Flight Service Stations (FSS) have served as aviation’s communication backbone, providing weather updates, flight planning assistance, and emergency support. From their origins as airmail radio stations in 1920 to their peak during World War II, these networks once handled 22,000 daily requests. Today, the FAA proposes shutting down this legacy system as radio calls have plummeted 99% since the 1980s – a move signaling aviation’s irreversible shift to digital solutions.
This transition reflects broader industry trends where only 300 daily radio requests now trickle through a network that once required 3,000 specialists. As pilots increasingly rely on mobile apps and internet briefings, maintaining 936 radio frequencies across three U.S. territories appears increasingly impractical. However, the plan raises questions about emergency preparedness and equitable access for pilots without modern technology.
From Vital Network to Obsolete Infrastructure
The FSS system’s decline mirrors aviation’s technological evolution. During the 1940s, 4,000 personnel manned stations critical for wartime operations. By 1960, the newly formed FAA standardized these into 350 Flight Service Stations. The system peaked during the 1980s jet age, when controllers used teletype machines and “Q” code shorthand to manage 22 million annual pilot interactions.
Three key factors drove the decline: the 1995 introduction of DUATS computer briefings, smartphone weather apps post-2010, and automated flight planning tools. By 2025, 98% of weather briefings are projected to occur digitally through platforms like 1800wxbrief.com. “We’ve seen voice requests drop from 800/hour to less than 13,” notes an FAA report, highlighting the network’s underutilization.
“From over 350 stations with 3,000 employees in 1985 to just two facilities with 200 specialists today – the math no longer justifies the $14 million annual maintenance cost.” – FAA Notice of Intent
Modernization Challenges and Solutions
The FAA’s VoIP transition plan faces technical and operational hurdles. While 93% of pilots now carry internet-connected devices, remote areas like Montana’s Glacier Park still rely on radio for mountain weather updates. The agency proposes shifting emergency monitoring to ATC centers, but some question response times without dedicated FSS operators.
Alaska’s exemption underscores regional disparities. With 80% of U.S. air taxi operations and limited cellular coverage, the state’s 54 FSS frequencies remain vital. Elsewhere, contract providers like Leidos will manage the transition through web portals and automated phone systems. However, 17% of GA pilots over 65 still prefer voice communication, suggesting phased training will be crucial.
Future of Aviation Communication
The FSS phaseout accelerates aviation’s digital transformation but requires careful implementation. While reducing redundant systems could save $200 million through 2030, the FAA must ensure backup protocols for cyber outages. Recent NOTAM system failures highlight the risks of over-reliance on digital infrastructure.
Emerging technologies like satellite-based ADS-B and AI weather prediction could fill service gaps. However, as the 2025 NBAA convention will discuss, balancing innovation with accessibility remains key. The industry watches closely – this transition may blueprint how agencies modernize other legacy systems like VOR navigation networks.
FAQ
Why is Alaska exempt from the FSS radio shutdown?
Alaska retains FSS due to unique operational needs – limited cellular coverage, extreme weather, and high air taxi traffic require reliable voice communication.
What replaces radio-based flight services?
Pilots now use 1800wxbrief.com for digital briefings, mobile apps for real-time weather, and automated phone systems. Emergency calls route through ATC frequencies.
How will this affect aviation safety?
The FAA claims enhanced safety through more accurate digital tools, though some pilots worry about losing human expertise during complex weather scenarios.
Sources: AVweb, FAA History, ATCA History
Photo Credit: flyinginfairbanks
[mc4wp_form id=1060]
Regulations & Safety
FAA Investigates Southwest Airlines Ground Collision at PVD
Two Southwest Boeing 737s collided during pushback at Rhode Island T.F. Green Airport on June 11, 2026. FAA investigation opened.

This is a developing story. Information may change as official details are released.
This article summarizes reporting by WPRI, NBC 10, Daily Voice, and CBS News Baltimore.
The Federal Aviation Administration (FAA) has opened an investigation after two Southwest Airlines Boeing 737 aircraft collided during pushback at Rhode Island T.F. Green International Airport (PVD) late on June 11, 2026.
The ground collision resulted in no reported injuries but forced the cancellation of both flights and the grounding of the involved aircraft for mandatory safety inspections. According to reporting by the Daily Voice and NBC 10, the incident highlights ongoing operational challenges on airport ramps, occurring just weeks after a similar event involving the same carrier at another East Coast facility.
Details of the ground collision
At approximately 10:45 p.m. local time, Southwest Airlines Flight 3515, bound for Ronald Reagan Washington National Airport (DCA), was pushing back from its gate. During the maneuver, the aircraft’s wing made contact with the tail of Southwest Airlines Flight 3409, which was scheduled to depart for Chicago Midway International Airport (MDW).
Both aircraft returned to their respective gates following the contact, allowing passengers to deplane normally. Southwest Airlines confirmed that no injuries occurred among passengers or crew members. The carrier subsequently canceled both flights and reaccommodated the affected travelers.
“Southwest Airlines is aware of an incident involving two of our aircraft at Rhode Island T. F. Green International Airport. We are investigating further and will be thoroughly inspecting the two aircraft,”
the airline stated in remarks provided to local media, adding that safety remains its highest priority.
Local media outlets, including NBC 10, reported passenger accounts suggesting that Flight 3515 continued to move briefly after the initial impact. These accounts claim passengers verbally alerted the flight crew to the collision. Neither Southwest Airlines nor the FAA has officially verified these specific passenger narratives, and the official sequence of events remains under investigation.
Regulatory response and recent precedent
The FAA confirmed on June 12, 2026, that it is investigating the circumstances surrounding the collision. Ground operations during pushback rely heavily on coordination between flight crews and ground personnel, particularly in ramp areas where air traffic controllers do not maintain direct communication with the aircraft.
This event follows a comparable occurrence on May 4, 2026, at Baltimore/Washington International Thurgood Marshall Airport (BWI). In that instance, two Southwest Airlines Boeing 737s clipped wings during pushback operations. The FAA investigated the BWI incident, noting the specific communication dynamics between ground crews and the flight deck in non-controlled ramp sectors.
AirPro News analysis
We note that while ground collisions during pushback rarely pose a severe threat to passenger safety, they represent a significant operational and financial burden for carriers. Ramp incidents require immediate grounding of the involved airframes, triggering mandatory structural inspections and potential repairs. The recurrence of pushback-related contact within a single airline’s network over a short period may prompt internal reviews of ground handling procedures, wingwalker positioning, and ramp communication protocols. Until the FAA concludes its investigation, the specific cause of the PVD collision remains undetermined.
Sources: WPRI
Photo Credit: Zachary Reis
Regulations & Safety
Turkish Airlines 777-300ER Wing Strike at Antalya Airport
A Turkish Airlines Boeing 777-300ER struck a radar antenna pole taxiing at Antalya Airport, prompting evacuation and a formal investigation.

This is a developing story. Information may change as official details are released.
This article summarizes reporting by Hürriyet.
A Turkish Airlines (TK) Boeing 777-300ER sustained damage and prompted a passenger evacuation after its right wing struck a ground radar antenna pole while taxiing at Antalya Airport (AYT) on June 11, 2026.
The incident, which occurred at approximately 20:00 local time following Flight TK2430 from Istanbul, resulted in minor injuries among the passengers. According to official statements reported by Hürriyet, the widebody aircraft was maneuvering toward its parking position on Apron-1 when the collision occurred, leading to an immediate evacuation on the tarmac.
Conflicting passenger and injury reports
Following the evacuation, official sources provided conflicting figures regarding the number of passengers on board and the extent of injuries. In a public statement, Turkish Airlines Senior Vice President of Communications Yahya Üstün confirmed the evacuation, stating that 267 passengers were safely removed from the aircraft. The airline reported that one passenger sustained minor injuries and was in good health.
Conversely, the Turkey Ministry of Transport released a separate statement indicating a higher passenger count. The ministry reported that the aircraft was carrying 284 adult passengers and four infants. Furthermore, the government authority stated that three passengers suffered minor injuries during the event. Both entities confirmed that the aircraft, registered as TC-LKD, was towed to a parking area after the necessary safety checks and passenger removal were completed.
Investigation into the ground collision
A technical investigation into the ground collision has been initiated by the Turkey Ministry of Transport and the General Directorate of State Airports Authority (DHMI). The official cause of the incident remains under investigation.
While the airline noted the aircraft was approaching its parking position, preliminary remarks from the Ministry of Transport suggested the Boeing 777-300ER made contact with the radar pole after entering an incorrect taxiway line. Final determinations regarding the aircraft routing, ground control instructions, and the sequence of events will be established by the investigating authorities.
AirPro News analysis
Ground collisions involving widebody aircraft like the Boeing 777-300ER often highlight the tight tolerances required when maneuvering large airframes around airport infrastructure. While we await the official investigation findings, safety reviews following such events typically examine airport taxiway markings, lighting, and the clarity of ground control communications. The discrepancy in passenger manifests between the operator and the regulator is a notable detail, though initial reporting conflicts frequently occur in the immediate aftermath of an evacuation before final reconciliations are completed.
Sources: X.com
Photo Credit: X
Regulations & Safety
NTSB Final Report: Southwest Flight 4273 Turbulence Encounter
NTSB cites ATC communication delays and sector overload in Southwest Airlines turbulence event over Gulf of Mexico.

This is original reporting and analysis by AirPro News.
The National Transportation Safety Board (NTSB) has released its final report on a severe turbulence encounter involving a Southwest Airlines Boeing 737-700, detailing how rapidly developing convective weather and air traffic control communication delays factored into an event that seriously injured two people.
The April 3, 2024, incident aboard Southwest Airlines Flight 4273 over the Gulf of Mexico highlights the operational risks when severe weather systems intersect with technical limitations at air traffic control facilities. According to the NTSB investigation, the aircraft was navigating complex weather en route from New Orleans to Orlando when the encounter occurred, resulting in serious injuries to one flight attendant and one passenger, alongside minor injuries to a second flight attendant.
Weather conditions and the turbulence encounter
Flight 4273, operated by a Boeing 737-700 (registration N567WN) with 140 passengers and five crew members on board, was traveling from Louis Armstrong New Orleans International Airport (MSY) to Orlando International Airport (MCO).
At 11:55 UTC, a Convective Significant Meteorological Information (SIGMET) advisory was issued for the region, warning of cloud tops exceeding 45,000 feet.
At approximately 08:20 Eastern Daylight Time, the aircraft encountered severe turbulence over the Gulf of Mexico. The NTSB confirmed the aircraft itself sustained no damage during the event and the flight crew was able to continue the flight.
Air traffic control workload and technical limitations
The NTSB report outlines compounding factors at the Jacksonville Air Route Traffic Control Center (JAX ARTCC) that affected the flight routing through the weather system.
During the incident, the specific JAX ARTCC sector was managing a traffic volume that exceeded its target capacity of 20 aircraft.
This high workload was exacerbated by a technical limitation involving the facility communication infrastructure. The primary VHF antenna at JAX ARTCC had been rendered inoperative following a fire in October 2023. As a result, controllers were utilizing a temporary satellite relay connection to communicate with aircraft in the sector.
The NTSB determined this satellite relay introduced a 600-millisecond round-trip transmission delay, complicating timely communication between controllers and flight crews navigating the dynamic weather environment.
AirPro News analysis
We note that the findings in this final report underscore a critical vulnerability in the National Airspace System. When primary communication infrastructure fails, the fallback systems must be robust enough to handle high-stress, time-critical scenarios like severe convective weather deviation. A 600-millisecond delay might seem negligible in routine operations, but in a saturated sector where controllers are issuing rapid heading changes to keep aircraft clear of building storm cells, that latency degrades situational awareness and increases the risk of weather encounters. The NTSB documentation of this technical shortfall will likely prompt further scrutiny of contingency communication systems at major en route centers.
Photo Credit: NTSB
-
Technology & Innovation2 days agoAirbus Vision Landing Application Enables AI Autoland
-
Route Development5 days agoDubai International Airport to Close in 2035 for Al Maktoum
-
Commercial Aviation5 days agoIATA 2026 Airline Profit Forecast Cut in Half by Fuel Costs
-
Defense & Military6 days agoWhisper Aero Launches Collaborative Logistics Aircraft for US Military
-
MRO & Manufacturing6 days agoGE Aerospace Q1 2026: LEAP Deliveries Up 60%, $170B Backlog
