![]() |
|||||||||
| Home | Profiles | Blog | Reports | About |
|
How do you come up with the predictions?
How far out do your predictions go? We look out four to five months.
How often are the models updated? We refresh our historical data monthly. However, we may fine tune our models where we see performance gaps, so updates can come at any time.
Why do I get a prediction for a time where an airline does not have, and has never had actual flights? We designed our models to extract
patterns about
carriers and airports, rather than specific flights. In this way we can
predict
a broad range of possible flights without being subject to the
constantly
evolving carrier schedules. We hope to cover as many possible flight
segments
and times as we can. On the day I fly there may be weather which can cause substantial delays, yet you don't take the weather forecast into account. These are planning tools which show you that, even before the effect of weather and mechanical problems, you may be at a disadvantage. In short, these are the predictions of delays before those factors even kick in.
How is this better than the historical flight performance statistics I get at my travel site? There are several differences.
My flight was on-time but you said it would be so many minutes late. What gives? Hopefully you will be on-time most of the time! The prediction of your delay length in minutes assumes your flight is delayed in the first place. See the predictions called “chance you your flight departing/arriving on-time.” Many flights do make it on-time, but if they don’t, the minutes delayed section tells you what to expect in terms of the length of the delay. Bear in mind, too, that these are estimates. Sometimes your flight will be on time even if we say it has only a 20% chance, and sometimes the delay will be 60 minutes even if we predicted 40. And always be aware that other factors such as weather may further delay your flight beyond our so-called “base expected delay” prediction.
Why is there a difference between the departure and arrival predictions for a flight segment/time I am considering? There will almost always be some difference. Here are several reasons for the gap:
If you see what you believe to be a large discrepancy, email us.
What airports and airlines do you cover? We currently make departure and arrival predictions for the top 60 airports. We track the following airlines:
Can you add my airport/airline to the list? We may expand beyond the current set after our beta period, depending on how solid we can get our predictions at smaller airports where fewer data points are available.
How good are the models? Good enough to aid decision making. That is the purpose. Frankly, we believe our model provide the most accurate forecast of flight delays available anywhere. That said, remember that models are representations of reality they are never exactly accurate. In our reviews, we are within 15 minutes 80 - 90% of the time. (If carriers were within 15 minutes of their published schedule 80-90% of the time, there would be no demand for Delaycast, or Congressional hearings.) Of course that varies by airport. We are constantly refining, so as time goes by we expect our forecasts to improve.
Can I purchase large chunks of your prediction data? Yes. Please email us your anticipated usage volume and application as well as your interest in widgets, APIs or hosted OLAP data.
Can you predict how long it will take me to get through security on the day/time of my flight? We feel your pain. We are working on it.
Who are you guys? We are analytical professionals who spend a lot of time waiting in airports and on tarmacs. We originally developed mental models to help us cope with travel woes and to set realistic expectations about our own travel. One of us actually kept a little travel log of data to run simple statistical models predicting the expected arrival times of his flights. After some conversations and the statisticians' equivalent of a few jam sessions, we came up with some amazingly solid models. From that, Delaycast was born and taken to a large scale. Mostly, we just like solving some of life's problems with big data sets, elegant equations, and brawny computers. We formed Delaycast, Inc to make this application available to as many people as possible.
|
|