At risk of sounding like a complaining millennial... a few years ago my squadron went through a safety workshop/seminar. We were in transition to our neglected Rhinos at the time (which I should probably add some stories about in the "Should I take that aircraft" thread for you guys) and my Training Officer brought up a question to the O-6 running the event. "How can we expect to be tactically proficient on cruise when our jets are barely flyable, we regularly face in-flight emergencies, and we're unable to achieve the tactical hard deck?" The O-6 essentially said "deal with it." Well, this Captain was wearing a 3000 hour patch and had been in the reserves since he was a JO. He proceeded to tell us how his reserve squadron had little notice that they were deploying and that they made it happen and they did well on deployment. He looked at our TO and said "you need to figure it out." Nevermind the fact that his squadron was filled solely with O-4s and O-5s with tons of experience and flight time. The complete disconnect was appalling, to say the least.
This is not an isolated event, and I bring that story up to highlight the tone-deaf approach of senior leadership...
A little devil's advocate here...
1) This reserve O-6 is doing a safety seminar. His job isn't to solve fleet manning/maintenance/funding problems. He's probably heard this "question" (in quotes because it's really just a gripe to a senior officer) a billion times over, there's very little he can do about it, and he doesn't want his seminar to become derailed into a griping session.
2) Somewhere along the lines in his career, an O-4 should have learned that you don't pass problems up to your chain of command, but solutions and communicate any shortfalls you
need addressed to succeed. I emphasize the word need because needs are things like manning shortfalls that make the mission unachievable, insufficient hours to maintain pilots proficient (proficient in terms of established fleet standards that keeps you authorized to continue flying, not proficient in terms of what a JO decided what it
should be), etc. I would expect any senior officer to be a bit testy toward me, at the very least, if I just threw a bunch of problems up at them.
3) When the details of what you need to maintain proficiency or get aircraft fully functional are not communicated, gripes about flight hours come across simply as complaining to your superiors that you don't fly enough as you'd like to, particularly if there are other options available like simulators to maintain that proficiency for a fraction of the cost. I suspect that any good senior officer wants you to fly and train in the cockpit as much as he can afford, but at the end of the day if you have met the fleet standard that someone above his paygrade decided is "good enough," then there's no magic wand he can waive to get you more than that.
I highlight these for two reasons: first, because it's easy for a relatively new officer to view the interaction like you did when there's probably more going on than another "tone deaf senior officer," and second because if you want to get traction on flying more or maintaining aircraft in better condition, there has to be a lot more of starting with an end state that solves a problem based on objective data (more flight hours are a means not an end), layout a few paths to get from A->B, and in there show how more [insert resource] is imperative to achieve that goal. There also has to be the understanding that if the problem you are trying to solve is not a requirement, you are probably going to get told no to getting more resources. Otherwise, it's all going to sound like another officer complaining to his boss that he doesn't fly enough.
When an O-6 says "figure it out," he means all of the above, and he expects that the O-4 knows that without a lengthy explanation.