Service forecast

The Service forecast panel in personal Insights turns an airframe's service clock into a practical worklist. It combines the service interval you set on the airframe with bound flights from the most recent 30-day window.

What the panel shows

• Service clock: minutes remaining and the percentage of the configured interval used.
• Projected due: an estimated date and an approximate number of days when the recent sample is strong enough.
• Reliability: hours per failure for an airframe and for the fleet when the sample supports a meaningful rate.
• Due in 30d / 90d: counts of airframes projected to reach service in each window.
• Not projectable: airframes with an interval but not enough recent evidence for a date.

Rows are ordered as a worklist: service due first, then the soonest projected service, then rows that need more data.

When a date appears

The forecast uses minutes flown per calendar day across the 30-day window. A date is published only after flights have occurred on at least three different days. This prevents one unusually long session from pretending to be a stable routine.

You will see an explanation instead of a guessed date when:

• the airframe has no recent flying;
• recent flying exists, but it happened on too few days; or
• no service interval is configured, because the airframe is serviced as needed.

An airframe already at its interval shows Due now without waiting for a projection.

Reliability sample

Hours per failure remains blank until the airframe or fleet has at least 50 hours of airtime and at least one logged crash. No crashes or an inadequate sample is reported as unknown, not as a perfect safety score.

Improve the forecast

Bind sessions to the airframe they used, set a realistic service interval, and keep crash counters current. A quick-added session with no airframe can still count toward your airtime, but it cannot be assigned to a specific rig's forecast.