FAA to Retire Floppy Disks in Air Traffic Control Systems by 2028

What happened

The US Federal Aviation Administration plans to eliminate floppy disks from its air traffic control information systems by 2028, according to TechRadar. The effort would replace outdated systems across more than 400 American air traffic facilities.

The timeline is the headline detail. Completing the work is expected to take until 2028, which reflects the scale of replacing legacy infrastructure spread across hundreds of sites rather than a single switch-over. The reporting frames the change as an attempt to retire a storage format that has lingered in operational systems that cannot easily be taken offline.

Why it matters

For a national air traffic network, the story is less about nostalgia than about operational resilience. Legacy storage and data-handling methods limit how quickly systems can be updated, integrated and maintained. Modernising these information systems is the groundwork that determines whether later capabilities, such as better data sharing, automation and analytics, can be adopted at all.

It also illustrates a wider pattern in public-sector digital transformation. Large, distributed operations must replace infrastructure facility by facility, so the experience of controllers, engineers and ultimately passengers depends on sequencing, training and continuity while old and new systems run side by side. Each site becomes its own change programme, with its own risks and its own staff.

By the numbers

• 400+ American air traffic facilities covered by the replacement of outdated information systems.
• 2028 target year for eliminating floppy disks from these systems.

The Renascence take

The headline will draw smiles, but the floppy disk is a symptom rather than the story. The real signal is that legacy operational technology persists until a deadline forces its replacement, and the workarounds built around it quietly shape how people do their jobs for years.

Most readers will miss that the hard part is not buying new hardware but changing the work around it. Experience teams should map where staff currently compensate for old systems, including the manual steps, duplicated checks and tribal knowledge, before cutover begins. Treat the 2028 date as a service-design project rather than an IT milestone, and measure success by how controllers and users work, not by how many machines have been retired.