Dauntless Aviation
FAA Written Test Prep
Checkride Oral Exam Prep
Pilot Logbook Software
Aircraft Systems Reviews
EASA Theory Exam Prep
UK PPL/IMC Theory Prep
Aircraft Recognition Tutor
SimPlates IFR Plates
FAR/AIM Reference
More Aviation Software
Aviation Freebies
Free Aircraft Checklists
Affiliates and Resellers

Safelog Pilot Logbook Software Safelog LogByEmail Dauntless Aviation

Welcome to Safelog LogByEmail!

LogByEmail is a revolutionary feature developed by the Safelog Pilot Logbook system team.  It allows you to log a flight and/or to receive your logbook information by email simply by sending a specially formatted email to log@safelogweb.com. Any flights logged will be synchronized with your Safelog electronic pilot logbook.  While in theory this can be done from any email client (such as logging in to your GMail, Hotmail, Yahoo, or work email account as usual from a PC or Mac), in practice this system is optimized for users of email-capable mobile phones and PDAs such as iPhones, BlackBerries, Symbian devices, and so on.  Basically, if you can compose, receive, and send emails from your device, then you should be able to log via LogByEmail!

Click here to see a video to learn more about LogByEmail

We strongly recommend that you get this working while sitting next to your desktop PC or Mac before trying to get it working for the first time while “in the field.”

Here’s how it works:

  1. Ensure that the email address that you are going to send FROM is on record with us and that you can log from your device.  To do this, you need to send the “HELLO” command to the LogByEmail system.   Sending commands in the LogByEmail system is done by sending an email to log@safelogweb.com with the command as the subject line.  So, right now, please send a message with only the word HELLO in the subject line (the body can be empty) to log@dauntless-soft.com. Here's an example of sending this HELLO command from a typical Mac email client:
    Email sample HELLO
  2. Once the HELLO command is received, you will receive instructions on verifying your email address if that is indeed necessary to connect you to a Safelog account.  If you are a user of a Safelog desktop PC program, it will be necessary for you have enabled synchronization of your system to our server (the orange arrows on the diagram below) for this to be able to work.
  3. You can now begin using the system.  To begin, we suggest you issue the command “REPORT” to the system.  This will result in you being sent back a summary of your logged flight time.  If this looks to be current and up to date, then the system indeed has your latest information.  If it looks out of date or the data is missing, then you should start your Safelog PC program and allow it to synchronize with the SafelogWeb system.  If you are a user of a desktop computer version of Safelog, it is not possible to use LogByEmail unless either your PC synchronizes with our sever which will be the intermediary between your PC and LogByEmail. Here's an example of the "REPORT" command sent from an iPhone:

  4. If you’re happy with the report, try issuing the “FORM” command.  “FORM” will result in you getting back a specially formatted email “flight form” for you to fill out and send back.  Here’s an abbreviated version of the content of this form as might be typical for an FAA pilot (the actual fields will be customized to your logbook!):

    From: Safelog LogByEmail <log@safelogweb.com>
    Subject: Reply using this form to record a flight

    [AC REGISTRATION][          ]
    [FROM][              ]
    [VIA][    ]
    [TO][     ]
    [PIC][    ]
    [XC][      ]
    [DUAL][                      ]
    [NIGHT][               ]
    [COMMENTS][               ]


  5. Now, to log a flight, click REPLY in your email client and type between the blank [ ]s for each field.  It is very important that you leave the basic formatting of the system in place – it relies on those open and close square brackets to figure out where the data is and what data is in the fields.   It is also vital to remember to leave [FLIGHTSTART] at the beginning and [FLIGHTEND] at the end of each flight.    So, you might start filling out the flight like this:

    To: Safelog LogByEmail <log@safelogweb.com>
    Subject: LOG

    [PIC][4.9 ]
    [XC][4.9  ]
    [DUAL][                      ]
    [NIGHT][               ]
    [COMMENTS][ 2 passengers ]


    You then send this email this back to log@safelogweb.com and your flight will be logged. If you’re a Safelog for PC user, you’ll be able to see this flight the next time you synchronize your PC software.  If you’re a SafelogWeb.com user, this flight will be available via the SafelogWeb. Easy!

  6. That’s it!  That’s the basics of the system. However, there’s a lot of nuance there (you might be having questions like “well, why didn’t I have to put the aircraft type?”).  To help you get the most of this system, be sure to check out the FAQ at the LogByEmail help page. Through this system, you can do a lot, including getting flight time reports and other useful stuff.


Frequently Asked Questions

Q Ok, so why in the example above didn't you enter the aircraft's type?
A Safelog generally will already know about your aircraft's type for your commonly used registrations because you will have already used them in the rest of your logbook. So, all it needs is the registration to match things up. If, on the other hand, this is the first time that you've flown this aircraft, it will be synchronized with Safelog as an aircraft of unknown or unspecified type for you to fill in later while you're at a SafelogWeb or computer interface. This is because it's too much information (given that we'll need to know a bit about the aircraft's characteristics to do useful analysis of it later) to enter productively via the email interface.
Q Will my fields be the same as they are in SafelogWeb / Safelog PC?
A Yes! Though there may be a few small allowances for the limitations of using email on small devices, in general you will be able to do everyday logging in the fields that you have set. When you issue the "FORM" command, the system generates an 'entry form' that is unique to the settings of your particular logbook.
Q Do I need to issue the "FORM" command each time I want to log a flight?
A No. In fact, one thing you can do is this: once you've issued the FORM command once, you will get via email a blank form that you can then 'reply to' as in the example above. In general, there's nothing stopping you from just keeping a single copy of this email in your inbox and doing a 'reply' every time you want to log a flight. That said, you should renew the 'FORM" every so often as we might have changed the format slightly. Certainly you should renew the form every time you make a change to your logbook setup, as your fields may have changed and you want the form to reflect this.
Q Do I need to enter flight times as "4.2" as in the example above?
A No, You can enter them in the format that is comfortable to you. For example, 4:14 if you're used to that. This is no different to Safelog in general - the system is very flexible.
Q What about dates?
A Safelog will suggest a date format for you based on your logbook type and other settings. Fill it in as it is asked. For example, DD/MM/YYYY will typically be asked of European users while MM/DD/YYYY of FAA/USA users.
Q What about monetary currency fields?
A Yes, Safelog allows you to enter these. Simply enter them as you'd expect to, but remember that Safelog supports only one currency per user to keep accounts consistent. So, for example, you can enter "$43.50" or "43.50" and Safelog will record it properly, but if you enter "€43.50", Safelog will record this as $43.50 if your system currency is set to US dollars.
Q How do I log a flight with multiple stops?
A If you have a VIA field enabled for your flight route, break up intermediate stops by putting a symbol that you normally use in your logbook(the one from your 'Route via' setup section) otherwise system will assume you are using dash or column between them (so we use a dash in the example above, but don't mix the separators).
Q Do I log airports using their ICAO, IATA, or FAA field identifiers?
A ICAO is always best, since this is more or less worldwide unique (we'd love to say that it is 100% unique, but, alas,ICAO isn't perfect). Of course, not all airports have ICAO identifiers.
Q What is the [RECEIPT][N] thing in the example above?
A If you want a confirmation email sent after you've successfully logged this flight, change this to "Y." If you get a new "FORM", then this value will be set to whatever you last requested for future use. Note that if you try to log a flight and there is an error, you will ALWAYS get this back via email along with, as much as the system can, a note telling you what it can not understand.
Q What are those [FLIGHTSTART] and [FLIGHTEND] sections for?
A Those tell the system where your flight data for a given flight begin and end. They are VITAL for logging flights. If you leave them out or modify them, the flight will not be logged. That said, if you want to be clever about it, you can use this to log multiple flights in the same email. Consider this:
To: Safelog LogByEmail <log@safelogweb.com>
Subject: LOG

[PIC][1:13 ]


Yes, this will indeed work in logging two flights in one email. Nice, eh? This will be particularly useful as we expand this system in the near future to cover whole duty periods in a natural way.
QWhen I press "Reply", my email client adds a bunch of nonsense on the left side like so:
To: Safelog LogByEmail <log@safelogweb.com>
Subject: LOG

> [DATE][21/21/2011]
> [TO][EDFH]
> [PIC][2:34 ]

A That's ok! There's no need to remove it. That's why we have this system of these square brackets - the system only reads what's in the square brackets.
Q What about extra spaces in the entry? Such as [KSFO    ] for San Fransisco?
A The system ignores empty spaces in such cases, so don't worry too much if your system's cursor is in 'insert' mode where you add a few extra. This applies to all the fields.
Q Is there anything I can't write in the more freeform 'comments' fields?
A You should avoid using a square bracket in the middle of the comments field, but if you feel you have to, than they should be balanced. For example:

[Comments][Two passengers [John and Mary]], had an extra baggage.]

', had an extra baggage.' will be ignored since you have unbalanced ']' square bracket following 'Mary]'. While it might work in some cases, a more sensible solution is to simply use round parentheses for (John and Mary) and thus not allowing the system to get confused. Also remember that you shouldn't use a square bracket in the middle of all other fields, except 'Comments'.
Q What should the subject line be for my logged flights?
A It doesn't matter. Or, more specifically, this is what the system does when it reads an email:
  • First, it looks in the body of your message to see if there are any [FLIGHTSTART] ... [FLIGHTEND] sections and it processes them sequentially.
  • If there were no errors in processing any logged flights, then it:
    • Sends you a receipt for the logged flights, if requested ([RECEIPT][Y])
    • Processes the subject line as a command.
  • However, if there were errors in the processing of your flight, then
    • It will send you an email indicating you of your error.
    • The subject line 'command' will not be processed.

What does this mean in practice? Well, for one, look at the subject line of our examples above. It was "LOG". LOG is not a valid command in our system - this is just a dummy subject line that will be ignored by our system. We recommend putting this since some email systems don't like it if you try to send a message with no subject, but as far as we're concerned it doesn't really matter.

However, let's say you did something like this:

To: Safelog LogByEmail <log@safelogweb.com>
Subject: REPORT 30D

> [DATE][Jan 12 2011]
> [TO][ZBAA]
> [PIC][3.2]

What you are basically telling the system is "Log my flight from Haneda Airport in Tokyo to Beijing Capital airport and send me a summary report of my last 30 days." (As you will learn later, "REPORT 30D" is a command for the last 30 days of reports). If this flight is logged successfully, this is what you'll get. This is a quick way to send one email and get two results, though if you're more cautious you might just send separate emails for these requests. There are pluses and minuses either way. Let's say you sent separate requests in quick succession and there was an error in your input. Well, in that case the 30D report will come, but it will be missing this flight and you might get confused (of course, you will also get an error message email). On the other hand, by sending the report request separately, you are at least guaranteed to get a report, even if it doesn't include this last flight.

Q What if I try to log multiple flights in one email and only one of them has an error?
A Only flights that have errors will be rejected and sent back to you (with an explanation of the error, if the system can in fact deduce it). Flights that have no errors will be logged, but if there were some with errors, then subject line will not be processed.
Q Will I get a response instantly or within a few minutes?
A Often yes, but not always. The system works on a queue basis. If the system is busy because of many complicated requests, it may take some time. The only exception to this is "HELLO" commands, which are processed as soon as possible. You can check system status by issuing a "HELLO" command. This is mostly a "fire and forget" system - send your email and then don't worry about it, though understand that it may take a bit of time to get a response.
Q Can I make as many requests as I want?
A Probably. For most users this won't be an issue, but we do make an upper limit on how many requests we'll handle. This is because, as you might imagine, it would be quite simple for us to overwhelm our server with thousands of requests for complex reports using some automated email-sending system. If you don't do this sort of wacky stuff, you should be just fine. If you start doing too many in a given time period, the system will generally warn you first before it cuts you off, but we can't guarantee this.
Q The email I sent to log@safelogweb.com bounced.
A You probably misspelled it. Check it again. That said, if you're sure something's up, first have a look to make sure you can send email elsewhere to make sure it's not a general problem with your email system. If the problem persists, contact us via our helpdesk.
Q I want to send emails using non-English characters.
A This system is designed around the standard 26-character English character set. If you want to use other characters, there is a nonzero chance that you will get the usual sort of system issues that you've doubtlessly run into in the past with such things. While we do as best as we can, remember that the problem is particularly difficult here since we're dealing with email system that use a billion different encoding schemes. For best results, just stick with the tried and true English letters. Or, just try it and see if it works for you - you never know.
Q I logged a flight but it didn't show up instantly in my Safelog for PC software. What's going on?
A First, remember that your email goes to our server. So, you need to sync your PC software with our server to get the latest data. Second, know that incoming emails go into a queue on our server and are worked on as system load allows. This system load can be a bit intense at times, especially if people are requesting many reports or other analysis features. So, it could be that your email is in the queue.
Q I'm worried that somebody can log a flight as me by faking my email address.
A Really? You must have made some really strange enemy for somebody to dislike you enough to go to all the trouble to do this rather involved mischief. No, really. We've thought about this every which way and have discussed it in our circle of users and we can't really see it being an issue. If it ever is, we'll deal with it then.
Q I guess you're right, but what about people seeing my flight data?
A Remember, when you request reports and other things from this system, Safelog will reply to YOUR email address. So, even if somebody were to go to a heck of a lot of trouble to make an email appear to be coming from you even if it wasn't, they wouldn't get the reply, since it would go to your real email address. And, if somebody gets access to your real email address, well, then you've got larger problems than somebody seeing your logbook. If you for example lost your iPhone or BlackBerry and are concerned that somebody is accessing your email, contact us via our helpdesk and we'll probably recommend that you remove that email address from your account.
Q I sent you a note when I logged a flight...
A No, no you didn't! Anything you send to log@safelogweb.com will be handled by the automated system. Outside of occasional maintenance-related observation, no human will ever see this. If you put something there that the system does not understand, it will simply ignore it and effectively delete it. If you want to contact us, please see our helpdesk.
Q I can't get something to work...
A No problem - contact us via our helpdesk and we'll be happy to help. However, we can help you best if and only if you provides EXAMPLES of what you are trying to do.



Command Reference

  • Send commands to the system by typing them in the SUBJECT LINE of your emails to log@safelogweb.com
  • ONLY ONE COMMAND per email! If you try to send more than one at a time, either only the first one will be processed or you'll get an error. Please not that something like 'HELP REPORTS' counts as one command.
  • We list all the commands in UPPERCASE, but it doesn't really matter if you do the same. Our system will capitalize all subject lines.
  • For all reports, you can also specify PDF or HTML at the end. This will cause the report to be delivered to your email in PDF or HTML format, when available. Not all reports are available in all formats, however, those formats may look nicer.



"HELP" gives you a basic list of the other commands you can use in the system.

The basic system commands are:

  • HELLO - tells you about system status and lets you know the relationship between the account that you just sent email from and the Safelog system.
  • FORM - returns a flight log form for you to fill out.
  • REPORT - returns a report of flight times
  • APPROACH - returns a report of IFR (and visual) approaches
  • CURRENCY - returns a report of flight time and other status as compared to regulatory requirements or custom currencies set elsewhere in the Safelog system.
  • MEDICAL - returns a status report on your medical certificates
  • CHECKRIDE - for FAA users, returns a report of how their aeronautical experience compares to FAA minima for various practical tests
  • FLIGHTS - returns a list of recent flights logged
  • AIRCRAFT - returns a list of your database of aircraft
  • TYPES - returns a list of your aircraft types

To find out more about any one of these, issue a HELP command on any of the above. For example, "HELP REPORT" to find out about the available reports.

It is also possible to get help on SOME but by no means all of the fields in the various fields. For example, "HELP TO" for help with the "TO" field in a log form.



Hello tells you about system status. This command is better experienced that explained. To experience it, send a blank email to log@safelogweb.com with the subject line of "HELLO". Whatever is returned to you should be self explanatory. If not, please contact us via our helpdesk and try to describe the issue as best as you can.


FORM causes a blank flight log form to be emailed to you that mimics your logbook settings in Safelog. You fill out the form and email it back to log@safelogweb.com.

Most of the time, you will want to call "FORM" without any arguments, simply as "FORM." However, "FORM" also supports a few options.


Send either one of the two above, and your form will come back asking for dates in the requested format. Furthermore, this tells the system that any subsequent emailed log data that you send should be sent in this format.

  • FORM EDIT1234

Send something like "FORM EDIT1234" and this tells the system that you want to edit flight 1234. Notice that there is no space between "EDIT" and "1234" - it's simply "EDIT1234". Where do you get this number 1234 from? You get it from doing the FLIGHTS command.

If you try to edit a flight that does not exist or that you don't have access to for whatever reason, you will get an error message.

You should be acutely aware of what you are doing if you try to edit a flight via email. Remember that emails are handled by our system in a queue - usually immediately, but not always.



Use the "report" feature to request summary reporting data of your flight times. Remember that any such data will only be current as of whatever has been processed at the server at that point. That means, for example, if you have yet unsynchronized flights on your Safelog PC copy, they will not show up in the reports.

The simplest and perhaps most useful report is provided by simply sending the command report:


This will actually be more than sufficient for a great many things. However, the system is a bit more powerful. The first thing you can do it specify a time period: WHEN SPECIFYING DATES, REMEMBER THAT THE BASE DATE WILL BE THE SYSTEM DATE, WHICH MAY BE DAY OFF YOUR LOCAL DATE DUE TO TIME ZONE ISSUES.

  • REPORT ALL - is actually the same as "REPORT." Requests your flight data over all its dates.
  • REPORT YTD -since January 1 of the current year, inclusive
  • REPORT MTD- since the first of the current month, inclusive.
  • REPORT 1Y - in the past 1 year. You can also do 2Y, 3Y, etc.
  • REPORT 7M - in the past 7 months.
  • REPORT 6CM - in the past 6 CALENDAR months as defined per the FAA 'Calendar Month' system.
  • REPORT 28D - in the past 28 days
  • REPORT MAR - this or the previous March.  Months can be one of JAN, FEB, MAR, APR, MAY, JUN, JUL, AUG, SEP, OCT, NOV, DEC.
  • REPORT JAN2008 - January 1 through 31, 2008. Notice no space between “JAN” and “2008”.
  • REPORT 2009 - January 1 through Dec 31, 2009

You can also add the modifiers PDF or HTML to your email to receive your report in PDF or HTML formats. These may be more convenient or easier to read

  • REPORT 2004 PDF



APPROACH (can also be entered as APC or APPROACHES) provides a listing of your recorded approaches. Generally, these will be instrument approaches, but if you have explicitly logged visual approaches, those can be shown too.

The simplest way to do this is to specify simple


This gets you a list of your approaches by default WITHIN THE LAST 6 CALENDAR MONTHS. We chose this as a default since otherwise providing you with all approaches may be too much while 6 calendar months is a common need for FAA pilots.

You can also explicitly specify the period you are interested in by using the same modifiers that can be used with REPORTs. For example:


Please see the HELP documentation for REPORTs to learn more about this. You can also use the PDF and HTML modifiers as you see above.



The FLIGHTS command returns a list of logged flights. Due to the inherent limitations of email, the returned lists will have certain limitations, but in a pinch you can use this feature to find some particular information that you are looking for. Note that the output of this command is not particularly pretty compared to the various print and display features found in the main Safelog products, so we suggest you use those if you can.


returns a list by default of the list of flights in the last 10 days in chronological order. You can also sort this by a date range by using the same date modifiers from the REPORT command. For example:

  • FLIGHTS 2009



This provides a quick view of your currency status. This is only available based on the present time.

  • CURRENCY FAA - General FAA currency Status. Mostly useful for FAA pilots only. Also provides medical certificate information, though not as much as the MEDICAL command does. Appends any custom currency information you have in the system.
  • CURRENCY 135 - Your flight time with regards to FAA CFR 14 Part 135 Limits. Only useful for FAA pilots
  • CURRENCY 121 - Your flight time with regards to FAA CFR 14 Part 121 Limits..Only useful for FAA pilots.
  • CURRENCY JAA - Your flight time with regards to certain JAA limits. Also provides medical certificate information though not as much as the MEDICAL command does. Appends any custom currency information you have in the system.
  • CURRENCY CUSTOM - Only any custom currency limits you have set in in the system.



This provides a status report on your medical certificates in the system. You can not update this information via email, but you can view it.

To: Safelog LogByEmail <log@safelogweb.com>
Subject: MEDICAL
From: Safelog LogByEmail <log@safelogweb.com>
Subject: Here is your requested MEDICAL CERTIFICATE INFORMATION

You hold an FAA 3rd Class Medical Certificate. The examination date was June 1, 2010. ....



CHECKRIDE provides you with a snapshot of your logged flight time against FAA aeronautical experience requirements for various FAA practical tests. This is ONLY useful if you are logging your flight in an FAA-style logbook.

To request one of these checkride readiness analysis reports, enter the command exactly as written. Note that 'SINGLE' is for single-engined airplanes, 'MULTI' is for multi-engine airplanes, and "HELI' is for helicopters.




The TYPES command returns a list of the various aircraft types which you have logged flights for.

A typical result is something like this.

To: Safelog LogByEmail <log@safelogweb.com>
Subject: TYPES
From: Safelog LogByEmail <log@safelogweb.com>
Subject: Here is your requested AIRCRAFT TYPE LIST

Airbus A340 (A340)
Airbus A380 (A380)
Boeing 787 (B787)
Cessna 150 (C150)
Cessna 172 (C172)
Cessna 177 (C177)
Lockheed SR71 BlackBird (SR71)
Piper PA-28-161 Warrior (P28A)



The AIRCRAFT command returns a list of the various aircraft registrations that you have flown in, broken down by types which you have logged flights for.

A typical result is something like this.

To: Safelog LogByEmail <log@safelogweb.com>
From: Safelog LogByEmail <log@safelogweb.com>
Subject: Here is your requested AIRCRAFT LIST

Airbus A340 (A340)
Airbus A380 (A380)
Boeing 787 (B787)
   N814TW N144CP JA-5105
Cessna 150 (C150)



Expert Tips and Tricks

Here are a few tips and tricks that are for experts. These tricks require experimentation and are not guaranteed.


FLIGHTDATE. - when entering dates in the system, you can use the words TODAY and YESTERDAY when logging flights. This saves you trying to remember what day it is! For example:


Now the question in this international world, is "what is today?" here's where it gets interesting in the world of the Internet. Basically, IF your email system appends a "Date sent" or equivalent field to the emails it sends, we will use that. In many cases, this will be fine. However, in some cases either that is not sent, or it is sent in "GMT Date" format rather than "Local Date". So, for example, if you're in Hawaii, the system might effectively send "Tomorrow's" date instead of today's, and if you're in Japan it might send yesterday's date. Our system will do its best, but we urge you to experiment and monitor things for a while until you are comfortable with how "TODAY" and "YESTERDAY" work on your system. Often, this is tied to things that your Internet Service Provider (ISP) appends to your emails without you knowing.


What we have written elsewhere states that you can only log the aircraft registration and that you must go back in Safelog PC or Safelog Web to fill in that aircraft's details later. This is not entirely true. You can do a few tricks if you're careful.

Let's say you're flying a new aircraft that you have never logged a flight in before. This will be one of two sorts: a type that you have flown before and a type that you have not.

Let's first assume that you have already plenty of time in Cessna 172s but want to log a flight in N172CN which you have just flown for the first time. To do this, you need to know the "short code" as you have defined C172 in your logbook. You can find this out by using the TYPES command. Let's say that in your logbook, the "short name" for a Cessna 172 is C172. You can then log the flight like this:


That is, after the registration you place a COLON and then the short form. If you make a typo and this short form doesn't actually exist in the system, it will be added as "Unknown Manufacturer", leaving you to clean things up manually later.

The other possibility is that your flight was in a type that you've never flown before. Such as, for example, let's say you lucky dog got yourself a flight in N51P, a P-51D Mustang. You can log this as such:

[AC REGISTRATION] [N51P:North American:P-51D]

That is, after the registration, you can add a colon (:) followed by the manufacturer's name followed by another colon followed by the aircraft type. If you do this, it will place these properly. However, you must still later go in and set the aircraft's characteristics manually - for example, telling the system that this is a single-engine, reciprocating, complex, tailwheel, warbird land airplane. If you don't do this, the system will not be able to do intelligent analysis of your time, and you'll be wondering why time is missing here and there.

So - if it sees ONE COLON, it thinks you are entering a type that you already logged. Two colons and it generally acts as if you're entering a new type. That also said, it will try to EXACTLY match up the manufacturer and type that you entered with what you have already in your logbook, you know, just in case you happened to have flown a North American P-51D before but just forgot.