Hello.

I just did a flight in the 737-700 from NFFN to AGGH, the descent went fine with VNAV on and followed the profile perfectly as assumed.

I flew the over head VOR arrival into AGGH 06, it went fine with vnav following everything. However I needed 6.0 DME to reference a turn, I tuned both nav selectors to 113.60 which was the frequency I needed.

I switched to see the VOR 1 + 2 on the the displays, they didn't show a distance.

I encountered extremely bad turbulence on the approach and performed a missed approach, I entered the published hold at 4000FT.

I armed hold exit and flew the approach again, the fms had calculated all the altitudes and speeds for me, so I engage vnav to follow them, however when I reach a waypoint vnav stays at 4000FT, yes I selected 2300FT for it to descend.

I went around again and soon after flew more of a visual approach.

Thanks, Mitch.

Hi Mitch, please note PMDG forum rules ask that we sign our full names on all posts in their forums.

I'm trying to parse your post and come up with a problem statement, and I think you have found a VOR that does not display DME? you didn't specify the VOR so a reader will have to pull charts of the AGGH arrivals and try to reconstruct your narrative. Also, I assume your "need" for a 6 DME reference was based also on a chart, and this implies that the VOR has a DME (not all VORs have a DME).

As for the second problem statement, this one is probably more procedural where knowing the state that the FMS was in (approach, missed approach, still missed approach for second approach?) would require much more detail about MCP settings and FMA indications than provided.

Hi, sorry.

 

Perhaps it doesn't use a DME, however I expect that as it's a VOR arrival, anyway.

I'm not sure what you mean by the plane still in go around.

I bounced back up off the runway and pushed TO/GA, I flew LNAV, then held at 4000FT.

After that I went and popped in the same arrival and arm the hold exit.

I then reset the MCP altitude and engage VNAV, it doesn't give me an altitude deviation, so I'm assuming it's not engaged properly.

I appreciate your help, are you able to link me where I can get information on the mode the aircraft was in, as you said it may be in go around mode.

Thanks.

Unless you are using a correct scenery add-on or have updated the stock navigation data then the HONIARA VOR within the scenery has a frequency of 112.60

That's strange, my navigraph is up to date and It publishes 113.60.

Navigraph does not update flightsim scenery files scenery from where the PMDG reads the VOR data.

If by chance you need your flight sim navigation data updated:

https://www.fsaerodata.com/

The default FSX/P3D navaids reflect the world as it was in 2006. At that time, the VOR on Guam was on 112.6.

Navigraph FMS data contains navaid information that is current, but the actual navaids themselves are contained in various scenery .bgl files and are not updated by Navigraph.

You can update all the simulator navaids (VORs and NDBs) to 2018 using freeware programs created by Hervé Sors at: http://www.aero.sors.fr/navaids3.html

I’ve been using his files to keep my navaids up-to-date for several years.

17 minutes ago, pracines said:

If by chance you need your flight sim navigation data updated:

https://www.fsaerodata.com/

Good information. Gonna try this.