Jump to content

737 FMC msg (discontinuty)


Recommended Posts

Posted

I got a msg on the FMC and it said discountunity (sp) and then the LNAV disengaged... and when I enabled the FMC again it just took made a hard turn left and steered way off course...what just happened?

Posted

Emir,Sorry, but this one is very simple: Pilot Error .... ;-)Search the FMC manual for "discontinuity" and all will be revealed...Cheers,S

Cheers, Søren Dissing

Intel i9-13900K @5.6-5.8 Ghz | ASUS ROG RYUJIN III | ASUS Strix RTX4090 OC | ASUS ROG Maximus Z790 Hero | 64Gb DDR5 @5600 | 1Tb Samsung M.2 980 PRO (Win11), 1Tb Samsung M.2 980 PRO (MSFS), | ASUS ROG Helios 601 | 32” ASUS PG32UCDM 240hz 4K | TM TCA Captain's Edition, Tobii 5 | Win 11 Pro 64 | MSFS 2020 & 2024 | BA Virtual | PSXT, RealTraffic w/ AIG models

 

 

Posted

>pilot error? lol I was just sitting watching AP do all the>work, what the #### did I do>>stupid #### computers :( :DYou did nothing when you should have done something.You need to check the LEGS pages for Route Discontinuties as adding route data STARS and SIDS may (and often does) leave dicontinuities that need to be fixed. Basically the FMC needs you to confirm or edit changes between some parts ofthe route.Checking the LEGS pages should be considered part of the checklist for route programming especially after any changes to the route such as selecting an appraoch and STAR.As suggested above check the FMC manual for more info on what to look for and what to do.

  • Commercial Member
Posted

Emir,Was the message "DISCO INSERTED AFTER XXXX"? If so, this is due to an improperly coded SID/STAR file that has a turn in it that the FMC is having trouble calculating the right direction for. As its not possible for us to handcheck every single file that's auto generated for the database, ocassionally you'll run into this sort of thing. If you open up the LEGS page, you'll be able to see where the discontinuity is and do something to fix it.If what you saw was just something like ROUTE DISCONTINUITY and LNAV disengaging, this most likely means you've either 1. Run into a route disco that existed on the LEGS page but wasn't closed earlier in the flight, or 2. you have no further waypoints loaded. In both cases, the FMC is blind, it has no idea where you want to go, so it kicks out and holds present heading. To get back into LNAV, you need to close the disco by line selecting the next waypoint up to the top line, or enter new waypoints.

Ryan Maziarz
devteam.jpg

For fastest support, please submit a ticket at http://support.precisionmanuals.com

Guest Ohio330
Posted

I feel your pain. I tried doing what stumpy said to fix discontinuities, but all i get when trying to fix the entry is "NOT IN DATABASE"..maybe im trying to fix an unfixable route..dunno

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
  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...