FloridaAirports cannot use aircraft tracking data to charge certain fees
Airports cannot use aircraft tracking data for certain flight fees in Florida when aircraft have gross weights up to 12,499 pounds and operate under federal Part 91 rules.
What it does
For aircraft with gross weights up to 12,499 pounds operating under federal Part 91 flight rules in Florida, airports cannot use aircraft tracking data to charge departure, landing, or airport airspace entry fees.
Argument forOwners of covered aircraft could receive fewer automatic landing bills because airports cannot use aircraft tracking system data to generate them.
Argument againstAirports may need other ways to track billable flights, which could make calculating and collecting these fees harder.
More detail
Airports cannot use aircraft tracking system data to calculate, generate, or collect fees for departures, landings, or entering a set radius around the airport. The restriction covers owners and operators flying within Florida with aircraft whose gross weight is no more than 12,499 pounds and that operate under federal Part 91 flight rules. The restriction covers information broadcast or collected by either service of the aircraft tracking system. Covered landings include touching down and taking off again without stopping or leaving the runway. The restriction took effect July 1, 2026.
Where do you stand?
Choose your position
Tell your reps
Take a position to see your representatives and ways to contact them.
Where it stands
- Introduced
- Passed Senate
- Passed House
- To Governor
- Became Law
Looking ahead
No hearings or votes scheduled.
History
- 2026
- Apr 24Chapter No. 2026-47Latest
- Apr 23Approved by Governor Ron DeSantisBecame Law
- Apr 21Signed by Officers and presented to GovernorTo Governor
- Mar 17Ordered enrolledMinor
- Mar 10CS passed; YEAS 108, NAYS 2Passed House
- Vote recorded Passage, Third Reading. Result: pass.Lower
- Mar 10Read 3rd timeMinor
- Mar 10Added to Third Reading Calendar
- Mar 10Read 2nd timeMinor
- Mar 91st Reading (Committee Substitute 2)Minor
- Mar 9Bill added to Special Order Calendar (3/10/2026)
- Mar 9Bill referred to House Calendar
- Feb 19In Messages
- Vote recorded Third Reading. Result: pass.Upper
- Feb 19Immediately certified
- Feb 19CS passed; YEAS 36 NAYS 2Passed Senate
- Feb 19Read 3rd timeMinor
- Feb 19Read 2nd timeMinor
- Feb 18Placed on Special Order Calendar, 02/19/26
- Feb 18Placed on Calendar, on 2nd reading
- Feb 17Favorable by- Rules; YEAS 24 NAYS 0Minor
- Vote recorded Favorable. Result: pass.Upper
- Feb 12On Committee agenda-- Rules, 02/17/26, 12:00 pm, 412 Knott Building
- Feb 10CS/CS by Commerce and Tourism read 1st time
- Feb 5Now in Rules
- Feb 4Pending reference review under Rule 4.7(2) - (Committee Substitute)
- Vote recorded Favorable with Committee Substitute. Result: pass.Upper
- Feb 4CS by Transportation read 1st time
- Feb 4CS/CS by Commerce and Tourism; YEAS 7 NAYS 1
- Jan 30On Committee agenda-- Commerce and Tourism, 02/04/26, 10:30 am, 110 Senate Building
- Jan 29Now in Commerce and Tourism
- Jan 29Pending reference review under Rule 4.7(2) - (Committee Substitute)
- Jan 27CS by Transportation; YEAS 9 NAYS 0
- Vote recorded Favorable with Committee Substitute. Result: pass.Upper
- Jan 22On Committee agenda-- Transportation, 01/27/26, 1:00 pm, 37 Senate Building
- Jan 13IntroducedMinor
- 2025
- Nov 17Referred to Transportation; Commerce and Tourism; RulesMinor
- Nov 6FiledIntroduced
Transportation