flightsimfan912

Sorry about not uploading yesterday's flight, I was quite busy. Anyway, yesterday's flight was a Horizon Air DHC 8 Q400 flight from Seattle-Tacoma International Airport to Sacramento International Airport. Here's all the nitty gritty details about the flight: Waypoints: KSEA, KSMF (Direct flight) Departure Gate: C4 Arrival Gate: 36 Type: IFR Time: 1 hour, 16 minutes Cruise Altitude: 24,000 feet Distance: 525.7 NM Takeoff Runway: 16L Landing Runway: 16R Landing: VFR SEA Weather: light winds, visibility: 40 M, cloudy KSMF Weather: Clear skies, no clouds, no wind, visibilty: 50 Mi Sacramento Airport is an airport that has two runways:34R, 34L, 16R, and 16L, and located in the central business district of Sacramento. The Runway arrangements is similar to Seattle's except that it has two runways and one is on the left side of the terminal and the other is on the right side. Southwest Airlines, Alaska Air, Delta Air Lines, United, Frontier, Jetblue, and American Airlines use the airport, I am not sure what airlines used the airport in 2006(when the simulator was released) Time for the details of the flight. As soon as FSX loads to KSEA, it's another busy morning, however there not that many airplanes taxiing. I got clearance to taxi to Runway 16L, and as soon as I got clearance, 6 other aircraft got directed to 16L as well, fortunately again I am the first flight to take off. From the ground it did not look like very many clouds to cause much wind, however that all changed when we were in the air. After probably around 2 minutes after takeoff clouds rolled in and all we could see was a small view of the ground, which wasn't very helpful. I now had to rely on my instruments. It took about 30 minutes to reach our cruising altitude of 24,000 feet when we reached the ceiling of the clouds. Still not very helpful as we now cannot see anything but the sky. It's a nice view but I would like to see where we are above ground. Oh well, at least we still have our GPS working. Around 90 NM we were directed to descend to 18000 feet. Seems a little early but everything worked. We descended at 2,100 feet per minute so it took us around 10 minutes to reach the altitude. When we were around 30 NM from the airport, the clouds broke away and now there no clouds, just a lot of wind, but after 5 minutes the wind stopped, which we were lucky because we had just gotten clearance to land. Landing was smoother than at Portland, Touched the back wheels first and then two seconds later the front wheels. Flaps were full and I believe we touched ground at 185 knots, so it took around 25 seconds to slow down to a taxi (5-10kts, standard throughout the US) Upon landing we were directed to Gate 36, via taxi way H9, A8, and B1. As I entered the terminal area, there wasn't a lot of planes I noticed only an Alaska Airlines 737 and two Southwest Airlines planes parked. Overall it was a nice, uneventful flight. Just a few clouds and winds. I'm still trying to learn when to exactly push the Approach hold switch as sometimes my planes make a wrong turn for a few seconds then turn the right way a few seconds late, causing me to miss my runway. In due time however, I will fully understand the ILS approach. Please suggest new routes for me to do and What plane types. If there is a different airline you want me to do, post me a link to the plane in this thread, and I will have a go. Pictures from this flight will be below. More to come in the following days, Cheers!

About to start today's flight, I'll try the screenshots feature. I've known it's been there I just have never really paid attention to it. By the way I meant 2300 fpm :)

The Fblog's Inaugural flight is a simple quick 20 minute hop from Seattle International Airport to Portland International Airport. Cruising altitude for the flight was at 24,000 feet and Cruising Speed was 270 Knots. The time of day was at 9:30(I meant to set the time to 8:30 because my PC is set at Mountain Time Zone and we're an hour ahead from Pacific Time, but oh well, I like night flying. Oh, and I flew VFR for this first flight. Most of the time I will do IFR but sometimes I will do VFR as well. The Pictures are at the bottom of the details. It was a busy night for KSEA with only all but at least 2 gates filled with aircraft, most of them Alaska Air and Horizon Air of course. The most I saw from other airlines were United and Southwest. Our plane's gate number was N10, Alaska's dedicated terminal. I first set my cruising altitude to 24,000 feet (max altitude for Dash 8 is 25,000 feet), and I set my Nav Source to GPS so the plane can fly according to the Garmin G1000. The weather was great for flying, so I decided we were ready for taxi. I contacted SEA_GND demanding which runway to take off from. ATC tells me to take off Runway 34R, which is the standard for the airport. The other runway i've ever taken off was once at 16C and 16R; I've never taken off of runway 16R, 34L or 34C. It took me about 15 minutes to get to 34R. During taxi I notice and hear that a Continental Airlines and another Horizon Air plane were told to takeoff runway 34R as well. I was privileged to be able to takeoff on 34R first. Takeoff was normal. I contact SEA_TWR and they give me clearance to takeoff. I do notice an airplane (Southwest if I remember correctly) in the distance but it was not for landing yet. Full Speed Ahead! As we takeoff, I set my altitude autopilot on to fly at 2100 per minute to 24,000 feet, but for some reason it decreased in altitude instead of gaining. It's normal for that but I wish it wouldn't do that. Anyone got any ideas? To counter my altitude bug(not to be confused with the control on some propeller aircraft (HAHAHA)), I set HDG while I manually control the altitude, now we're climbin, I tell ya! It was a pretty smooth and uneventful flight, with lots to see and look at (not including my cockpit), but it did take me until 30NM out to realize that it was a 20 minute hop, so I quickly start to descend at 23000 feet per minute. Not Bad! but I spotted the Airpot at 15 NM, so I decided my excuse was, that, since we were coming from the North, our landing runway was Runway 3 at KPDX. Bingo, Problem Solved! Nothing Happened! :) I waited until -10NM to begin turning back toward the runway for final descent and landing so I set our altitude to 3000 until 5NM out, at which I pulled out the gears and full flaps, at which I started the final descent and landing. Probably the hardest landing I ever had. Due to VFR, I cleared myself to land at Runway 3 (as no other airplane was landing or near to landing). As I touched the ground with my back two tires, my plane immediately touched the ground with the front tire. Smooth clean landing, eh? Once firmly on the ground and on a taxiway, I contact ground for gate assignment. I am told to taxi to Gate D5 via B E M T. It took me about 10 minutes to find the gate(with the help of the progressive taxi), and at the gate I decided to end the flight. Thanks everyone for reading, much more to come! Sorry about my screenshots, apparently I still do not know how to work with paint. I'll make sure the next ones aren't as bad.

I am going to start a forum blog here on Avsim.net. Here's how it's going to work: I will fly routes daily with certain airplanes(mainly Horizon Air's Dash 8 Q400, CRJ700, and Alaska Air's 737, or others on popular requests). The AI Traffic I use is Ultimate Traffic 2. The Airports I will fly to/from are KSEA, KBOI, KPDX, KLAX and other regional airports Alaska/Horizon Air fly to. My Fblog will detail such things as: From/To Airport Runway Landed/Take Off From Whether my flight was IFR or VFR Busyness of Airport Time of Flight And many other things. At the end of the details I will post around 5-10 screenshots of FSX. I will use this thread for my Fblog. Hope ya'll are interested in this, Let me know of other things I should include in my posts Cheers!

c97019, The Dash 8 I use can be found here: http://www.flightsim...ts&cm=LISTFILES, the second one down. dhc8-q400_x.zip It has Virtual Cockpit which is really nice. By far my favorite aircraft to fly in FSX. It comes with 3 liveries: Horizon Air, Flybe, and QantasLink. Horizon Air I use all the time because they are Alaska Airlines planes and our family loves Alaska Airlines.

What's your favorite route to fly in FSX(Or route that you fly most)? And what is your favorite plane to fly it with? For example, my favorite is KBOI -> KSEA with the Dash 8 Q400.

ek1, You live in Boise too? Why did you move here?

firehawk44, If I remember correctly my dotnet framework was updated. I think I said this above, but the UAC settings for Windows 7 will never allow FSX to work properly in Program Files (x86). Why? Who knows. Microsoft probably wanted better security for Windows users so programs won't alter or change the way files or processes(that Windows 7 needs to work) so that Windows 7 won't crash, etc. If people get crashes outside of Program Files (x86) they shouldn't be Fatal Errors as FSX will be able to do all that it needs to work right; they should be getting Not responding errors (not fatal errors) and these errors track down to Windows 7, NOT FSX, to which uiautomationcore.dll could be the fix, but I haven't had an issue with the errors yet.

Thanks. I do realize some people may already know about this fix but I couldn't find anywhere where there was a fix like this otherwise I wouldn't have posted. Stupid Microsoft, Why couldn't they be nice? :) Also I do realize uiautomationcore.dll is essential for some programs like Photoshop, but I don't really think you need it for FSX. I think I said it in the original post, that I tried placing the uiautomationcore.dll in the FSX folder when I had it in Program Files (x86) but it still didn't help. I don't currently have it in FSX in C:/Games/Flight Simulator x (new custom folder) but it's been working great. Once I got an unresponsive flight simulator program (like what you said) that caused me to lose a BOI - DEN flight, I think I can track it to uiautomationcore.dll, but I haven't had the problem since.

My first day on the forums. I've had an account for the library for a few years but never got onto the forums. Look for me around in the forums, I'm a hardcore flight simmer.

if you like turboprops, you can't go wrong with the Bombardier Dash 8 Q400. Absolutely my favorite plane to fly in FSX. The Plane I use for FSX can be downloaded here: http://www.flightsim...ts&cm=LISTFILES Place the aircraft folder into the main folder or the SimObjects/Airplanes folder(can't remember which) and remember to place the files in the sound and effects folder into their respective folders in the FSX folder. The only reason why I linked to flightsim.com was because the plane wasn't available on avsim's library, so that's why I linked to a different library (forgive me :) ) Here's a link to the history and specifications of the Dash 8: http://www.flightsim.com/vbfs/content.php?106-Search-Results&cm=LISTFILES

This is my first post in the AVSIM forum as I am new to forum but not to the website (actually been downloading aircraft for a few years actually). Anyway, here's my background. I first got interested in FSX back in 2008 when I first started loving flying. I found the Airport Tycoon series and bough the 2nd and 3rd one. I love the airport management simulation genre but I didn't actually get to fly the airplanes - just watch them come and go - buggily ( :) ). I found FSX after doing a simple figuring out that, hey, maybe if there's an airport sim, maybe there's a simulator where I can fly the airplanes!!! Of course, after a simple google search I found my life's dream: being a pilot. I have been on countless Alaska Airlines flights and have always wanted to fly aircraft myself. I gladly purchased FSX 6 years ago and have not regretted a penny paying $50.00 for it, maybe I've gone through 4 copies though :). Enough Background. I got a laptop for Christmas last year becaue I wanted FSX to perform better (while at the time i did not know the difference between laptop gaming and desktop gaming). So I get FSX installed and it works flawlessly for a few months. That's when I started getting these crappy Fatal Error screen that started P me off, and so I almost gave up flight simulator as I could not find a fix to my problem My laptop is a Windows 7 and I thought it would solve everything I had, well, of course it didn't. It would take about a year to save up for a desktop ($1300) with 8 GB ram, 640 GB hard drive, i7 processors, Nvidia graphics, everythin FSX needed to run smoothly. Well of course my fatal errors kept happening! I'm like what will it take to fix these problems??!?!? I'm pleased to find that I have finally found the fix(or at least a good suggestion) to Fatal Errors in FSX on Windows 7 when you switch between menus. Either most of you know about this possible fix or none of you do, I'm speaking to the ones who still can't fix this problem. It's a simple solution. I heard If you put FSX inside C:\Program Files(x86), FSX will surely get fatal errors because, absurdly, FSX does NOT, and never will, have the required permissions to fully work! You have to place FSX in a folder inside the Root of C:\ or some place other than C:\Program files(x86). I tried this and and I have run several KBOI (Home Airport)-> KSEA(Birth airport - Born in Seattle :) ) Ffights with the Horizon Air Dash 8 Q400 that you can download on flightsim (My favorite airplane to fly) fatal error-less. Smooth as clockwork. Not a cinch of a problem. This must be the fix to the error. Now I realize I may be over-hyping this as some may already know about and have spread this around, but this is for people who still don't know and have their FSX inside C:\Program Files(x86). Changing the UAC or whatever will still not work. I tried it but I had no success. I now laugh at myself as it took me 4 years to figure out that all I had to do was to place FSX in a different folder. LOL. If anyone is still having this problem even after trying this out I'll try to help but I'm not much help after this. Look for me around in the forums. Sorry if I'm overhyping this it's just that some people may not know about this fix. Peace! Also of note, I tried to download uiautomationcore.dll(it worked) but it did not fix these problems. No .dll downloading is required. Also, I deleted the uiautomationcore.dll in the SysWow folder and the Sys32 folder, not sure if that makes a difference though.