Originally Posted by Verdell

Edge case example I'm curious about:

RES, trip originally ends on a LC day followed by X-days. Reroute (tag-on, legal) on the end of the trip (on an LC-day) that adds a day (additional duty period on X-day) to the trip. The rerouted duty period on that last LC day is "scheduled" to release late that day, but delayed ops carry that duty period beyond midnight and into the next (X) day (but still less than 4 hours past original release.) Then, an additional duty period the next day (on the X-day) to complete the reroute/trip.

Obviously the duty period on the X-day would pay L9. But what does it take for the duty period on the last LC day (the day the reroute began) to pay L9? What if it was scheduled to end duty before midnight, but actually ended duty after midnight (X-day.) Does the LC day reroute duty period ALSO have to be scheduled to extend beyond 4 hours from original release AND infringe an X-day to pay L9? L8 pay doesn't have such a restriction and gets paid on the original last day of the trip even if that duty period didn't exceed >4 hours (scheduled or otherwise.) The reroute itself pushes scheduled release beyond 4 hours by adding a new duty period, and L8 gets triggered.

At the risk of confusing my example above, here are a few more. All for RES, all on last LC day:

1) Tag-on reroute scheduled to release <4 hours and before X-day, actually releases after midnight (into X-day) and < 4 hours after original (I don't think L9 because scheduled <4.)
2) Tag-on reroute scheduled to release <4 hours and before X-day, actually releases after midnight (into X-day) and >4 hours after original (I don't think L9 because scheduled <4.)
3) Tag-on reroute scheduled to release >4 hours and before X-day and after midnight (into X-day.) Actual release.... probably not important (I think actual release is irrelevant for this, it's due L9.)
4) Tag-on reroute scheduled to add additional duty period on X-day well beyond >4 hours, but last LC day is from #1-#3 above.