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.

Crashes

Featured Replies

I was wondering how you all treat a crash? I think we've all been there, we have all crashed or otherwise had some sort of an emergency. I crashed last week. I was on a beautiful short flight from KMBS (Saginaw MI) to KGRR (Grand Rapids MI) and on my final approach it happened......I stalled out and fell out of the sky. Amateur mistake by me; I looked away from my airspeed and was so concentrated on that runway and staying lined up. Suddenly the aircraft shuttered and fell straight down. In my panic, another amateur mistake, I pulled up rather than pointing the nose down to gain speed. Although I doubt it would have mattered since I was merely 500 feet above the ground.In my 3 years of simming, I have crashed relatively few times. When I crash, it hits me pretty hard. Not emotionally of course ( i think sometimes we forget this is simulated ) but I take time to dissect the situation and learn from it. I may sit out of the cockpit for a week at time... Which is exactly what I did this time. What are some of the things you do when you crash? Just restart right away? Take a break?

i7 950 OC 4ghz - GTX 570 Superclocked - X58 Sabertooth - 1 TB HD - 12gb RAM - Saitek Flight yoke, throttle quadrants, rudder pedals.

I think most people turn crash detect off. It's unrealistic and a pain.

  • Author
I think most people turn crash detect off. It's unrealistic and a pain.
I have it off too. But when the bird falls from the sky and hits the ground; it's still a crash.

i7 950 OC 4ghz - GTX 570 Superclocked - X58 Sabertooth - 1 TB HD - 12gb RAM - Saitek Flight yoke, throttle quadrants, rudder pedals.

I was wondering how you all treat a crash? I think we've all been there, we have all crashed or otherwise had some sort of an emergency. I crashed last week. I was on a beautiful short flight from KMBS (Saginaw MI) to KGRR (Grand Rapids MI) and on my final approach it happened......I stalled out and fell out of the sky. Amateur mistake by me; I looked away from my airspeed and was so concentrated on that run way and staying lined up. Suddenly the aircraft shuttered and feel straight down. In my panic, another amateur mistake, I pulled up rather than pointing the nose down to gain speed. Although I doubt it would have mattered since I was merely 500 feet above the ground.In my 3 years of simming, I have crashed relatively few times. When I crash, it hits me pretty hard. Not emotionally of course but I take time to dissect the situation and learn from it. I may sit out of the cockpit for a week at time... Which is exactly what I did this time. What are some of the things you do when you crash? Just restart right away? Take a break?
I hear ya. Someone needs to come up with a Funeral Simulator.Black%20Eye.gif Last year I "controled flight into terrain". Don't feel too bad. The "sim" element is always in the back of your mind ( not dying for real). Quite often I am sipping a beer when flying. Right after the crash, you have to comprehent what failed, exactly. Simming is great for this. You have heard the term "letting the plane get in front of you" and "keeping your head in front of the airplane". Or commonly known as a brain fart. Whats most important is to -recognise the condition- and impliment the correct procedure to stay alive. If the plane gets in front of you, you will crash. This is how I prevent that. In your case most would say you failed to "guage scan" but I break it down more than that. You have probably heard the term "Aviate/Navigate/Communicate". Priority in that order. When I look at a panel I group guages in these catagories. Aviate, you have to be 100% on. Nav. is second and then com. I never spend more than 6 seconds looking at either catagory. The guages that fall under "Aviate" would be IAS, VSI, Altitude. Myself I separate engine guages when flying a complex single and will just create a 4th catagory. On approach I would be thinking this.-- Aviate, navigate (runway lineup), communicate (foam the runway please). Even though nav and comm may be half done I always scan back to my Aviate guages. Like dialing up a radio frq, I don't force myself to complete that task. Don't linger on Nav or comm at all. If you droped in on approach, no doubt you went more than 6 seconds on your Aviate guages, or your approach speed was not established (still speeding up or slowing down). A good exercise for this would be an ILS approach, no visability...I take crashing to heart too.

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.