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.

ATR 42/72 -600 updated v. 1.0.36

Featured Replies

10 minutes ago, mryan75 said:

Seems like it's an option but I can't find DME anywhere in the plane.

See screenshot:

spacer.png

Best Regards,

Vaughan Martell  PP-ASEL KDTW

  • Replies 160
  • Views 38.7k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • The prop brake seems to confuse a lot of people, and when it is used.     The prop brake needs a few things before the ready light will become available.     The aircraft has to be on th

  • If you’re in Hotel Mode, for a turnaround, then I assume you don’t have a GPU plugged in.    You would start engine one normally, and then we put the condition lever on that engine to Auto to p

  • Try rudder trim.  We rarely use aileron trim in the real thing; usually only if the plane is rigged a bit funny.  Rudder trim is your friend in the ATR.  Always Trimming Rudder.  (And Always Try Reboo

1 minute ago, vonmar said:

 

My point isn't about the terminology, my point is that from ELUVA to RW11 should be 6.0NM, and it's 6.4NM. And it's the same with every RNAV approach I've tried with the ATR: the distance from the FAF to the runway threshold waypoint (if there is one for the approach) is wrong. That's a problem.

11 minutes ago, mryan75 said:

My point isn't about the terminology, my point is that from ELUVA to RW11 should be 6.0NM, and it's 6.4NM. And it's the same with every RNAV approach I've tried with the ATR: the distance from the FAF to the runway threshold waypoint (if there is one for the approach) is wrong. That's a problem.

If you were driving a car from ELUVA it would be 6.0NM

DME is Slant Range. In this case from 2000 feet. So in this case 6.4NM.

Edit: I reposted your screenshot link for better viewing.

 

 

spacer.png

 

 

 

Edited by vonmar

Best Regards,

Vaughan Martell  PP-ASEL KDTW

6 minutes ago, vonmar said:

If you were driving a car from ELUVA it would be 6.0NM

DME is Slant Range. In this case from 2000 feet.

Edit: I reposted your screenshot link for better viewing.

 

 

spacer.png

 

 

 

But this is an RNAV approach. At the FAF on an RNAV approach you should see the distance on the chart regardless of your altitude. In every other aircraft in MSFS the distance matches.

4 minutes ago, mryan75 said:

But this is an RNAV approach. At the FAF on an RNAV approach you should see the distance on the chart regardless of your altitude. In every other aircraft in MSFS the distance matches.

The RNAV you posted does not show DME ranges.

Altitude matters when talking DME.

BTW, if you could not find DME in the ATR how did you come up with 6.4NM?

Edited by vonmar

Best Regards,

Vaughan Martell  PP-ASEL KDTW

 

20 minutes ago, mryan75 said:

But this is an RNAV approach. At the FAF on an RNAV approach you should see the distance on the chart regardless of your altitude. In every other aircraft in MSFS the distance matches.

It's distance to threshold not distance to DME. That particular approach doesn't even use any DME for reference. 

 

You should look at the distance readout in the ILS approach. If that gives you 11.2 from IATO at TABEB then everything is as it should be.

Edited by Farlis

6 minutes ago, Farlis said:

It's dis

It's distance to threshold not distance to DME. That particular approach doesn't even use any DME for reference.

I say again: the distance from ELUVA to the RW11 waypoint should be 6.0 NM. In the ATR it is 6.4 NM. That is the problem. If you are in the TBM, the distance indicated is 6 NM. If you are in the 172, the distance indicated is 6.0 NM. If you are in the 737, the distance indicated is 6.0 NM. In the ATR it is 6.4 NM.

The distance from the FAF to the RW waypoint on every RNAV approach I have flown in the ATR is wrong. I don't know how much clearer I can explain it.

13 minutes ago, mryan75 said:

I say again: the distance from ELUVA to the RW11 waypoint should be 6.0 NM. In the ATR it is 6.4 NM. That is the problem. If you are in the TBM, the distance indicated is 6 NM. If you are in the 172, the distance indicated is 6.0 NM. If you are in the 737, the distance indicated is 6.0 NM. In the ATR it is 6.4 NM.

The distance from the FAF to the RW waypoint on every RNAV approach I have flown in the ATR is wrong. I don't know how much clearer I can explain it.

"I say again: the distance from ELUVA to the RW11 waypoint should be 6.0 NM. In the ATR it is 6.4 NM. "

It is but not a DME distance.

Now, you did not mention DME in this post?

What were you viewing to see 6.4 when at ELUVA in the ATR?

Edit : are you sure the 172 has DME receiver?

 

Here is the ILS DME for TNCC:

 

spacer.png

 

Edited by vonmar

Best Regards,

Vaughan Martell  PP-ASEL KDTW

12 minutes ago, vonmar said:

"I say again: the distance from ELUVA to the RW11 waypoint should be 6.0 NM. In the ATR it is 6.4 NM. "

Now, you did not mention DME?

What were you viewing to see 6.4 when at ELUVA in the ATR?

Correct, I did not mention DME. This is an RNAV approach, it is GPS distance. The distance is indicated upper right of the MFD and below the speed tape on the PFD. I have no radio frequencies tuned. This is GPS distance.

spacer.png

Edited by mryan75

Need to zoom in your screenshot to make the small print readable.

Per your last post we are no longer talking ATR DME, correct?

Best Regards,

Vaughan Martell  PP-ASEL KDTW

14 minutes ago, mryan75 said:

This is GPS distance.

And you are correct, it is off in the ATR.

I just checked it at TNCC, sitting at the ramp just loading up the procedure. Gives me a distance of 6.5NM between ELUVA and THR11 in the FMC of the ATR. With the default Garmin I get 6NM. As it should be.

19 minutes ago, Farlis said:

And you are correct, it is off in the ATR.

I just checked it at TNCC, sitting at the ramp just loading up the procedure. Gives me a distance of 6.5NM between ELUVA and THR11 in the FMC of the ATR. With the default Garmin I get 6NM. As it should be.

Thank you for that! I didn't think to check the FMC for the distances in the flight plan (duh! 🙂). What's weird is that I'm fairly certain that the ATR use MSFS navdata, like the default Garmin (I have Navigraph navdata installed).

So why would the different? It just doesn't make any sense.

29 minutes ago, vonmar said:

Need to zoom in your screenshot to make the small print readable.

Per your last post we are no longer talking ATR DME, correct?

Yeah it is small. Correct, talking GPS distances. @Farlis just confirmed that it's incorrect in the ATR. The question is why? It's bizarre.

38 minutes ago, mryan75 said:

Yeah it is small. Correct, talking GPS distances. @Farlis just confirmed that it's incorrect in the ATR. The question is why? It's bizarre.

I first thought it might be computing the distance to the runway midpoint rather than the threshold, but runway 11 at TNCC is longer than two times 0.4 nm.

Maybe it's computing the distance to the ARP? Should be relatively easy to check... if you create a leg from ELUVA to TNCC, how long is that leg? 

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.