Well I think I figured out why my LTP report was making the margin on the bottom so large. I log all my landings during one flight day as one line, since I do so many. Some days I do 12 landings or more. When you put all those under the Route of Flight section (under the "To" column) it will make it go quite wide if there are a bunch of destinations, and by default it will NOT "wrap" around to make a new line. This would be a great feature if it could. In fact, on the Jeppesen report it just cuts it off completely, and doesn't expand the column much (it has a fixed limit), so you only see a few destinations under the "To" section, which is no good either. At least for the Coradine report, when it widens that column, it forces the table to get wider, but it keeps the same number of rows, which in turn makes the whole table height shorter, creating the large white space at the bottom. This affects both sides of the pages, since the rows need to stay aligned.
So the moral of the story is, if you're like me and you log all your day's flights in one line, but you have lots of landings (I had one day with 19 landings in a day, all point to point stuff, not just patterns), it will screw with your logbook when it's time to make a report. A better solution for the LTP engineers if you're reading this is to force the line to wrap around once it reaches a pre-determined column width, and just make the row taller. For me it's not practical to log each flight on a separate line with the short legs we do. I have over 6000 landings but not yet 4000 hours which would make my logbook a silly number of pages if I logged it each flight a separate line. YMMV
