Yet Another Digital Logbook Thread — Except I Built This One

I do admit, I'm continually surprised that people keep using Windows after all of the gross stuff Microsoft does, and the fact that they can't seem to code their way out of a paper bag. My gaming computer constantly nags me about upgrading to windows 11 every few times I boot into windows. I'm waiting for it to just decide to install without my consent one of these days.

Granted, Linux is pretty frustrating lately, too.

MacOS is sorta the last tolerable desktop I can recommend, unless you're a weird hax0r like me. (posix, *nix, reasonable desktop environment, no vibe coding, support reasonable standards, don't spyware you, don't inject ads into your OS, don't install updates without consent, etc.)
 
Ian_J said:
You're right, you're right... I'm getting there eventually!
Click to expand...

Ian - not an immediate need, but you might wanna talk to Larry over at FC View. His app - which talks to FLICA for scheduling, has a terrific feature that exports your schedule to LogTenPro.

For me, and everyone else who uses FLICA (which, yes is going away eventually) it means I never have to load anything. When my schedule updates, I just touch the button in FC View that says send to LogTen and everything drops in there. Kind of like what you are doing with CCS.

You might get some user uptake if you can work with Larry to get Flica to export to blue deck.
 
Oh thank you…. I’ll have to give this a try…

I’ve been using APDL for 15 years which exports logbook stuff to Logbook pro which is what I’ve used for my logbook for the last 25 years.

Well APDL just ate all of the data for my 32-day trip and I lost tail numbers OOOI times and PF/PM/IRP legs for the last trip I was on and I’m finding it hard to get flight times and tail numbers from my airline and I’m too cheap to pay flight radar $2 for tail numbers older than 7 days but less than 30 days ago.

I’m up to date on my electronic logbook in logbook pro for everything except for this trip I’m currently on day 23 of 32. So I’ve lost 23 days worth of flight information that I’m finding very hard to reconstruct…



So that is the last straw for APDL. Plus APDL is 117 only and always flags my flights as illegal.. yeah they’re 117 illegal. But they’re 121 supplemental legal….

Right now I’m writing it down tail numbers and OOOI times in Google Sheets until I figure out a new logbook program

I just downloaded a trial of logten pro. But I’m more pissed about reconstructing my last 22 days of flying… and how useless my airline is in providing access to the info I need to reconstruct it.
 
@Ian_J Fantastic man, thanks for putting the effort into this.

For someone who hasn’t kept their logbook up to date in about 2 years and with all the CCS+ “features” the co has implemented over the last several months, is there a quick way to import our flights over?
 
Nicely done @Ian_J, seriously! Looks like a very nice UI at first glance, something I'd be very interested in.

As a current LogTen user, I shall keep an eye out for future iOS/Mac versions. Personally, I log each leg during trips via my phone then it syncs to my Mac which I don't use a ton but it's kinda nice having both.

Keep up the good work!
 
Sculprit said:
@Ian_J Fantastic man, thanks for putting the effort into this.

For someone who hasn’t kept their logbook up to date in about 2 years and with all the CCS+ “features” the co has implemented over the last several months, is there a quick way to import our flights over?
Click to expand...
Yes—and two years is actually the sweet spot. CCS+ keeps roughly two years in its Logbook, and Blue Deck can import the whole CSV in one shot.

Go to CCS+ → Training and Qualifications → Logbook, export the CSV, and import that into Blue Deck. That’ll build most of the logbook and handle the deadheads. Then paste in Flight Time History to fill in the aircraft, seat, flight time and landings. After that, Calendar Sync makes it pretty painless to keep current.

Not quite one click, but a hell of a lot easier than entering two years by hand.
 
killbilly said:
Ian - not an immediate need, but you might wanna talk to Larry over at FC View. His app - which talks to FLICA for scheduling, has a terrific feature that exports your schedule to LogTenPro.

For me, and everyone else who uses FLICA (which, yes is going away eventually) it means I never have to load anything. When my schedule updates, I just touch the button in FC View that says send to LogTen and everything drops in there. Kind of like what you are doing with CCS.

You might get some user uptake if you can work with Larry to get Flica to export to blue deck.
Click to expand...
Much appreciated! Thanks!

Edit - yeah thanks to you I just discovered Logten has an API i can plug right into Blue Deck. Much appreciated!
 
Last edited:
woodreau said:
Oh thank you…. I’ll have to give this a try…

I’ve been using APDL for 15 years which exports logbook stuff to Logbook pro which is what I’ve used for my logbook for the last 25 years.

Well APDL just ate all of the data for my 32-day trip and I lost tail numbers OOOI times and PF/PM/IRP legs for the last trip I was on and I’m finding it hard to get flight times and tail numbers from my airline and I’m too cheap to pay flight radar $2 for tail numbers older than 7 days but less than 30 days ago.

I’m up to date on my electronic logbook in logbook pro for everything except for this trip I’m currently on day 23 of 32. So I’ve lost 23 days worth of flight information that I’m finding very hard to reconstruct…



So that is the last straw for APDL. Plus APDL is 117 only and always flags my flights as illegal.. yeah they’re 117 illegal. But they’re 121 supplemental legal….

Right now I’m writing it down tail numbers and OOOI times in Google Sheets until I figure out a new logbook program

I just downloaded a trial of logten pro. But I’m more pissed about reconstructing my last 22 days of flying… and how useless my airline is in providing access to the info I need to reconstruct it.
Click to expand...
That sucks, man - I had a similar thing with CrewLounge that motivated me to build this. Yeah, please try the demo and if you find a feature you need I'll build it in just days if it's feasible to do.

It sounds like you actually have two separate issues — reconstructing the 22/23 days APDL lost, and finding something to replace APDL going forward. Blue Deck can definitely be the logbook side of the second problem, but I don't want to oversell the first one. If your airline has any source you can still get for those flights — schedule export, flight history, spreadsheet, PDF, whatever — send me an example and I'll take a look at whether Blue Deck can use it to help reconstruct the trip. If the data simply isn't available from the airline anymore, unfortunately Blue Deck can't recreate information that isn't there.

Going forward, though, if you're already writing the tail numbers and OOOI times into Google Sheets, Blue Deck can import that kind of data, and I'd be interested in seeing what your airline provides because airline-specific import support is exactly the kind of thing I'm building around.
 
Last edited:
You must log in or register to reply here.
Back
Top