I need some help making sense of an EICAS message.   I have looked in the QRF and FCOM, but cannot match it exactly.  In my most recent flight on the 777F, I saw the following message in white:  ".FMC"   I know that "FMC" alone would indicate a failure of one or both FMCs, however, I was puzzled by the presence of the period in front of it.  Does that signify something else?  I could not find this in the manual.  Also, if it was a failure wouldn't the message be in yellow?  I did not notice any unusual behavior of the FMC system during the flight.  Thanks.

 

Andrew Jones

Never mind.  I just found the answer here in the forum.  Sorry for the trouble.  I did not find it when I first searched for it, as it was an asterisk and not a period that I was seeing.  For any who need it, the answer, I have pasted it below:

 

"Realistic behavior.

 

*FMC means "pay attention to the FMC."

 

When this happens, there will be a scratchpad message.  Most people seem to delete it without reading it for some reason, but it would tell you what the *FMC was alerting you to.  If you mistakenly cleared it, go to the FMC COMM page and look for any prompts for uplinked information.  Periodic *FMC messages on the EICAS are usually for the ALTN list updates.

 

I believe this is covered in the Intro Manual Supplement, which should be read."

 

 

Andrew Jones

How do you deal with ALTN list updates?  I had problems trying to figure out how to load them in to the FMC.

 

 

Never mind.  I just found the answer here in the forum.  Sorry for the trouble.  I did not find it when I first searched for it, as it was an asterisk and not a period that I was seeing.  For any who need it, the answer, I have pasted it below:

 

Thanks for searching the forum for the answer.  I'm always impressed when I see people take this kind of initiative.

 

As for the *FMC, I couldn't find a character that was web-safe that would display it correctly, but it should be "[circle] FMC."

 

...or...if this displays correctly: •FMC

 

 

How do you deal with ALTN list updates?  I had problems trying to figure out how to load them in to the FMC.

 

I don't recall an action needing to be performed.  If I recall correctly (I haven't flown the PMDG 777 with the option enabled for a while, so my memory is sketchy), the scratchpad message doesn't allude to an action; rather, it just mentions that the list has been updated.  Clear the message, truck on.

 

 

*FMC means "pay attention to the FMC."



When this happens, there will be a scratchpad message. Most people seem to delete it without reading it for some reason, but it would tell you what the *FMC was alerting you to. If you mistakenly cleared it, go to the FMC COMM page and look for any prompts for uplinked information. Periodic *FMC messages on the EICAS are usually for the ALTN list updates.

 

Actually it seems to be the request looking into FMC COMM, It's not only about ALTN list updates but could include weather updates, too. At least in this case I can remind the possibility for taking action directly. I might be wrong and it might apply for weather only.

Actually it seems to be the request looking into FMC COMM, It's not only about ALTN list updates but could include weather updates, too. At least in this case I can remind the possibility for taking action directly. I might be wrong and it might apply for weather only.

 

You're neither right nor wrong, really.  Note how the text you quotes states "periodic '•FMC' messages."  The weather imports - at least in the PMDG implementation - only occur at the beginning of the flight, or when you specifically request them.

 

The periodic messages - meaning, they occur periodically, or regularly, during the flight - are usually because the ALTN List has been updated.

 

I don't recall an action needing to be performed.  If I recall correctly (I haven't flown the PMDG 777 with the option enabled for a while, so my memory is sketchy), the scratchpad message doesn't allude to an action; rather, it just mentions that the list has been updated.  Clear the message, truck on.

 

Maybe the problem is that I had not flown a livery with this option enabled prior to a recent AFR flight to Miami.  I did clear the message but it just showed up again over and over for the entire 9 hour flight.  Eventually I just ignored it but good to know I can turn it off in the options menu.

Maybe the problem is that I had not flown a livery with this option enabled prior to a recent AFR flight to Miami.  I did clear the message but it just showed up again over and over for the entire 9 hour flight.  Eventually I just ignored it but good to know I can turn it off in the options menu.

 

It's showing up again and again for a reason.  The ALTN List needs to update during the flight because an ALTN from hour 1 will not be relevant when I'm at hour 8.  Say I depart EGLL and EGKK is listed (among others, but being an American, I don't quite pay attention to the outside world to know more codes  ...okay maybe EGSS).  When I'm clear across the ocean, and closer to my destination (e.g. KIAD), EGKK isn't really a relevant option.  The list should reflect other airlines (like KBWI, KORF, KJFK, KMRB, and so on).  As such, the prompt appears as the plane's list is being updated throughout the flight with more appropriate airports.

 

There's an option for it back around the rest of the options for datalink so it won't bother you with it (though you'll have to manually update the list yourself in that case).

Kyle,

 

There was a lot of TS activity around Miami at time of landing (in fact I landed in a major TS.....should have diverted but unfortunately my VA does not recognize the flight if you do).  So I guess that is why the ALTN list kept changing/updating whereas flights with clear weather would not need to update.

 

 

There was a lot of TS activity around Miami at time of landing (in fact I landed in a major TS.....should have diverted but unfortunately my VA does not recognize the flight if you do).  So I guess that is why the ALTN list kept changing/updating whereas flights with clear weather would not need to update.

 

Another reason why I'm not in a VA...too many decisions of good airmanship are discouraged.  Still, I did enjoy some of the structure it offered.

 

As far as it updating, I'll clarify the earlier point a little more:

It updates it naturally as the normal progression of a flight.  It does this to ensure the ALTN list contains relevant airports.  Since your plane is always moving during a flight, this list will always have limited validity.  As you move, airports become more and less relevant because they get closer and farther away.  *DING*  New airports.  For a plane moving at about Mach 0.85, airports on a list from even 5 minutes ago are less relevant...particularly in a place like the United States where we have airports everywhere.

 

Don't get tricked into thinking regional airports aren't good ALTNs, either.  If I was in a big pinch, I'd shove a 777 into ROA.  The longest runway is a shade under 7000', which can handle a 77W at nearly MLW (with an EMAS at the end).  Not an obvious choice of ALTN, because most people think of ALTN in terms of "can handle a 777 at a gate nicely," but ALTNs on that list are more for quick-action "a 6500' runway is a lot better than a highway or a field of corn because I need to be on the ground NOW."

 

I will add, though, that weather is not taken into account for the auto-listing, from what I can tell.

These topics are the ones that I find most instructive.

 

Many thanks to Andrew for asking the original question, and to all for contributing to my education.

 

Cheers, Richard

You're neither right nor wrong, really.  Note how the text you quotes states "periodic '•FMC' messages."  The weather imports - at least in the PMDG implementation - only occur at the beginning of the flight, or when you specifically request them.

 

The periodic messages - meaning, they occur periodically, or regularly, during the flight - are usually because the ALTN List has been updated.

That's helpful Kyle. I only have the T7 about two weeks and did not experience messages regarding alternate airports. And yes, during a flight between Frankfurt (EDDF) and Sao Paulo I just ignored the weather related messages before taking off and was wondering about the discussed notification ( '•FMC') later.

 

Just another question regarding the ALTN updates: Does this mean that I should add all ETOPS relevant airports to the list? It sounds like this - and it would make sense for me. However, How can I be sure that the listed airports in the message are "relevant" (I did not read the books in order to find it out up to now, sorry)?

Hi Axel,

 

With ETOPS, because the process requires me to nominate diversion airports within my ETOPS rating, I only add those 2 or 3 airports to my ALTNS. Then I know roughly where they are if I have to divert. I also add the waypoint of the equal-time point to my route so that I am prepared to make the diversion airport decision, if necessary.

 

The same goes with re-dispatch in that the re-dispatch point may added as a useful waypoint, if desired.

 

Apart from those situations, I would not enter additional airports which can complicate the instruments unnecessarily.

 

HTH.

Regards, Richard

Good info Kyle, thanks.

 

 

Just another question regarding the ALTN updates: Does this mean that I should add all ETOPS relevant airports to the list? It sounds like this - and it would make sense for me. However, How can I be sure that the listed airports in the message are "relevant" (I did not read the books in order to find it out up to now, sorry)?

 

For ETOPS airports, pilots usually throw them in the FIX page, which is described and shown in the tutorial (if you haven't done it, please do - it will answer so many questions before you even have them - to include this one...).

 

As far as relevance, I've already addressed it, for the most part:

The plane's datalink function "receives" a new ALTN list from "dispatch" (in reality, the list in FSX is entirely internal to the PMDG 777 - it's not reading any external files or anything) with new ALTNs to keep them relevant for you.  The relevance in this case is distance and runway length (configurable in the PMDG SETUP > menus, which also drives what airports show up on the ND when you hit ARPT on the display controller).

 

So...if it shows up in the list, it's relevant.  Why are you questioning its relevance?

 

Again, the function is included for quick decision making.  Say a passenger has a heart attack.  Thirty years ago, that meant hauling out a chart, looking for close fields, looking at the "longest runway" designator (if it was a sectional/terminal chart), or flipping through an A/FD to see if the runway is long enough, and then notifying ATC.  That, or, depending on the airline, you'd have a list of suitable enroute alternates, but that also requires figuring out which one is closest at that point in time.

 

Now?  The plane is getting updates to the ALTN list from dispatch, based on position reports.  This list is then interpreted by the plane to keep abreast of the closest airports in that list to be used for emergencies.  When it comes to medical emergencies, every second counts.  When I was with IDE, a passenger had a heart attack between IAD and MCO.  The crew tried to get into CHS to get him attention, but he ended up passing away before they got on the ground.

 

Instead of questioning it and considering it an annoyance, I'd encourage people to sit there during a flight to watch and see what it's doing and actually marvel at the usefulness of the thing.  Play around with it.  You won't break it.  If it starts acting weird, try and get it back to normal (you learn a TON doing that, btw), and if you can't, it'll be fine by the next leg you fly.

 

^^^ Words to live by for any feature on the plane, really...particularly the break and fix bit.

 

Good info Kyle, thanks.

 

Welcome!

For ETOPS airports, pilots usually throw them in the FIX page, which is described and shown in the tutorial (if you haven't done it, please do - it will answer so many questions before you even have them - to include this one...).

 

I read it, but obviously I have to read it again. Even if I can handle the B737NGX quite well (but far away from knowing each and everything) the given information for the T3 is specific enough to be quite overwhelming when trying to manage a first flight while reading the manual. It's definitely a different focus, at least for armchair pilots like me.

 

The plane's datalink function "receives" a new ALTN list from "dispatch" (in reality, the list in FSX is entirely internal to the PMDG 777 - it's not reading any external files or anything) with new ALTNs to keep them relevant for you. The relevance in this case is distance and runway length (configurable in the PMDG SETUP > menus, which also drives what airports show up on the ND when you hit ARPT on the display controller).

 

So...if it shows up in the list, it's relevant. Why are you questioning its relevance?

 

I should have used the term "adequate" instead of "relevant", sorry. The answer is simple: The same time I'm trying to understand the T3 (including the books, of course), I'm on a pathfinder tour through PFPX, and there the term "adequate airport" is used in this context. I just did the introduction flight once but definitely not the last time.

 

Instead of questioning it and considering it an annoyance, I'd encourage people to sit there during a flight to watch and see what it's doing and actually marvel at the usefulness of the thing. Play around with it. You won't break it. If it starts acting weird, try and get it back to normal (you learn a TON doing that, btw), and if you can't, it'll be fine by the next leg you fly.

That's exactly what I'm doing, but I'm just at the beginning and it will take a bit before I can consider to be rather on a level flight.

 

However, thanks again for you patience, I'll keep reading, promised.