Skip to content
CorrectiveActionReport.comSupplier CAR Response Desk — home

CAR & SCAR Response

Aerospace Root Cause Corrective Action (RCCA): Answering a Prime's SCAR

Aerospace SCARs ask for disposition by serial or lot and close attention to human factors. This guide walks an AS9100 supplier through a clocked first-draft response ready for its own sign-off.

Rovaryn Digital · · 9 min read

What an aerospace SCAR asks for

An aerospace SCAR asks for things a commercial request often leaves out. Suppose an aerospace prime issues one against a lot of titanium brackets, and the finding is a bore diameter that measured out of tolerance at the customer's incoming inspection. Three things stand out on the first read. The response window lives in the customer's manual, not in the email. The form asks for the disposition of every affected serial number. And there is a section headed human factors that has no obvious place for a one-line answer.

Meanwhile, the same bore feature showed up on another customer's rejection last quarter. The notes from that one sit in a former colleague's inbox.

None of this is unusual for an AS9100 machining or fabrication supplier. What makes it hard is that the clock starts before the analysis does, and the answer will be read closely by someone who knows the part. This guide walks through an aerospace root cause corrective action (RCCA) response from the supplier's side of the desk: what to read first, how to handle disposition, how to separate occurrence from escape, and how to ask human factors questions that lead somewhere.

What an aerospace root cause corrective action (RCCA) response has to show

A SCAR is a supplier corrective action request: a customer's formal notice that something you shipped did not conform, with a request for your response. Your answer has to show three things in order. You controlled the suspect product. You found out why the problem happened and why it left your building. You changed something so it does not return.

That shape follows the nonconformity and corrective action requirements in AS9100 clause 10.2. Wording and sub-clauses differ by edition, so read the clause in the edition your certification body audits you against.

Two other documents often sit behind a prime's request. SAE AS13000A, "Problem Solving Requirements for Suppliers", defines the process a supplier uses to respond to a customer request for corrective and preventive action. It was issued by the G-22 Aerospace Engine Supplier Quality (AESQ) Committee, according to SAE International's listing. EN 9136 is an aerospace-series standard that some customers reference for root cause and problem solving. Whether either document applies to you depends on your contract and your customer's manual, so confirm with your customer's supplier quality engineer and check the current title, scope and edition. Neither text is reproduced here.

If you want the general mechanics first, the supplier corrective action request guide covers the request lifecycle across industries.

Read the SCAR before you answer it

The first hour is for reading, not for analysis. Aerospace SCAR forms vary a good deal, and one misread field can send the whole response back. Work through this checklist against the request and your customer's current supplier manual:

  1. Identify the clocks. Find every dated expectation: initial containment, root cause, corrective action plan, closure. Note whether each is counted in calendar days or working days.
  2. Confirm the population. Which part numbers, serial numbers, lot or heat numbers, and shipment dates does the customer consider affected?
  3. Find the disposition fields. See whether the form wants disposition per serial, per lot, or both, and which dispositions are allowed.
  4. Check the method requested. Some requests specify a format, a method such as 8D, or a referenced standard. Use what the customer prescribes.
  5. Locate the human factors section. Read what it asks you to address and whether it expects evidence or narrative.
  6. Note required attachments. Look for inspection data, process records, certificates of conformance, and photos.
  7. Record who signs. Identify who must approve the response on your side before it leaves.

Keep the manual revision number with the record. Customers revise these documents, and a response written against last year's revision is a quiet way to lose a day. The SCAR response guide goes deeper on reading the request itself.

Disposition by serial number or lot

Aerospace requests tend to care about traceability in a way many commercial requests do not. A prime may want to know exactly which serialized parts were suspect, where each one is now, and what happened to it. Build that table early, while containment is still moving. The rows below are invented to show the layout.

Serial or lot Location Status Evidence Owner
SN 0412 Customer stock Returned for rework Return authorization, reinspection record Quality engineer
SN 0413 Your quarantine Scrapped Scrap tag, disposition approval Material review lead
Lot 2217-B In transit Recalled for 100% re-inspection Recall notice, inspection sheet Inspection supervisor

Three habits keep this table honest. List every unit in the suspect population, including ones you believe are fine, and say how you know. Separate containment (stopping suspect product) from correction (fixing the units already affected), because customers read those as different steps. And attach the evidence to each row rather than describing it in a paragraph.

Whether a nonconforming unit can be reworked, repaired or used as-is is governed by your customer's disposition authority and your own procedures, not by this table. Where a disposition needs customer approval, record the approval reference and date.

Occurrence and escape: two root causes, not one

Many weak SCAR responses stop at the occurrence: why the feature went out of tolerance. A close reader will also ask the escape question: why your own checks did not catch it. These are separate causal chains, and a complete response states both. The occurrence and escape guide covers the logic in detail.

Here is a 5 Whys layout for the bore diameter example. The chain is illustrative, not a finding about any real part.

Occurrence branch

  1. Why was the bore out of tolerance? The finishing pass ran with a wear offset that no longer matched the tool.
  2. Why did the offset not match? The boring bar wore faster than the tool-life setting assumed, so the offset was not updated in time.
  3. Why did the setting not reflect actual wear? It was carried over from a different alloy's job file.
  4. Why was it carried over? The job-file release step has no check of the material-specific tool-life value.
  5. Why is there no check? The release checklist was written before this alloy entered the shop.

Escape branch

  1. Why did the part pass your inspection? The check measured the bore at one depth only.
  2. Why one depth? The control plan calls for a single-point measurement.
  3. Why does the control plan say that? It was copied from a similar part where taper was not a concern.
  4. Why was it not reviewed for this part? Control plan review is triggered by drawing changes, not by new material.
  5. Why is that the trigger? The review procedure never listed material changes.

Each chain ends at something you can change, such as the release checklist or the review trigger, rather than at a person. The D4 root cause analysis article shows how this fits the 8D discipline sequence. For a fishbone to sort the candidate causes before you run the whys, see ASQ's overview of the diagram, one of its seven basic quality tools. Machining-specific candidates are in the CNC machining defects guide.

If your customer names a method or a standard for the response, follow that structure and check the current edition for what it expects you to show.

Human factors prompts that go past "operator error"

A human factors section can feel like an invitation to name a person. A reviewer reading a response that ends at "operator did not follow the instruction" will usually ask why the system allowed that, so treat the individual's action as the starting point of the analysis, not the end.

Human factors root cause analysis in aerospace work asks how the task, the environment and the organization made the error likely. Use prompts like these as a conversation guide with the people who did the work, and record what you learn:

  • Task and instructions. Was the work instruction current, clear and available at the point of use? Did it match how the job is actually done?
  • Tools and fixtures. Did the tooling or gauging make the wrong action easy and the right one hard?
  • Workload and timing. Was the job running behind, or was the setup rushed across a shift change?
  • Training and experience. Had the person been trained on this operation and this material, and how was that verified?
  • Communication. Did information about a change, a deviation or a known issue reach the person doing the work?
  • Detection. Would a reasonable check have caught the error, and was that check in place?

Do these conversations without blame, and say in the response that they were done that way. The goal is to find conditions you can fix. Keep the language factual and keep personal details out of the record.

A response reads as credible when every root cause ends at something the organization can change: a procedure, a trigger, a fixture, a check.

A first-draft layout you can use without software

An AS9100 corrective action request template does not have to be elaborate. When the customer supplies its own form, use that form. When it does not, or when you want an internal working draft before you transfer anything, this layout gives the response a spine:

  1. Request details. Customer, SCAR number, part number and revision, quantity, date received, manual revision consulted.
  2. Clocks. Each due date in the customer's terms, with the counting rule noted.
  3. Team. Names and roles.
  4. Problem description. What was found, where, by whom, against which requirement.
  5. Containment. Suspect population, actions, dates, evidence.
  6. Disposition table. By serial or lot, as above.
  7. Root cause. Occurrence chain, escape chain, and the human factors findings.
  8. Corrective actions. Each with owner, due date and status.
  9. Effectiveness check. What you will measure, over what period, and who reviews it.
  10. Review and sign-off. Who approved the response internally, and when.

Draft in your own words first, then re-key into the customer's form or portal. The portal is a channel the customer runs, and your record is where the history lives.

Keeping the record across customers

Keeping the draft, the clocks and the evidence in one place per request is easier said than done when requests arrive from several primes and tier-1 customers, each in its own layout. A supplier-side record helps most when the same bore feature shows up on a second customer's request.

Supplier CAR Response Desk is designed to hold each request as its own record, with editable per-customer response rules, a guided D1–D8 with 5 Whys and fishbone entry, action items with owners and due dates, and evidence attached to each discipline. It is built to export PDF or Excel in a customer's field order, with a generic 8D fallback. It is not yet open, and it records and calculates; it is not advice or certification.

If you would like to hear when the Response Desk opens, you can join the waitlist.

Put it to work

Compare plans on the pricing page.

Get the next guide

Practical guides for supplier quality teams, delivered straight to your inbox.