Flight-Time Calculation Where Consecutive Legs Have Missing Start/End Times

Current Behaviour

OSS calculates flight hours using the Start Up / Shut Down or HOBBS Start / HOBBS End fields. Each flight leg should normally contain a valid start time and end time.

When an end time is missing, the current configuration checks only the immediate next leg for a corresponding start time. If that next leg does not contain a valid start time, the calculation fails and the affected legs are excluded.

Example

Consider a flight containing Legs A to D:

• Leg A: Complete record (has both a start time and an end time).

• Leg B: Has a start time, but no end time.

• Leg C: Has no start time and no end time (blank entry).

• Leg D: Has only an end time (no start time).

Under the current logic:

• Leg B looks only at the immediate next leg (Leg C) for a start time to close its interval. Because Leg C is blank, Leg B cannot be resolved.

• Leg C has neither start nor end times, so it cannot be calculated.

• Leg D has an end time, but the system cannot link it back across the blank Leg C to resolve Leg B.

As a result, only Leg A is calculated.

Current Workaround and Associated Risk

To force the system to calculate, crew are required to manually insert artificial Shut Down or Start Up times on incomplete legs.

Example: "Offshore" operations routinely involve continuous hovering where traditional shutdowns, landings, restarts, or take-offs never occurred. Forcing artificial time entries introduces serious data-integrity risks.

Proposed Enhancement

Enhance the calculation logic so OSS can search beyond the immediate next leg to find the next valid, chronological end time in the sequence.

In the 4-leg example above:

• Leg B would skip the blank Leg C and draw its closing time from Leg D.

• This seamlessly completes the continuous flight period for Legs B–D without requiring false start/stop events to be entered.

Kind regards,