Complaining about “in flight” or “cloud” or “serverless” even though everyone understands what those terms mean seems like bikeshedding at its worst.
I try not to make others feel stupid just because they don't know the keywords. Sure it would be easier and faster to talk but if I'm not understood it's meaningless.
Far too often I hear people argue "it's not in the cloud, it's on a server" which makes people think it's hosted on-prem on a server that we own and control and maintain, but it's not. It's on someone else's network, on someone else's server, a server that they own and control and perform the maintenance for. But that's a really long winded response, so luckily we agreed on a single word to represent that concept: cloud. Like it or not, words have meanings and those meanings have definitions. If someone isn't likely to understand the word, explain it using its definition. Don't just unilaterally switch to a completely different word.
My CEO might not know what "serverless" means, but once I explain it using its commonly accepted definition she can now read the commonly accepted word in a trade magazine and understand what they're talking about. Otherwise she'd never know to link the word to its definition. That's the basic concept of language.
Running already is a metaphor for what a CPU does. Do you object to that, too?
I don't actually object to the "Flight Recorder" either, I just find it to be a weird name that I probably wouldn't have picked, hence my comment on it.
We're not "using 'flight' as a metaphor for the runtime of our code".
We just adopted wholesale the terms "preflight check" and "flight recorder".
And at least the former has been adopted in several other industries/contexts.