ExpertFlyer beta program - April 2025

[themaiz]

Flight avails from BNE to SYD for tomorrow are cactus, but my saved seat queries seem to be OK, and the future flight seat maps that I checked on QF match what QF is telling me (ooh, ah: F is almost empty on my flight!). Kevrosmith: temporary problem maybe?

 

[whughes3]

Flight avails from BNE to SYD for tomorrow are cactus, but my saved seat queries seem to be OK, and the future flight seat maps that I checked on QF match what QF is telling me (ooh, ah: F is almost empty on my flight!). Kevrosmith: temporary problem maybe?

For a while yesterday it was not showing any QF flights at all in flight availability, This seems to have been fixed,

 

[dajop]

One thing I used to like about EF is it showed exit row and bulkhead seats as blocked on SQ if they weren't occupied. After the recent downgrade to the site, it now just shows them as occupied, regardless of whether they are or not. i.e. shows as occupied even though on the SQ website they are available (for free for us, due to status, or for purchase without status), before the downgrade it would have showed them as blocked.

Not sure if other tools are available for this, apart from doing dummy bookings for individual flights on the SQ website.

 

[themaiz]

One thing I used to like about EF is it showed exit row and bulkhead seats as blocked on SQ if they weren't occupied. After the recent downgrade to the site, it now just shows them as occupied, regardless of whether they are or not. i.e. shows as occupied even though on the SQ website they are available (for free for us, due to status, or for purchase without status), before the downgrade it would have showed them as blocked.

Not sure if other tools are available for this, apart from doing dummy bookings for individual flights on the SQ website.

I don't know whether I'd call it a downgrade. There have been changes for sure, but some parts of EF work better. I've found recently that seating maps sometimes work and sometimes don't (eg as in: you're told it's not possible to display seats for that flight).

With QF mostly the seating map works, and it largely maps what QF shows. However I get the impression that QF masks some info on its own site (eg: what you might see as avails if you're SG or WP). Combining the QF and EF views is illuminating. ATM seating for my Monday flight matches in both sites, but QF shows front row as unavailable where EF shows the seats as blocked. Both claims might be true, since QF doesn't distinguish between "above your grade" and "there's a body in the seat".

My guess is that SQ does similar things with their website compared to EF.

 

[kevrosmith]

One thing I used to like about EF is it showed exit row and bulkhead seats as blocked on SQ if they weren't occupied. After the recent downgrade to the site, it now just shows them as occupied, regardless of whether they are or not. i.e. shows as occupied even though on the SQ website they are available (for free for us, due to status, or for purchase without status), before the downgrade it would have showed them as blocked.

Not sure if other tools are available for this, apart from doing dummy bookings for individual flights on the SQ website.

You could always log this as feedback - they’ve been reasonably goodish at responding to issues when ppl log them comparing before and after functionality.