Flightplanning

Flightplanning is a rather complicated job, where several conciderations must be made:

  1. Finding the route from departure- to destination-airport
  2. Checking of the weather
  3. Determining a proper alternate airport
  4. Finding the required amount of fuel

I will go thru each item with you and give ideas as how you can implement this in your planning. For further explanations consider visiting my homepage at http://users.cybercity.dk/~bcr4637 , where the "MyWay"-series goes a bit deeper into this topic. One of the keypoints is to get the information such as charts, description of procedures, weather etc. Check the Planning Section.

Charts for this flight can be found at:

EGKK: http://www.ais.org.uk/aes/pubs/aip/html/egkk.htm (login needed), 
LFML: http://neige.fleurb.jmsp.net/aip/enligne/METROPOLE/AIP/index.htm#TopOfPage 
Enroute: https://164.214.2.62/products/digitalaero/terminals/enroutelist.cfm?charttype=enroutechartscur&country=ename (H-6 and H-7).

As an example I'll plan a flight from London/Gatwick to Marseille - Flight EV.1601. The flight is operated with a Boeing B737-800 (or B738 in short) with departure from London at 06:40 and arrival at Marseille at 08:20. The time is given in UTC - not local time - and is written 0640Z and 0820Z.

1. The route

When you use the Pegasus FlightManager, you get a recommended route. It is written like this:

BOGNA UA1 XAMAB UL612 MOU A§ MTL (The "§" being an error in Pegasus)

You may wonder, why the route apparently doesn't begin at London/Gatwick (EGKK), but at BOGNA. The reason for this is, that the route is divided into several segments. Normally we have 4 segments:

  1. Departing (via vectors given by the AirTrafficController or via a SID)
  2. Enroute
  3. Arrival (via vectors or a STAR)
  4. Approach (the final into a specific runway at the airport.

The route you should file is the ENROUTE part of our route. The rest depends on which runway you depart from and lands on. This is determined by ATC according to wind, noise, aircrafttype and time of the day. As you have no influence on  this, you can/should not include runway(s), SIDs and STARs in your flightplan.

In our example BOGNA is the endpoint of our departing-segment. How we get there is up to the controller. From BOGNA we fly on an airway called UA1 until we get to XAMAB. There we enter airway UL612 and follows this to MOU, which is a VOR (navigationradio) and finally we use A§ to MTL, which also is a VOR. MTL is the startingpoint of the STAR.

Unfortunately this route is not valid, as the routestructure in Europe has changed since the route was incorporated in Pegasus. Therefore, I recommend that you use online resources to get the route and check their result with Pegasus'. However, the idea is the same:

Now let's have a look on the result you get, if you use routefinder.

Insert the ICAO code for London/Gatwick (EGKK) and Marseille (LFML).

Insert between which Flightlevels you want to fly (FL290 and FL410)

Restrictions (RAD and CDR) can be omitted, but I usually mark them.

Also I choose not to use the latest database, but one which is incorporated in my planes FlightManagementComputer.

Click on "Find route" to get the route.



You then get the following result:

 

The plan is divided into 3 parts:

The route from fix to fix until you get to your destination with distancies and airways.

The fixes position and track and distance between them. And for radionavigation-aids you get the frequency.

Finally you get the Flighplanroute = the route to send to the ATC.

 


From this you can see, that the route is a bit changed, due to changes of the airwaystructure after Pegasus was made.

An other ressource on the internet is Eurobook, which also has a routedatabase. Eurobook gives the same result as the above, but also has a route using SFD as endpoint of the SID.

The result to enter into your flightplan is thus:

BOGNA UN615 XAMAB UL612 RESMI UM728 LERGA UY30 MTL

[The Weather]