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.

question on how to define an altitude restriction betwe...

Featured Replies

Hi!I wanted to create the new procedures for LOWW and ran into the following problem:there are two fixes on a STAR, between them the MEA changes to 6000 ft. The fix where the MEA changes is defined by the distance toa VOR (DME in other words :-) ). The radial on which the fix lies is not indicated, is just lies on a direct line between the two other fixes.How can I put this MEA change into a STAR procedure (I'm talking about a text procedure file, NOT about the FMC itself....)?I'd be very thankful for a hint!regards,Joerg

Probably a stupid question, but does the STAR chart give the lat/long coord's of the MEA?John http://homepage.eircom.net/~eamonnmca/images/logo_ba.JPGwww.bavirtual.co.uk Senior Captain Simflight.com Staff Reviewer

Hi John!No, it doesn't give Latlon for the MEA, sorry....:-)regards,Joerg

Hi JoergI think you have to define a fix at this point in some way. You could testfly the route and when you reach the distance from the VOR (between the two fixes)pause the sim, and take a note of the LATLON. Then define the fix with the new altitude based on the LATLON.Or maybe better, when paused, you know the heading and distance from fix A. Take a note and write a new fix. The syntax will then be as an example: " FIX MEA COLOCATED FIX A 145 7", where 145 is the heading from fix A and 7 the distance from fixA. (Actually when paused, you also know the distance and heading from the VOR so you could also use this as reference).The STAR file: ... FIX A 8000 FIX MEA 6000 FIX B...Hope this helpsPerA

You clould get the Lat/Long from FS Navigator if you have it???"Lairy"Liam Reynolds

Liam Reynolds - EGNS
 

sig_smaller.jpg

             Youtube Channel

Hi,I would recommend using NAV24 freeware available within the Hangar site of AVSIM. With this software you can graphically reproduce any terminal procedure. Several tools available in this software make standard turns, arcs, intercepts of headings etc.. a very simple execrcise. You can define fixes and automatically get the appropriate coordinates. This is my preferred tool for writing terminal procedures.As to the LOWW STARS I am a bit puzzled by your question (maybe I did not understand it fully). There are a couple of STARS where altitude restrictions apply but as far as I can see from the latest charts they are all starting from a fix. For example the MALUG1W STAR foresee a flight level of 150 until reaching PINKA then descend to 8000 feet and maintain when crossing DME 16 from PINKA. On the chart you have the coordinates of PINKA should this navaid not be in the database. The same applies for LAMSI5W star (flight level 9000 feet until crossing RINIG then descend to 6000 feet and maintain when crossing DME 23 from RINIG).DISCLAIMER:The above reflects only a personal opinion and was written without any intend to offend, harm or criticize in any way or manner any individual, institution, association or company including PMDG.Michael

Hi Michael!Have a look at this site:http://www.flightproject.net/au/main.php?l...rvice&id=chartsThese are new procedures for LOWW (and I guess the other airports in Austria got new procedures, too. I have yet to check it out ...).That's where I got the MEA definitions from.Thank's for the hint (NAV24). I will try to use it to create the new procedures.regards,Joerg

Hi Joerg,I am sure you will find NAV24 useful. There is a steep learning curve but it is worth it especially if you create a lot of procedures. I had a look at the charts published on the flightproject site. They are identical to the charts published at Eurocontrol and Jeppesen. To make sure we are talking the same language, you mentioned in your opening post having difficulties with the STARS right? then form my point of view all MEAs can be defined using the intermediary fixes mentioned on the charts ie Rinig and Pinka or are you looking at different segments?DISCLAIMER:The above reflects only a personal opinion and was written without any intend to offend, harm or criticize in any way or manner any individual, institution, association or company including PMDG.Michael

Hi Michael!Have a look at the ASTUT6W - STAR: between ASTUT and NORPA you can see the MEA change I was talking about. There is no MEA at ASTUT, but at 40 nm distance to the FMD-VOR (on the direct line between ASTUT and NORPA) there's a MEA of 6000 indicated.But maybe I might have read the chart in a wrong way: does this MEA only apply between D40 FMD and NORPA or does it apply all the way between ASTUT and NORPA?I have to check this out in my Jeppesen IFR manual :) ...regards,Joerg

Hi again,The altitude restriction of 6000 feet applies all the way from ASTUT until reaching NORPA. Same applies to MIKOV (5000 feet) all the way to NORPA. The D40-FMD mention relates exclusively to speed restrictions which may or may not be issued by ATC depending on traffic and weather conditions. If issued these speed instructions apply at 40DME FMD on the STAR procedure.If not issued 250 KT is the rule.Hope this help.DISCLAIMER:The above reflects only a personal opinion and was written without any intend to offend, harm or criticize in any way or manner any individual, institution, association or company including PMDG.Michael

Hi Michael!Thanks for this information!regards,Joerg

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.