Jump to content

SEC F-PLN causes complete system lockup


Recommended Posts

Posted

Hi eveyone,

When selecting SEC F-PLN in the FMS, after attemping to enter a waypoint in my second flightplan, the FMS and all aircraft systems freeeze. Although knobs and buttons are selectable as usual, they have no effect (windows, displays and guages are frozen in place). The FMS itself also becomes completely unresponsive.

I've noticed a few posts here already about the FMS causing similar issues. Right now I don't know if it's reproducible because it only just happened.

Regards,

Louis

Posted (edited)

Dear Support,

No problem, here are the steps I captured on video.

  1. Select the SEC F-PLN key on the FMS
  2. Select LSK 2L (< SEC F-PLN)
  3. Enter any airport ICAO code into the FMS scratchpad
  4. Select LSK 1L
  5. The FMS and most controls/switches are now frozen
Edited by fsgeek91
Posted

Yup, can easily reproduce it like this, thanks for reporting 🙂

Ill forward it to the respective team!

 

FWIW, that´s not how you´re supposed to enter airports into the SEC F-PLN; but it shouldnt freeze up the FMC either way 😄

 

  • Thanks 2
Posted

Thanks very much for reporting this! I know what I’m doing is nonsense 🙃 This was actually discovered after copying the existing route and selecting a waypoint, but I found that this simpler method is reproducible and not route-specific.

Thanks!

  • Like 1
Posted

(Copy from other thread)
I had something similar happening after an entry in the FMC, all controls (knobs, dials, gauges etc.) became unresponsive (i.e. they turned, but nothing changed).
What I did was entering a bearing/distance waypoint in the FPLN page, then deleting it with CLR, then deleting the disco. After that it locked up. All during cruise by the way.

Posted
2 hours ago, Fiorentoni said:

(Copy from other thread)
I had something similar happening after an entry in the FMC, all controls (knobs, dials, gauges etc.) became unresponsive (i.e. they turned, but nothing changed).
What I did was entering a bearing/distance waypoint in the FPLN page, then deleting it with CLR, then deleting the disco. After that it locked up. All during cruise by the way.

Heya,

can´t reproduce this unfortunately. It might has something to do with double clicking the FMC, which other people reported.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...