On Tuesday, September 15, 2026, Customer A (example) stopped its assembly line when three fittings from Meridian Aerostructures would not take the thread gauge to full depth. This is how the kit carried the complaint from the first email to the effectiveness check. Every reference number below is in the tools' own worked examples.
Day 1: receive, acknowledge, stop the flow
11:15. Receive (B14 ). Reject report CR-142 arrives by email to R. Chen, quality manager. She fills in the Intake record while on the phone with the customer's supplier quality engineer: 6610-150 rev D, lot L-2663 (50 pieces, shipped September 8), GO thread plug gauge stops 2 to 3 turns short on 3 fittings at installation, full thread depth 0.50 in. minimum. She reads it back. The customer asks for containment in 24 hours, root cause and escape cause in 10 business days (September 29), and their 8D form in 30 days. Logged as CPL-26-008, owner R. Chen; the customer's dates go on the log.
13:00. Stop the flow and escalate. M. Okafor places holds on all 6610-150 and 6610-152 in stock and work in process, with an ERP hold. Escalated to T. Brooks, plant manager, as a customer escape that stopped a line (B13 ).
13:20. Acknowledge (B15 letter 1). Received, CPL-26-008, the owner, the holds in place, the request to hold L-2663 at their site, and the next update by 16:30.
16:30. Tell them what they have not found. The program log shows the tap-drill cycle changed on August 26, on 6610-152 as well. R. Chen calls the customer: lot L-2664 (30 pieces, shipped September 10) is also suspect. Written notice with lot numbers follows at 08:00 on September 16.
Days 2 to 3: validate and contain
Validate. The three rejected parts are checked at the customer's site by D. Ruiz with a full-length gauge: all three short. Substantiated: Yes. Escape?: Yes. NCR-26-334 raised; CAPA-26-052 opened, run as an 8D because it is an escape and the customer asked for one.
Contain (B12 Part C, B15 letter 2). Suspect window from August 26 (program revision 5) to the point output was gauged to full depth. Every location searched: 170 suspect, 170 checked with a full-length gauge, 155 good, 15 nonconforming (8 at the customer, 7 in our stock and work in process), none in transit, at processors or in spares. Containment complete September 17; 8 replacements shipped September 22. Temporary check: every thread gauged to depth at final until 10 clean lots. Letter 2 carries the table.
Log (B14 ). Containment done September 16, inside the customer's 24 hours; the log shows Contained in time: Yes.
Days 4 to 14: investigate and respond
Root cause (B12 Part F, the 8D's D4). A trial on Mill 6 on September 18 gives 2 short threads in 20 parts with the single-pass tap-drill cycle and none in 20 with the peck cycle; sectioned holes show packed chips. Program O6610 rev 6 restores the peck cycle on September 19.
Escape cause (B12 Part E). Walking the route: the operation 40 check and final inspection both used gauges with a 0.38 in. thread length, too short to find a 0.50 in. depth problem, because inspection plan IP-6610-150 rev B said 'GO/NOGO' with no depth. The first-piece check after a program change did not run, because cycle-time edits were exempt. Three detection points, none able to find the defect.
Actions. Peck cycle restored (root cause). IP-6610-150 rev C with full depth, and full-length gauges TG-31 and TG-32 at operation 40 and final (escape point). Change procedure revised so any drill, tap or bore cycle change needs a first-piece check (escape point). 23 inspection plans with blind tapped holes reviewed, 4 updated (other places). Effectiveness criterion set before the actions went in: no short threads at operation 40, final or the customer over 10 lots and at least 90 days (B08 ).
Respond (B15 letter 3). Sent September 29, on the customer's date, written from the escape record: the same 170, 155 and 15, the trial, the gauges, the four actions with dates, the criterion, and one sentence of regret for the line stoppage. No promise that it will never happen again; a commitment to send depth readings with the next five shipments. The customer's own 8D form follows on October 14.
Weeks 3 to 14: acceptance, verification and the bigger picture
Accepted (B14 ). The customer accepts on October 21, the first time. The log line moves to Accepted: verify and close, and stays open.
Verify (B08 , B15 letter 4). By October 31, six lots are clean, with depth readings sent with each shipment. The window ends with the tenth lot and not before December 18; letter 4 is drafted to report the result for all ten lots and ask the customer to close CR-142. Only then do the temporary checks come off and the line close.
The scorecard (B16 ). ESC-26-004 goes on the escape register: detection point Final inspection, escape cause Not in the inspection plan. Customer A's quarterly quality rating for the third quarter is 94 percent, up from 91 after the June bore escape but still short of the 95 percent Preferred line it held until March. On the customer view, Customer A now shows four escapes in twelve months.
The pattern. Read down the escape register: the anodize escape (ESC-26-001) got through receiving on a supplier certificate; the bore escape (ESC-26-002) through an in-process gauge out of calibration; the thread escape through an inspection plan that left out the failure mode; the mixed lot (ESC-26-005) at the packing bench. None was an inspector's lapse; each was a gap in how detection was planned or maintained. At the quarterly management review this becomes one corrective action of its own: review every inspection plan's ability to detect the failure modes on its drawing, starting with Customer A's parts.
What the example shows
The kit did not make the escape smaller. It made the response faster, more complete and more believable: acknowledgment in two hours, the second lot reported before the customer found it, containment inside 24 hours, a response accepted the first time, and a complaint that stays open until the data says the actions worked. And it turned four separate escapes into one finding about detection that no single investigation would have shown.
← Chapter 17 For your general manager: one page Chapter 19 → Quick reference: one page Need more than one resource, or not sure where to start? Book a complimentary 30-minute Aegis Quality Guidance Call . We'll find the tools that fit your situation and a sensible place to start. No sales pressure, no obligation.
A management aid, not certification or a registrar audit. Using it does not by itself show conformity to AS9100D or any other standard, and your customers' requirements may add to it.
Clause numbers refer to AS9100D (SAE AS9100 Rev D) unless another document is named. The standards' text is not reproduced here: use your own licensed copy.
Aegis Insights are our own guidance, labeled wherever they appear: how we approach this work, not a requirement of any standard or customer.