mccPILOTLOG requires each flight sector to be logged as a separate record in the database.  Contrary to some other logbooks, you cannot log a single record for multiple flights, such as ORD-JFK-MIA-JFK.


While ROUTE logging is time saving, it substantially increases the risk of making entry errors, like ORD-JKF-MIA-JFK 


Furthermore, a lot of valuable knowhow remains stuck in your database and cannot be deployed to reports and statistics…


Logging each flight as a separate record from A to B, allows mccPILOTLOG to validating your entries. The software will detect and report invalid entries, such as 4.0 hours for a flight from JFK to MIA (this throws up a message “the average flight time on this route is 3.0 hours”) or 2.0 hours (“your average ground speed is too high”)…


The airfield name turns red when you enter a code of an airfield where you have never been before, e.g. you accidentally enter LAZ (an airfield in Brasil) instead of LAX…


Logging by ROUTE doesn’t reveal these kinds of errors and it does not allow for statistics on average flight time between two airfields, average fuel consumption or passenger load.


Logging each flight leg as a separate record may seem cumbersome. mccPILOTLOG offers many built-in features to facilitate your entries, such as automatic flight number recognition, automatic return / triangular flight suggestion and automatic flight roster import from over 250 airlines worldwide…