Recently FlightLogg.in has switched to a more reliable host. The constant downtime and slowness will now hopefully be a thing of the past. Also, some of the software that was being used to run the site has been upgraded, so for the time being email updates, states maps, and RSS feeds have been turned off. Once the site's code has been updated to work with these new versions (hopefully within a week) these features will return.

Hello everyone! As you know, the site was down all day yesterday. The reason for this was that the company that runs the servers that FlightLogg.in' is hosted on shut it down. The reason for this, according to the hosting company, they did this because it had received complaints from people saying the backup emails the site sends out are spam. So if you don't want to get those emails any more, then please go to your preferences and change it there. Don't just mark the emails as spam.

Over the past 3 or so days the site has been kind of up and down. This is because as the site has grown in popularity, search engines are becoming more and more interested in FlightLogg.in's content. Web crawler activity had picked up, which is causing server load to be very high at times. The problem crops up explicitly when the googlebot starts crawling the site's KMZ files, which are quite CPU intensive to render. I have instructed googlebot to back off, so well see...

The automatic backup feature has been slightly modified. Now it only sends you an email if you have edited any part of your logbook during the backup interval. For instance, if you have requested to get an auto email backup sent to you monthly, you will only get an email if you have edited some part of your logbook in the past month.

The FlightLogg.in' Forum has moved. You now no longer need to resister a new account for the forum. The new url is http://flightlogg.in/discussions

UPDATE: Also, if you're wanting a copy if your old FlightLogg.in' data, sending an email to info@flightlogg.in won't work currently as the email system is currently down. Make a forum post instead for the time being.

There has been some recent enhancements to the way FlightLogg.in' handles planes. First off, you can select to make certain planes 'retired'. This means they will no longer show up in the plane dropdown menu on the new flight popup window. This is useful for when a plane gets sold and it no longer comes available to you, or if the plane changes, and therefore a new entry for that tailnumber is required. Instead of having duplicate planes with the same number show up in the dropdown, you can retire the old one so there's only one.

The next addition is the ability to make a plane hidden. This makes all flights in that airplane hidden from FlightLogg.in's site-wide aggregate pages. If you are the owner pilot, and you don't want the flights you log in your own plane to show up, then you can just mark that plane in your 'Planes' section as hidden. All though this will not prevent flights logged in that tailnumber from other people from showing up in those pages.

And the third enhancement is the ability to define a plane's default fuel burn. The fuel burn field on the flight section was originally designed to enter actual, measured fuel burns. The problem was that many users were adding estimated fuel burns in that column when the plane they flew had no way to actually measure the fuel burned for the flight. For instance, people were putting "6 gph" for all flights in a C-172, even though it is unlikely they actually had a measured fuel burn of exactly 6.0 each time.

Now, if the plane does not have a way to measure fuel burn, then it is recommended you enter the estimated fuel burn on the plane section of each tailnumber you fly. This way, all flights you log in that tailnumber will use that default value if no exact fuel burn has been entered on the flight popup. This has the benefit of not making you enter the same value in the new flight popup every time, as well as separating the actual measured fuel burn numbers with estimated fuel burn numbers.

In the fuel burn columns on the logbook page, all estimated fuel burns calculated from the value associated with the plane will be depicted in gray. All measured values that are entered from the flight popup will be depicted in black.

FlightLogg.in' now supports gravatars! You may have noticed a strange monster image in the top left corner. That is your gravatar. If you want to change it, you must go to Gravatar's website, sign up for an account, upload a photo, crop it with their cropping utility, then make sure your flightlogg.in email address matches your gravatar email address. The image is to make it easier to identifiy your logbook from others'.

The colorized states maps were updated today. They are now automatically updated every six hours, instead of you having to manually update them. Also, the corners are transparent, so they look a little better when displayed onto a non-white background. One important thing to note is that the urls for all maps have changed. So if you have one of these images linked somewhere, the image will still work, but it will not be updated anymore.

Over the past few days there has been some improvements to the HTML code which allows for better rendering in older Internet Explorer browsers. So now if, for whatever reason, you're still using IE6 or IE7, you can now log in and use the site. IE6 and IE7 are still not officially supported browsers, so much of the site will still be messed up, but at least you can now sign in and have basic functionality. Browsers that are recommended are Firefox 3.5+, Google Chrome, Opera 9+, and Safari 4.

Now when you open the new flight popup, you'll be greeted with a entry field you've never seen before. Below the remarks box, there is a space to enter a fuel burn value. For details on which units are supported, refer to the help page.