TODO: if we schedule at a takeoff outside the fetch range, we won't see
our registration (or any other registrations for takeoff). how should we
solve this? we can't really fetch schedule for every takeoff, too much
data (because we have to send data about the empty ones too). rewriting
the protocol will take too much time. we could force takeoff to become a
favourite when scheduling and go back to include favourites when
fetching schedules. that's probably the easiest solution for the time
being, but confusing for the user.
forcing favourite of takeoffs you schedule flights on, including
favourites when fetching schedules
updated list of takeoffs (and incidentally got a corrupted file in the
process, and i got no idea how. it's fixed now, though)