Jump to content
Sign in to follow this  
Guest visualchaosfx

Flight Planning issue with the PMDG 747 FMC

Recommended Posts

Guest visualchaosfx

I used routefinder to generate a flight plan. route finder flightplan: NAT: Eastbound track message identification is 75NAT: Westbound track message identification is 75Computed route from HEATHROW (EGLL, EG) to SAN FRANCISCO INTL (KSFO, K2): 41 fixes, 5131.9 nautical miles Cruise altitude between FL250 and FL350EGLL (0.0nm) -SID-> CPT (28.4nm) -UL9-> KENET (37.3nm) -UL9->BASET (47.2nm) -UL9-> DIKAS (106.3nm) -UP4-> EG190 (209.8nm) -UP4->EVRIN (229.0nm) -UL607-> CRK (300.8nm) -UN523-> DOLIP (430.9nm) -UN523->LIMRI (541.8nm) -NATB-> 51N020W (738.1nm) -NATB-> 50N030W (1124.3nm) -NATB->49N040W (1518.6nm) -NATB-> 48N050W (1920.6nm) -NATB-> NOVEP (1962.1nm) -NATB->YYT (2039.8nm) -J575-> LEXAK (2063.1nm) -J575-> YQY (2346.3nm) -J509->YYG (2473.8nm) -J509-> YQM (2534.4nm) -J509-> HUL (2670.5nm) -J509->PATTA (2744.1nm) -J509-> VLV (2796.4nm) -J565-> CATOG (2881.5nm) -J565->YMX (2943.9nm) -J513-> YMW (3012.4nm) -J513-> BOBRA (3036.7nm) -J513->SMARE (3104.3nm) -J513-> YYB (3157.1nm) -J500-> BILPA (3281.3nm) -J500->SSM (3359.2nm) -J140-> DLH (3685.2nm) -J32-> ABR (3954.9nm) -J32->DPR (4097.8nm) -J32-> CZI (4309.9nm) -J32-> BOY (4397.0nm) -J32->MLD (4594.9nm) -J32-> BAM (4818.8nm) -J94-> LLC (4899.1nm) -J32->FMG (4960.2nm) -STAR-> KSFO (5131.9nm) Details: ID FREQ TRK DIST Coords Name/RemarksEGLL 0 0 N51

Share this post


Link to post

>Then I inputed the IDs in the simroute generator at>simroutes.com and generated a flight plan that I can save and>access from the PMDG 747 FMC. I'm at the parking gate now and>I've loaded the flight plan into the FMC but I get a "DISCO>INSRTD AFTER" message and it only loaded 1/4 of my flight>plan. EGLL to EG190> >What am I doing wrong here??? Ms/Mr Nameless,Please sign your posts with your real name as per forum guidelines.Did you enter the NAT waypoints as 5020N, 4930N, etc. into simroutes.com? If not you will have errors in the .rte file you downloaded.A "DISCO" is not an error. It's just a message from the FMC that that particular part needs your attention and is common even in the real world. Always go through the flightplan to check for DISCOs before executing.Hope it helps,

Share this post


Link to post

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
Sign in to follow this  
  • 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...