Regulations & Safety
Florida Law Limits Use of ADS-B Data for Airport Fees
Florida’s Senate Bill 422 bans airports from using ADS-B data to charge fees to general aviation pilots, effective July 2026.

This article features original AirPro News reporting and analysis based on primary legislative documents.
Florida Governor Ron DeSantis has officially signed Senate Bill 422 into law, establishing new restrictions on how airports within the state can utilize Automatic Dependent Surveillance-Broadcast (ADS-B) data. According to reporting by AVweb, the governor signed the legislation on April 23, 2026, preventing airports from using this safety-critical tracking information to assess and collect fees from general aviation pilots.
Taking effect on July 1, 2026, we view this measure as a major legislative win for aviation privacy and general aviation advocates. By prohibiting the use of ADS-B data as an automated billing mechanism, Florida lawmakers aim to ensure the technology remains dedicated to its primary purpose: enhancing airspace safety and situational awareness.
According to the enrolled bill text published by the Florida Legislature, the new regulations specifically target automated toll-style collections for light aircraft conducting standard operations, such as touch-and-go landings, or simply transiting local airspace.
Key Provisions of Senate Bill 422
Weight and Operational Limits
The protections outlined in SB 422 are specifically tailored to general aviation. The legislative text restricts ADS-B fee collection for aircraft with a gross weight of 12,499 pounds or less. Furthermore, these protections apply to aircraft operating under standard Federal Aviation Administration (FAA) rules, ensuring that private pilots and small flight schools are shielded from automated tracking fees.
Restricted Fee Scenarios
The legislation explicitly outlines the circumstances under which airports are barred from monetizing ADS-B data. Whether the data originates from ADS-B In or ADS-B Out systems, airports cannot use it to calculate, generate, or collect charges from aircraft owners or operators in two specific scenarios.
First, the prohibition applies when a fee would be assessed for a departure or a landing. This explicitly includes touch-and-go landings, which are a fundamental component of flight training. Second, airports cannot charge fees based simply on an aircraft entering a specified radius of the facility’s airspace.
“An airport may not use information broadcast or collected by automatic dependent surveillance-broadcast systems… as a means for calculating, generating, and collecting fees from aircraft owners or operators who operate aircraft within the geographic boundaries of this state,”
the enrolled bill states.
The Broader Push for Aviation Privacy
AirPro News analysis
In our assessment, the enactment of SB 422 in Florida highlights a growing national consensus against the monetization of aviation safety data. ADS-B technology was mandated by the FAA to modernize the national airspace system, providing air traffic controllers and pilots with highly accurate GPS-based positioning to prevent midair collisions. We believe it was never intended to function as a digital cash register for local airport authorities.
Florida’s legislative action aligns with broader industry efforts to protect pilot privacy. In May 2025, Montana became the first state to ban the collection of ADS-B-based fees from most general aviation pilots, according to reporting by GlobalAir.com. Meanwhile, at the federal level, the proposed Pilot and Aircraft Privacy Act (PAPA) has been gaining momentum in Congress. As noted by GlobalAir.com, that federal legislation seeks to prohibit the use of aircraft identification data for profit without explicit permission from the owner or operator.
Aviation advocacy groups have consistently argued that using ADS-B for billing purposes could create perverse incentives, potentially discouraging pilots from utilizing the safety technology to its fullest extent. By passing SB 422, we observe that Florida has reinforced the principle that safety systems should remain strictly focused on safety.
Frequently Asked Questions (FAQ)
What is ADS-B?
Automatic Dependent Surveillance-Broadcast (ADS-B) is an advanced aviation surveillance technology. According to the Florida bill text, it combines an aircraft’s positioning source, avionics, and ground infrastructure to broadcast data such as GPS location, altitude, and ground speed to air traffic control and other aircraft.
When does the new Florida law take effect?
Senate Bill 422 officially takes effect on July 1, 2026.
Which aircraft are protected under SB 422?
The law applies to aircraft with a gross weight of 12,499 pounds or less operating under FAA rules.
Sources
Photo Credit: Miami Airport
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
-
Defense & Military6 days agoWhisper Aero Launches Collaborative Logistics Aircraft for US Military
-
Commercial Aviation5 days agoIATA 2026 Airline Profit Forecast Cut in Half by Fuel Costs
-
MRO & Manufacturing5 days agoGE Aerospace Q1 2026: LEAP Deliveries Up 60%, $170B Backlog
