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.

PIC FMC problem !

Featured Replies

Hi!I encountered a weird problem today.When I try to enter an arrival route in the FMC for a route where the STAR begins from a WPT where the ROUTE ends, the FMC won't accept the LSK and then FS2002 crashes. Ie. I'm able to SELECT every other STAR other than the one that BEGINS where the ROUTE ends. When I try to SELECT the one that JOINS the route perfectly to a STAR (for the correct RWY), it just crashes.This happens everytime, and I've tried it today many times.However, if I select a STAR that begins somewhat AFTER the LAST WPT on the route, the FMC accepts it, and once the RTE DISCONTINUITY is cleared everything's OK, and I'm able to fly the STAR smoothly. I wonder what could be causing this. Initially I suspected a corrupt STAR-file, but when I discovered that this in fact happens at other aerodromes as well, I left that option out.Any help is appreciated!!Tero

PPL(A)

Are you selecting the STAR with the common waypoint as the TRANSITION?

  • Author

Hi Stiffy,Nope. As a matter of fact, these airports that I've tried don't have transitions for STARs. I'll give you an example.I'll program a route from EFHK-EFTP. The route is: PIVAK P854 PIR.When I look at the LEGS page, there is a waypoint called VELUN at the end of the route. Then I goto DEP/ARR and just select Runway 24 for landing (I don't even select any approach, which are also available), and THEN I try to select the VELUN1A arrival for EFTP, but to no avail. The STARs are listed as Arrivals and neither of the Runways have any transitions at all from STARs to IAFs. Ie., just a regular STAR.Another example. I'll program in a flight from EFVA-EFTP (again to Tampere, EFTP). Route: MOLEG P854 PIR. Now this route ends in a waypoint called KYROS. Now if I try to select the KYROS arrival (for either of the rwys) the FMC crashes. But IF I select an arrival, other than the one starting at KYROS, say the VELUN1A, it will work fine.I discussed this problem in the IRC just a while ago, and it seems that others have the exact same problem as I do. Could this be caused by some corrupt navdata ?Puzzled...Tero

PPL(A)

Tero,This is a known bug in the FMC software. I am afraid we have to live with it. Ways around it are:1. delete the waypoint (the beginning of the STAR) from your legs page, before you choose such a STAR, or (a more permanent solution)2. remove the first waypoint form the STAR in the STAR definition file.It's very sad to have your FS2K2 crash after a long flight just before you are going to descent, therefore I recommend to do all the FMC planning at the originating airport when you're still on the ground, if possible. A crash is less annoying when you're still in that fase of the flight.Regards,KiekEHAMhttp://home.planet.nl/~nwkaan/

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.