ATR FUN facts - Performance

今日講小小關於performance

大家都知每個takeoff同landing都唔同。

Airbus compute takeoff同landing data就比較簡單， 有個flysmart app喺部ipad;

入哂d data入去，個app就會generate d performance data俾我地用。

而ATR就唔係咁簡單， ATR72-500 cockpit裏面有三大本FOS chart.

Based on唔同機場，唔同runway, 唔同condition去揾performance charts.

例如 要operate一個CEB-MPH (長灘島) flight; 我地depart 之前,要問dispatch攞當地最update ge weather report; 因為有D runway 比較短. 而Caticlan 就係出名short runway (當時得950m X 30m, 仲要runway 24 前面有d terrain)

(而家d terrain 鏟平左 去extend 條runway, 所以依家airbus 都去到) (小小離題)

Back to performance~

出發前, 我地要based on 當時weather condition, compute max landing weight; 再compute個payload; 所以有時人飛左去，d 行李cargo就之後先到。

如果唔好彩, Compute 左dry runway (due to current condition), 但係飛到之後 wet runway, Landing weight 可能會exceed Wet runway ge MLW; 之後就要無奈divert Kalibo.

Takeoff performance 就再麻煩d~ E.g. Caticlan 雖然得一條runway(rwy06/24), 每條最小都4 版 takeoff performance. (RW06 90%/RW06 100%/RW24 90%/RW24 100%) 如果d runway有intersection departure就再多d~ 我地會base on weather condition 用100%chart 去揾max takeoff weight 再determine max. Payload. 攞到loadsheet之後，compute 個actual takeoff weight；睇下90%thrust夠唔夠power走。 有好多時候臨door close轉風 轉runway, 之後又搞餐死~ 所以用FOS chart 計performance, 有時departure仲麻煩過arrival~