I have crash damage enabled always, Just noticed on a bad landing that would normally result in a usual restart/main menu result, it didn’t. Checked options, disabled crash damage save, enable again and save, load up a plane and try again, on purpose crash, no damage plane just rolls around? Tried with 172, citation and king air 350i so far all with the same result. Does anyone else have this or is it just me? I’m not on beta, just pc store su14.
I noticed it several months ago. I don’t hit the ground too often but some time ago I left my PC when flying Comanche 250 on autopilot and on my return, I found it lying on the ground. Apparently, it hit the mountain that was on the flight path :). The game didn’t register it as a crash. I also once stalled on approach to Lukla and dropped like a rock. Same result, the plane hit the ground and nothing happened.
2 Likes
Noticed the same, also with the Comanche.
1 Like
Not just me then 
maybe should be reported as a bug, I did a brief search earlier and nothing showed up, be interesting to see if someone on beta 15 could try it out to see if its affected too, before I submit a bug report though!
I can’t test again but I have crashed into the sea - Vertically at speed. Then the aircraft just appeared to float, right way up. I did not worry about it.
My point is all crashed into ground/sea are not registering. sPK
1 Like
I tried this on xbox too and crash damage is definitely working there?
I have similar issue with the game being very tolerant regarding the virtual law of physics.
Thanks to @SmotheryVase665 who pointed this thread, I link my observations/issues I wrote in my thread:
I didn’t post here first because I thought it was an A310 bug but maybe it’s related and the issue is systemic in the game.
1 Like
Few days ago I derped on checking fuel and so ran out over the pacific in a C152, I decided to go with it and attempt a ditching. Pretty sure I followed the correct procedure but on contact with the ocean I got the typical you rekt screen.
Are you on the beta 15?
Me? No.
Lorem ipsum
I’m just wondering if it’s fixed on beta 15 is all. Cheers.
According to @RomoRocket in this post, stress damage is working on the A320neo in the .9 build of the SU15 beta.
2 Likes
Hmm 
It’s not really a problem for me I don’t crash much, was just weird, I’m interested to see how this develops though.
Obviously crash/stress damage should work properly so we learn by our mistakes.
Same here. Crash effects are not working
I just had a play around in assitance settings, enabled crash damage, stress damage and engine damage, took the a320 for a ride and oversped it around 520kts got the menu “you overstressed the aircraft”, turned stress and engine damage off but left crash damage on, went and crashed and hey it detected it as normal, took a 172 out and crashed that and it works again. I don’t know if its a fix, but I’ll try it again tomorrow!
So just to clarify.
Engine damage off.
Stress damage off.
Crash damage on.
C172 asobo, collision results in crash detected.
A320 (whose?), collision results in NO crash detection.
I set all to on and saved, then tried a320 first and oversped it to around 520kts and got stress damaged screen. Back to settings and just disabled stress and engine damage, then tried 172 G1000 with just crash damage enabled and it works again as it should.