One of my favorite flights using Flight Simulator 2004 is from Kennedy to Washington, DC in a variety of aircraft. I usually fly at least twice weekly using the awesome Level D Simulation

Hi, Jim.I've never experienced 2 or 3, but I have had to go around an aircraft that is sitting short of the runway. It's usually due to the hold short line being messed up and ATC not recognizing it. It happens at KGEG and I had to use AFCAD to move the hold short line to accomodate where ATC will recognize you are holding short of the runway. Since then I haven't had a chance to fly when other traffic is there, but I hope it fixed it.

Thanks for the comments Steven. In my case there were several aircraft in front of me that ground controllers would not allow to taxi across the hold short line. I really had no other option but to go around the aircraft.Jim

FS9 generates a NTSB report if you have a mid-air collision? Really? That's very nerdy and kind of cool. I gotta see that. I have never seen FS9 do that.

You are now under investigation by the NTSB.Pending investigation will depend the contents delivered to your gravestone at Arlington.And it looks as though you have 48 lost in the Potomac?:-)Daniel

Suggestion: "AISMOOTH" (freeware). There probably are a few other downloads that address such problems as well.The only problem of which I read with AISMOOTH is that you may want to run it minimized and ignore the table display. She seems to shut down erratically if not minimized.This might cure your traffic problems.Happy flying:RTH

Hi Jim,The answers:1. This is a common situation. The solution is to open teh airport in AFCAD, and on the taxiways that cross the runway, draw a taxiway inA AFACD that doesn't "touch" the runway "line". If you observe that Z taxiway, it should be linked to a node that intercepts the runway, and then to another node on the other side. You can either insert another node that doesn't touch the "runway" line, or link directly the two sides of the runways with a direct link. Only this way, ATC will not stop you from crossing the runway, because you will pass a node that is in the way of a takeoff or landing aircraft. (hope you understand what I meant)! The drawback, is that you may see airplanes crossing the runway as other takes-off or land!!! But for me its torable!!2. This is another common problem with AFCAD files, specifically those that with the crossing runways method! You should ask ATC for another runway, when he clears you for that one, and you'll see that the others are available. And that one that your were cleared, is not!!!!! Confuse hum? That runway 10 is one of the "stars" that were created to enable the multiple runway operations! It's a drawback sometimes. But it's not always!!!!3. That should be any add-on installed on your system! I never saw it!Hoped it helped.Regards,Miguel

Jim, As to number 3, I have never seen anything like this before and I have been simming for a long time. If this indeed did occur I have two guesses, either you have some sort of add on that generates some sort of report when you crash or Microsoft added this when they released the patch which I find unlikely. I am curious though so I may have to crash and see what happens. What add ons do you have that could do something like this? I suppose it could be a part of the ATR 72 but I do not have that aircraft so I can not test that myself. Maybe you could purposely crash and find out what that report says to get a clue as to what add on is generating it.Philip Olsonhttp://www.precisionmanuals.com/images/forum/supporter.jpg

Thanks Philip. I have had several "land" crashes and have seen the analysis of the flight after that crash but this mid-air collision was definitely different. I too have been simming for a number of years and have never seen it before. I was hoping someone might be able to read the programming code as I'm guessing the info is built into a .dll or other file. It could be part of an addon but that would be very difficult for me to determine as I have quite a few addon's. If you crash, make sure it's with an aircraft in the air and not on the ground. Thanks anyway for your help.Jim

Thanks for the excellent info Miguel. I am familiar with AFCAD's and understand what you're talking about. I just thought it was a bit different since AI traffic is being held at the runway 22R intersection. As I stated in my original thread, I went around the aircraft via another intersection and taxiway to get to my takeoff runway, 31L. ATC ground did not stop me or place me in a hold before I crossed runway 22R but they kept the AI traffic on hold until I took off.I do not fully understand your second answer. My flight plan was to KDCA but Washington Center was trying to make me land on Runway 10 at Atlantic City. Atlantic City was not in my flight plan and Runway 10 does not exist at KDCA.Thanks again for your help!Jim

Have you ever thought of VATSIM?If you enjoy complex aircraft, you may well enjoy real ATC. It's much better than the FS ATC.Here's a link: http://vatsim.net/http://online.vatsimindicators.net/916312/3.png

>>This time I was heading back toward Washington. Nearing waypoint Graco I was advised by Washington Center I was cleared for landing at runway 15. Runway 15? How did they come up with that runway! Now I live in this area and have never heard of aircraft landing on this runway. If it

Are you sure that the runway 10 was at KACY? To get multiple non-parallel runways to be active at the same time you have to make many small runways in the AFCAD with headings about 8 degrees apart to "bridge the gap" between the two actual runways. Usually these runways are as short as possible (10m), closed and located far away from the actual airport so ATC doesn't send anyone to them but AFCAD isn;t perfect and sometimes ATC will vector to them if you are or AI is coming from that direction. If you have AFCAD you can try selecting the "bridge" runways and moving them to another location which is less likely to have traffic. It should be about 100 miles away, maybe out in the Atlantic somewhere. hope this makes sense. Cool story though.Drew

I was flying my PMDG 737 the other from Edmonton to Saskatoon. During my climb to FL290 I heard my TCAS go off, but didn't pay much attention then all of the sudden my autopilot disconnected and went into a dive for what I thought was no reason. It was strange since I had my TCAS set to TA only, so anyway I looked around for another airplane and didn't see anything so I changed to my spot view and panned around for a while and all the sudden a 767 (don't remember which airline) came shooting across the screen right on top of me, he was less then a hundred feet above me, it was pretty cool.Jeff

Thanks Drew for the info and your kind comments concerning "my story". I'm getting very confused though. Are you saying an AFCAD caused ATC to send me to another airport other than my final destination (KDCA)? I think I'll disable any AFCAD's for KACY (Atlantic City) and see if that will keep me on course to KDCA. Thanks again.Jim