|
|
Post by klm617 on Jan 13, 2007 19:54:20 GMT -5
Almost finised with this one but I seem to have a problem with Mumbai (VABB) when I am compiling I always get the 20 hour error message. Also had the same problem with KSBN when I was doing NCA but was able to fix it. Has anyone had this problem and how can I fix it. Also if anyone could p[aint up the A310 that would be great.
|
|
|
|
Post by chrisP on Jan 13, 2007 21:16:54 GMT -5
I ran across one just like that with BOAC - check in the schedule to see if the time zone Sabena used for Mumbai is the same one as in the mraic database (airportsDB.txt file, I think).
|
|
|
|
Post by klm617 on Jan 13, 2007 21:26:36 GMT -5
How did you correct the problem
|
|
|
|
Post by klm617 on Jan 13, 2007 21:27:27 GMT -5
How did you correct the problem
|
|
|
|
Post by chrisP on Jan 13, 2007 22:30:36 GMT -5
modify the mraic database so that the time zone for the "offending" airport is the same as in the flightplans (make a backup first, though  |
|
|
|
Post by Andy on Jan 13, 2007 22:39:23 GMT -5
These are actually two different problems.
India is not an even number of hours different from GMT. Mumbai (Bombay) is GMT +5.5. The MRAI airport database is just wrong on this one. Change the line for VABB to this:
VABB|BOM|5.5|5.5|N19* 5.44'|E72* 51.99'|26
It should work fine. Any other Indian airports in your flightplan probably need to be changed as well. Same problem holds for airports in Newfoundland.
The problem with KSBN I'll bet is related to the fact that Indiana does not observe DST.
Hope this helps!
Andy
|
|
|
|
Post by klm617 on Jan 13, 2007 22:41:35 GMT -5
Got it fixed after searching forums for about 2 hours the problem is in India the difference is 5 and a half hours. In the airports database VABB is listed as 5,5 this is incorrect it should be 5.5. So one has to change the comma to a period. Sabena will be ready and submitted by tomorrow. Once again if any one can do the A310 that would be great. I will sleep better knowing I solved the problem and the flightplans will be ready tomorrow.
|
|
|
|
Post by Andy on Jan 13, 2007 22:44:37 GMT -5
That's right. That was it. Do a search for "," in the airport database file and replace all commas with decimals because this error applied to every airport with a GMT differential that is not a whole number of hours. Make a backup copy first, of course.
Andy
|
|
|
|
Post by klm617 on Jan 13, 2007 22:45:57 GMT -5
Andy you are correct on SBN thats how i fixed just change the on -5 to -6 and it compiled.
|
|
|
|
Post by Andy on Jan 13, 2007 22:53:01 GMT -5
Andy you are correct on SBN thats how i fixed just change the on -5 to -6 and it compiled. It will compile but I don't think it's correct. Indiana did not observe DST (except the counties in the Northwest, near Chicago, which are on Central time). KSBN should be |-5|-5| since there is no DST adjustment. Andy |
|
|
|
Post by klm617 on Jan 13, 2007 23:04:36 GMT -5
Yes -5-5 is correct but unless you change the first -5 to a -6 you will get the 20 hour flight error.
|
|
|
|
Post by Andy on Jan 13, 2007 23:21:08 GMT -5
Where is the offending flight coming from? Is it from Michigan, perhaps? As you probably know, Michigan at one time did not observe DST, either. At any rate, I would probably just adjust the time for that flight in your schedule file. Otherwise you are going to be incorrect on other timetables that use KSBN.  Andy |
|
|
|
Post by klm617 on Jan 14, 2007 9:58:45 GMT -5
OK Sabena 1984 completed and submitted. Once again thanks to my daughter she kicked this one out in a mere 4 hours.
|
|
qxductape
Gate Agent
QX, now with flights over Jason house every 30 mins
Posts: 60
|
Post by qxductape on Jan 14, 2007 16:14:43 GMT -5
Where is the offending flight coming from? Is it from Michigan, perhaps? As you probably know, Michigan at one time did not observe DST, either. At any rate, I would probably just adjust the time for that flight in your schedule file. Otherwise you are going to be incorrect on other timetables that use KSBN. Andy That's not entirely true. During that time the 4 counties that border Wisconsin in the UP did go on Central Daylight time when the rest of the State did not. Then it was the whole State on EST, but that screwd-up commerce, because most of the UP does business with Wisconsin, not the Lower Peninsula. That is why it's still that way now. I know that used to drive NC pilots nuts, because Ironwood, Iron Mtn, & Marinette, were on CST, but Marquette was on EST. |
|
|
|
Post by Andy on Jan 14, 2007 22:48:33 GMT -5
I tend to forget that the UP exists! No, actually, it's beautiful up there. Been there several times -- in SUMMER!
Andy
|
|
