The calculation you want to do can be done if you apply the following steps:
1. If your ObjectID sort does not match the sequential order of the trip, use the Sort tool to create a replacement feature class that matches the sequence of the trip point order. If you must maintain the original feature class, first add a Long field to the original feature class and calculate the original non-ordered ObjectIDs into that field so they will be preserved in a new feature class, and then create a new feature class using the Sort tool.
2. Now that your ObjectIDs are sorted, add a Long field and calculate the ObjectID values plus 1 into the field ([OBJECTID] + 1).
3. Create a copy of the feature class with feature class to feature class tool.
4. Join the original ObjectID of the first sorted feature class to the ObjectID +1 field in the copy.
5. Calculate the fields you want to using formulas that use the differences between the record you are calculating and the record joined to it, which will be the previous point in the trip sequence.
6. To make the joined feature class point to the point after the records you are calculating, recalculate the ObjectID+1 field in the copy to be OBjectID - 1. Now your join links the records you are calculating to the data of the point that follows it.
7. Perform the calculations you need that need data from the point after the point records you are calculating.
8. Break the join. If you can replace the original feature class or your original feature class was already sorted correctly, you are done. If you need to transfer the data back to the original non-ordered point feature class, do a Join on the original ObjectID to the field in the sorted feature class that holds the static copy of that ObjectID and do calculations to transfer the data from the joined records into the original and then you will be done.
Note: Using cursors and dictionaries is much faster than using the field calculator if you have a large number of points in your trips and many fields that need to be calculated, since a cursor can operate on all of the fields in a single pass, while the field calculator will repeatedly have to do a complete pass on all of the points for each and every field you need to calculate, and join calculations are slower than loading and reading a dictionary to do the point matching and data transfer.
