Header1200x385

facebook_page_plugin
× Welcome to the CPL Performance question and answer forum. Please feel free to post your questions but more importantly also suggest answers for your forum colleagues. Bob himself or one of the other tutors will get to your question as soon as we can.

How to identify the accurate intersection of ECHO loading chart forward limit?

  • Posts: 31
  • Thank you received: 0

Star Alliance created the topic: How to identify the accurate intersection of ECHO loading chart forward limit?

As you all know, some questions ask us to add ballast to make ECHO back into the forward limit.

However, the line you draw crosses the boundary line of envelope (whick is very thick!) in a poor distinct way. I even can not find the intersection, because two lines almost overlap with each other for nearly 1 cm! But even a few mm can make so much difference!

Can some one help? How to identify the accurate intersection of ECHO loading chart forward limit?I even never make one this question correct……
#1

Please Log in or Create an account to join the conversation.

  • Posts: 2447
  • Thank you received: 257

bobtait replied the topic: How to identify the accurate intersection of ECHO loading chart forward limit?

I agree that is a problem. Now that CASA have introduced 'type in' answers it is more of a problem. Surely CASA should accept the limitations of the chart. It was never intended to give exact numerical answers. CASA wont reveal how much margin is allowed. For the sake of the exam, it may help to use the chart to get a 'rough estimate' of the ballast required and then, using the forward limit formula, compare that CofG position with the calculated forward limit. They should be the same. You can then try it again with another ballast value and try to get as close as possible to the recalculated forward limit. That is nothing like what the designer of the envelope intended.
#2
The following user(s) said Thank You: Star Alliance

Please Log in or Create an account to join the conversation.

Time to create page: 0.094 seconds