- Jun 19, 2006
It is years since I helped out with these requests and I have to say again PLEASE make it easy for us by telling is the departure and arrival airports as expertflyer requires these. I can find it out using another tool (in this case FR24) but you already have this info!
Avauilability: J0 R0 D0 I0 W3 P3 Y7 B0 H7 K7 M7 L7 G7 V7 S7 N7 Q7 O7
View attachment 184864
Seatmap as below:
View attachment 184863
The seatmaps will always show more vacant seats than there are tickets available because some people won't be allocated a seat until checkin.Looking at the seatmap and inventory of a QF flight, I am having difficulty understanding how I can best estimate the number of seats available the inventory and the seatmap is telling different storiers
For one flight, I see this inventory with little availability in J, but lots on the seatmaps
Does anyone understand how the relationship between seat maps and inventory works (at least on Qantas)?
The blocked seats (X) are also a bit of a mystery for me, anyone knows how to interperte them on Qantas international?
If you look at a flight such as SYD-LHR which is comprised of multiple sectors it will show you the lowest number of seats available on a component sector.
Because U is hidden from the usual availability search.Is anyone able to explain what seems to be an anomaly in EF showing/not showing QF U bucket availability depending on whether you search for Award & Upgrade Availability or Flight Availability?
They match for X but U is absent from Flight Availability - and it seems to be across all dates into the future that I randomly checked.
See snips below.
View attachment 195800View attachment 195801
There's no need for me to do that, as I can see what I want to see. But (and this answers @esseeeayeenn as well), in the past U would show in Flight Availability. Furthermore, it seems strange that X shows and U doesn't.JohnM, if no response, here, you can also ask ExpertFlyer>FAQ/Help>Contact us. They usually respond fairly quickly.
As esseeeayeenn says, things have changed (recently), and also according to my interaction with EF.