Originally Posted by
ZippyNH
The purpose of systems knowledge beyond just being able to reset a breaker is to understand the possible failure modes, and to give you the ability to speak with MX about EXACTLY what is happening, so the problem can be fixed the FIRST time....
Sometimes an incorrect indication is more dangerous than a system not working, and knowing a system and what can happen when it fails is important.
A simple, it doesn't work write-up is ok, but to understand the system in enough detail to have a discussion about it with a mechanic is invaluable in getting the item fixed, and back in service.
Additionally, a deeper understanding of a particular system will give you more insight into how it MAY interact with different systems....
Under 135, you may not have a mechanic at every stop, and on some routes, it possible to go 5 stops before going to a base with a company mechanic.... knowing the airplanes systems in detail so you can pass the correct info to mx control to get a part and a mechanics enroute in an AOG situation while on a scheduled route is very important.
135 is NOT just sit down, strap in and fly job like 121...that's why some people LIKE 135...There is judgement involved...it's not flying with a yes/no flowchart.
It's going out, and as the the previous posters have shown, running numbers, doing charts, math, weather, flight plans, etc, with some help from dispatch, but understanding they don't DO IT FOR YOU LIKE 121.
You are often showing up at an FBO, with a suitcase and a "mission", then figuring out how to accomplish the trip safely. It may include getting a plane hangered or DEICED, fueled, limiting cargo weight if needed, loading, etc....
It's hands on... flying is just ONE of your duties.
Yes, you do have support of a company, dispatch, and previous captains on the route, but it not JUST FLYING.
I understand the job of the P135 as far as the doing everything on your own - I've been flying under P135 for the last 8 years.
I don't consider myself a system guru by any means, some of the guys I fly with are systems guru.
I've not seen them as having been able to do anything more than I have been able to do in regards to helping maintenance diagnose a problem
any better to be honest.
Now I agree that being able to tell them some of the troubleshooting that I may have done or at least having the experience to know what to look for and take some pretty good notes so when they may ask 'well did you try this, what was this reading, was this matched. etc.... you have the answers rather than the 'it just didn't work' answer as you alluded too is helpful; but I have this much experience without being able to build the system.
Some of this also comes from my military community comes from the attitude of 'if you can't affect it from the cockpit, then you don't need to know about it'. Of course that community also spends A LOT more time on the mission than the airplane necessarily too - - - LOTS AND LOTS AND LOTS of mission stuff to worry about.
I continue to try and learn more and more about the inner workings of the airplane but it doesn't come to me naturally as I am not much of mechanical/systems type of guy (and I'll even add in UNFORTUNATELY) which is why I still after 8 years listen intently to the days in the classroom during recurrent and fly a lot of QAFs with the test/maint./engineering guys who do know A LOT about the inner workings of the mighty King Air 300 in my case.
...flying is just ONE of your duties.
Try having a MISSION on top of everything else you listed
