Not exactly. Here's the problem: The iPad version is different, and less flexible, than the Mac version that you took that screenshot from. And I only have an iPad, don't plan on getting a Mac.

On top of that, all the "How Tos" on their website and in the website knowledgebases say that the tracking I wanna do CAN be done. Well, maybe it can on a Mac, but that level of functionality doesn't go as deep in the iPad version. And there's no "How To" for what I need to do from an iPad frame of reference. In fact, Jay's already told me that the iPad version won't do what I want it to do correctly.

Here's the thing: When I go into the LTP setup and tell it that my main role is a commercial pilot, then it should automatically set up the "Radar" screen to track the things that will keep me legal and I therefore care about the most: 1400 hours per calendar year limit, 800 hours in two consecutive calendar quarters limit, 500 hours in a calendar quarter limit, 10 hours flight time in a rolling 24 hour period, and 14 hours of duty in a rolling 24-hour period. These are the things I need to monitor every day on the line.

For what it costs, that should happen automatically, so I can get to work and not spend days trying to figure out how to make it do what I want it to do. I BOUGHT it because the literature said it WOULD do what I need it to do. If there were a trial period, I would have NOT bought it when I figured out that it doesn't work for 135 pilots without a whole lot of thrash, but I didn't have a choice because Coradine doesn't do "try before you buy."

I shouldn't have to set up all those things manually and continually update the current dates in the Limit Group setups to make them work. The new "Start Date" and "End Date" fields in the Limits Group setup make it less painful than it used to be, but it's a piece of computer software, it should be able to do what I'm asking without any trouble at all.

So, I did go in and create those calendar year and quarterly limit groups. Other than having to go in and reset the dates at the appropriate times, they work fine and display the correct number of hours remaining in their respective fields on the Radar screen.

Set up the rolling flight and duty time limits too. The 10 in a rolling 24 hour flight time limit group I set up displays fine on the Radar screen, because there's a "Sched Total" Criteria field I can use when I set it up, it properly looks back 12 hours and forward 12 hours, grabs the time I've already flown, adds the time I've planned to fly tomorrow, and correctly calculates and displays the hours I have left to give. All is well.

The 14 in a rolling 24 hour duty time limit group, though, doesn't work right, I believe because there is no "Sched Total Duty" Criteria in the Limit Group setup like there is for flight time. It can look back and see what yesterday's duty was, but can't properly look forward at my planned duty. Because of that, it doesn't correctly calculate the duty time I have left to give when I enter my next day's projected schedule in the logbook. That's critical for me in my current job, because I'm far more likely to be tight (or over) on duty time than on flying time. I know the information is IN THERE because it tracks my planned rest and duty with the progress bar display in the upper left corner of the Radar screen--I just can't access that info to set up a Limit Group.

Then there's the visual duty limit tracking graphical display. Works OK for the quarterly limits, other than the vertical current day marker is way too far to the right side. The flight and duty limit graphs don't work right at all. The flight time one displays correctly, but the duty time one does not: the hours burned and remaining don't match the Radar screen, and the flight and duty time graphs look identical--they shouldn't.

I've posted on the website and corresponded with Jay, sent him all this info, screenshots, detailed descriptions like this, etc. His response was he'd have his guys look at it. That was many months and more than one update ago. I think wt93205 hit the nail on the head--they don't quite understand what we (Part 135 pilots, anyway) actually need in our crosscheck with respect to time tracking and what we don't.

For example, I'd personally like to delete the "Last 7/28 Days" and "6/12 Months" entries in the upper left of the Radar screen if I could because that's info I don't need or use on a daily basis. I can make a smart group for that if I want it. But I CAN'T delete it to make more room for something I DO use on a daily basis because it's hard-coded to show up there.

Like I said, if it was free, I'd be inclined to work around its limitations. But it's not. For $80 or so, it should be ready to do what I need it to do out of the box. And I think that after I've explained what I need as a 135 pilot in excruciating detail more than once, that Coradine should be a little more responsive, since it's marketed toward 121 AND 135 pilots and I couldn't test drive it before I plunked down my money.

Don't get me wrong, there's a lot I like about this program and I intend to keep it and hope that Coradine makes it more 135-friendly. What I'm asking for here may sound like a lot, but the tweaks to make this much more usable should be straightforward. I don't think that's too much to ask for my money.