It is a good point, or you wouldn’t have asked in the first place. I thought if I stayed quiet and read your guide I might learn something!
@smokinhole has already pointed out that the word “philosophy” is not all that applicable to Boeing (I can’t remember ever seeing it in a 737 manual, IIRC), but it does tend to litter Airbus publications.
Of course, it is your call, but I’d personally suggest using the FCTM for information, as a primary source for any guide, followed by QRH for some operational stuff. Some important points.
A general to specific method would probably be appropriate.
Airbus bases their “philosophy” on four “Golden Rules” (used to be more, but they cut them down recently). I’d state them. I’m not looking for them right now, so here they are off the top of my head (so order and specific words might not be exact)…
- Fly, navigate, and communicate, in that order (fairly straight forward, huh?)
- Use the correct level of automation for the task at hand.
- Know your Flight Mode Annunciator at all times.
- If things on automation are not going as expected, take over immediately.
That last point, LOL! I’ve watched friends on the VS let autopilots do the oddest things to their flight trajectory, without disconnecting it, so that one is not so “doh!” obvious, it seems, to some sim players.
When familiarizing readers with the panels’ controls, also try to emphasize flows. The QRH Normal Procedures will help here, too, and expanded definitions can be found in the FCOM Normal Procedures section.
There’s a tendency I have noticed with sim players to dive straight into the MCDU and get route programming. Yeah, fine, it has probably got its attractive, but it is pointless if you don’t know where you enter the loop in executing it. There’s an Airbus process for this, and the aircraft is designed to be flown as much as possible on automation. My point; avoid the trap of making a guide into an advanced instruction read on MCDU programming.
As much time as is given to the MCDU should also be given to;
- FCU, with a clear description of the “Managed” and “Selected” levels of automation.
- FMA, including the significance of its color coding.
- FD and FPV.
- ND symbology.
- Warnings/Cautions levels, with associated visual and aural annunciation.
Some time can be given to Normal, Alternate, Direct, Mechanical Back Up, and Abnormal Attitude Flight Control Laws, but save a brief description that protections exist, what they are, what they do, and that they degrade as certain associated systems fail, I don’t feel a great big FBW description is essential. Just enough about each protection so that a player, for example, understands what has happened if they invoke Alpha Floor, and how to get out of it, would probably suffice.
Memory items (there are not many) and Limitations, of course (FCOM).
Finally, there is also the use and programming of FLEX T/O thrust. A small briefing on flat ratings, TFlexMax, and TRef might be in order. There’s a really nice little chapter about Thrust Ratings in the Performance section of the FCOM, which would be a fine reference.
I do believe the FCTM, QRH, and FCOM are available in generic form on the internet.
I don’t want to rabbit on for ever, and I’d quite understand if you think some of this is superfluous to a quick start guide. These are just my thoughts, as you asked for them. Hope it helps, and my thanks for your attention…