Access Official Technical PDF

Share Summary:LinkedInEmail

In aircraft maintenance, repair and overhaul (MRO), a schedule is only useful if it reflects how work actually unfolds. Parts can arrive late, inspections can uncover defects, and several teams may need the same limited resources. The Critical Chain MRO approach used at Embraer’s Le Bourget service center addressed these challenges by planning around dependencies, uncertainty and the work that governs the overall completion date.

The case, presented in 2018, focused on improving the planning and execution of business jet maintenance, particularly major Check-C events. Its practical lessons are relevant to operations leaders and planners managing complex, resource-constrained work: coordinate the system around delivery, make progress visible, and respond to emerging delays before they threaten the whole schedule.

Why conventional planning was falling short

Embraer’s Le Bourget facility supports its executive jet fleet across the Europe, Middle East and Africa region. The hangar was fully booked throughout the year, while maintenance teams also supported scheduled line work and aircraft-on-ground (AOG) requirements. Reliable turnaround and customer service were therefore central operational concerns.

Before the changes, the center faced limited schedule visibility and inconsistent planning during checks. The reported issues included:

  • Planning that was ineffective before and during maintenance, particularly for Check-C operations.
  • Only 40% of parts being delivered to the hangar on time.
  • Late customer approvals for additional work identified during inspection.
  • Technicians lacking clear daily priorities.
  • Limited visibility into work progress and unreliable management of hangar slots.

These problems are connected. A delayed part or approval can interrupt a task, but the consequences depend on where that task sits in the sequence and which people or resources are needed next. Improving the utilization of every individual team does not necessarily improve the aircraft’s release date.

Critical Chain MRO focuses on the whole schedule

Critical Chain Project Management (CCPM) is an application of the Theory of Constraints (TOC). TOC treats an operation as a system whose overall performance is governed by constraints. In a maintenance project, the constraint may involve a resource, a task sequence or another dependency that limits the pace of completion. The management focus is therefore on protecting and improving the flow of the entire check, rather than optimizing each activity in isolation.

Traditional schedules often include safety time within individual task estimates. CCPM challenges task durations and consolidates schedule protection into a project buffer. This shared buffer protects the project completion date against variation in task execution. It also makes the schedule easier to manage: teams can track how much of the buffer has been consumed relative to the work completed, rather than treating every task-level delay as equally important.

A project fever chart provides a visual way to interpret that relationship. Green indicates a comfortable position, yellow signals that the causes of delay should be investigated and an action plan prepared, and red indicates that corrective action is needed promptly. The chart supports attention to projects requiring intervention without requiring managers to review every task in equal detail.

Building a workable Check-C plan

At Le Bourget, implementation began with a macro-schedule that established short-term objectives. Previous Check-C experience was used to identify aircraft areas that tended to generate more findings—unexpected problems discovered during inspection—and to consider the supply of frequently required parts. The team also defined minimum and maximum resource levels by area and trained employees in Critical Chain principles.

For an individual aircraft, the detailed schedule was created in Microsoft Project with a Critical Chain add-on and aligned with the macro-schedule. The team reorganized approximately 1,200 work cards into 170 work packages, making the plan more manageable at the execution level. Durations were challenged, with protection placed in a final project buffer rather than distributed across every task.

Because inspection findings can create additional work, the plan also included a separate “Findings Buffer” to represent the workload associated with defects discovered during the check. The critical sequence of dependent tasks and resource requirements was analyzed and optimized against the objective of completing a check in five weeks. The buffer did not remove uncertainty; it gave the team a structured way to account for it and monitor its effect.

Changing daily execution and communication

The planning method was supported by new shift handover and work-release practices. At the end of each shift, the planner and team leader prepared work cards for the incoming team. All cards were handed back to the team leader for rescheduling, regardless of status. To keep work-in-progress low, planners issued new work cards when closed cards were returned.

This approach gave planners a clearer view of available work and helped limit the accumulation of partially completed tasks. Fever charts were used to monitor both individual aircraft and the hangar, while a modified control room supported visual oversight of checks. The shared view made it easier to identify schedule impacts from issues such as late parts or internal and external interventions.

Managers could also use the schedule to explore “what if” scenarios and assess potential effects on aircraft delivery dates. Instead of tracking every activity at the same level, attention could be directed to aircraft in the chart’s red zone, where schedule risk called for action.

Reported results and practical implications

The presentation reported that aircraft downtime for the measured work decreased from 63 days before 2013 to 42 days following a Lean project in 2013, and then to 35 days after the TOC project in 2015. It also reported a 45% productivity increase and a 40% performance improvement. These figures describe the Le Bourget case; they should not be treated as guaranteed outcomes for other MRO operations.

The center also reported that late deliveries, poor visibility of release dates, heavy planner workload, constantly changing priorities, forced multitasking and associated workplace stress had disappeared. Critical Chain had been embedded in Le Bourget practices since 2015, according to the 2018 presentation.

For MRO organizations considering a similar approach, the central lesson is operational rather than software-driven. A more reliable schedule depends on clear priorities, realistic treatment of uncertainty, disciplined work release, effective shift handovers and visible signals for when intervention is needed. Critical Chain MRO can provide a framework for coordinating those practices around the aircraft’s completion date. Its value lies in helping teams manage the constraints and variability that shape turnaround—not in making every task proceed exactly as planned.

Access Official Technical PDF

About The Author