A fleet can report 95% dispatch reliability and still have technical dispatch reliability of 88%. Those figures measure the same operation differently: one includes every departure delay, while the other isolates technical causes. That gap can give maintenance planning a false read. Knowing how each metric is calculated changes how you assess the planning result.
Dispatch reliability and technical dispatch reliability
Dispatch reliability (DR) is the share of scheduled departures leaving within a set threshold, typically 15 minutes. It includes weather holds, crew availability, ATC slots, gate conflicts, and technical issues. A late crew member affects DR just as a hydraulic fault does.
Technical dispatch reliability (TDR) looks only at departures delayed or cancelled for technical reasons, including aircraft unserviceability, maintenance defects, and MEL restrictions. A 95% DR alongside 88% TDR means one in eight technical departure attempts meets a mechanical problem. That points to maintenance planning, not general operations.
Most regional operators monitor DR because contracts or regulations require the report. Maintenance and engineering teams usually track TDR, but it does not always feed scheduling decisions and complete the feedback loop. As a result, the same planning gaps return. The clearest metric is not always visible to the people setting the schedule.
Scheduled and unscheduled maintenance hours
Another useful measure compares scheduled and unscheduled maintenance hours. Scheduled work is planned in advance: A-checks, B-checks, C-checks, component overhauls, and task card work within interval limits. Unscheduled work appears as a preflight defect, an in-service crew report, or a finding during an overnight turn.
In a well-planned fleet, unscheduled work is typically about 30-40% of total maintenance hours, varying with aircraft age and type. Once it exceeds 50%, the usual signal is either a scheduled program that misses something or a recurring defect category being handled reactively rather than proactively.
A high unscheduled ratio alone does not prove a planning failure. Some aircraft types have defect categories that are hard to predict and require reactive work. We are not saying every unscheduled event belongs on the planned schedule. The issue is whether the work is genuinely unpredictable or whether repeated defects reveal a scheduling gap that can be closed.
Utilization rate and scheduled aircraft availability
Utilization rate compares an aircraft's actual daily block hours with the hours it is theoretically available to fly. A narrowbody in regional service often operates 8-12 block hours per day during peak periods. Scheduled maintenance downtime and overnight checks reduce that figure.
Scheduled availability is the inverse measure: the share of time an aircraft remains on the available list instead of undergoing planned maintenance. With scheduled work managed well, aircraft should be available on 92-95% of operational days, with planned checks using the rest. Sustained availability below 88% usually indicates excess downtime, caused by poorly timed checks against the flight schedule or findings that extend checks beyond plan.
How MEL deferrals affect availability figures
An aircraft flying under a Minimum Equipment List deferral remains technically available and dispatches, so it appears in the DR numerator. It still has a known defect and a compliance deadline. That deadline creates a future scheduling constraint missing from availability figures until the deferral nears its limit.
A fleet with many MEL deferrals may show healthy dispatch reliability while accumulating deferred work for a later, compressed clearance window. Clearance often lands alongside scheduled checks. Together, they create avoidable spikes in hangar demand and parts stock that better forward visibility could have exposed earlier.
In scheduling data from early-access operators, the MEL backlog effect is one of the first recurring patterns we see. Each deferral may be benign within its limit. Taken together, they create planning pressure that remains hidden until it becomes visible.
How these metrics connect back to maintenance planning
The point of tracking TDR, the scheduled-to-unscheduled ratio, and MEL deferral load is not the figures alone. The figures help identify the scheduling decisions behind them. A TDR decline in a given month, linked to an aircraft or system, usually indicates an interval needing adjustment or a recurring defect to address during the next scheduled check instead of at the gate by the crew.
That is the feedback loop maintenance planning should provide: set the schedule, measure technical reliability outcomes, trace deviations to planning decisions, and apply the findings to the next cycle. If availability metrics are not tied to the choices that produced them, the numbers accumulate without guiding action.
Tailsight links these relationships in the planning view. When maintenance records reveal a defect pattern, it flags the upcoming task window for proactive work instead of waiting for another unscheduled event. We are not saying every defect can be predicted. The aim is to prevent known problem patterns from falling between scheduled check visits.