Frequently asked questions

Where do you get your data, dude?
The theAirDb is a project aiming for a unify clustered data as flights from different airlines, and everybody is welcome to add its contribution, in terms of suggestion, develop work, donations, etc.
The data collection is performed in two ways:
1) Website scraping for low cost carriers.
2) IATA SSIM file for majors that collaborates with us and send us periodically the data (the same file they provide periodically to IATA for scheduling).
Believe it or not for some airlines the web page scraping is more up to date, and sometimes bring us some exclusive sneak.
On the other side, it is fair to say that for airlines that lowcost that provide connections, we have not so good data, as they tend to sell every city to every city via one of their hub. We tend to only publish direct routes, but for those airlines we don't have a choice. Some examples are Air Lingus, Dragonair, Air Berlin.
The list of airlines we maintain is in bold at airlines list
For some airlines that are neither low cost (so don't exposes data directly on their website), or that didn't get in touch with us to provide their collaboration, we don't have any data.
The position of this airport is wrong, can you please fix it?
Sure, but can you please pass us the correct coordinate of the airport? To find those, you can use various tools on the Internet, as for example this one where you can double click on the map to get the coordinate of any point
What technology is used in theAirDB?
The underlying technology resides in framework written in a OO language that is hooked up to a DB. When you connect to theAirDB, you don't connect to this DB though. We infact create static HTML pages as soon as some data changes in the DB so to produce what it looks like static pages on the web (similarly to what IMDB does). This results in a faster data transfer as everything is static.
We also uses mySQL and PHP for the frontend API (yes we have some!), although those are not documented (yet)
OK, you guys rock, but what the hell is this "Hub Attitude" on the airline pages?
Hub attitude is something we come up with, not even Google knows about it!.
The idea is that if an airline is pure hub and spoke (so from one airport connect all others, and no other route is present), then its hub attitude is 100%. If the airline a pure network connected grapgh (so from each airport, you fly directly to all the other airports), then your hub attitude is 0%. In few words is the attitute of an airlines to have most of the flights originating from one (or few) airports. The algorithm to calculate this is somehow complicate as it is basically a measure of how totally connected is the graph.
Of course this works like a charm for airline for which we have no-stop flight only data. For the airlines for which we have mixed direct and connecting routes, our published hub attitude has got a value that is much lower than in the reality, because our engine is fooled to think that secondary airports are directly connected.