Latest / The Operator's Manual with Fexingo: Daily Decisions, Tactical Wins, and Business Execution / How One Airline Cut Fuel Costs 12 Percent With One Data Feed
Transcript
- Lucas: So this morning I want to talk about jet fuel. Specifically, how one airline cut its fuel costs by 12 percent with a single data feed. Luna: Twelve percent — that's huge. Most airlines are scrambling for fractions of a percent. Lucas: Right. The industry average for fuel optimization programs is maybe three to five percent. This carrier got double that. The airline is Alaska Airlines. And the change wasn't a new plane or a lighter seat or a different engine wash. It was a real-time weather data feed piped directly into their flight planning system. Luna: Wait — they weren't already using real-time weather for flight planning? Lucas: They were using forecast data, like every airline does. But forecast data is averaged over time and space. What Alaska did was buy a feed of actual — not forecast — wind and temperature data at multiple altitudes along the route, updated every few minutes. And they fed that into their optimization engine to pick the best cruise altitude for every leg, in real time. Luna: So instead of flying at a fixed altitude based on a forecast, they're constantly adjusting based on what the wind is actually doing. That makes a lot of sense. Lucas: Exactly. And the numbers are striking. Over a year, they saved about 450,000 gallons of fuel, which at today's prices is roughly 1.2 million dollars per month. Annualized, that's around 14 million dollars. And that's just from the altitude optimization piece. They also used the same data to optimize routing — picking paths that take advantage of tailwinds and avoid headwinds more precisely. Luna: Combined, the total savings was what, around 42 million per year? Lucas: That's what they reported. A 12 percent reduction in fuel costs per flight, across their entire fleet. And the implementation cost was relatively small — a software integration and some pilot training. No new hardware. Luna: It's a great example of how a very targeted data source can unlock savings that were already there. The physics hasn't changed. They just got better at reading it. Lucas: And that's the thread I want to pull on today. How one operational change — adding one data feed — creates an outsized result. It's the kind of thing that feels obvious in hindsight, but almost nobody does it. Luna: Before we go deeper, I have to say — this show is ad-free and listener-supported. If these conversations have helped you think differently about an operation you run or work in, you can support us at buy me a coffee dot com slash fexingo. It's a simple way to keep the episodes coming without sponsors. Lucas: Appreciate that. And we mean it — every contribution goes straight into keeping this independent. Now, back to why this works. Luna: So what was the psychological or operational barrier that kept other airlines from doing this? Lucas: Great question. I think there are two. First, the data feed itself. Real-time wind and temperature data at altitude is not cheap. It comes from weather satellites and aircraft reports — it's a subscription service from companies like The Weather Company or Spire. For a long time, the cost was seen as prohibitive for something that 'might' save fuel. Luna: But Alaska did the math and realized the potential savings dwarfed the subscription cost. Lucas: Exactly. The feed cost them around half a million dollars a year. They saved 42 million. That's an 84-to-1 return. The second barrier is cultural. Flight planning has been done the same way for decades. Pilots are used to filing a flight plan with a fixed altitude, and changing that mid-flight requires coordination with air traffic control. There's a comfort in predictability. Luna: So Alaska had to change that mindset. How did they sell it internally? Lucas: They ran a pilot program on a subset of flights. They showed that the optimized flights burned less fuel without any increase in delays or safety incidents. Once the data was clear, the culture shifted. Now it's standard procedure. Luna: It's a classic case of 'measure what matters.' They measured actual wind and temperature, not forecast. And that allowed them to optimize continuously. Lucas: Right. And this isn't just for airlines. Any operation that relies on predictions — demand forecasting, delivery routing, energy consumption — could benefit from shifting from forecast to real-time data. The principle is the same. Luna: But there's a catch, right? Real-time data is noisy. You can over-optimize and make things worse. Lucas: That's a fair point. Alaska handled it by using a rolling average of the data — not reacting to every gust, but updating the plan every 15 minutes. They also built in thresholds. They wouldn't change altitude for a benefit smaller than a certain amount of fuel. So they smoothed out the noise. Luna: Smart. So it's not about raw real-time data, it's about the right signal processing and decision rules. Lucas: Exactly. And that's the operational nuance that separates a 3 percent saving from a 12 percent saving. It's not just the data — it's how you act on it. Luna: So what's the one takeaway for a listener who doesn't work in aviation? How do they apply this? Lucas: Pick one variable that drives cost or waste in your operation. Ask: are we using forecast data or real-time data? If it's forecast, what would it take to get real-time? Then run a small test. The barrier is usually not technical — it's the assumption that real-time is too expensive or too complex. Alaska proved otherwise. Luna: And the ROI on that test might surprise you. Thanks, Lucas. Lucas: Thanks, Luna. That's it for today. See you next time.