a flightplanning example
You asked for it, so here comes a #weatherwednesday #flightplanning example!
For a general overview, I checked satellite images and SIGMET against today‘s North Atlantic Tracks (A). After a glimpse at the HIL (hold item list) I knew my #plane was fully fit for #flight (B) – but that particular #aircraft was not PBCS (performance based communication / surveilance) certified, so I wouldn‘t be able to plan tracks S/T/U.
Next, I checked NOTAM and #airport weather for departure, destination and possible Alternate #aerodrome (C) – eventually selecting CGN as 1st ALTN (D), given all operating minima were met (D).
After adjusting the ZFW (zero fuel weight) and setting the CONT (contingency fuel) policy, I performed a brief pre-calculation of take-off / landing performance, finding no restriction.
Now, it was route planning time!
I routinely calculated a minimum fuel, charge, time track, plus the available NAT tracks (E). Murphy‘s law struck: most efficient routes were tracks Y -Z…which looked fine on the significant weather chart (SIGWX, E). However, once again weather didn’t stick to the forecast, and thunderstorms with tops above #flightlevel 400 (B) affected those optimum tracks.
I quickly ruled out a routing slightly further north, as severe turbulence was forecast around Newfoundland (see E). A routing along the east coast and a northern track proved some 30 mins longer (let alone the additional fuel/cost).
So I tried some options further south – and there it was: the best alternative I‘d get! At just some 3-5 mins slower (G), the red route (also shown in E) was south and clear of both tracks and thunderstorms (F) and turbulence.
I checked on possible enroute NOTAM/restrictions (none) and adjusted the flight profile to avoid the tropopause (as this tends to be bumpy; H).
Then, I released the #flightplan, attaching some #briefing remark for the #pilot and the NAT track message.
So all done? Well, no – there was another Florida #flight waiting to be planned 🤷🏼♀️
#flightplanningissexy #ilovemyjob #flying #avgeek #aviation #lovemyjob #flightdispatcher #dispatcher #dispatcherproblems #aviationlovers #dreamjob
This little flightplanning-article was written by Kirsten, working a a flight operation officer in FRA