A minor item, but the runways at KCLE (Cleveland-Hopkins) labelled 6 and 24 on the FMC are actually marked 5 and 23 in real-life. FS2002 designates them that way, as does FSNav 4.5.
Thanks.
A minor item, but the runways at KCLE (Cleveland-Hopkins) labelled 6 and 24 on the FMC are actually marked 5 and 23 in real-life. FS2002 designates them that way, as does FSNav 4.5.
Thanks.
But they are 6 and 24 in real life! See http://edj.net/cgi-bin/echoplate.pl for KCLE.
Lee Hetherington (KBOS)
>A minor item, but the runways
>at KCLE (Cleveland-Hopkins) labelled 6
>and 24 on the FMC
>are actually marked 5 and
>23 in real-life. FS2002
>designates them that way, as
>does FSNav 4.5.
>
>Thanks.
Well, actually, FS2002 and FSNav 4.5 are WRONG. ;-) The reason why the FMC states that the runways are CLE are 6R/24L and 6L/24R is because the FMC uses the realworld AIRAC database, which is updated every 28 days. It is the same data that is loaded into every real world FMC. Here is the updated plate for KCLE.
http://www.flightsim.com/dcforum/Use...783635992a.gif
The problem lies in that FS2002's database IS NOT update. It remains the same as it was as release. However, as runway designations change, due to magnetic variation, FS2002 can not keep up. Similarly, FSNav is based on the FS2002 database, so it suffers from the same limitations.
The only solution is to no longer use the free FMC database updates that are provided by DF and Prabal. :-)
.
[hr color=gray]http://home.earthlink.net/~snyders2000/ga.jpg
Then I guess the guys who actually go out and paint numbers on the ends of the runways have really screwed up!
In the end, I suppose it doesn't matter a whole lot when doing an ILS or paying attention to your heading during a visual.
Bookmarks