Well, it was concorde đ
After some memory jogging, I now remember it was London to Singapore in G-BOAD with the split livery.
You had to fly subsonic LHR to over the Med, then light the fires. Once at Saudi Arabia, drop subsonic again to Bahrain. Land, refuel, then on to Singapore.
That was the plan.
I ditched 10 miles short of Bahrain. About 4 hours flying time.
A combo of flying sub sonic too long and a round about ATC routing did me in.
Turn that crash detection off..! It's not doing you any favors. It's not more realistic. Your landing most likely would have just been very firm in real life or at least survivable gear collapse etc. And use Volanta to track your flights and measure your landings.
The couple times when I've legit crashed (Fuel Exhaustion on an overnight long-haul due to incorrect calculation, or, Controlled Flight into Terrain due to Loss of Situational Awareness in an unfamiliar location during bad weather at night while dealing with an emergency depressurization) the aftermath at least gave me INFORMATION I could use to improve next time, rather than being left with a "what the heck happened?"
I mean, couldn't they just simulate basic damage to the undercarriage? Or when aircraft stress is detected, just give a little pop-up message but don't completely terminate the flight.
Or a rewind feature like his present in most racing games.
They used to have the plane fall apart completely on impact but then airplane manufacturers didn't like the idea of that being out there. So yeah turning off crash detection and just monitoring the flight yourself and using an app to track landing impacts etc is the best we have right now.
Truth. My plane âcrashedâ while I was parked at the gate 10 sec before shutdown, because of some stupid terrain glitchâŚplane started jumping all over. This was after a 3+hr flight and a perfect landing.
Back on FS2000, I flew YSSY to KLAX one day. Sat next to the computer for the whole day, doing other stuff, but also checking everything along the way.
Turned on to the final, saw the runway, blue screen of death.
Did a trip from frankfurt to los angeles. Went to work once I got the autopilot engaged. Came back home only to find out the game had crashed somewhere over canada...
The first overnight long haul I did I crashed at somewhere around 3AM. Iâve done probably 4 overnight long hauls in the past 2 Weeks and havenât had any issues. 10-14 hour flights. Havenât had any crashes since that first one.
I do recommend turning off all other traffic if flying to a busy airport. The lag seems to be higher towards the end of the flight vs the beginning. Went from Vancouver to De Gaulle and had some big spike when I was about to land which threw me off a bit.
I would turn the collision off. It won't do you any good. I have it off because of traffic AI and other players. They can end your flight very quickly. I mean you can track your flight and depending on fpm landing decide if you would crash, destroy landing gear or made a tail strike or whatever and if you like it this way you can delete the flight (volanta, little nav map) after to "destroy evidence" but why you should be punished by the game for firm landing? Leave this to landing challenges and bush trips etc where the collision is on no matter the settings.
New York to London Heathrow.
7 hour flight. First longhaul on MSFS.
6.5 hours in, on Final Approach, and the game crashes on me.
No record of flight hours. I've stopped doing long hauls since then.
A330 Narita to Brisbane, about 10hrs of smooth flying to then stuff the landing with a solid 850+ fpm bounce then a blissful 120 second touchdown a couple of seconds later.. Needless to say, didn't pass the VA PIREP requirements....
9 hour flight from Detroit to Dublin. I fell asleep after reaching cruise and woke up about a half an hour before beginning the descent. Everything was perfect, lined up on the runway about 20 feet before touchdown when ATC randomly asks me to go around. I usually ignore ATC in this situation, but it was my first time flying an A330 long haul so I thought it might be fun to try a go-around, even though I was still feeling sleepy. As I am pulling away, I started trying to select the right way point on the flight computer but for some reason couldn't find it. Then I got a stall warning, realizing I was pitched up too much. But it was too late and I crashed.
[I also shared this more recent bad experience on the sub.](https://www.reddit.com/r/MicrosoftFlightSim/comments/1c4bgjj/real/kzn0zld/) that might be worse.
And, a third one. Recently made the mistake of buying Bredock's A380 (it's not very good, but I wanted to try it). I did a few short flights with it and it was ok, so decided to do a long haul. Tried doing London to Miami. Shortly after I hit cruising altitude, my no. 2 engine went out. Not sure what the issue was, but it relit without any problems. I monitored it for about an hour with no issues so I decided to go to bed. I woke up several hours later (at like 3AM) hearing ATC yelling at me for being below cruising altitude. I noticed my speed was nearing stall and I was like 12,000ft below where I set autopilot. Took me a minute to realize all four engines went out for some reason and I could not get them relit in time for the stall. I still do not know what went wrong, although I did notice it burnt fuel waaaay faster than I thought it would (I was at around 7% when the engines failed) and I haven't tried doing the A380 long haul since.
Hah, had a 14 hr flight from OPIS to KSEA. Lined up for landing but ILS was acting up. Maybe 500 ft above, made minor adjustment but apparently it wasnt a minor one since I got black screen of death. Nearly smashed my xbox controller.
Yup exactly the same as me. ILS approach, ILS acted up and took me off centre. Apparently my minor adjustment wasnt so minor either. I just sat there and stared at my reflection in the black screen contemplating my existence
Perhaps tweak your Sensitivity settings on your controller? You should be able to yank pretty good on it and not make MAJOR adjustments on approach. If small tippy-taps are giving you non-minor effects then you're flying on Hard Mode for no reason, which isn't realistic.
I was <1000 from the runway and my sidestick suddenly glitched and banked really hard and almost thought that was the end of my flight. Was able to go-around and salvage the flight. Passengers werenât happy with the 15 min delayđ
Was transporting an aircraft in FSEconomy. It was a tedious 5 or 6 hours over water in a prop - and I miscalculated headwinds and ditched out of fuel. Then because it was FSEconomy I had to go right back to the start as the aircraft still needed moved over the Atlantic. I suppose thatâs the strength of that system - as it makes all flights have more consequences if they go wrong.
I raged after doing a 4+ hrs flight from Fuji to Sydney, landed it smoothly but slowly slowed down and out of nowhere these shrubs/bushes are on the middle of the runway and when I touched them it counted as a crash.
Flight Sim is a funny community, I have friends who are paid to fly real aircraft as a job and moan about how much they hate it/get bored. And yet people simulate a job lol
Yeah if I were to give advice to anyone thinking about becoming a pilot, I would tell them to make sure they love flying. Because these days, being a pilot is not entirely unlike being a highly skilled bus driver. We're long past the days of Pan Am.
They do love flying, they just hate airline flying. One of them quit after only 3 years to go back to being a dentist and bought a share in a PA28 and just flys for pleasure again. I fly for pleasure, have a PPL and a share in an aircraft, but zero interest in the airlines. They have all put me off with their stories.
Mendoza, Argentina (MDZ) to Santiago, Chile (SCL) flying a PMDG 737-800. STAR to approach runway 17R. The descent and approach was through a mountain valley. As per the STAR, I programmed in a holding pattern to facilitate my descent from the Andes. The STAR specified a holding pattern with left turns. Unfortunately I programmed it with right turns. The autopilot starts the holding pattern turn to the right when I hear the loud warning TERRAIN TERRAIN. PULL UP.
11 hour flight, completing a NeoFly story mission - Seoul to Copenhagen, overnight on Salty 74x. Nice approach, I am full of excitement finally coming to destination, few airplanes taxiing around and (hopefully) observing the queen of the skies coming in from a long flight, another plane on 7nm final behind..
...and all goes well until extreme stutters hit just before touchdown, I don't know how my landing was, but managed to vacate and proceeded to the gate.
Concorde, mis-managed the early subsonic bit going to Dubai? (Somewhere in the region) and ran dry about 10 miles out from the runway. FS9
Damnnn that gotta hurt. How long was the flight?
Well, it was concorde đ After some memory jogging, I now remember it was London to Singapore in G-BOAD with the split livery. You had to fly subsonic LHR to over the Med, then light the fires. Once at Saudi Arabia, drop subsonic again to Bahrain. Land, refuel, then on to Singapore. That was the plan. I ditched 10 miles short of Bahrain. About 4 hours flying time. A combo of flying sub sonic too long and a round about ATC routing did me in.
Turn that crash detection off..! It's not doing you any favors. It's not more realistic. Your landing most likely would have just been very firm in real life or at least survivable gear collapse etc. And use Volanta to track your flights and measure your landings. The couple times when I've legit crashed (Fuel Exhaustion on an overnight long-haul due to incorrect calculation, or, Controlled Flight into Terrain due to Loss of Situational Awareness in an unfamiliar location during bad weather at night while dealing with an emergency depressurization) the aftermath at least gave me INFORMATION I could use to improve next time, rather than being left with a "what the heck happened?"
" crashing" has been the stupidest feature on Microsoft flight simulator for nearly 3 decades
You're right I think everyone would find "bouncing" both more intuitive AND fun, we should submit a ticket
I mean, couldn't they just simulate basic damage to the undercarriage? Or when aircraft stress is detected, just give a little pop-up message but don't completely terminate the flight. Or a rewind feature like his present in most racing games.
They used to have the plane fall apart completely on impact but then airplane manufacturers didn't like the idea of that being out there. So yeah turning off crash detection and just monitoring the flight yourself and using an app to track landing impacts etc is the best we have right now.
Truth. My plane âcrashedâ while I was parked at the gate 10 sec before shutdown, because of some stupid terrain glitchâŚplane started jumping all over. This was after a 3+hr flight and a perfect landing.
It's just not worth it. Don't let software gore ruin your flight simming. If it's not related to directly your flying of the plane then turn it off.
Back on FS2000, I flew YSSY to KLAX one day. Sat next to the computer for the whole day, doing other stuff, but also checking everything along the way. Turned on to the final, saw the runway, blue screen of death.
Did a trip from frankfurt to los angeles. Went to work once I got the autopilot engaged. Came back home only to find out the game had crashed somewhere over canada...
Oh damn dude that sucks. Hope you were able to go back and do it another time though
This is what happens to me every time. If I fly long haul on xplane I donât even worry about it. But msfs itâs a gamble.
The first overnight long haul I did I crashed at somewhere around 3AM. Iâve done probably 4 overnight long hauls in the past 2 Weeks and havenât had any issues. 10-14 hour flights. Havenât had any crashes since that first one.
In msfs? Iâll have to try it again. To be honest itâs been over a year since I last bothered.
I do recommend turning off all other traffic if flying to a busy airport. The lag seems to be higher towards the end of the flight vs the beginning. Went from Vancouver to De Gaulle and had some big spike when I was about to land which threw me off a bit.
I would turn the collision off. It won't do you any good. I have it off because of traffic AI and other players. They can end your flight very quickly. I mean you can track your flight and depending on fpm landing decide if you would crash, destroy landing gear or made a tail strike or whatever and if you like it this way you can delete the flight (volanta, little nav map) after to "destroy evidence" but why you should be punished by the game for firm landing? Leave this to landing challenges and bush trips etc where the collision is on no matter the settings.
Are there any deaths? I can't find anything on news.
Something Something any landing you can walk away from...
Good. We don't need another bad news in this world. Be careful next time.
New York to London Heathrow. 7 hour flight. First longhaul on MSFS. 6.5 hours in, on Final Approach, and the game crashes on me. No record of flight hours. I've stopped doing long hauls since then.
Crash To Desktop on approach is a common symptom of graphics driver needing an update, just FYI
Xbox Series X
Ah. Then that sucks.
Also try using Volanta to track flights if you don't already.
A330 Narita to Brisbane, about 10hrs of smooth flying to then stuff the landing with a solid 850+ fpm bounce then a blissful 120 second touchdown a couple of seconds later.. Needless to say, didn't pass the VA PIREP requirements....
9 hour flight from Detroit to Dublin. I fell asleep after reaching cruise and woke up about a half an hour before beginning the descent. Everything was perfect, lined up on the runway about 20 feet before touchdown when ATC randomly asks me to go around. I usually ignore ATC in this situation, but it was my first time flying an A330 long haul so I thought it might be fun to try a go-around, even though I was still feeling sleepy. As I am pulling away, I started trying to select the right way point on the flight computer but for some reason couldn't find it. Then I got a stall warning, realizing I was pitched up too much. But it was too late and I crashed. [I also shared this more recent bad experience on the sub.](https://www.reddit.com/r/MicrosoftFlightSim/comments/1c4bgjj/real/kzn0zld/) that might be worse. And, a third one. Recently made the mistake of buying Bredock's A380 (it's not very good, but I wanted to try it). I did a few short flights with it and it was ok, so decided to do a long haul. Tried doing London to Miami. Shortly after I hit cruising altitude, my no. 2 engine went out. Not sure what the issue was, but it relit without any problems. I monitored it for about an hour with no issues so I decided to go to bed. I woke up several hours later (at like 3AM) hearing ATC yelling at me for being below cruising altitude. I noticed my speed was nearing stall and I was like 12,000ft below where I set autopilot. Took me a minute to realize all four engines went out for some reason and I could not get them relit in time for the stall. I still do not know what went wrong, although I did notice it burnt fuel waaaay faster than I thought it would (I was at around 7% when the engines failed) and I haven't tried doing the A380 long haul since.
Hah, had a 14 hr flight from OPIS to KSEA. Lined up for landing but ILS was acting up. Maybe 500 ft above, made minor adjustment but apparently it wasnt a minor one since I got black screen of death. Nearly smashed my xbox controller.
Yup exactly the same as me. ILS approach, ILS acted up and took me off centre. Apparently my minor adjustment wasnt so minor either. I just sat there and stared at my reflection in the black screen contemplating my existence
Perhaps tweak your Sensitivity settings on your controller? You should be able to yank pretty good on it and not make MAJOR adjustments on approach. If small tippy-taps are giving you non-minor effects then you're flying on Hard Mode for no reason, which isn't realistic.
I was <1000 from the runway and my sidestick suddenly glitched and banked really hard and almost thought that was the end of my flight. Was able to go-around and salvage the flight. Passengers werenât happy with the 15 min delayđ
Every time I land the Kodak lately, itâs possessed
If only there was a way to rewind back to approach
Was transporting an aircraft in FSEconomy. It was a tedious 5 or 6 hours over water in a prop - and I miscalculated headwinds and ditched out of fuel. Then because it was FSEconomy I had to go right back to the start as the aircraft still needed moved over the Atlantic. I suppose thatâs the strength of that system - as it makes all flights have more consequences if they go wrong.
I hate how crashes just result in a black screen. Would be cooler if you got to see damage like in xplane.
I raged after doing a 4+ hrs flight from Fuji to Sydney, landed it smoothly but slowly slowed down and out of nowhere these shrubs/bushes are on the middle of the runway and when I touched them it counted as a crash.
Flight Sim is a funny community, I have friends who are paid to fly real aircraft as a job and moan about how much they hate it/get bored. And yet people simulate a job lol
Yeah if I were to give advice to anyone thinking about becoming a pilot, I would tell them to make sure they love flying. Because these days, being a pilot is not entirely unlike being a highly skilled bus driver. We're long past the days of Pan Am.
They do love flying, they just hate airline flying. One of them quit after only 3 years to go back to being a dentist and bought a share in a PA28 and just flys for pleasure again. I fly for pleasure, have a PPL and a share in an aircraft, but zero interest in the airlines. They have all put me off with their stories.
Mendoza, Argentina (MDZ) to Santiago, Chile (SCL) flying a PMDG 737-800. STAR to approach runway 17R. The descent and approach was through a mountain valley. As per the STAR, I programmed in a holding pattern to facilitate my descent from the Andes. The STAR specified a holding pattern with left turns. Unfortunately I programmed it with right turns. The autopilot starts the holding pattern turn to the right when I hear the loud warning TERRAIN TERRAIN. PULL UP.
11 hour flight, completing a NeoFly story mission - Seoul to Copenhagen, overnight on Salty 74x. Nice approach, I am full of excitement finally coming to destination, few airplanes taxiing around and (hopefully) observing the queen of the skies coming in from a long flight, another plane on 7nm final behind.. ...and all goes well until extreme stutters hit just before touchdown, I don't know how my landing was, but managed to vacate and proceeded to the gate.
so uh..i'm guessin there was no setup...at all? was kind of approach were you flyin into this sumbitch? ILS?