Jump to content

CaptRich

Member
  • Posts

    3
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

CaptRich's Achievements

1

Reputation

  1. I would like to see KMKE (Milwaukee Mitchell Intl), KMCI (Kansas City Intl), and, or, a good rendition of KATL (Atlanta Intl) to add to my ever growing collection of MSFS airports.
  2. That is odd! I have the Drzewiecki Design KMDW (Midway Chicago) airport (a very nicely done airport) and I see IA traffic always doing go-arounds instead of landing. I haven't seen one land yet. Maybe it's because all the runways are too short in length for the AI to deal with? idk, but it sure does look hilarious.
  3. Hi, just wondering if anyone else has had this issue. Upon loading in a flight plan into my PMDG 737-700 to do an ILS land at the Oklahoma City airport runway 35R, the plane does not pickup the Localizer at all. I can even choose this runway directly in the FMC under the Approach menu, it will add it, even show me the localizer freq (110.90 mhz) and course (356 degrees), and yet when I set it up, and arrive near the ILS feather or even further back, my LOC display doesn't show it, and will not pick it up at all. Here's the mysterious thing. I've tried an ILS approach on runway 35L, (next runway over, just west of 35R) and that one works just fine! I haven't tried runways 17L or 17R yet, (and may today) but so far the issue is only on 35R. Again, I've tried both twice, 35L works just fine, 35R does not. Anyone else have ILS issues with 35R? Other than that, I LOVE this airport! Great job on its design! Rich
×
×
  • Create New...