× 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.

Gusting wind and Takeoff Charts

  • Flyingpom
  • Flyingpom's Avatar Topic Author

Flyingpom created the topic: Gusting wind and Takeoff Charts

There is a question in the cyber exams that looks requires me to use a Gusting wind.

"You arrive overhead Wlycheproof . wind is 260/20 G25. CW limit for each is 20Kts"

I used the mean wind only ( i.e 260/20 ) in the calc but was incorrect.

In terms of using wind for calculating landing or takeoff performance charts can you explain how I use the Gust Factor e.g

1. If i have a wind of 220/10 G 25 and I am using this to calculate a landing distance to I use just the 10kts or do I average the amount between the mean wind and the gust factor??

So far I have been ignoring the gust factor which seems fine if you have a headwind ( as you take the worst case i.e less HW ) but in the case of a cross wind if I take just the mean wind then I could exceed the CW limit ( in this case for echo )

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

  • Posts: 1914
  • Thank you received: 99

bobtait replied the topic: Re: Gusting wind and Takeoff Charts

You should always take the worst case. For a crosswind situation, you should really get both the headwind and crosswind component. Use the maximum gust value when considering the crosswind because it is possible that that may happen just as you are landing. If that makes the cross wind component go above the maximum allowable cross wind, then you will need to use another runway or carry an alternate. Use the lower value when you are considering the headwind component for the same reason.

The lower value is actually the Met Man's average of wind strength. You will never have to take an average between the lower value and the wind gust value.

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

Time to create page: 0.361 seconds