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.

Resume own navigation

Featured Replies

I must have missed some obvious step. I filed a genuine Malev flightplan from LRTM to LHBP by downloading from FSBuild to the FS2004 planner. I opened RC 4.3 and loaded this - it showed up as it should. I checked 'No Dep Proc' as there are no published departure procedures from LRTM. I followed ATC instructions and at around 25 nm out he handed me off with 'resume own navigation direct to LHBP'. I did not want to go direct! When I attempted to get onto my flight plan track (by turning left about 60 degrees) ATC came back up, said I was off track and gave me a new heading direct to LHBP. I tried going to my flightplan again much to the annoyance of ATC and I was forced to fly direct. What did I do wrong?

Supporter.png

 

John

I may be wrong, but direct to is somewhat a point A to B straight line from where you are now to your next way point and has nothing to do with your FMC flight plans lines from way point A to B.I usually get a heading direction that is close to my filed plan after I contact center/departure just after take off.

  • Author
I may be wrong, but direct to is somewhat a point A to B straight line from where you are now to your next way point and has nothing to do with your FMC flight plans lines from way point A to B.I usually get a heading direction that is close to my filed plan after I contact center/departure just after take off.
Thanks, Jim. I know what 'direct to' is! My point is that RC ATC ignored my flight plan and routed me 'direct to LHBP', not my next waypoint. When I tried to route to my next waypoint ATC went nuts. What I would like to know is why it did that, and how can I make it use my flight plan in future. John

Supporter.png

 

John

  • Commercial Member
I must have missed some obvious step. I filed a genuine Malev flightplan from LRTM to LHBP by downloading from FSBuild to the FS2004 planner. I opened RC 4.3 and loaded this - it showed up as it should. I checked 'No Dep Proc' as there are no published departure procedures from LRTM. I followed ATC instructions and at around 25 nm out he handed me off with 'resume own navigation direct to LHBP'. I did not want to go direct! When I attempted to get onto my flight plan track (by turning left about 60 degrees) ATC came back up, said I was off track and gave me a new heading direct to LHBP. I tried going to my flightplan again much to the annoyance of ATC and I was forced to fly direct. What did I do wrong?
can i see your flightplan?better yet, make a log, instructions pinned to the top of the forum. remember to click debug before loading the plan. then duplicate the problem, and send me the .log.

Is this what FSB generated?LRTM TGM T802 EVRIK UL850 DODAR UL617 TPS LHBPFS9:[flightplan]title=LRTM to LHBPdescription=LRTM, LHBPtype=IFRroutetype=3cruising_altitude=32000departure_id=LRTM, N46* 28.03', E024* 24.45',+000963.00departure_position=07destination_id=LHBP, N47* 26.21', E019* 15.42',+000495.00departure_name=TRANSILVANIA-TARGU_MURESdestination_name=FERIHEGYwaypoint.0=LRTM, A, N46* 28.03', E024* 24.45', +00963.00, waypoint.1=TGM, N, N46* 26.48', E024* 18.23', +02000.00, T802waypoint.2=TIRGU, I, N46* 26.25', E024* 08.01', +05000.00, T802waypoint.3=VALIN, I, N46* 24.18', E023* 17.49', +21000.00, T802waypoint.4=EVRIK, I, N46* 21.06', E022* 14.32', +32000.00, UL850waypoint.5=BUDOP, I, N46* 41.14', E021* 29.47', +32000.00, UL850waypoint.6=DODAR, I, N47* 12.52', E019* 31.39', +09000.00, UL617waypoint.7=TPS, V, N47* 29.35', E019* 26.46', +03000.00, waypoint.8=LHBP, A, N47* 26.21', E019* 15.42', +000000.00, FSX:<?xml version="1.0" encoding="Windows-1252"?><SimBase.Document Type="AceXML" version="1,0"> <Descr>AceXML Document</Descr> <FlightPlan.FlightPlan> <Title>LRTM to LHBP</Title> <FPType>IFR</FPType> <RouteType>HighAlt</RouteType> <CruisingAlt>32000</CruisingAlt> <DepartureID>LRTM</DepartureID> <DepartureLLA>N46

  • Commercial Member
Is this what FSB generated?LRTM TGM T802 EVRIK UL850 DODAR UL617 TPS LHBPFS9:[flightplan]title=LRTM to LHBPdescription=LRTM, LHBPtype=IFRroutetype=3cruising_altitude=32000departure_id=LRTM, N46* 28.03', E024* 24.45',+000963.00departure_position=07destination_id=LHBP, N47* 26.21', E019* 15.42',+000495.00departure_name=TRANSILVANIA-TARGU_MURESdestination_name=FERIHEGYwaypoint.0=LRTM, A, N46* 28.03', E024* 24.45', +00963.00, waypoint.1=TGM, N, N46* 26.48', E024* 18.23', +02000.00, T802waypoint.2=TIRGU, I, N46* 26.25', E024* 08.01', +05000.00, T802waypoint.3=VALIN, I, N46* 24.18', E023* 17.49', +21000.00, T802waypoint.4=EVRIK, I, N46* 21.06', E022* 14.32', +32000.00, UL850waypoint.5=BUDOP, I, N46* 41.14', E021* 29.47', +32000.00, UL850waypoint.6=DODAR, I, N47* 12.52', E019* 31.39', +09000.00, UL617waypoint.7=TPS, V, N47* 29.35', E019* 26.46', +03000.00, waypoint.8=LHBP, A, N47* 26.21', E019* 15.42', +000000.00, FSX:<?xml version="1.0" encoding="Windows-1252"?><SimBase.Document Type="AceXML" version="1,0"> <Descr>AceXML Document</Descr> <FlightPlan.FlightPlan> <Title>LRTM to LHBP</Title> <FPType>IFR</FPType> <RouteType>HighAlt</RouteType> <CruisingAlt>32000</CruisingAlt> <DepartureID>LRTM</DepartureID> <DepartureLLA>N46

I was just verifying his FSB version and checking the plan format experienced by others.

instead of guessing what his plan is, could we see what the plan is? and a log from a flight where the problem occurss, so we can solved the problem on his machine, with his flight. we'e just guessing and speculating on what could of happened. guess isn't very productive.jd
  • Author
Is this what FSB generated?LRTM TGM T802 EVRIK UL850 DODAR UL617 TPS LHBPFS9:[flightplan]title=LRTM to LHBPdescription=LRTM, LHBPtype=IFRroutetype=3cruising_altitude=32000departure_id=LRTM, N46* 28.03', E024* 24.45',+000963.00departure_position=07destination_id=LHBP, N47* 26.21', E019* 15.42',+000495.00departure_name=TRANSILVANIA-TARGU_MURESdestination_name=FERIHEGYwaypoint.0=LRTM, A, N46* 28.03', E024* 24.45', +00963.00, waypoint.1=TGM, N, N46* 26.48', E024* 18.23', +02000.00, T802waypoint.2=TIRGU, I, N46* 26.25', E024* 08.01', +05000.00, T802waypoint.3=VALIN, I, N46* 24.18', E023* 17.49', +21000.00, T802waypoint.4=EVRIK, I, N46* 21.06', E022* 14.32', +32000.00, UL850waypoint.5=BUDOP, I, N46* 41.14', E021* 29.47', +32000.00, UL850waypoint.6=DODAR, I, N47* 12.52', E019* 31.39', +09000.00, UL617waypoint.7=TPS, V, N47* 29.35', E019* 26.46', +03000.00, waypoint.8=LHBP, A, N47* 26.21', E019* 15.42', +000000.00,
LRTM TGM T802 EVRIK L602 BUDOP Y558 ABONY LHBPThanks, ronzie. I could not find the source of the remainder of your thread to check. I run FS9 only. JC, thanks, I will run the flight again tonight and post a debug log.

Supporter.png

 

John

  • Author

The explanation? I had LHBP programmed in as the 2nd waypoint. How stupid is that?Even more embarrassing is that I had to find out from jd himself. :(:(:(

Supporter.png

 

John

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.