Anyone who has worked with a large aerospace component supplier on a fuel measurement or fuel management program knows the experience well. You submit a request, and it routes through a portal. A program manager gets back to you — eventually. You ask a technical question and wait three days for it to reach someone who can actually answer it. Change requests go into a queue. Pricing adjusts at renewal in ways that were not part of the original conversation.
None of it is anyone’s fault, exactly. It is just what happens when a supplier is managing hundreds of programs across dozens of product lines, and your fuel quantity indication system is one line item among thousands.
Working with LMS is a different experience. Not because LMS is trying harder, though they are. Because the structure of the company makes a different kind of relationship possible.
What Sets This Aerospace Fuel Measurement Supplier Apart: You Talk to the People Doing the Work
When a customer has a technical question about an aircraft fuel measurement system at LMS, they talk to an engineer. Not a liaison. Not a customer success representative reading from a product brief. The actual engineer who worked on the design.
That sounds like a small thing. In practice it changes everything. Questions get answered in one conversation instead of three. Problems get diagnosed faster because the person on the call already knows the system. And when something unexpected comes up during integration or testing — as it always does — there is no internal escalation process standing between the customer and the person who can solve it.
LMS engineers have worked on military rotorcraft, commercial fixed-wing platforms, turboprops, experimental aircraft, and UAV applications. When a customer brings a new program challenge, the team has almost certainly seen a version of it before. That institutional knowledge is accessible directly, not filtered through layers of account management.
“You shouldn’t have to fight to get a straight answer from your fuel measurement supplier. At LMS, the people picking up the phone are the people who built the system.”
Decisions Get Made by People Who Care About the Outcome
George and Elizabeth Lamphere have owned LMS since 2005. Before that, George spent years working alongside his father, David, who founded the company in 1991. This is not a management team that rotates in and out on three-year cycles. These are people who have spent their careers building something and whose reputation is tied directly to how every program performs.
That ownership structure has a real effect on how decisions get made. When a customer needs a faster turnaround, or a program requires a design iteration that was not in the original scope, or a fleet sustainment question comes up that falls outside the standard product offering — those conversations happen with people who have the authority to say yes and the motivation to find a way to make it work.
There is no committee. No approval chain that stretches back to a corporate parent. No quarterly earnings pressure driving a decision to deprioritize a smaller program in favor of a larger one. The people at LMS who are accountable to customers are the same people who are accountable for the business. That alignment matters more than most supplier scorecards capture.
The Experience Compounds Over Time
One of the things that distinguishes long-term LMS customer relationships is how they tend to deepen rather than flatten out. Early in a program, LMS is learning the customer’s aircraft, their engineering standards, their documentation preferences, and their internal processes. By the time a system goes into production, that knowledge is embedded in the relationship.
What that means in practice is that follow-on work moves faster, support requests require less context, and the customer is not re-explaining their program to a new account team every eighteen months. The engineers who worked on the original design are still there. The institutional knowledge stays with the program.
For fleet operators and defense program offices managing aircraft over decades-long service lives, that continuity is not a nice-to-have. It is one of the most practical arguments for choosing a supplier like LMS over a larger organization where staff turnover, restructuring, and shifting business priorities can erode the accumulated knowledge that makes support actually useful.
George and Elizabeth: The Business Behind the Engineering
David Lamphere built the technical foundation of Liquid Measurement Systems. His son George and George’s wife Elizabeth built the business around it.
George came to aerospace from a different direction – he ran a successful diner in Vermont for ten years before joining his father full-time in 2000. What he brought was not an engineering background. It was something equally important: an instinct for customer experience, operational consistency, and the accountability that comes from running a business where your customers return every morning and know immediately if anything has slipped.
Elizabeth took on everything the growing business needed — the operational infrastructure that lets an engineering company function like a real business rather than a collection of projects. When they took full ownership in 2005, the decisions they made reflected a clear view of where the industry was heading: ISO 9001, then AS9100 pursued proactively before it became a baseline requirement, investment in the facility, and building a team with a genuine culture around it.
The result is a company that has the technical depth of a specialist and the operational reliability of an organization that has been doing this consistently for over thirty years. That combination is rarer than it should be. And for customers who have worked with both kinds of suppliers, the difference tends to be apparent pretty quickly.
Built different from the start. Still built that way today.
