Good question! We will not have the hold page up yet...where you can enter holds wherever you want. Neither will we have procedural hold entry paths drawn (in magenta). That, of course, requires a bit of work depending upon your entry angle. Also, we do not have "abeam points" implemented. We have all the infrastructure in place to implement it...just not enough time. Um....what else......we do not have an 'offset path'. That is more common on oceanic routes and so shouldn't be missed by most. I will say we have designed our code to handle most anything, so we are not in so deep that we can't address whatever a real FMS can do in the future, its just a matter of picking and choosing after 5 years. Our FMS development has gone through some ups and downs (it is our first one) and we are shooting for a high level as we have some catching up to do. That being said, we are really happy with what we have so far. If Jan can conduct a flight with it as normally as he does in the real word...we're in a good spot! We are hoping to get a last video in before release that showcases the FMS features in a real world scenario (you know that Jan ALWAYS has problems on his flights). ...if you're on a Lufthansa flight and the pilot says, "Hallo, I'm your captain Jan Vogel"...get off the plane! So....I've been at it for about 14 hours today and spent the whole day programming in "flight plan loading and saving". We will be implementing our own flight plan format initially, (*.ixg) and it should be available on onlineflightplanner.org at some point. Ideally, we'd like to be able to read in multiple formats, but alas....we have to draw the line for the initial release. At the least, you can save your routes (with some limitations) and can share these text files if you like. We will be providing a "coroutes" folder that holds "company routes" flight plans for the initial release. Ok, back to it, this was just a break to blog about today's work. -tkyler