Jump to content

FSX Visual Approach Problem


Recommended Posts

Hello everyone.I faced with a terrible problem today,though i have faced with it before but i havent asked here.

Today i was having that Barcelona-Salzburg flight.Until approaching,everything was fine,after i began descending(i was flying IFR) things happened.I was about 10 miles far from airport and i was at 13.000 ft.The ATC said to me descend to 3.400 feet.That was impossible.I should have descended with 5.000 ft vertical speed in order to make ATC's wish.

I dont know why is this happening ? I am not enough to fly online.So i am still around this default world.So i would be so grateful if you guys could help me.

Kind Regards..

Intel 4790K 4.0 GHz Processor,Geforce GTX 660 2.0 GB,8 GB DDR3 Ram,1TB HD
Link to comment
Share on other sites

FSX ATC is notorious for doing this. Now that you are aware, I would advise asking for descent about 125 miles from destination. I would usually get myself down to 17,000 feet or so, by the time ATC gives me my approach to the airport.


A couple of times when I was flying into Palm Springs, Ca. ATC had me at 12,000 feet, 6 miles from touchdown. I call that "Diving for the Deck"!

Still thinking about a new flightsim only computer!  ✈️

Link to comment
Share on other sites

I would check you flight plan.


10 miles from the airport means nothing if ATC plans on flying you 20 miles past to turn onto the inbound heading with other traffic. Were you actually on a runway approach vector under ATC at the time?

Link to comment
Share on other sites

Agree default ATC doesn't always provide efficient descents. You should always do a calculation yourself which results in your aircraft being near 4,000 AGL @ 20 miles from the runway (terrain permitting.) If the ATC is not providing timely descent, use the altitude request menu to drop in stages. In a typical airliner, descents starting 120-150 miles from the airport should get you near the target.


Also, when the ATC gives instructions which cannot be followed, that's your cue to take control and do the right thing even if it means doing a 180 to give yourself room to descend. The ATC will eventually get straightened out so no worries.



2 carrot salad, 10.41 liter bucket, electric doorbell, 17 inch fan, 12X14, 85 Dbm
Link to comment
Share on other sites

A rough ball park calculation is altitude x 3, and drop the extra zeros..

Say 30,000 feet.. You want to start descending at least 90 miles out using a normal

descent rate. A small plane at 7500 ft.. Start around 22-23 miles out. I use that at

various stages of the descent to see if I'm coming up short, or need to shallow up a bit.

Of course, jets and such are much faster than small prop planes, but it still tends to

work out overall, as the fast planes tend to also descend at higher rates than the

smaller ones.


With the 737, I often descend with MCP vertical speed once ATC is directing me, and

I'm off VNAV. I usually use 2200 fpm for the upper stages, and slowly reduce the rate

once I'm getting towards 10,000 ft. Say 1400 fpm or so.. Shallow up to get below

250 knots, and then whatever I think I need using the alt x 3 rule at that point.

At 10,000-11,000 ft, you normally would be about 30 miles out or so.. That's also

around about the time center will hand you off to approach.


And like one mentioned, it depends on the runway direction and if you are shooting

straight in, or passing the airport and coming back whether that altitude would have

been a real issue or not. FSX ATC tends to go overly long on the approaches in

such a case.. Usually a good bit longer than in the real world, and often a different

path too.. IE: say going into Dallas Love from the south and they give you 13R..

In the real world, you would usually run on the east side of the airport and turn around

not too awful far north of the airport.. In FSX, they run you way out west, west of

DFW, and then across the north of DFW over to Love.. Lots longer than real world,

and gives you a lot of time to slow down and get down before you get to the airport.

But FSX ATC does sometimes hand out bones that are hard to chew on, and it's

usually on the straight in approaches.. :( That's why it's good to do calculations

every once in a while during the approach to see how you stand before you get too

close to repair the damage caused by FSX ATC mayhem. :/

Luckily, if you do have to go missed, the second approach will usually be routed OK

and easy to do, as those tend to be routed overly long also.

Link to comment
Share on other sites

To be really honest, I just turn ai off as the fsx atc is so bad. I prefer to manage the descent and approach myself as apposed to letting the default atc direct you one way, then the other, and to descend faster than the aircraft can. I guess the other option is to look at atc addons but I do not have any experience in that area.



Rupert's Software

PC Specs: i7 4790K 4.4ghz, 16gb 2400 mhz, GTX970 4gb, 128gb ssd, 1tb hdd, zalman z11 plus
Link to comment
Share on other sites

Hello everyone thank you all for your answers.I am pretty busy to reply back because i had some mid-terms (!) unfortunately :(

Okay,i just have decided that i am not going to use IFR flights anymore.I will calculate my own descend process,and land the airports accordingly.


However,when i was having a flight this morning,i have faced with another disgusting problem.It included this report;


Faulting application name: fsx.exe, version: 10.0.62608.0, time stamp: 0x54abe5b4

Faulting module name: g3d.dll, version: 10.0.62608.0, time stamp: 0x54abe5dd

Exception code: 0xc0000005

Fault offset: 0x000c7c0a

Faulting process id: 0x1fc0

Faulting application start time: 0x01d07475e91a3973

Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\FSX\fsx.exe

Faulting module path: C:\Program Files (x86)\Steam\steamapps\common\FSX\g3d.dll

Report Id: 71f5c7aa-e073-11e4-8287-28d244633d35

Faulting package full name:

Faulting package-relative application ID:


Does anyone have an idea how to solve this fatal error problem ?

Intel 4790K 4.0 GHz Processor,Geforce GTX 660 2.0 GB,8 GB DDR3 Ram,1TB HD
Link to comment
Share on other sites


This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Create New...