{"id":1316,"date":"2026-11-21T08:00:08","date_gmt":"2026-11-21T08:00:08","guid":{"rendered":"https:\/\/planespart.com\/blog\/?p=1316"},"modified":"2026-11-21T08:02:08","modified_gmt":"2026-11-21T08:02:08","slug":"fix-now-or-count-first-repeat-part-faults","status":"publish","type":"post","link":"https:\/\/planespart.com\/blog\/fix-now-or-count-first-repeat-part-faults\/","title":{"rendered":"Fix It Now or Count It First? Two Ways to Handle Repeat Part Faults"},"content":{"rendered":"<p>The hangar smelled of cold metal and coffee when the argument started. Two groups of hobbyists and part-time mechanics at a small airfield had the same complaint: a certain cabin component kept turning up on the bench for the same reason. One group wanted to replace it every time and move on. The other wanted to pause and write things down first. Watching both camps over a season gave a neat side-by-side look at two ways of dealing with repeat part faults, and the comparison is useful far beyond aviation maintenance.<\/p>\n<h2>Approach one: fix it now, every single time<\/h2>\n<p>Call the first group the sprinters. When something failed, they fixed it. Fast, cheerful, hands-on. Their shelf of spares was always tidy, because they restocked the moment anything ran low. Visitors admired them, and with good reason: the aircraft they looked after were rarely out of action for long.<\/p>\n<p>There is real merit in this style. It builds practical skill, it keeps schedules intact, and it rewards people who like to get things moving. When a fault is truly isolated, a quick swap is the right call and a long investigation would be a waste of an afternoon.<\/p>\n<p>The weakness only shows up with time. The sprinters kept replacing the same type of part at roughly the same intervals, and nobody had a view of the interval. Each replacement felt like a fresh event with its own story: bad batch, hard landing, unlucky week. Because the stories differed, the repetition stayed hidden. The shelf stayed tidy, and the budget quietly absorbed a recurring cost that no one had named.<\/p>\n<h3>What the sprinters were good at<\/h3>\n<ul>\n<li>Quick turnaround on straightforward faults.<\/li>\n<li>Strong hands-on confidence and a feel for the equipment.<\/li>\n<li>Keeping spares organised and visible.<\/li>\n<\/ul>\n<h3>Where they lost ground<\/h3>\n<ul>\n<li>No shared record connecting one replacement to the next.<\/li>\n<li>Explanations that changed each time, so nobody saw the loop.<\/li>\n<li>Money and time spent on symptoms rather than the underlying reason.<\/li>\n<\/ul>\n<h2>Approach two: count first, then decide<\/h2>\n<p>The second group, the counters, did something that looked slow. Whenever a part came in with a familiar complaint, they logged it on a shared sheet: the part, the aircraft, the date, the flying hours since the last time, and a line about conditions. Then they repaired it exactly as the sprinters would have. The repair was never delayed; the record was simply added.<\/p>\n<p>After a couple of months, the sheet earned its keep. Entries for the same component came up again and again on one particular aircraft, and the interval between failures was strikingly regular. That regularity was a clue. A part that fails at random points to bad luck. A part that fails on a rhythm points to something that is wearing it down in a predictable way, whether that is vibration, a mounting issue, moisture, or the way the equipment is handled between flights.<\/p>\n<p>The counters did not need a laboratory to follow the clue. They compared the aircraft that kept eating the part against the ones that did not and found one difference in how it was stored overnight. They changed the storage habit and the replacements dropped away. Most of the savings came from not needing the repair at all.<\/p>\n<h3>What the counters were good at<\/h3>\n<ul>\n<li>Seeing intervals and repeats that nobody could remember unaided.<\/li>\n<li>Giving a clear sentence to take to the person who could change the routine.<\/li>\n<li>Spending effort on a cause once rather than on symptoms indefinitely.<\/li>\n<\/ul>\n<h3>Where they paid a price<\/h3>\n<ul>\n<li>A few minutes of record-keeping after every job.<\/li>\n<li>Occasional false alarms when a small sample looked like a trend.<\/li>\n<li>A temptation to keep gathering information after the answer was already clear.<\/li>\n<\/ul>\n<h2>Head to head: how the two compare<\/h2>\n<p>It is tempting to declare a winner. The honest answer is that each approach wins in different conditions. The list below keeps it in plain words, because the situation, not the person, decides which fits.<\/p>\n<ul>\n<li><strong>Speed on day one:<\/strong> the sprinters win. A direct swap beats any amount of paperwork when the aircraft is waiting.<\/li>\n<li><strong>Cost over a season:<\/strong> the counters win once a repeat is real, since they remove the cause instead of paying for it repeatedly.<\/li>\n<li><strong>Learning for newcomers:<\/strong> a mix works best. New mechanics learn from the hands-on repair and from reading the sheet afterwards.<\/li>\n<li><strong>Handling the truly random fault:<\/strong> the sprinters win again. A single failure with no echo should not trigger a study.<\/li>\n<li><strong>Handling a stubborn repeat:<\/strong> the counters win by a wide margin, because they can describe the repeat precisely.<\/li>\n<\/ul>\n<p>The best operators are neither group in pure form. They keep the sprinter&#8217;s willingness to act and add the counter&#8217;s habit of recording. The record does not slow the repair. It just waits quietly until the third or fourth entry, and then it starts to talk.<\/p>\n<p>One more difference deserves a mention: morale. The sprinters enjoyed the satisfaction of a finished job every hour. The counters enjoyed something slower, the relief of a problem that stopped coming back. Teams that mixed both kinds of satisfaction tended to stay together longer, perhaps because the work felt both busy and meaningful, and because nobody was doomed to repeat the same Tuesday forever.<\/p>\n<h2>A pattern from the money side<\/h2>\n<p>The same contrast shows up in household finances. Someone who pays every surprise bill the moment it arrives behaves like a sprinter, while someone who lists the bills and sees what repeats behaves like a counter. A piece on <a href=\"https:\/\/planespart.com\/blog\/where-your-money-actually-goes-every-month\/\">tracing where your monthly spending actually ends up<\/a> makes that argument well, and it reads like a cousin of what the hangar discovered.<\/p>\n<p>If you travel to reach the airfield, a note about <a href=\"https:\/\/planespart.com\/blog\/discovering-canada-on-four-wheels-and-two-motoshare\/\">exploring Canada by car and motorcycle through rentals<\/a> may seem a distant topic, but it is relevant in one way: people who tour regularly learn the same predictable snags, and the experienced ones keep a short list so they stop meeting them as surprises.<\/p>\n<h2>How to start counting without slowing anyone down<\/h2>\n<p>If you belong to a sprinter team and want to borrow the counter&#8217;s benefits, begin with the smallest viable record. One shared sheet. Five columns. Two minutes per entry, filled in by whoever did the job. Resist the urge to design anything fancy. The fancy version is how record-keeping dies in a drawer.<\/p>\n<p>After four weeks, spend fifteen minutes looking at the sheet together. Sort it by part, then by aircraft, then by date. Ask the room which line makes them frown. Often someone says, &#8220;Hold on, that is the third one.&#8221; That sentence is the signal you wanted. You do not need to solve the problem in that meeting. You only need to pick one cause to test and one person to try it.<\/p>\n<p>Engineers in software face precisely the same decision between patching instantly and grouping similar failures first. On the software side, <a href=\"https:\/\/devopsschool.org\/\">DevOpsSchool.org<\/a> bills itself as an open community for software engineers, built around study paths, career maps, exercise labs, a vocabulary page and a directory of tools. It is a handy window if you wonder how that other trade treats repeat failures. The hangar does not need the vocabulary, only the habit.<\/p>\n<h2>A caution about overcorrecting<\/h2>\n<p>Counters can go too far. A team that logs everything and acts on nothing has swapped one blind spot for another. The sheet exists to support decisions, not to replace them. When an entry involves anything safety-critical, the proper channel and a qualified person take priority over any home-grown tally. The tally helps you notice where to ask questions; it never decides airworthiness.<\/p>\n<p>Sprinters can also be unfairly judged. Their instinct is correct for a large share of faults. The point is not to slow them down but to add a light layer of memory on top, so the quick fix and the long view live together.<\/p>\n<h2>The verdict<\/h2>\n<p>Over the season, the counters spent fewer hours on repairs of that cabin component and fewer pounds on spares, though they spent a few extra minutes a day writing. The sprinters kept their lovely shelf and their reputation for speed. Interestingly, by the end of the year the groups had started to merge. The sprinters borrowed the sheet, the counters borrowed the quick swap, and the argument that began the story became a shared routine.<\/p>\n<p>The lesson is a simple one. Repair first when something is broken. Record as you go. When the same fault returns, treat that return as information rather than bad luck, and use the record to find the cause you can remove once.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Two hangar crews met the same recurring part failure in opposite ways. Here is how a quick swap and a simple tally compare, and what each one costs.<\/p>\n","protected":false},"author":6,"featured_media":1317,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[617],"tags":[],"class_list":["post-1316","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-aviation-maintenance"],"_links":{"self":[{"href":"https:\/\/planespart.com\/blog\/wp-json\/wp\/v2\/posts\/1316","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/planespart.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/planespart.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/planespart.com\/blog\/wp-json\/wp\/v2\/users\/6"}],"replies":[{"embeddable":true,"href":"https:\/\/planespart.com\/blog\/wp-json\/wp\/v2\/comments?post=1316"}],"version-history":[{"count":1,"href":"https:\/\/planespart.com\/blog\/wp-json\/wp\/v2\/posts\/1316\/revisions"}],"predecessor-version":[{"id":1392,"href":"https:\/\/planespart.com\/blog\/wp-json\/wp\/v2\/posts\/1316\/revisions\/1392"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/planespart.com\/blog\/wp-json\/wp\/v2\/media\/1317"}],"wp:attachment":[{"href":"https:\/\/planespart.com\/blog\/wp-json\/wp\/v2\/media?parent=1316"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/planespart.com\/blog\/wp-json\/wp\/v2\/categories?post=1316"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/planespart.com\/blog\/wp-json\/wp\/v2\/tags?post=1316"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}