As a pilot for UPS Airlines, I would like to renew a longstanding request for some BASIC support for Part 91 calculations in APDL. I understand that full support for Part 91 operations might require a large reprogramming effort that NC Software is apparently not interested in investing in, but I believe some BASIC improved support would be very easy to program.
I have two wish-list requests. First, simply show the scheduled and/or actual time between scheduled flights AND duty periods. Scheduled time between flights (within a duty period) is already calculated, while scheduled time between duty periods in a pairing is already available in the imported data, or it can be easily calculated, yet currently shows as "Rest: NA." I don't care if APDL won't tell me if the break is legal; at least just show me the time between flights.
Second, don't divide duty periods by calendar date--this currently often makes the APDL display make it look like I only have one or two flights in a duty period when in fact I really have more. Part 91 cargo ops typically fly at night, with a single duty period very often spanning two calendar dates. The solution is simple--look at the time between all flights from my first request. If this time is less than 8 hours, then assume the flights are part of the same duty period. If the time is more than 8 hours, then assume the flights are part of different duty periods, and APDL can group flights into separate duty periods accordingly.
I have been an APDL customer since 2005, but without further basic support for Part 91 ops, I'm going to be looking at other alternatives to the very expensive APDL. This support would be FAR more beneficial than the all the latest minor software updates, to a large number of pilots in the only growing segment of the industry.
I have two wish-list requests. First, simply show the scheduled and/or actual time between scheduled flights AND duty periods. Scheduled time between flights (within a duty period) is already calculated, while scheduled time between duty periods in a pairing is already available in the imported data, or it can be easily calculated, yet currently shows as "Rest: NA." I don't care if APDL won't tell me if the break is legal; at least just show me the time between flights.
Second, don't divide duty periods by calendar date--this currently often makes the APDL display make it look like I only have one or two flights in a duty period when in fact I really have more. Part 91 cargo ops typically fly at night, with a single duty period very often spanning two calendar dates. The solution is simple--look at the time between all flights from my first request. If this time is less than 8 hours, then assume the flights are part of the same duty period. If the time is more than 8 hours, then assume the flights are part of different duty periods, and APDL can group flights into separate duty periods accordingly.
I have been an APDL customer since 2005, but without further basic support for Part 91 ops, I'm going to be looking at other alternatives to the very expensive APDL. This support would be FAR more beneficial than the all the latest minor software updates, to a large number of pilots in the only growing segment of the industry.