Frontier IT can't display my future flights
 

Does anyone at Frontier even care how bad their IT is? I've had to use their app to keep track of my future reservations -- their website has, for months, failed to display them -- but now the app is a mess, too. It's recently been leaving off my next trip and then when it displays my future trips, it includes my original reservations, and then separate listings for the new flight times when Frontier has changed my flights. :rolleyes:

F9 IT is an absolute mess. Old or missing itineraries, randomly "forgetting" my KTN, inconsistent behavior between the app and website, etc. All the things you mentioned OP happen to me also.

Airline IT in general just isn't that great. It's viewed as a cost to be minimized rather than a source of competitive advantage. Airlines also just can't afford to compete for top-tier IT and CS talent, so it's usually outsourced to the lowest bidder.

I guess it depends on what you call IT. The customer-facing stuff (website, app), sure, it's not always super amazing. But come on, the back-end IT to run an airline (scheduling, routing), even a LCC like Frontier, is pretty intense. Some airlines (Southwest) have underinvestd for years, and occasionally you see meltdowns (Christmas 2023). But it's actually pretty incredible just how much self-serve you can do on United's website, for example.

Me too. It's so weird to log in and expect to see a flight coming up in a week or two and, instead, see something from 2022 where that flight should be. Forgetting the KTN seems to be new, though, at least for me. Either way, it's definitely happening.

Agreed the app is terrible. But a workaround is to search for your flight last name and confirmation code and it will show up in the app again.

Out of curiosity, does ANYONE'S future flights now display when signed on to Frontier's website? I remain irritated by this, but since their app generally keeps track of my flights (with some glitches), it's not the end of the world. I've just adjusted to doing business that way.

Working fine for me. They actually finally fixed it on Chrome after years of it being broken.

Amazing. I'm using Chrome. :confused: