SavvyAnalysis Puzzlers
Every month, Joe Godfrey, Savvy’s chief data analyst, presents captivating aviation “puzzlers” derived from real-life engine monitor data on the SavvyAnalysis platform, guiding pilots in identifying anomalies for real-time safety decisions and assisting owners in informed maintenance choices.
Recently, one of our clients upgraded his JPI 700 to a Garmin G3X. Our tech specialist Kurt changed the account configuration so the new data will use the correct parser. In his note to the client, Kurt said “you’ll now have a dizzying array of data available to you.” I remembered my own upgrade from an Insight GEM 602 to a JPI 830. The old GEM didn’t display numbers – just a series of bars for each 25º – and they were almost always higher than I wanted to see. I always wondered if that extra bar meant that my number 3 CHT was 401° or 424°. One of my favorite things to do on a rainy day at Oshkosh is to stroll the avionics booths and compare how the various monitor manufacturers display their data. Bars, needles, numbers – lots of options to choose from. And if a rainy day at home finds you curled up with a favorite old airplane movie like Spirit of St. Louis or Air Force or 12 O’clock High or The High and the Mighty, it’s remarkable how little engine data they had to process. So it’s good to have real time access to […]
Macco’s Razor
Is there a mirror image for Occam’s Razor? Seems like if we have a name for relying on the least complex explanation for a scenario, then we ought to have one for the most outlandish, unlikely, logic-defying explanation. For instance, recently we got engine data for a Cessna TR182 Turbo Skylane RG. The shop replaced a failed CHT probe and all of a sudden that cylinder’s CHTs were about 100º hotter. EGT’s hadn’t changed so the problem seemed to be cooling related. We recommended checking baffles and – although no exhaust maintenance had been performed – checking for an exhaust leak. After coming up empty checking all the logical explanations, somebody at the shop noticed that the new CHT probe in cylinder 3 didn’t look like its neighbors in cylinders 1 and 5. Installing the wrong probe gave us bad data and a pretty good goose chase. And something to consider next time we see that scenario. Let’s take a closer look at the data from the Turbo Skylane. The engine is a Lycoming O-540 and data is from a JPI 830 with a 1 sec sample rate. EGTs on top, with CHTs and FF below. Max CHT is 491 […]
Once in a Blue Moon
When we started our engine data analysis service in 2014, I wondered if we would see seasonal patterns in the data. For instance, would we see more probe failures in the heat of the summer? Would we see more stuck valves in the colder months? Would we see more anomalies in general in the fall months after the busy flying season? Data supports that last one, which shouldn’t surprise anyone. But in ten years of working tickets I haven’t yet been able to connect the dots on other seasonal patterns. I’ll keep looking because my spidey sense tells me there’s something to find. Meanwhile, this month’s collection covers a lot of ground in terms of issues and powerplants. We’ll start with data from a Cirrus SR20 powered by a Continental IO-360 with data from an Avidyne Entegra with a 6 sec sample rate. EGTs on top, with CHTs and FF below. Nothing special about curser placement – just moving it out-of-the-way. After about 15 minutes of warming up, CHT 5 starts jumping between 500º and zero. After about 15 minutes of that, it settles down and tracks CHT normally until shutdown. Meanwhile, CHT3, which was tracking normally until takeoff, is […]
Can Lapping Save My Valve?
We rolled out Savvy’s Borescope Initiative in January. In the ensuing 7 1/2 months users have uploaded over 65,000 images to the repository. If you’re still waiting to participate, or if this is news to you, check out Savvy’s Borescope Initiative. Before the rollout, we suspected that most of the valves we looked at would show normal – symmetrical – heating patterns. We also suspected that we would catch some valves in various stages of burning that may not have been detected through compression checks or oscillations in EGT. We were right on both counts. A borescope image report prepared by an analyst will classify exhaust valve head images Normal, Early/mid-stage uneven heat pattern, or Advanced uneven heat pattern. We hope the following examples assist you in deciding what intervention, if any, is appropriate. If you are a SavvyMx client, your dedicated account manager can help you make this determination, and if you are a SavvyQA client, an account manager on our team will provide guidance. Normal heat pattern A normal heat pattern in the exhaust valve head deposits will show symmetrical rings of varying color, or possibly uniform color over the entire valve head. The colors are not so […]
Mayday, Maybe
I’m brushing up my French for an upcoming trip and was reminded that Mayday comes from M’Aidez – Help Me. When I started flying in the ’70s the conventional wisdom from the old timers was “whatever you do don’t declare an emergency”. Now that I’m an old timer, the prevailing attitude in my pilot circle is to declare the emergency and get whatever help you can – and you might be surprised at how little follow up you’ll encounter. Engine failure, structural failure, smoke in the cockpit; those are easy. Declare and get the help. What’s more challenging is when you see something troubling on the engine monitor – but you’re not sure if it’s a real problem or just a sensor acting up. Declaring entitles you to priority handling, and if you declared but it turned out to be nothing more than sensor failure, that would likely be the end of it -unless you had a history of crying wolf when there was no wolf. In your preparation for 91.103 compliance – a.k.a. “all the information about the upcoming flight” – you could review what scenarios would trigger an emergency declaration. It’s a tougher decision in the moment. We’ll […]
Intermittent
If an engine monitor probe or sensor is going to fail, would you rather have it just fail and be done with it, or have it be reliable some of the time and distracting some of the time? Neither has much appeal, but at least with the failure, you can skip the detective work of does it only happen in flight, or when the engine is warm, or when the tanks are full, or…? With intermittent data, it almost always makes sense to check the connection first. Sometimes the data can give you clues as to the odds of it simply being a case of a loose or dirty connection. Sometimes the data is accurately logging the intermittent failure of an engine component. For each case, a decision tree helps guide the process. In this puzzler we’ll analyze some examples and see what they can tell us. Here’s data from a Cirrus SR22 TN powered by a Continental IO – 550 turbo normalized engine and data from a Garmin G1,000 with a one second sample rate. Here are EGT, CHT and FF for the 35 minute flight. Something happens at the 10 minute mark, but I put the cursor on […]
Hockey
Hockey playoffs are in full swing. It’s usually about this time of the year that I rewatch my favorite hockey movie “Miracle”, about the 1980 Olympics. So many great performances, including fellow pilot Kurt Russell as Herb Brooks, but none better than Eddie Cahill playing US goalie Jim Craig. And now you’re wondering, how is he going to tie hockey to engine data analysis? Here’s how. Sometimes analysis tells us exactly where to look to fix a problem. a clogged injector, a bad spark plug, a pinched cooling baffle – all pretty easy to spot in the data and gratifying to know that we helped save the owner time and money. That’s offense. Equally gratifying from an analysis point of view is when we keep an owner from scheduling and paying for unnecessary maintenance on something that isn’t broken. That’s defense. First up is a Piper Saratoga powered by a Lycoming IO – 540 and data from an Insight G4 with a 1 second sample rate. The flight is only about seven minutes starting at the 15 minute mark, but this includes ground ops before and after the flight. EGTs on top, CHTs and FF below. Cursor is on the […]
Broken
The analysis team sees lots of malfunctions in the data we review. No surprise – most clients request analysis when something’s not right, so we’re not seeing the thousands of flights that go off without a hitch. So you could say we’re spring-loaded for malfunctions. This month we had a surge in things that were broken – not just malfunctioning. Surely the engine data offered signals that something was about to fail. Either in real time, or in post flight review. Yeah but it’s not that simple – and as they say in the movies, don’t call me Shirley. This month, Savvy’s Director of Analysis Joe Godfrey looks at data from a Cessna 206, a Bearhawk, a Cirrus SR22T and a Beech Bonanza 36. First up is data from a Cessna 206 powered by a Lycoming IO-540 with data from a JPI 900 with a 1 sec sample rate. EGTs, CHTs and FF. There’s an early indication of trouble in EGT and CHT 3. EGT 3 is low until takeoff, then it’s up with the others. CHT 3 is also low until takeoff, then it jumps past the others and stays high – until it fails at about 2 hrs […]
Deep Fake
Lately the news is filled with examples of deep fakes. This is nothing new for pilots. We practice partial panel approaches for scenarios where technology is trying to convince us that something phony is real. It’s nothing new for engine data analysts. We start the process with evaluating the reliability of the data. The difference is the perpetrator. A good deep fake usually has a bad actor or a comedian attached to it. We almost never see either in an airplane – it’s just bad data from a loose connection or a failing part. Or is it? This month Savvy’s Director of Analysis Joe Godfrey looks at data from a Cessna 182, a Beech Bonanza 36, a Cirrus SR22T and a Cessna 210. Let’s start with a Cessna 182 powered by a Continental O-470 engine and data from a JPI 900 with a 1 sec sample rate. Rather than take up space depicting CHTs and FF for each flight, let’s stipulate that both looked normal for all cylinders. The is EGTs only for four consecutive flights. There are a few things in this data that we could examine, but let’s stick with the green trace of EGT five. On the […]
Looking for Trouble
When the analysis team started looking at engine data about 10 years ago, we could confidently recognize the patterns for clogged injectors, spark plug misfires and detonation events. Other patterns, like broken valve springs and induction leaks, came later. Last month the analysis team began reviewing borescope pictures. Just as with engine data, some conditions are easy to spot. And I’m confident that, as we gain experience will be able to identify more anomalies, and take advantage of the synergy of having pictures combined engine data. We’ll start this month with data from Cessna 210 powered by a Continental IO-520 and data from a Garmin 275 with a one second sample rate. This is a 30-minute segment of an hour-long flight – displaying only EGTs. All EGTs are a little noisy, but there’s a distinct and recurring pattern in the red trace, which is EGT 1. The original FEVA 1 algorithm scanned for this pattern. FEVA 2.1 uses a machine-learning algorithm designed to spot exhaust valve failures earlier in their demise. Both algorithms spotted this one. That green spot means this valve is too far gone for lapping compound to bring it back. Next is data from a Cessna 320 […]
The Best Laid Plans…
Scottish poet Robert Burns wasn’t a pilot – but his words are good advice for flight planning. This Puzzler is about anomalies that happened in flight. 14 CFR 91.103 directs pilots to become familiar with all available information concerning a planned flight prior to departure. We plan and prepare for what we think and hope will unfold, then we use our training and experience to deal with what really happens. Captains Al Haynes and Sully come to mind. And Apollo 13. It’s a January tradition to restate the mission of these Puzzlers. Our goal is to help pilots recognize data anomalies in real time to make good decisions about the safety of the flight, and help owners to make informed maintenance decisions. This month we’ll look at data from a Cessna 182, A Commander 114 and a Cirrus SR22TN. How often do you review your engine data? If you had a runaway CHT event in flight are you sure you would have noticed it in real time? A CHT excursion would not necessarily lead to poor performance after the event. It might, but it might not. It might just be a warning sign for more serious event to come. That’s […]
The Perry Mason Moment
I was channel surfing recently and landed on a Perry Mason rerun. First of all, it’s one of the great TV themes of all time. Hats off to Fred Steiner. Private Detective Paul Drake just oozes cool with his wild sport coats and convertible sports cars. Della Street was smart with just the right amount of allure. Poor DA Hamilton Burger – like Wile E. Coyote and the Washington Generals – he was destined to be outplayed. Over the course of the hour, Perry would often get foiled – sometimes by Lt. Tragg and sometimes just by events – but would eventually solve the case and get the murderer to admit guilt on the witness stand. When we’re analyzing engine data, most of the time we can spot the guilty party, and confidently make a recommendation for the appropriate maintenance. We know your time is valuable, and we know operating and maintaining an airplane isn’t cheap, so the goal is to only make recommendations that we are confident will solve the issue. Sometimes the analysis team will consult each other, or one or more Savvy account managers to try and get the Perry Mason moment. When we’re all stumped, our […]
Provocation
It’s a logical question. You see something abnormal in the data and you wonder if your powerplant management triggered or provoked what happened. I’d say about a third of the tickets I work include some form of the question. Another popular question is “Should I have seen this coming?” and that’s more or less the mission of the monthly Puzzlers. When SavvyAnalysis Pro opened our doors 10 years ago we saw a lot of high CHTs in initial climb because pilots were leaning aggressively just after takeoff. Apparently they were anxious to set their cruise fuel flow for lean of peak – but doing it too soon. We don’t see that scenario as much these days. Exhaust valve failure is another one where pilots wonder if powerplant management triggered or provoked what happened. The legacy mindset was that high EGTs were causing valves to burn – just keep fuel flow high to keep EGTs lower and you won’t have burned valves. If that were true then we should see a far greater number of burned valves in low compression/higher EGT engines like the Continental O-470-R than in a high compression/lower EGT engine like the IO-520-K. And we don’t. (Mike Busch’s […]
MacGyver
I never watched MacGyver. It’s not like I watched it once and thought it was junk and never went back. I just never watched it. It must’ve been on when I was busy doing something else. But I think it’s cool that his name has entered the lexicon as a verb. People I know from all walks of life use the word when they cobble together a temporary solution to a problem. Sometimes the analysis team gets a scenario that we have to solve as a group. Usually the first analyst to see it will have a theory – or two – and just wants a second or third set of eyes to review the data and the thinking. We want to be confident that when we propose a remedy it, it’s going to be an efficient use of time and money and will resolve the problem. No MacGyvering. First up is data from a Cessna P210 powered by a Continental IO-550TN with a Vitatoe mod, and data from an AuRACLE CRM 2100 with a 1 sec sample rate. EGTs on top, with CHTs and FF below. Cylinder 4 is the obvious problem, but there are a couple of details to point […]
Hiding in Plain Sight
When I taught in the classroom one of my favorite scenarios was teaching software. Typically I would introduce a concept, give examples of its application in the real world, and then show the students how to do it in the software. Inevitably, in a group of 25 students, there would be one or two who missed an important setting or step, and they were stuck. Sometimes the hand would go up right away. Sometimes you would see them look at the screen of the student next to them and try and figure out why that one was working but they were stuck. And then the hand went up. So the fun part as an instructor was the walk up. After a couple of years of teaching, I had seen all the rookie mistakes, and often I could spot the incorrect setting or the missing step before I even got to the student’s workstation. Of course, the real satisfaction in teaching came from the students who breezed through the exercise, and left the classroom knowing more than they did when they arrived. But there was something fun about quickly looking at the display of a stuck student and seeing the clue […]
Sweat the Small Stuff
Years ago my wife got a set of books as a gift. It’s the series devoted to sweating the small stuff in life. I guess the gifter thought she needed help prioritizing. They’re on the bookshelf in her office still shrink wrapped – so much for sweating. I’m not going to read them either, because writing a Puzzler is usually a deep dive into small stuff. Sometimes a small adjustment in cooling baffles can fix an engine that’s running too hot. What’s smaller than the orfice in an injector? But often cleaning one can solve a mixture distribution problem. A small fracture in a spark plug insulator can be the trigger for a detonation event. Airplane maintenance tolerances are often measured in thousandths. We’re all about the small stuff. Let’s start this month with a Cessna Turbo 210 powered by a Continental TSIO–520 engine and data from a JPI 830 with a 2 sec sample rate. Layout is the default of EGTs, CHTs and FF. This is a Savvy QA client. The analysis team supports Savvy Analysis Pro, Savvy Mx, Savvy Prebuy and Savvy QA. The issue was that the pilot couldn’t shut down the engine with the mixture control. […]
Succession
Judging from the ratings, I’m not the only one that just finished watching Succession. I’m an only child, and often wondered what it would be like to have siblings. Granted, it’s fiction, and granted it’s a supremely dysfunctional family, but wow. I’m fine with OC. As I reviewed the candidates for this month’s Puzzler, I noticed cylinders forming alliances, selfishness, pouty moods, tantrums, withdrawal – everything the Roys are famous for. We even had a case of backstabbing sabotage – an exhaust leak torching its downwind sibling. I admit it’s a stretch. The engine is just metal. Not complex like an heir or heiress. If you’ll allow me to torture this analogy a little more, that’s the draw of the show – the myth that if you had stupid amounts of money your life would be rich and full and strife-free. Guess again. It’s the stress the money brings with it that they don’t tell you about. And, back to engines, if you thought that adding bigger cylinders, or electronic ignition, or boost from a turbo would deliver you to the promised land of strife-free power, the data reveals that there’s still conflict in the C-suite forward of the firewall. […]
Better off Without it?
Most of the time engine data is an important tool for helping us with powerplant management during a flight, and choosing efficient options when maintenance is needed. If you’re a regular Puzzler reader, you’ve seen lots of examples of that. But every once in a while, the data is so erratic or mysterious that it can cause distractions or confusion. Every flight starts – or should start – with good preflight planning. For short trips, your planning might start a day or two ahead. For longer trips, you might start checking weather several days ahead, and maybe explore different options for rest breaks and fuel stops along the way. Ultimately all your planning leads to that moment when you start the engine and taxi out for takeoff and encounter the real-world weather and the airplane’s condition. Engine data helps us assess the airplane’s condition. This is taxi-out and runup data from the first 14 minutes of an hour and 25 minute flight of a Piper Saratoga powered by a Lycoming IO-540 and data from a JPI 830 with a 1 sec sample rate. EGTs, CHTs and FF. Nothing special about cursor placement – just getting it out of the way. […]
Engine Data Analysis for Prebuy Exams
In a prebuy exam, the logbooks are the most important item to review. If the logbooks check out ok, reviewing a set of borescope pictures is a good next step. If there are no dealbreakers so far, take a look at the engine data – at least for the last couple of years. When a non-pre buy ticket comes with data from a test profile we’re looking at a specific flight. If we have a question about something, we might look back at a few flights or ahead a few flights for corroboration. But the goal is to take specific measurements and deliver a report using our standard report form. With a pre-buy, we want to look at history and we’re looking for showstoppers. Persistent high CHTs, frequency and length of flights and data reliability as a proxy for attention to maintenance all have a story to tell. If you’re the seller, you want the data to confirm your good powerplant management skills, that the airplane is not a hangar queen, and that when a problem arises it gets dealt with. If your data does all that, your airplane is more valuable than one whose data isn’t as attractive. If […]
Edge Case
After ten years of reviewing engine data, it’s getting harder to hit us with something we haven’t seen before. This month we had the usual contingent of clogged injectors, weak spark and induction leaks. But we had a few scenarios that caused some head scratching, speculating and postulating. Since day one, our goal has been to keep the wrenches in the box unless we’re pretty certain that our recommendation will fix what’s wrong. In other words, we don’t like to guess. This month’s data from a Piper Seneca offered quite a Puzzle. Here’s data from the R engine of a Piper Seneca powered by Continental TSIO-360 engines with data from an EI CGR-30P using a 1 sec sample rate. Most engine monitors for twins give us data for the L and R engines in the same file. This installation gives us separate files for L and R. It’s easy enough to open them side by side for analysis, but that’s why you’re seeing R engine EGTs, CHTs, FF and oil temp – and not the L data. Sure gets your attention, doesn’t it? The cursor is hiding the data just before the runaway, but I wanted you to see the […]
Is Flying Safer Now?
As Savvy Analysis turns ten, I thought I would try and see if the data shows that more engine monitors and more data analysis over the last ten years contributed to fewer accidents attributed to mechanical failure. You would think so, right? Engine data should make it easier to recognize problems, and knowing what the problem is should impact the cost of fixing it – less shotgunning. I turned to the Nall Report which AOPA publishes annually and updates frequently. Nall Reports are archived here. Using data for non-commercial fixed-wing, the number of accidents fell from 1154 in 2012 to 892 in 2020 (the most recent year available). 334 fatalities in 2012 vs 273 in 2020. So that’s a good trend line, although you could argue that COVID had a big impact on data from 2020. Trying to answer my question, in 2012 there were 156 accidents attributed to mechanical issues. Of those, 55 were powerplant issues, with 1 fatality in that 55. In 2020 , there were 153 accidents attributed to mechanical issues. Of those, 77 were powerplant issues, with 10 fatalities in that 77. I don’t want to jump to conclusions based on two data points, and anecdotally […]
Chat GPT
When we started Savvy Analysis Pro ten years ago, we wondered how long it would take before deep learning and artificial intelligence would take over and push the human analysts to the curb. In those ten years, we’ve rolled out Report Cards, Trend Analysis, reports, and three iterations of FEVA reports. Ten years ago we wondered how the computer would be able to identify and ignore bogus data. We’re closer to that now, as Mike Busch explains in his November article for AOPA Pilot. As 2023 dawns, watching Chat GPT explaining quantum physics and writing Haiku poetry, we’re probably a little closer to the curb than ten years ago. The Puzzler was born to examine unusual engine data. It was an homage to – ok, we stole the idea from – Click and Clack on NPR. They asked a question on one episode, then gave you the answer a week later. That format wasn’t going to work. Our format was to display some data, float some possibilities, then explain why one answer was correct, or at least more likely. We didn’t give you a week, you got the answer right away. But you could take as much time reviewing the […]
Declaring an Anomaly
Chapter 6 of the AIM covers emergency procedures, including the difference between distress – like fire, mechanical failure, oil on the windscreen, or structural damage – and urgency – like being lost, low on gas, encountering dangerous weather, or any other condition that could adversely affect flight safety. And 6-1-2 ends with “Pilots who become apprehensive for their safety for any reason should request assistance immediately.” No argument there. If you’re reading this Puzzler I probably don’t have to convince you of the value of your engine monitor. But it does present the pilot with a lot more real-time information to process than the pilots of yore had to worry about. And sometimes you see something that doesn’t look right, even though performance is normal and everything else looks ok. You’re not ready to key the mic and ask for assitance yet, you’re not even sure there’s a real problem. You just know something doesn’t look right. It’s time to declare – if only to yourself – an anomaly. For example, let’s say you’re cruising along and making good time and you notice fuel flow indicates zero. Not fuel quantity – not what’s in the tanks – but fuel flow to […]