I'm indeed trying to familliarize myself with the airports I'm using frequently, but EHAM is a second choice, because I had a lot of trouble finding charts for EHEH, but I found them now and starting to see the picture. Think I'm still a bit hessitant to trust myself, since this is all new, hehe. ;)

 

Thanks a lot guys! :D

No problem. I think I know most of the EHAM procedures. I also have charts for EHEH, EHBK and EHRD. If you have questions, PM me and I'll see if I can get them answered.

 

Cheers,

I'm trying to fly a route between EHAM and ESGG. I used vroute to find my route and it came up with: ANDIK UN873 TUSKA VES N873 LOBBI

Everything seems to work, up to the point my FMC gives me a warning: Unable 220 kts at EH037

 

This happened a few times now, that I find I get errors in the FMC that arent covered by the explination in tutorial #1. How do I know how to fix those errors, while I'm still at the learning stage of that tutorial? If I just ignore the message, I cant actviate the VNAV and the speeddisplay gives a message: NO VSPD

I've been trying to find help in the manuals, but there I cant find an index where I can look for keywords and randomly looking through the 4000 pages of the manuals hasnt helped me at all.

 

And this is one example, so its not how to fix this particular one, but how to know how to find and fix errors in the route in general, that arent mentioned in the tutorial.

 

I notice there's a huge gap between the lessons I've learned from flying the native 737 from FSX and the PMDG, isnt there a way to close this gap step by step, instead of all at once? From an earlier question I understand I can fly the PMDG the same way as I'm used to from the native 737, with the native flightplanner, but the first important thing I'm missing is the native GPS I normaly use, so I get stuck there right away...

Since the gap between what I know from FSX and what I do with PMDG is so big, I dont understand a major part of what I'm doing and what is happening, so basicly, what I'm doing is repeating the tutorial #1 with different route data. This of course will result in a situation where everything that happens that isnt explained in the tutorial is gonna give problems.

Unable 220 kts at EH037

 

Look at the chart. At EH037 your speed must be at 220 or below so all you have to do is enter 220B/ at EH037.

 

 

How do I know how to fix those errors, while I'm still at the learning stage of that tutorial?

 

FCOM11.60.1 - 11.60.26.

 

NO VSPD

 

V1 and Vr are not selected.

 

I've been trying to find help in the manuals, but there I cant find an index where I can look for keywords and randomly looking through the 4000 pages of the manuals hasnt helped me at all.

 

Just enter the messages you see and you would definitely get the answer. Search is a very good thing if you know how to use it.

It also very good to understand the structure of FCOM and FCTM.

Hmmm, On your chart the speed restrictions are pointed to a specific place by the text balloon, at mine they dont, so I have to guess where those restrictions point to.

I'm starting at runway 18L and am using the current chart of the Dutch VACC for that runway. I see a route with 220kts restriction going east direct to EH024 and I see a restriction past EH073 going south for either VALKO, LEKKO, or both, but I cant tell for sure. But there's no route pictured between the runway and EH037 and none between EH037 and EH024 and there are no restrictions given for either one of them. Here's the chart:

 

http://www.ais-netherlands.nl/aim/120419-120531/eAIP/html/graphics/eAIP/EH-AD-2.EHAM-SID-18L.pdf

 

About the NO VSPD, I was pretty sure I got the V1 and VR activated, but I tested again and indeed they are activated and I still get the NO VSPD in yellow along the speed indicator.

 

About that manual. Let me start by explaining a bit about concentration dyslexia, if I cant draw a picture from the words I read and picture in my head what is happening along the way, the words dont mean a thing to me, they're simply not processed. Also, while reading I get past so many terms and phrases I never needed in FSX, that with every sentence I read, I have to stop to search for the meaning of the terminology used, resulting in the fact that my focus is divided over so many different pages ánd the search for the right explanations, that I cant manage to concentrate on any of them anymore, so I cant draw the picture in my head, I dont understand whats happening between the parts of the picture and it only ends up with frustration.

Then, as far as I can make pictures of the smaller parts of the whole, for example, one of the solutions for a wrong database entries:

 

"Clear the message, delete unneeded supplemental flight plans and re–attempt entry."

 

From this I can draw a picture in my head of what to do and I do understand what it tells me, of course, but FSX never thought me anything about how to recognize what might be 'unneeded', or what might be 'supplemental', so this still doesnt help me recognize which parts of the data should be altered. And this 'lack of information'-error is just one of many I pick out already, when simply glancing over the pages 11.60.1 to 11.60.25...

 

At age 12, I was reading manuals for high-end studio equipment, written at a university skill-level in a language that is not native to me and at that point, was not thought to me in school yet, and I never had any difficulty with those, EVER. But this manual, seriously, is written worse then the consumer manual of my TV... This is not written for people who think visually (If my translator gives me the right phrase for 'beelddenken').

For several days already I notice my autism is starting to get provoked and besides this draining my energy in a huge way, this is starting to get me stressed out. This is no fun and this is not relaxing. I give up. The lack of a proper written manual, thats conform with an HSP way of visual thinking (as is needed for over 20% of the people at this time), and that matches the lessons thought by FSX is making this impossible for me. This is written by an unprofessional writer who is not up to date on how to write for people with a visual way of thinking. I'm sorry to say, but this package should have come with a warning that its not suitable for people dealing with specific handicaps, since this does not comply to the rules/laws that anything that is public should be accessible for people with a handicap.

 

Let's just stick to flying this aircraft the way FSX thought me, if someone would be so kind to tell me how to call up the standard GPS, so I can start flying it with the FSX flightplanner and ATC, as I'm used to and leave the FMC completely out of the picture. Unless there's a proper manual this isnt gonna work for me.

 

Sorry for wasting your time.

I understand your problem, i'm sorry this is the most i can do for you.

 

Jeppesen charts are good because they made for lots of airports around the world. And you don't have to look for the description of them for every country you fly and serch AIP of this countries.

I have checked my chart and easily see that 220 is the maximum speed for first left turn. After that you can accelerate.

 

I also found text pages.Here is description: http://www.ais-nethe...ndex-en-GB.html

In jeppesen chart this description nicely included in the bottom of the page. In AIP in takes minute or two to find them.

 

Track 183° MAG. At 3.1 SPL turn left (turn MAX 220 KT IAS) to track 093° MAG. At PAM 226 turn left to intercept PAM 220 inbound PAM VOR to intercept PAM 015 to ANDIK (25.2 PAM).

RNAV: THR 18L / EH037 (MAX 220 KT IAS) / EH024 / PAM / ANDIK

Coding advice B737 according to results of PDT trials:

RW18L / DF (EH037) E 220 / TF (EH024) E / TF (PAM) V / TF (ANDIK) EE

What is often the problem when you get an UNABLE XXX KNOTS AT ABC message is that the restriction is to be at or below a certain speed, but in the FMC it gets entered as a restriction to be at exactly that speed.

 

In your example, when the FMC reads 220 the plane will try to be at exactly 220 knots at that point. If that's just after take-off for example that might be impossible, since you can't accelerate that fast. Simply change the 220 into 220B (telling the plane to be at 220 knots or below) and the problem is solved.

 

Coming in to EHAM there is often a similar problem when one of the waypoints has a 250 or below restriction. This is read in by the FMC as a restriction to be at exactly 250 knots, which conflicts with the overall default speed limit of 240 knots below 10,000' in the FMC. Again changing the 250 into 250B solves the problem.

Let's just stick to flying this aircraft the way FSX thought me, if someone would be so kind to tell me how to call up the standard GPS, so I can start flying it with the FSX flightplanner and ATC, as I'm used to and leave the FMC completely out of the picture. Unless there's a proper manual this isnt gonna work for me.

I hadn't realised the additional difficulties you were faced with. However can I suggest give the FMC another chance having got this far, but ignore detailed charted departure and arrival procedures, just as you would if you went back to using GPS and FS flight planner. Trying to absorb all the information from the chart is a tall order for anyone who isn't trained to do so. However once you get the hang of pre-flighting the FMC and inputting a plan (which is a logical process if you use a written flight plan as a source) you can simply select a SID which ends at a waypoint on your route and let the FMC plan the departure. Without charts I use the ND PLAN mode to preview the SID and choose one which joins the route best. That might help you by being a visual presentation, rather than needing to interpret the words on the chart. A simpler alternative would be to just input the departure runway with no SID and give yourself vectors to steer for the first waypoint.

 

Hope this helps. :good: