Application guide

Fleet-Scale Blade NDT Across Mixed Turbine Models

RAS Thermal Co., Ltd.: mixed turbine models, short weather windows and the standardisation that makes fleet data comparable

Author: · Updated 2026-10-07

TL;DR A single technician deploying the crawler in about 15 minutes per blade, so a fleet campaign does not stall on crew waiting. One scan protocol across mixed OEM blades so the data is comparable rather than machine-specific. Fleet aggregation into trending dashboards with automated anomaly flagging. Integration with ERP and CMMS so a flagged blade enters the maintenance plan rather than a separate report.

A land-based farm spreads hundreds of turbines across a wide site, and the inspection problem is as much logistics as method. Mixed turbine models make a hand-held pass inconsistent, and short weather windows push a campaign to move fast. The answer is a standardised scan that produces comparable data across every machine on the site.

What this stage covers

The scope is a whole fleet rather than a blade. A crawler that deploys in about 15 minutes per blade with one technician turns a farm campaign into a repeatable routine, and a standardised protocol makes a scan on one OEM’s blade comparable with a scan on another. That comparability is what turns a set of readings into fleet trending.

What the inspection includes

  • A single technician deploying the crawler in about 15 minutes per blade, so a fleet campaign does not stall on crew waiting
  • One scan protocol across mixed OEM blades so the data is comparable rather than machine-specific
  • Fleet aggregation into trending dashboards with automated anomaly flagging
  • Integration with ERP and CMMS so a flagged blade enters the maintenance plan rather than a separate report

Where the value sits

The value at fleet scale is comparability. Manual readings vary 15-25 % between operators, and across a hundred turbines that variation is larger than most defect growth, so a mixed fleet cannot be trended from hand-held data. A standardised crawler pass repeats within plus or minus 0.5 mm and indexes at plus or minus 0.1 mm, so a blade scanned this year sits on the same basis as one scanned last year and on a different turbine model. The scan protocol is what makes a fleet a dataset rather than a pile of site reports.

How to plan this stage

Run these checks in order. By Step 5 the scan, the threshold and the record are aligned to the stage.

  1. Fix the acceptance threshold. Start from the threshold the zone carries, not from the method you happen to own. IEC 61400-5 Section 11 asks for volumetric detection of indications 6 mm and larger in the laminate plane, and DNV-ST-0126 tightens the leading edge to 3 mm, so the threshold is set before the probe is chosen.
  2. Read the geometry off the drawing. Measure the thickness and the curvature the probe has to travel. A spar cap up to 80 mm of unidirectional laminate and a root transition of changing radius are two different scan problems, and the radius decides how the array is coupled.
  3. Choose the modality pair. Pick modules by defect geometry, not by habit. PAUT images planar separations that lie parallel to the plies, TOFD catches volumetric clusters whatever their orientation, and running both on a 256-channel system puts the two mechanisms in one pass.
  4. Automate the scan path. Put the probe on an encoder-driven carriage and let the path, not the technician, set coverage. A 600 mm spar cap falls to one longitudinal pass at 500 mm/s on a linear array, where a single-element probe needs 20 parallel passes and runs about five times longer.
  5. Lock the evidence chain. Write the coverage map, the daily calibration and the indication log to the blade serial while the scan is running. It is the difference between a 3-day type-certification audit and a 3-hour document review, and it is what ISO 9712 qualification is there to sign.

Values quoted here come from the same verified data the product pages carry, so this page and its sources agree line for line.

Frequently Asked Questions

How do you inspect blades across a mixed turbine fleet?

With one standardised scan protocol on a crawler that deploys in about 15 minutes per blade with one technician. A single protocol makes a scan on one OEM's blade comparable with another, which hand-held inspection cannot deliver.

Why does operator variability matter at fleet scale?

Because manual readings vary 15-25 % between technicians, and across a hundred turbines that spread is larger than the defect growth a programme is trying to see. The automated pass repeats within plus or minus 0.5 mm, so the fleet can actually be trended.

How does fleet data reach the maintenance plan?

Through ERP and CMMS integration. A flagged blade enters the maintenance plan directly rather than sitting in a separate report, so the inspection result turns into scheduled work instead of a folder.

What makes short weather windows manageable?

A fast deployment and a standard path. One technician setting the crawler in about 15 minutes per blade, and a scan that runs on its programmed route, means a window that opens briefly is still enough to finish a turbine.

Bottom line: At fleet scale the method matters less than the comparability, so run one standardised crawler protocol across mixed OEM blades and let the data trend. Deploy in about 15 minutes per blade, repeat within plus or minus 0.5 mm, and route flagged blades straight into the maintenance plan.

Standards and sources

Need the scan plan behind this?

Tell us the blade spec, the zone and the standard you report against. We come back with the modality, the pass layout and the evidence chain that suit it.

Talk to an engineer
Add NDT Windblade as a preferred source on Google