Hi all,

 

I was wondering what your checklist look like?

 

Here is mine. Of course it is simplified (I'm a beginner) and mainly based on the PMDG tutorial flight plus some personal additions.

 

It fits on one page for easy display on my Ipad.

 

I enclosed the template here in Powerpoint format.

 

If want to use it, feel free to change it according to your tastes and needs.

 

Page 2 are personal notes related to my usual flights and home airport.

 

I use the ECL that came with the plane along with some of the flows that are in the manuals. 

My checklist:

 

- daughter is sleeping - checked

- 2 hours of free time remaining - checked

- yoke plugged - checked

- a bowl of milk with cereals - checked and filled

 

The rest of real checklist in my world is not THAT important like the above one.

My checklist:

 

- daughter is sleeping - checked

- 2 hours of free time remaining - checked

- yoke plugged - checked

- a bowl of milk with cereals - checked and filled

 

The rest of real checklist in my world is not THAT important like the above one.

LOL funny but true -captains need feeding and any (kids) distractions need to be put to bed!! I also use the ECL

fly and scan for anything illuminated and then,,,press it 

 

 

Of course it is simplified (I'm a beginner) and mainly based on the PMDG tutorial flight plus some personal additions.

 

Nicely done!  It's always cool to see people creating things to help themselves learn new stuff.  I don't want you to get the wrong impression of real world operations, though, so I'll point something out, and you can choose to use it, or simply ignore me - everyone has their own tastes  :wink:

 

I noticed that your POS INIT workflow includes selecting the AIRPORT and then selecting the GATE.  The gate isn't truly necessary.  Selecting the airport is nice so that you can cross-check the reported LAST POSITION and GPS POSITION, but the GATE feature is a little antiquated.  Before we had reliable GPS (when GPS first came out, error was actually built into civil GPS to give the military a leg up on anyone using it), or used GPS at all, the only way you could provide a position to the aircraft was to use the last position, or type in the gate position.  At some airports, you'll actually see the gate position up on a sign on the terminal building next to the gate name/number.  Now that we have reliable GPS, though, it's not really as much of an issue, and you can ignore the GATE entry and just select the GPS position that it offers.

 

As I mentioned earlier, it's good to verify your position against known sources (AIRPORT, or more specifically GATE), but don't feel like you have to (particularly because most FMS data available to us as simmers doesn't include it).

 

 

 

I also noticed that you're selecting your runway on the ROUTE page.  While it's an option there, it's better left until later when ATC assigns it to you, and even then, it's better to enter it on the DEP/ARR page to ensure you do not get database errors (because runway numbers change over time, occasionally).  The tutorial goes over this in a little more depth.

Nice one! I used to do things like this for my PMDG 747, but then used the PMDG manuals. They taught me a lot...

Thanks all for your comments.

 

Indeed we all have our daily checklist / todo list to accomplish before we can get to the 777 checklist  ^_^

 

Although it is a nice feature, I don't use the ECL otherwise I loose too much time switching views (even with EZDok).

 

Kyle, it's OK. I am not under the impression of the Real World Operations Company :lol: I take it easy. It's always good to hear the options and then pick what seems relevant or best suited to me.

 

Regarding the gate, I don't like to leave a page "unachieved" but on the other hand it is not a mandatory information and you convinced me to leave the gate blank.

 

Regarding the runway, actually I enter it in the ROUTE page and in the DEP/ARR page. Will remember that it's an option for ROUTE .

 

 

Regarding the gate, I don't like to leave a page "unachieved" but on the other hand it is not a mandatory information and you convinced me to leave the gate blank.

One of the pages that is also tricky to fill out is the one with runway conditions (I can't think of the page number, it is after your takeoff REF page.) The issue is that all runways in FSX have 0 slope, and I may be wrong but have the same friction whether wet or dry. So although you can fill it out, I don't know if it has any effect. (Feel free to correct me somone)

Nicely done :-)

 

A few minor things (that might not matter too much in our simming world):

 

- one of the first thing you do normally is check ATIS for weather and runway in use.

so I would put this under point 5 or so.

- under point 7. In Europe every countey has a different Transition Altitude which can be found on the SID plate.

- point 8. untill we have perfomance calculating software all we can do is guess as far as Assumed Temp goes. But I just wanted to point out that the temps you put in here would change for every flight, depending on ambiant conditions and aircraft weight, etc.

- MCP Altimeter - set METAR.....not sure what you mean with this, but if you mean Barometric pressure, then you want to use the actual ATIS QNH.

- point 10. in real life you do not get a clearance to Cruise FL on the ground. So you would set the lowest altitude restriction as published in the SID on the MCP.

Dont want to bust an altitude restriction now do we!

Then you would get higher and higher altitudes, step by step, by ATC (and/or according SID if it has multiple restrictions) till you reach cruise FL. A bit hard to simulate if you dont fly online or with an ATC addon. But at least simulate climbing to the SID altitudes to develop an awareness for altitude restrictions I would say.

- point 11.

Make sure you put the hydraulic pumps to AUTO, not ON!

All fuel pumps on is only correct if the center tank hold 4800KG or more fuel

Also, the transponder is turned on to XPNDR here so ATX can see you moving.

The Cancell/Recall button is clicked at this point also, to make sure no unexpected EICAS messages (problems) show before starting pushback.

- point 13. Dont forget to to turn Engine Anti Ice ON (if icing conditions exist) after the engines have been started.

- point 14. The Runway lights and strobe lights are not turned on untill entering the runway for take off. (you would be blinding everybody else during taxi.)

-point 15. Flaps up....Engine anti ice Auto.

- point 17.

same as for departure, you dont get a clearance to 2000ft from cruise FL.

Also, dont forget that at some places you would fly into a mountain at 2000ft.

Again I suggest you follow (and set in the MCP) at least the STAR altitude restrictions.

Minimums are set to BARO minimums (unless you are doing a CatII or III ILS).

MCP Altimeter - see METAR?

Just for info, Flaps 15 and 25 are normally skipped. You just go from 5 to 20 and from 20 to 30 unless you are at such a high weight that you need those intermediate flap settings. Or if you are landing with Flaps 25 of course.

- point 18.

Hey, the flight is not over yet, lol :-)

Engine anti ice On if taxiing in icing conditions.

start APU

landing lights and strobes off

weather radar off

auto brakes disarm

flaps retract (unless you landed in slush and snow)

transponder XPNDR

 

Oh ps...the engines are still running :-)

 

 

Happy landings :-)

@Wes : I don't know the page you are refering about but I noticed that the friction of parts of some runways are different from other depending on the textures and I have to apply power accordingly to taxi

 

@Rob : thank you for reviewing my checklist items. I am most appreciative.To be honest I am aware of some points you are raising but in my learning process I make some simplifications even if it's not always realistic. The idea is to enjoy each step of my learning so that I get motivated to go further. For example all my landings are AUTOLAND because it is a joy for me to see the aircraft land on its own. I plan to handlfy her in a later stage. But hey all your comments are educational: some points I did not know and other bring new light on my practice.

 

I did not write it on the checklist but I start by checking the DEP and ARR weather in Active Sky Next and choose the runways accordingly. At this time I do not use ATC yet.

 

- Point 7 : transition altitude. Yes you are right, I was lazy and copied pasted the PMDG tutorial (Maldives-Dubai)

 

- Point 8 : Yes I know the temp changes according to conditions and again I took the value of the tutorial. I heard about TOPCAT software but that will be a later investment

 

- MCP Altimeter - set METAR = ATIS QNH. Yes that is what I meant.

 

- Point 10 : cruise FL and alt restrictions. Right. I don't use ATC yet but Radar Contact is on my list. Good advice to fly to the SID restriction to develope awareness. Will do

 

- Point 11 : hydraulics pumps : yes I made a typo error.

 

- Point 13 roger that

 

- Point 14 : Yes i heard that  Runway lights and strobe lights can blind if you stare at them directly for too long. Will change the checklist accordingly

 

- Point 15 : OK

 

- Point 17 : altitude restrictions... yes again a copy-paste from PMDG tutorial flight lol. Interesting info for the flaps skipping. I did not know.

 

- Point 18 : haha again I was lazy!

 

All your comments are a good opportunity to improve my knowledge and practice!

 

Thank you!

I use a complete flow printed on 2 pages, but the checklists are done via ECL.  Will have to re-adapt when FS2Crew comes out.

You are welcome :-)

 

I like the way you are doing things.

Simplifying at first makes perfect sence.

Autoland now, manual flight later, simplified performance and ATC for now...all fine.

 

Maybe you could post your updated flow chart, I am sure others can use it too.

I call it flow chart, because the ECL would be the checklist.

 

One thing, the ECL is a really nice feature.

Does EZDok not allow for keystokes to be linked to a certain view??

If it does, then just assign Ctrl+Shift+1 to a view that looks at the ECL.

All you need to do then is hit those keys.

Assign another keystroke to your normal view, and boom you are back in the Capt (or FO) seat :-)

Or you could click on the lower center display (before you open the ECL) and move (and resize) the popup anywhere you want (even a second display if you have it......or to an IPAD also I think, if you use one of those APPs that extend the windows desktop on an IPAD).

 

I like the way you are doing things.

 

Thanks!

 

Maybe you could post your updated flow chart, I am sure others can use it too.
I call it flow chart, because the ECL would be the checklist.

 

Sure, I will post a new version as soon as it is ready.

 

One thing, the ECL is a really nice feature.
Does EZDok not allow for keystokes to be linked to a certain view??
If it does, then just assign Ctrl+Shift+1 to a view that looks at the ECL.
All you need to do then is hit those keys.
Assign another keystroke to your normal view, and boom you are back in the Capt (or FO) seat :-)
Or you could click on the lower center display (before you open the ECL) and move (and resize) the popup anywhere you want (even a second display if you have it......or to an IPAD also I think, if you use one of those APPs that extend the windows desktop on an IPAD).

 

I do not have a second monitor but I have EZDok and it allows indeed to assign a view to a keystroke. I have 5 cockpits views set that way (Captain, left MPC, right MCP, CDU and Overhead). I will think about an ECL view. Even if it's fast to change views you have to do an action, then swithch back to the ECL, tick the item in the ECL, then do the next action etc. In my case it takes more time than reading my paper flow document ;-)

 

 

I have created my own dynamic flow charts based on an excel sheet. I have it available on my notebook while flying fullscreen in fsx. Works good for me, although I am not sure the flows are super realistic. :ph34r: