If you think this is an easy problem to solve, here's an old article that discusses some of the challenges in doing so:

https://medium.com/google-design/google-maps-cb0326d165f5

This screams vibe-coded slop. Think about it, if you were to implement zoom based detail level, you would have to try hard to introduce a bug on line 3, yet it happens to hit prod.

Yet, this thread is full of people defending this pre-alpha quality thing.

Haha I came in to write the exact same thing. Such a weird choice

A select airport view has flight data limited to some x hours, meaning you cannot even see if a flight later in the day is still scheduled to arrive on time without consulting those official pages anyway. So quite objectively no, it's not even objectively worse, it's effectively useless.

Going back to a map view from an airport view resets the map, so exploration for fun is again borderline unusable.

Not sure how they're getting their data, but https://tsa.fromthetraytable.com/

Ideally the TSA at each airport would measure it and release it. They should be measuring it anyway since they should both have efficiency targets for how much of a delay they introduce, and also so that they can show data about how much or little inconvenience they cause when DOGE finally comes to cut one of the actually utterly useless government expenditures.

Since the TSA doesn't seem to be releasing this data though, apple or google could spy on GPS and motion data for individuals to estimate when people entire the line and pass through security, and derive a better-than-nothing estimate. It does seem like the government refusing to do something, and apple/google stepping in and doing a government-like thing is a norm, so even though I'm joking I wouldn't even be that surprised.

the app has so many bugs and missing features, I'm not a heavy user just like 60 flights a year but I love and hate flighty

> Airports desperately need to be displaying accurate information [..]

Airports and airlines may have information that they deliberately do not share with passengers.

For example: a large European airport that I once did some work for ran a trial in which they announced departure boarding gates significantly earlier. The effect was that passengers went to their gates earlier.

The side effect was that retail revenues in the terminal fell during the trial. Yes, this was a metric.

Guess what? They decided not to proceed with announcing departure gates earlier and went back to the previous system.

Yeah, I think that flighty already aggregates various data sources to predict flight delays, I thought maybe they were expanding to include security wait times.