Case I

Second for mccPILOTLOG

ONLY COSTS $79 ONE TIME FEE - not per year. Been using this for over a year. Does what most of the other programs do. One fee for numerous PC and Androids on ur account (don't kno about Apple products), and they sync each other thru the cloud every time u log in.

It sync's to Flica or CrewWeb to get ur schedule. You can import .csv files from other log programs. Slice and dice ur flt time on numerous reports. Can even print a map with all ur flts on a Google Earth map (not useful, but fun to show non-pilots).

Five93H

I'm thinking of switching to MCC pilot log, but not sure about the way it logs. If it imports minutes and I have display as decimals, it looks like it could lead to a discrepancy in times: Page Totals in my logbook show an error up to 0.2 hours : mccSUPPORT

I'd like to avoid something like that, as up until now I had been converting minutes to rounded down decimals for the purpose of adding it correctly in a logbook. Anyone encountered the same issue?

Case I

Maybe I'm misunderstanding, but not sure that rounding down is formally accepted way to do it. This is what is commonly used:
0-3: .0
4-9: .1
10-15: .2
16-21: .3
22-27: .4
28-33: .5
34-39: .6
40-45: .7
46-51: .8
52-57: .9
58-60: 1.0
When it syncs from CrewWeb etc, it imports clock time, then it converts it to decimal. If u are importing from another program, I believe, it will recognize some program outputs directly, requiring no user intervention.
You can also output your old stuff as a .csv file, then import to mccPilot, specifying "column 1 = PIC," "column 2 = SIC," "column 3 = night time," etc. Then in your mccPilot logbook, those flights' OUT/IN TIME will just show blank, but they will have the other pertinent data imported in decimal form. If you fear error in the time/decimal conversion process, you could just import ur decimal time and leave the clock time blank.

Five93H

I don't mean directly round down, but if you read the link they say that on the logbook, you can get 0.2 and 0.6 to equal 0.9 and not 0.8, want to avoid that.
Ex: 15 mins is 0.2 and 39 mins is 0.6. Add them up, 0.8 but if you do 15+39 you'd get 54, and therefore 0.9. Don't want a logbook at an interview showing something like that.
I guess I'll have to play around and see.

What I do right now is convert minutes to decimal, similar to the scale above. Add them up on a logbook as you do, and that's your time. If you use the internal calculator, you can end up with a discrepancy.

Case I

I read the FAQ, I get it.
Looks like you could probably go back and tickle the out/in times up or down a few minutes on a flt to get it to add up, if u find that issue. A bit painful, but perhaps other programs do this too?

Five93H

Yeah, might as well keep the system I have. A little time consuming compared to download and sync, but it gets the results I'm looking for.

inky13

I would have mccpilotlog import your exact times and have them in the e-log as exact times in minutes. That way there are no issues for rounding errors and your times are precisely what they should be. I use mccpilotlog and log by the minute--anything I've logged outside of airline stuff I will use the rounding method and enter a 1.3 hour flight as 1:18 in mccpilotlog.

By the way, I'm another advocate of mccpilotlog. It may be a foreign based company/software, but they sure have a nice product. And their support is phenomenal! Plus, if you work for a supported airline to sync your stuff, it's a cake walk. Unfortunately, Envoy has antiquated software (DECs) so I can't partake in the sync, but I will log my flights as I go with my phone app, then sync, and even that is very easy to do.

Buy it now while the Euro is low! (It costs 69 Euros for the Enterprise license, which is the one you can sync stuff with multiple devices. Today, that's about $76 US.)

inky13

If you are talking about an interview, then BRING ALL OF YOUR LOGBOOKS! It's fine if you've converted your previously logged time into an e-log and printed it, but make sure you bring your originals too (with all your endorsements/sign-offs).

PermaFo

LogTen user here but I do the exact same... Pre-121 flying is logged as decimals, just as we it read from the Hobbs. All of my 121 flying I input using only out and in times. LogTen computes the difference to minutes, automatically computes Night, and if I were to ever again print my logbooks, I can simply change the preferences to display in decimal (or keep in hour:minute).

FWIW... for my interview I had my logbook printed up, subtle nondescript binder and on the standard green paper. No one said a thing other than... "looks nice" and "your time here matches your application." They hadn't specified what format the logs HAD TO be in. Even then, I had my written logs in the hotel and up to date... JIC

Five93H

I'll have to do that. Fortunately my time is relatively low, so it won't take too long. Downside is my paper logs are all decimal, don't want to scratch anything out, always looks bad. Might have to just use digital from now on. Not like I need any dual signed off...