ATR flight plan page gone yellow

Hi all,

Recently i’ve encountered a problem regarding the flight plan page in the fmc in the ATR 72 aircraft, which happens randomly. Whenever i want to switch pages (for example when i go to perf page or the sec flight plan) randomly, my flight plan goes yellow and i cant revert it back to green, here is an example:


Does this happen to other simmers. Is there a solution to this?

1 Like

Here is the color code valid for the displays
couleurs atr
Your flight plan is waiting for validation , there is a CLR TMPY information , the EXEC light is green.
check TMPY page

TMPY / FPLN REVISIONS ACTIVATION
image

When required revisions have been inserted:
– REVISED FLIGHT PLAN … CHECK

Once the TMPY is open, the EXECUTE active light is green to remind the pilot that the
EXEC key should be pressed to execute the FPLN revision.
If the active light is green:
– EXEC KEY (ON MCDU KEYBOARD) … PRESS
Transfers TMPY into FPLN, activates the revised FPLN and displays the first FPLN page.

or

– LSK L6 / >CLR TMPY … PRESS
Cancels all revisions inserted in the present TMPY and maintains the active FPLN unchanged.
image

I had the same happen to be today. I did not find a way to confirm the flight plan. It does seem like I did something that messed up an internal logic for the temporary plan.

Did you import FP from Simbrief or else or did you enter each leg by hand ?
What about AIRAC cycle ? (for exemple , I have Aerosoft CRJ and if AIRAC is not uptodate , I get a CTD when choosing STAR)

In my case I imported from simbrief with default msfs nav data. The flightplan was fine, initially. If I recall correctly, I added an approach procedure and before executing it I clicked on direct. After this it was broken.

For me, i entered the fp manually and entered the appropriate approches, sids ans stars. The problem is that it happens randomly during the flight or on the ground when i go to other pages.

I can’t help more , maybe you should report this bug …

Had the same issue several times the last days. It is definitly a bug - the flight plan goes into “TMPY” mode, but “CLR TMPY” and “EXEC” both do not work, so the flightplan remains in “TMPY” mode and not be used any more. Unfortunatly I did not found a solid repro szenario yet.

Happened to me tonight. Cannot go back to active flight plan. Stuck in temporary data plan, neither CLR TMPY or Execute work, or trying to change any other FP parameters. Just stuck in Yellow as per the screenshot. Had to manually land the aircraft. Reporting the bug…

Happened to me as well. It just locks itself in TMPY.

I can tell you how you got into this state but unfortunately not how to fix it. If you press the FPLN button when you are already on the flight plan page, it will switch to the secondary flight plan. At that point the primary flight plan will go into temp mode and you cannot get out of it.

Just happened to me as well, very frustrating as cannot get out of it

try going back to make sure all your perf data is still entered properly; cruise altitude, transition altitude, etc.

Until they fix this bug, the only solution is to re-import the flight plan.
If you are on air, just set heading mode and re-import flight plan. Then go dct to your next waypoint from where you are.

Sadly, the Import Flightplan option is greyed out on the EFB.

I had this problem earlier and found a workaround by accident.

On the FMC:

  1. Go to DATA \ INIT \ FPLN INIT \ ROUTE
  2. Put in a new FROM/TO combination for example just the same as your current route
  3. Displayed route below should only contain FROM and TO airports
  4. Go to FPLN (FMC button)
  5. Clear TMPY should work now

Hope this helps someone

3 Likes

Brilliant, thank you!

When i put a new FROM/TO combination, it just says not allowed.
Not with EDSB/LFSB or with EDSBLFSB. Nothing works.

Machine was completely programmed and ready for Engine start.
Clicked on FPLAN and suddenly everything yellow. Cant EXEC. Nothing.

OK, back to hangar. Not usable. I dont see me programming the flighplan everytime new when this bug randomly appears. What a buggy mess this is.

Experienced this bug today, but this workaround works.