Let’s pick this up right where the regulation leaves off — Page 1, Lesson 9

Let’s pick this up right where the regulation leaves off. We’re inside the European operational rules for mass and balance, and we’ve just covered the standard mass tables — Tables 1, 2, and 3 — which give you the default passenger and baggage masses you may use. Now we’re dealing with what happens when those standard values don’t fit reality. The first point, paragraph (g), is about an operator who wants to use ard mass values — I think that’s a typo in the source for "standard mass values" — other than the ones in Tables 1 to 3. If an operator wants to deviate from those published tables, he must do three things. First, he must advise the Authority — that’s the national aviation authority — of his reasons, and he must gain its approval in advance. So this isn’t something you can do after the fact; the approval has to come before you use the revised values. Second, he must submit for approval a detailed weighing survey plan. That’s a formal document describing exactly how he intends to weigh passengers and baggage to gather his own data. And third, he must apply the statistical analysis method given in Appendix 1 to OPS 1.620 (g). That appendix prescribes the specific statistical technique he has to use to turn his raw weighing data into revised standard masses — it’s not a free choice of how to crunch the numbers. Now here’s the key limitation. After the Authority has verified and approved the results of the weighing survey, the revised standard mass values are only applicable to that operator. They are not transferable to any other operator. And even for that operator, the revised values can only be used in circumstances consistent with those under which the survey was conducted. So if you surveyed, say, a particular route or a particular season or a particular aircraft configuration, you can’t apply those masses to a different set of circumstances that the survey didn’t cover. There’s also a safety floor built in. Where the revised standard masses exceed those in Tables 1 to 3, then such higher values must be used. So the regulation never lets you use a lower value than the table just because your survey came out lower — if your survey says the masses are higher, you must use the higher ones. The higher value always wins. Now let’s move to paragraph (h). This is about a significant number of passengers whose masses, including hand baggage, are expected to exceed the standard passenger mass. If an operator identifies such a flight, he must determine the actual mass of such passengers — and he has two options: by weighing them, or by adding an adequate mass increment. So you either physically weigh those passengers, or you add a safety margin on top of the standard value to cover the expected excess. Paragraph (i) is the same logic applied to checked baggage. If standard mass values for checked baggage are used, and a significant number of passengers check in baggage that is expected to exceed the standard baggage mass, then the operator must determine the actual mass of such baggage — again, by weighing or by adding an adequate mass increment. Finally, paragraph (j) is about communication to the flight crew. An operator shall ensure that a commander is advised when a non-standard method has been used for determining the mass of the load. And critically, this method is stated in the mass and balance documentation. So the commander — the captain — must be told, in writing, that the load mass was determined by a non-standard method, and the documentation must say exactly what that method was. That way the commander knows the load figures he’s working with weren’t derived by the standard tables. So the whole structure here is: the standard tables are the baseline, deviation is allowed but only with prior Authority approval, a formal survey plan, a prescribed statistical method, and the results are locked to that operator and those circumstances. And whenever reality is expected to exceed the standard, you must either weigh or add an increment, and the commander must always be told in the documentation when a non-standard method was used.