Wow. Your commitment to customers and your taking immediate action based on customer feedback is impressive. You will go far.


This is an interesting way of doing things; airlines make up configuration-specific aircraft codes all the time, so you're bound to be always missing some. Plus, the way it's currently implemented, you're still not showing the pertinent information: a query on the site made right now for the seatmap of the above flight shows a label of "Aircraft: Boeing 777", yet there is no subtype (which is what is of interest here, since the seats are a generation apart from other subtypes). Wouldn't it be far simpler to simply pass through the 3-letter code on the non-mobile site as well, such as "Aircraft: 77C (Boeing 777)" (or, in case you don't have it in your database, simply "Aircraft: 77C")?

The problem, as it is, is not solved!

This is very inefficient way of doing things; if you want to keep a database of all airline-specific non-IATA configuration-specific aircraft codes, you probably shouldn't rely on the small percentage of customers that care enough to let you know when you miss one. A more scalable way is to have your system email customer service whenever it finds that an airline has returned a code that is not in the database, so that customer service can research what it is and update the database thusly minimizing the amount of incorrect/missing data you're displaying to customer. Case in point, the BA-77C code has been in use for at least a month (if not more) and you're fixing your database only now, with much delay.