The Standard for Systems Knowledge

How Much Systems Knowledge Should a Pilot Retain? 

Complex aircraft like the MH-60T can overwhelm an operator with systems detail. Pumps, filters, buses, compressors, sensors, logic — it’s endless. At some point, every pilot asks the same question: 

How much of this perishable knowledge do I actually need to retain? As an Instructor Pilot and Flight Examiner, I keep two principles in mind. 

1. Relevance drives learning. 

Operators are motivated when the material clearly connects to their craft. If the knowledge directly influences how you employ the aircraft (e.g., fly, manage risk, or make decisions) — it matters. 

If it doesn’t, there is other perishable knowledge worth protecting such as procedures, policy, limits, etc. 

Time and cognitive bandwidth are limited. Use them optimally. 

2. Standards are shaped by what we emphasize. 

In our community, standards are not always perfectly defined. What we choose to teach, question, and evaluate becomes the standard over time. 
 
So, here’s the filter I use: 

If you can affect it as a pilot, you need to understand it — for every button, switch, or lever in an aircraft, you should know the basic system logic/function, if there is redundancy, and how system operation shapes normal use and your contingencies during a malfunction. 

If you can’t affect it from the cockpit — it’s “nice to know.” Interesting. Sometimes impressive. But it won’t determine your effectiveness in the aircraft, so it shouldn’t consume disproportionate training bandwidth. 

For example: 

• If you can initiate an automatic approach, you should understand what conditions indicate it is functioning properly. 
  
• If a hydraulic system isolates during a malfunction, you should understand when that isolation occurs. 
  
• If a caution or advisory appears, you should understand what triggered it, and what it implies operationally. 

The specific gas inside a rotor blade? Interesting. 

The indication that tells you there’s a leak/pressure loss in the blade— and what that means for your mission? That’s necessary operational knowledge. 

This trivia series will provide some example systems trivia for the MH60T helicopter that relates to: 

• General system operation. 
• Switches. 
• Levers. 
• Buttons. 
• Knobs. 
• Cautions and advisories. 

The focus will be on things the pilot can affect. The goal isn’t to be the systems hero at a briefing table. The goal is knowledge that translates to optimal performance in the aircraft.