Value Stream Mapping for Aircraft Maintenance (MRO): From Landing to Return-to-Service Without the Hangar Delays

[pac_divi_table_of_contents included_headings=”off|on|on|on|off|off” scroll_speed=”2100ms” active_link_highlight=”on” marker_position=”outside” title_container_bg_color=”#1FE0BA” open_icon_color=”#000000″ close_icon_color=”#000000″ allow_collapse_minimize_tablet=”on” allow_collapse_minimize_last_edited=”off|desktop” default_state_tablet=”closed” default_state_phone=”closed” default_state_last_edited=”on|tablet” _builder_version=”4.27.2″ _module_preset=”default” title_text_color=”#000000″ sticky_position=”top” sticky_limit_bottom=”section” global_colors_info=”{}”][/pac_divi_table_of_contents]

In the realm of aircraft maintenance, repair and overhaul (MRO), the aircraft itself is only one part of the value stream. Materials, technical records, engineering decisions, tooling, inspections, approvals and maintenance personnel must move in a coordinated sequence. When one element waits, the aircraft waits: and every additional hour can affect fleet availability, customer commitments and operating cost.

Value Stream Mapping (VSM) makes this end-to-end flow visible. It connects the physical movement of the aircraft with the information flow that governs its release. Applied through the Lean Six Sigma DMAIC framework, VSM helps MRO teams distinguish genuine maintenance work from avoidable waiting, handoff delays, rework and administrative loops.

A documented GE Aerospace MRO improvement project illustrates the opportunity. Its engine cost-estimate approval process was taking approximately 24 days. After mapping the current state, the team designed a future state with an 11-day target and identified 21 actions that could remove an average of 13 days from turnaround time. The breakthrough did not come from asking technicians to work faster. It came from connecting the flow of work.

1. Select the Right MRO Scope Before Mapping

A complete airline maintenance system is too broad for a useful first VSM. Select a product family with a similar routing, demand pattern and service requirement.

Suitable scopes include:

  • A-checks or C-checks for one aircraft type
  • Narrow-body aircraft induction through return-to-service
  • Engine performance restoration shop visits
  • Landing gear, wheels and brakes, avionics or ULD repair
  • AOG component replacement and certification
  • Findings approval and cost-estimate processes

Define the start and end points precisely. For example:

Start: Aircraft arrives at the maintenance base and receives an induction record.
End: Aircraft is released to operations with approved technical records complete.

Before collecting data, document:

  1. Aircraft or component family
  2. Check or repair type
  3. Planned demand per week or month
  4. Required turnaround time
  5. Internal departments and external suppliers included
  6. Safety, regulatory and customer approval constraints

Use a Project Scope Boundary Calculator to establish a practical boundary. Do not remove mandatory inspections, independent sign-offs or airworthiness records from the map. Instead, identify whether the surrounding information flow can be simplified, parallelised or standardised.

2. Build the Current-State Map at the Genba

A current-state map should be built where the work occurs: the hangar, planning office, stores area, engineering desk and inspection station. Include technicians, planners, quality personnel, materials coordinators, engineers and operations representatives.

Walk the aircraft through every process step and record:

  • Touch time or cycle time
  • Queue and waiting time
  • Number of people assigned
  • Handoffs and approvals
  • Rework and repeat findings
  • Material and tool availability
  • Information-system transactions
  • First Pass Yield and release defects

The Voice of the Customer may require an aircraft back by a contractual time, while the Voice of the Business may prioritise labour utilisation and fleet availability. The Voice of the Process, revealed through actual data, shows whether the current system can meet both requirements.

MRO current-state map showing queues and delays

3. Fully Worked Example: Narrow-Body C-Check

The following example is illustrative, but uses realistic MRO operating conditions.

A maintenance base processes one narrow-body C-check per week across three hangar bays. Available scheduled capacity is:

  • 3 bays × 40 available hours per week = 120 bay-hours per aircraft
  • Required demand = 1 aircraft per week
  • Takt time = 120 hours per aircraft

Takt time establishes the required production rhythm. It does not mean the aircraft must be completed in exactly 120 hours through sequential labour; several tasks may run in parallel. However, it shows whether the overall flow can keep pace with demand.

Current-state data

Process step Touch time Waiting time Assigned staffing
Induction and technical records review 2 hours 8 hours 1 planner, 1 records specialist
Work-package planning 6 hours 20 hours 2 planners
Jacking, de-fuelling and preparation 4 hours 8 hours 4 technicians
Inspection and findings capture 18 hours 40 hours 10 technicians, 2 inspectors
Engineering and finding review 8 hours 30 hours 1 engineer, 1 inspector
Parts and tool staging 6 hours 55 hours 2 materials coordinators
Repair and installation 20 hours 20 hours 10 technicians
Functional testing 5 hours 15 hours 3 technicians, 1 test specialist
Independent inspection and sign-off 2.5 hours 18 hours 2 inspectors
Records closure and release 1 hour 8 hours 1 records specialist
Total 72.5 hours 222 hours 22 peak personnel

The current-state lead time is:

72.5 hours touch time + 222 hours waiting = 294.5 hours, or approximately 12.3 calendar days.

The touch-time-to-lead-time ratio is:

72.5 ÷ 294.5 = 24.6%

If only 48 hours represent direct customer-value-adding maintenance activity, the process cycle efficiency is:

48 ÷ 294.5 = 16.3%

The largest delays are not concentrated in wrench time. They sit around inspection findings, engineering review, parts and tools, and independent approval. The principal bottleneck is the combined inspection-to-material-readiness chain. Aircraft findings are discovered faster than the support system can respond.

4. Identify the Eight Wastes in Aircraft Maintenance

The eight DOWNTIME wastes appear in distinctive MRO forms:

  • Defects: Incorrect work-card completion, missing records, repeat findings or failed functional tests.
  • Overproduction: Preparing parts, paperwork or inspections before the work scope is confirmed.
  • Waiting: Aircraft, technicians or inspectors waiting for parts, tools, engineering decisions or approvals.
  • Non-utilised talent: Qualified technicians spending shifts searching, expediting or performing avoidable administration.
  • Transportation: Moving components, documents and tooling between distant stores, shops and hangar bays.
  • Inventory: Excess serviceable stock, poorly located consumables or incomplete kits that create hidden shortages.
  • Motion: Walking long distances to locate tools, manuals, parts or authorisation records.
  • Extra processing: Duplicate data entry, repeated approvals, unnecessary status meetings or redundant inspections.

A box plot of turnaround times can reveal skewness and outliers, while a Pareto chart can show whether parts, approvals or rework account for most delay hours. Where multiple aircraft types or work areas are involved, ANOVA can test whether average delay differs significantly between groups. Bartlett’s Test can first assess whether the group variances are sufficiently equal for that comparison.

5. Build the Future-State MRO Flow

The future state should protect airworthiness while reducing the time between decisions and action.

Countermeasure 1: Create an I-minus readiness gate

Before induction, confirm:

  • Work package released
  • Critical parts and consumables available
  • Tools and ground-support equipment reserved
  • Engineering contacts assigned
  • Inspection capacity scheduled
  • Technical records and applicable revisions verified

This converts late discovery into early preparation.

Countermeasure 2: Introduce sequenced kitting

Prepare parts and tools by work package and task sequence. Use point-of-use staging for frequently required items. A visual shortage signal, similar to an Andon, should alert materials and planning teams when a kit is incomplete.

Countermeasure 3: Parallelise finding review

When an inspection area is complete, transmit the finding electronically to engineering while the next inspection continues. The objective is not to bypass technical authority. It is to avoid making engineering wait until every inspection is finished.

Countermeasure 4: Establish approval service levels

Define an approval clock, escalation rule and clear ownership for findings, cost estimates and work-scope changes. Formal approval checkpoints support governance, but poorly designed checkpoints create bottlenecks. Use risk-based routing so routine, well-defined decisions move quickly while complex decisions receive the required review.

Countermeasure 5: Standardise normal and abnormal flow

Create standard work for common findings, escalation criteria and documentation closure. A visual board should show each aircraft’s status, ageing, missing input and next owner.

Future-state data

Metric Current state Future state target
Touch time 72.5 hours 64.5 hours
Waiting time 222 hours 47.5 hours
Total lead time 294.5 hours 112 hours
Calendar duration 12.3 days 4.7 days
Touch-time-to-lead-time ratio 24.6% 57.6%
Customer-value-adding time 48 hours 48 hours
Process Cycle Efficiency 16.3% 42.9%
Peak staffing 22 people 20 people, cross-trained
First Pass Yield at release 86% 95%
Repeat approval loops 3.2 per aircraft 1.0 per aircraft

The future-state lead time of 112 hours fits inside the 120-hour takt requirement, creating an 8-hour protection margin. The staffing reduction is not achieved by removing capability. It comes from cross-training, clearer sequencing and fewer people acting as expediters.

Future-state MRO flow with kitting and visual management

6. Kaizen Sequencing Plan

Sequence improvement work according to dependency and impact:

  1. Days 1–5: Stabilise measurement
    Define turnaround time, waiting categories, First Pass Yield and release defects. Validate timestamps and measurement definitions.

  2. Week 2: Remove readiness gaps
    Launch the I-minus checklist, confirm kit ownership and create a daily shortage review.

  3. Weeks 3–4: Improve material and tool flow
    Apply 5S, point-of-use storage, sequenced kitting and Andon-style escalation.

  4. Weeks 5–6: Redesign information flow
    Parallelise engineering review, clarify approval authority and introduce ageing visibility.

  5. Weeks 7–8: Standardise and control
    Publish standard work, audit checklist completion and monitor lead time with control charts.

  6. Day 60 onward: Sustain and expand
    Review performance weekly, confirm gains by aircraft type and extend the method to engines, components or other maintenance checks.

Use an online Process Cycle Efficiency Calculator to quantify the effect of each improvement. For broader capability, explore the Lean Six Sigma Green Belt course, which develops practical skills in data-driven analysis, project management and process control.

MRO performance dashboard measuring takt, lead time and yield

Turn MRO Delays into a Structured Improvement Project

Aircraft maintenance requires discipline, traceability and technical judgement. Value Stream Mapping does not replace those requirements. It gives teams a clearer way to protect them while improving flow.

When planners, engineers, technicians, inspectors and materials teams map the same process, the conversation changes from “Who is holding up the aircraft?” to “Which part of the system is creating the delay, and what evidence will remove it?” That is the foundation of sustainable Lean Six Sigma improvement.

Build the capability to lead aircraft maintenance improvement projects with a CSSC-accredited Lean Six Sigma certification from White Belt through Black Belt. Start your training with Lean 6 Sigma Hub and learn how to apply VSM, DMAIC, statistical analysis and practical kaizen in real operational environments.

Kaizen. Kai-Care. Kai-Done. ( Lean Six Sigma)

Related Posts