Have signed to to take a look at it tonight, and it does look very promising.
Plain jane look aside (and looks don't matter too much anyway), it's very functional, simple and easy to understand control interfaces, and clean results screen. Also, huge props for clean, semantic and accessible coding techniques - I know the odd blind flyer who is seeking out awards would love you for this.
I also like how previous searches can be easily retrieved, and the table layout is quite reasonable. I would suggest you look at changing the style for your A tags in the table heading on the list page so you don't have blue links atop gray text. THEAD & TBODY tags here for accessibility would also be a plus.
Some initial suggestions for your consideration:
- Switch the Javascript alert dialogue used for bringing up the routing/timing information for something a little less abrupt: Suggest using a lightbox or similar, as users would be more likely to understand they can copy/paste text from there and can degrade gracefully. The lightbox could also be designed to go back and forward to details on the next possible
option for that day.
- Split feedback/help, move tips into the help page: This explains itself, your tips page is essentially help for using the service - yet when people access the help page, this information isn't there.
I've left this next one out of my main list, as it might be a bridge too far - but is it possible or already part of your development plan to be able to see how many points each possible routing would cost with the respective program?
This would require some additional knowledge, such as what programs the person is a member of or which one they intend to use. Doing so if anything would remove one additional user step, by allowing them to define in a profile preferred alliances/carriers on the search/build screen for them without having to select these each time.
Other than that, a brilliant effort - well done. Look forward to seeing how this evolves in the future.