Airline Pilot Forums

Airline Pilot Forums was designed to be a community where working airline pilots can share ideas and information about the aviation field. In the forum you will find information about major and regional airline carriers, career training, interview and job seeker help, finance, and living the airline pilot lifestyle.




View Full Version : Fixing Logbook Errors


2xAGM114
05-23-2015, 12:24 PM
I'm inputting my stuff into Log Ten Pro for airline apps. I'm finding minor errors from six logbooks ago which have been carried forward in totals for subsequent books. I.E., the total of every book afterwards is also off.

From anyone who has done an interview recently or a 141 chief pilot type: is it better to go back and fix every page of every logbook? Or would it be sufficient to make note to the totals page of the most recent book and take it our there?

The specific error is dual received is short 2.4 hours, not the end of the world and probably won't effect a hire/don't hire decision.

Thanks.


JohnBurke
05-23-2015, 12:31 PM
Don't go back and try to fix ever error in place. Go to your current logbook and make a new entry under the current date. Under each column (single engine land, PIC, etc), put the corrected numbers, positive or negative. Perhaps you need to add two tenths of PIC, take away four tenths of multi, add five hours SIC, and reduce your total time by ten hours. Put those values on this single line, then make a note in the remarks that these are corrections to your logbooks to date. If you have enough room, you can cite page numbers.

When you total up the page, the results at the end of the page will be current and correct. When someone reviews your logbook, they're not going to go back and add every page. They're going to look at the last page of the logbook, and they may flip through at read an entry here or there, but that's generally about it. What you're looking for is the neatest, most concise correction you can make; a single line entry that calls no attention to itself is best, and the most professional way of handling the correction.

If you like you can also go to each corrected page and make a small note in the margin that a correction was applies in logbook #, on xx/xx/xxxx.

Any actual corrections in your logbook shouldn't be done by scratching anything out. Your log is a legal document, and should be treated as such. If you do find yourself needing to make a correction to the log anywhere, strike through the item with a single, clean line, and initial it in small letters. Don't use white-out or other correction tape or fluid, or scribble over the error. You can write the correct information next to the lined-out entry.

Shoot for the lowest visibility, most conservative way you can to adjust your log, and avoid doing anything that draws attention to the error.

2xAGM114
05-23-2015, 03:36 PM
Shack. The line entry correction sounds good. Gracias.


JohnBurke
05-23-2015, 04:16 PM
De nada. Buena suerte.

Turbo and Ozone
05-24-2015, 02:14 PM
I just switched from Logbook Pro to Logten Pro X, about 6 months ago, and am amazed at how much easier it is to slice and dice the data any way you want in LTPX. Like you, the switch uncovered many previous errors (missing time entries, missing it inaccurate night time etc)... Wish I had made the switch years ago. For anybody still on LBP, I know there is not much info out there regarding reviews/comparisons, etc, but as a guy who has used both, I'll say that LTPX is head and shoulders above and beyond LBP. It's built in 117, visual representations, smart groups and filters put it in a class of its own. Oh, and it can format the data in airlineapps or pilot credentials format, just like LBP can... Only it does it in a more visually pleasing style. To switch, all you need to do is a simple csv or txt export from LBP and import it into LTPX. Double check the headers, and it will be done in less than 30 minutes (learning time included). Good luck! (Ps, I don't work for either company, just an airline dude who is very impressed with LTPX.)

hooks82
05-27-2015, 05:46 AM
I used the method JohnBurke described. The errors weren't ever mentioned in my interview and I got a CJO.