Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Help with PDMG FMC programing

Featured Replies

Using a flight planning program, I created a flight plan from San Jose Ca. to Salt lake city. I choose the LOUPE SID. The plan looks like: D303B FAITH LOUPE OAK37 SJC D339H BYBLO BVL.....My plane is the PMDG 747 for FSXNow, the plan does not appear correct in the FMC after I select the flight plan, so I tried to manually add the entries. The FMC has problems with two entries. They are the OAK37 and the D339H entry. The FMC reports "Not in Data Base". I downloaded the latest cycle 802 from navigraph, but, still the same problem.What is OAK37 and D339H (are the intersections?). What must I do to get the FMC unit to accept these entries?Thanks,Jim

Problem solved. I had failed to update the flight plan located under the PMDG, "flight Plan" folder. Once I did that, all works A-OK,Still interested in what OAK37 and D339H are?Thanks,Jim

They look like normal airways to me, based on the format of that route you quoted.

Regards,

Max    

(YSSY)

i7-12700K | Corsair Vengeance LPX 64GB 3600MHz DDR4 | Gigabyte RTX4090 24Gb | Gigabyte Z690 AORUS ELITE DDR4 | Corsair HX1200 PSU

 

OAK37 is a fix 37 dme from the OAK VOR.D339H is a fix on radial 339 from the SJC VOR.They are basically RNAV fixes, you won't see them on the published chart, but they are used in some FMS databases. It's a way they include unpublished fixes in the FMS's database the FMS can follow in LNAV mode and still be compliant with the published SID/STAR procedure/route. They may be named differently depending on the FMS or Navdata source or supplier.Its probably not in the Navdata supplied by Navigraph (or has a different Ident), probably why your getting the 'Not in database' message.Also your waypoint listed as 'BYBLO' should be 'DYBLO'Regards.Ernie.

ea_avsim_sig.jpg

Thanks Ernie,I had DYBLO corrected entered in my flight plan, but had a typo in my AVSIM message. Is it possible to add a FIX to the FMS? Thanks for the explanation, this is what I was looking for.Jim

If you want to get even more technical -D339H is the 8mi fix on the 339 radial from the SJC VOR.Letter "H" is the eighth letter in the alphabet.The FMC alphabetical keys are laid out in 5 rows, with 5 letters in each row, and the letter Z being the only letter on the 6th row. Each letter on an RNAV departure or arrival can be associated with a 1 mile distance to identify various fixes up to 26 miles. For example, D339N would be the 339 radial and N would relate to the 14 mile fix on that radial since it is the 14th letter, 4 keys in on the 3rd row of 5 on the FMC. Make sense? :-) enjoyron

Create an account or sign in to comment

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.