FAA Moves Away From Floppy Disks in Air Traffic Control Systems

What happened

The US Federal Aviation Administration (FAA) has begun moving away from floppy disks in its air traffic control systems, according to a report from The Register dated 6 November 2026. The change is one step in a broader overhaul of the agency's technology, and the report notes that the FAA will need additional funding to complete the wider programme.

The reporting is brief, so the details of which systems are affected and how the transition will be sequenced are not yet clear from the available coverage. The core development is the shift away from a storage medium that has long been associated with legacy infrastructure, and the funding gap that now sits alongside it.

Why it matters

For public-sector technology leaders, the story is a reminder that modernisation is rarely a single project. Replacing a legacy component, such as the media used to load data or software, often exposes dependencies in surrounding systems, procurement cycles and staff skills. Each of those dependencies shapes how far and how fast an operator can move.

For the people who depend on these systems, the stakes are operational rather than cosmetic. Air traffic control is a service where reliability, speed and clarity of information matter to controllers, pilots and passengers alike. Any transition that touches core systems has to be managed so that the service experience of each group remains stable throughout.

The Renascence take

Most coverage of legacy technology focuses on the obsolete artefact, which makes the story sound like a quaint anecdote. The more useful question is what the funding caveat reveals about how the programme is structured. When a modernisation effort depends on money that has not yet been secured, the timeline is no longer a plan but a hope, and frontline teams are left to work around systems in transition.

Legacy replacement fails less often because of the technology than because of the gap between the roadmap and the budget. The behavioural principle at play is that people build workarounds around whatever they cannot rely on, and those workarounds quietly become the real process. A customer-obsessed operator should map those workarounds before retiring the old system, so the new one is designed around how people actually work. Funding should be tied to the experience milestones that matter, not only to the technical ones.