Creating Flight Plans from Timetable Data Testing

[tgibson]

Hi,

You mention in your development thread to test AIFP using the timetable data to flight plan feature. So I have. I am using Development version 3.2.02(s).

I compared a compile of one of my propliner AI files (Aeronaves de Mexico 1962) using the MRAI Compiler and AIFP. They created flights for the same number of aircraft (1 Britannia, 6 DC-3s, 7 DC-6s, and 1 DC-8) - good job. But many of the 15 flight plans did not have valid returns to the original airport:

while the MRAI Compiler was able to achieve that.

Also, when I first loaded the timetable data file and tried to edit the Default Sit Time box, the following error appeared:

After clicking OK, the error returned if I tried to do anything else. I could only click the red X and click through many of these error messages to get back to the main screen. But I was able to change that screen by then going back into that dialog box - my changes to most boxes (including Default Sit Time) were saved and re-displayed, and then I could move on. I set Default Sit Time to 2 minutes (I had override ETAs for all flights) and the Priority to Same FN to 60 min. I did not click the Ensure Closure box since I was testing things (I realize fake flights would be added in that case). I tried both setting the Separator to Other ; and left at Auto - both seemed to work.

PS. To get the results below the Parking Code box above was set to AMX, the parking code in the plane's aircraft.cfg file (not shown above).

Then this box popped up:

I'm not sure what AIFP is looking for in this case? The aircraft entries seemed to be correctly assigned:

Finally, I chose File/Save File Set to get my compiled text files.

This is the source file I used:

AM;100;MMMX;MMGL;0845;1010;1234567;DC6
AM;100;MMGL;MMCL;1040;1120;1234567;DC6
AM;100;MMCL;MMCN;1150;1255;1234567;DC6
AM;100;MMCN;MMHO;1325;1410;1234567;DC6
AM;100;MMHO;KTUS;1445;1600;1234567;DC6
AM;101;KTUS;MMHO;1000;1115;1234567;DC6
AM;101;MMHO;MMCN;1200;1245;1234567;DC6
AM;101;MMCN;MMCL;1315;1420;1234567;DC6
AM;101;MMCL;MMGL;1450;1740;1234567;DC6
AM;101;MMGL;MMMX;1810;1935;1234567;DC6
AM;102;MMMX;MMLO;0700;0810;13;DC6
AM;102;MMLO;MMMZ;0825;0855;13;DC6
AM;102;MMMZ;MMLP;0920;1035;13;DC6
AM;102;MMLP;MMTJ;1100;1355;13;DC6
AM;102;MMTJ;KLAX;1430;1525;13;DC6
AM;103;KLAX;MMTJ;1000;1055;24;DC6
AM;103;MMTJ;MMLP;1130;1425;24;DC6
AM;103;MMLP;MMMZ;1450;1605;24;DC6
AM;103;MMMZ;MMLO;1630;1900;24;DC6
AM;103;MMLO;MMMX;1915;2025;24;DC6
AM;104;MMMX;MMSP;0615;0745;135;DC3
AM;104;MMSP;MMDO;0800;0935;135;DC3
AM;104;MMDO;MMMZ;0950;0955;135;DC3
AM;104;MMMZ;MMCL;1010;1105;135;DC3
AM;104;MMCL;MMLM;1140;1235;135;DC3
AM;104;MMLM;MMCN;1250;1345;135;DC3
AM;104;MMCN;MMGM;1415;1455;135;DC3
AM;104;MMGM;MMHO;1510;1550;135;DC3
AM;104;MMHO;MMNG;1605;1710;135;DC3
AM;105;MMNG;MMHO;1030;1135;246;DC3
AM;105;MMHO;MMCN;1201;1240;246;DC3
AM;105;MMCN;MMGM;1255;1335;246;DC3
AM;105;MMGM;MMLM;1350;1445;246;DC3
AM;105;MMLM;MMCL;1500;1555;246;DC3
AM;105;MMCL;MMMZ;1625;1720;246;DC3
AM;105;MMMZ;MMDO;1735;1945;246;DC3
AM;105;MMDO;MMSP;2000;2140;246;DC3
AM;105;MMSP;MMMX;2155;2330;246;DC3
AM;108;MMMX;MMLO;0700;0810;6;DC6
AM;108;MMLO;MMMZ;0825;0855;6;DC6
AM;108;MMMZ;MMLP;0920;1035;6;DC6
AM;108;MMLP;MMTJ;1100;1355;6;DC6
AM;109;MMTJ;MMLP;1500;1755;6;DC6
AM;109;MMLP;MMMZ;1820;1935;6;DC6
AM;109;MMMZ;MMLO;2000;2250;6;DC6
AM;109;MMLO;MMMX;2305;0015;6;DC6
AM;111;MMTJ;MMGL;1430;1915;1234567;BRT
AM;111;MMGL;MMMX;1945;2100;1234567;BRT
AM;112;MMMX;MMGL;0800;0915;1234567;BRT
AM;112;MMGL;MMTJ;0945;1220;1234567;BRT
AM;116;MMLP;MMCL;1000;1125;7;DC3
AM;117;MMCL;MMLP;1440;1605;7;DC3
AM;118;MMLP;MMMZ;1700;1845;246;DC3
AM;119;MMMZ;MMLP;1900;2045;246;DC3
AM;120;MMMX;MMAA;0615;0715;57;DC6
AM;120;MMAA;MMLP;0745;1020;57;DC6
AM;120;MMLP;KLAX;1050;1415;57;DC6
AM;121;KLAX;MMLP;1515;1840;57;DC6
AM;121;MMLP;MMAA;1910;2345;57;DC6
AM;121;MMAA;MMMX;0015;0125;16;DC6
AM;122;MMLP;MMLT;1010;1115;135;DC3
AM;122;MMLT;MM0S;1130;1220;135;DC3
AM;122;MM0S;MMGM;1235;1320;135;DC3
AM;122;MMGM;MMHO;1335;1415;135;DC3
AM;122;MMHO;MMTJ;1435;1735;135;DC3
AM;123;MMTJ;MMHO;0840;1140;246;DC3
AM;123;MMHO;MMGM;1155;1235;246;DC3
AM;123;MMGM;MM0S;1250;1335;246;DC3
AM;123;MM0S;MMLT;1350;1440;246;DC3
AM;123;MMLT;MMLP;1455;1600;246;DC3
AM;200;MMMX;MMTC;0730;0940;1234567;DC6
AM;200;MMTC;MMCU;1010;1120;1234567;DC6
AM;200;MMCU;MMCS;1150;1245;1234567;DC6
AM;201;MMCS;MMCU;1430;1525;1234567;DC6
AM;201;MMCU;MMTC;1555;1705;1234567;DC6
AM;201;MMTC;MMMX;1735;1950;1234567;DC6
AM;205;MMCU;MMCG;1200;1315;135;DC3
AM;205;MMCG;MMCA;1330;1330;135;DC3
AM;205;MMCA;MMNG;1345;1410;135;DC3
AM;205;MMNG;MMML;1425;1515;135;DC3
AM;205;MMML;MMTJ;1530;1615;135;DC3
AM;206;MMTJ;MMML;0700;0745;246;DC3
AM;206;MMML;MMNG;0800;1050;246;DC3
AM;206;MMNG;MMCA;1105;1130;246;DC3
AM;206;MMCA;MMCG;1145;1345;246;DC3
AM;206;MMCG;MMCU;1400;1515;246;DC3
AM;208;MMMX;MMLO;0800;0925;135;DC3
AM;208;MMLO;MMSP;0940;1025;135;DC3
AM;208;MMSP;MMIO;1040;1210;135;DC3
AM;208;MMIO;MMMV;1225;1310;135;DC3
AM;208;MMMV;MMPG;1325;1450;135;DC3
AM;209;MMPG;MMMV;0800;0925;246;DC3
AM;209;MMMV;MMIO;0940;1025;246;DC3
AM;209;MMIO;MMSP;1040;1210;246;DC3
AM;209;MMSP;MMLO;1225;1310;246;DC3
AM;209;MMLO;MMMX;1325;1450;246;DC3
AM;210;MMMX;MMCV;0900;1115;123456;DC3
AM;211;MMCV;MMMX;1145;1355;123456;DC3
AM;214;MMMX;MMAA;0630;0730;246;DC6
AM;214;MMAA;MMGL;0800;0930;246;DC6
AM;214;MMGL;MMMY;1000;1150;246;DC6
AM;214;MMMY;KSAT;1230;1345;246;DC6
AM;215;KSAT;MMMY;1615;1730;357;DC6
AM;215;MMMY;MMGL;1830;2020;357;DC6
AM;215;MMGL;MMAA;2050;2220;357;DC6
AM;215;MMAA;MMMX;2250;0001;357;DC6
AM;216;MMMZ;MMTC;0800;1015;357;DC6
AM;216;MMTC;MMMY;1045;1145;357;DC6
AM;216;MMMY;KSAT;1230;1345;357;DC6
AM;217;KSAT;MMMY;1615;1730;246;DC6
AM;217;MMMY;MMTC;1815;1915;246;DC6
AM;217;MMTC;MMMZ;1945;2000;246;DC6
AM;220;MMMX;MMMA;1230;1420;1234567;DC6
AM;221;MMMA;MMMX;1530;1720;1234567;DC6
AM;300;MMAA;MMMX;0630;0730;1234567;DC6
AM;301;MMMX;MMAA;0930;1030;1234567;DC6
AM;302;MMAA;MMMX;1115;1215;1234567;DC6
AM;303;MMMX;MMAA;1330;1430;1234567;DC6
AM;304;MMAA;MMMX;1515;1615;1234567;DC6
AM;305;MMMX;MMAA;1700;1800;1234567;DC6
AM;306;MMAA;MMMX;1830;1940;1234567;DC6
AM;307;MMMX;MMAA;2030;2140;1234567;DC6
AM;308;MMAA;MMMX;2210;2320;1234567;DC6
AM;309;MMMX;MMAA;2200;2310;1234567;DC6
AM;311;MMMX;MMZH;0830;0955;136;DC3
AM;312;MMZH;MMMX;1030;1155;136;DC3
AM;400;MMMX;KJFK;0930;1520;1234567;DC8
AM;401;KJFK;MMMX;1800;2006;1234567;DC8

Hope this helps,

 

[gadgets]

Thanks for the detailed report, Tom

But many of the 15 flight plans did not have valid returns to the original airport:

Did you check the Ensure Closure checkbox. If not, that's why you got those errors. (AIFP is giving you a chance to fix the non-circularity as you wish). If checked, AIFP will (should) add a deadhead leg back to the originating airport.

when I first loaded the timetable data file and tried to edit the Default Sit Time box, the following error appeared

A last minute change that I obviously didn't check. It's fixed in the next release.

Then this box popped up:

Can't explain. You had previously provided this data to me and that's what I used for testing. I've never saw this error. What the message was telling you was that the input data is faulty. But, clearly, the first 15 lines in the file are not faulty. It may have something to do with the issue you experienced with the default sit-time and the extraordinary actions you had to take to get around it.

Don

 

[tgibson]

Hi again,

I did not check the Ensure Closure box since I did not need to add any extra flights when using the MRAI Compiler - it made the correct circular flights. I was comparing AIFP to that result.

I don't think that AIFP was telling me that the input was faulty? It mentions 15 lines, which matches the 15 flight plans in the OUTPUT file. Logical?

Thanks,

 

[gadgets]

I did not check the Ensure Closure box since I did not need to add any extra flights when using the MRAI Compiler

I have not made use of the MRAI compiler beyond testing against AIFP. It's documentation suggests non-circular FPs require manual attention - which is why that box is unchecked at startup. The next release of AIFP will check this box by default and it will be up to the user to uncheck it when necessary. (Or, perhaps I should dispense with the option entirely.)

I don't think that AIFP was telling me that the input was faulty? It mentions 15 lines, which matches the 15 flight plans in the OUTPUT file. Logical?

No. That message refers to timetable input data. "15" seems to be a coincidence.

Don

 

[tgibson]

Yes, you must manually edit any non-circular flight plans when using the MRAI Compiler. This flight plan file did not require any such editing when so compiled.

Now when I try to compile this data file, after pressing Continue I get the error message with 15 missing aircraft. I click OK, then nothing appears. The three boxes are empty. Using the same version of AIFP.

 

[gadgets]

You recall, I assumed the cause was the extraordinary actions you took to get out of the earlier situation since I had never received such messages. I've not done any further investigation. Apparently I need to, and will.

Don

 

[gadgets]

Tom, I have not been able to duplicate this issue with the data I have.

Referring to the code, AIFP "thinks" there are less than 8 fields in the first 15 lines of the input file. Please take a look at the file and see if there is anything unusual. (an extra space, anything) If you don't find anything, please post the file so I can investigate further.

Don

 

[tgibson]

I did post the source file in my original post, just copy and paste it into a text file.

 

[tgibson]

OK, now I'm getting a third result. I changed the aircraft types in the source file above (I changed BRT to Britannia and DC8 to DC85 which are installed in my AI aircraft, the rest are already installed) and now I get a message that it cannot find an aircraft which matches DC6. I have two AI aircraft that use aircraft_type=DC6 and ai_airline=AMX installed in my Aircraft folder. When I then use the search box that pops up and identify the desired DC-6 I get one flight plan using that plane instead of 7 that should be there, and there should be 15 plans total. No planes other than the DC-6 are listed in the aircraft box. I've attached the relevant aircraft.cfg files and the actual source file used.

 

[gadgets]

Thanks for the file and the aircraft.cfgs, Tom. (While I appreciate the list above contains all the data, I'm suspicious of anomalies in the file such as control or other non-printing characters. Clearly, the problem is not due to the data shown above.) This should allow me to test exactly what you are using.

OK, now I'm getting a third result.

Curious, nothing has changed in AIFP since your earlier tests. From you first post above, it would seem that all was well then.

ai_airline=AMX installed in my Aircraft folder

This should not have any affect on AIFP. AIFP uses aircraft type and parking codes only. Perhaps that's why you lost the DC-6s.

When I then use the search box that pops up and identify the desired DC-6 I get one flight plan using that plane instead of 7

Don't know what search box you are referring to that lists flight plans. From a quick scan of the input data, if you eliminate the first 15 lines, I suspect you'd need only one FP to accommodate the remaining 5.

I'll get back to you as soon as I have something to report.

Don

 

[gadgets]

Tom, from a first look at the data you sent, of the aircraft, only the Britannia will be found. This is because, while the ui_type in the [General] block in each other case matches the timetable A/C designation, the ut_type entries in the [Fltsim.x] block don't. As noted at the bottom of page 23 of the manual, the [Fltsim.x] takes precedence over the [General] entry.

Unfortunately, I haven't seen the 15-line error report you received. I'm still working on that. Obviously, it's not the data that's at fault and, since I can't duplicate it using your data. Since I can't "trap" the error - this is going to make life difficult.

Don

 

[tgibson]

Hi,

Sorry, I meant atc_parking_codes=AMX and atc_model=DC6. I was tired.

I've tried it a fourth time and got the result you did above.

1. Loaded the plans_AMX62_text.txt file using File/Open Timetable Data File.
2. I get this box and I fill it out as below, then click Continue:

3. Then this box appears. Note that AIFP has found only one aircraft in my FS2004 installation (Britannia), due to the incorrect ui_type lines in the fltsim sections as you state above. However, I don't understand why this is should be true, and I wish that behavior could be changed or at least selected using a radio button in step 2 (Use atc_model or Use ui_type). I then click Yes.

4. This brings up the "search box" I mentioned above. In this box if I choose Britannia from the drop down box, it lists the 4 Aeronaves Britannias I have on my system (2 AI and 2 flyable). I delete the two flyable versions. All of the other aircraft (DC3, DC6, and DC85 are blank. For each aircraft I click the Add button and add the relevant planes from the aircraft list. I then click the Continue button.

5. I then get this error box, although hidden behind the main screen. I click OK. (Yes, I know AIFP can create fake plans to close these.)

6. I'm now back to the main screen, with the following display:

Note that only the flight plan using the Britannia is filled out completely with AC# and reg number, although it would seem that AIFP could do the same thing with the aircraft I added manually in step 4. It would be nice to add this feature.

7. I double clicked a DC-3 to show it says it has the correct parking code (AMX) and aircraft type (DC3) and should have been found in step 3. That's why I was confused, since this box does not display the incorrect code in the fltsim section but only the correct code in the General section. I realize now that data is in the fltsim block tab. Got it.

Hope this helps,

 

[tgibson]

I can confirm that once I change the aircraft types in the data file to the ui_type values in the fltsim sections, I get the expected result. If I include more than one aircraft for a given aircraft type AIFP only uses the first such aircraft, I assume by design. That would be logical if the first one is the "default" aircraft and the rest are special paint jobs, etc., but often times it would be nice to split the plans evenly between the aircraft (i.e. two different paint jobs, etc.) or assign them individually (different reg numbers). I can do that manually of course, no problem.

So the only actual problems I see are the lack of closure in the plans vs the MRAI Compiler's results and the lack of AC# and reg number in the plans of aircraft added manually. The other things would just be nice to have. Thanks for stepping me through the process.

Hope this helps,

 

[gadgets]

So, it appears that the "15 line error message" is no longer happening to you. I'll stop looking for it.

If I include more than one aircraft for a given aircraft type AIFP only uses the first such aircraft, I assume by design. That would be logical if the first one is the "default" aircraft and the rest are special paint jobs, etc., but often times it would be nice to split the plans evenly between the aircraft

If there is more than one flight plan generated for a given aircraft type and more than one aircraft of that type exists, AIFP should assign those aircraft sequentially. But, I can see this is no longer occurring. It will in the next release.

Don

 

[gadgets]

Not sure what happened to the automatic distribution among available aircraft, Tom, but I the attached should resolve it. Please give it a try.

Don

 

[tgibson]

Hi,

Yes, that works fine now. The only error box that comes up is the No Closure warning when I uncheck the Ensure Closure box.

The odd thing is that I end up with 15 flight plans when the Ensure Closure box is unchecked (1 Britannia, 6 DC-3s, 7 DC-6s, and 1 DC-8), but 19 flight plans when the box is checked (1 Britannia, 7 DC-3s, 10 DC-6s, and 1 DC-8). I'm not sure why adding an extra leg should create four more aircraft?

Hope this helps,

 

[gadgets]

Tom, the main difference between MRAI and AIFP now is that AIFP ensures that when it adds a deadhead leg, there's time for normal completion. Sometimes, this necessitate first stripping off the last leg and placing it in another FP.

It appears that MRAI just adds the d3eadhead leg to the end of the file and damn the consequences.

In the next release (hopefully later today), the Ensure Closure box will be checked by default.
Don

 

[gadgets]

Tom, while my previous post explains why AIFP generates more plans than MRAI when deadhead legs are added, it does not explain the differing sequence of legs - even when they both generate the same number of FPs - given that they use identical methodology. I have discovered that MRAI fails to convert the local time in the timetable data to UTC. In the MRAI-generated flightplans text file, all times are local whereas FS is expecting UTC time in flightplans. Since sequencing is based solely on leg departure time, its no wonder the two applications come up with differing sequences.

Don

 

[Bob Keeshan]

I'm trying to use the open time table data file option, and while it finds my AI aircraft based on the aircraft type, it only assigns an aircraft to the first flight plan it creates. The other flight plans has no aircraft assigned to them.

Here's my flight plan
day depart arrival dtime atime flnum actype
7 KMSY KLAX 20:05 22:35 1325 A319_DL
7 KLAX KMSY 13:10 18:53 1325 A319_DL
7 KCMH KLAX 7:54 10:15 1327 A319_DL
6 KLAX KCMH 22:50 6:05 1170 A319_DL
6 KMSY KLAX 19:05 21:35 1325 A319_DL
6 KLAX KMSY 12:45 18:20 1325 A319_DL
6 KSLC KLAX 11:02 12:05 2576 A319_DL
6 KBNA KSLC 7:25 10:19 1254 A319_DL
5 KSLC KBNA 17:25 21:38 1390 A319_DL
5 KSJC KSLC 13:15 16:08 1182 A319_DL
5 KSLC KSJC 11:35 12:37 1182 A319_DL
5 KSEA KSLC 7:15 10:18 1634 A319_DL
4 KSLC KSEA 22:15 23:30 1557 A319_DL
4 KRNO KSLC 16:55 19:20 1509 A319_DL
4 KSLC KRNO 15:14 15:46 1509 A319_DL
4 KJAC KSLC 13:10 14:09 927 A319_DL
4 KSLC KJAC 11:17 12:22 927 A319_DL
4 KCLT KSLC 7:40 10:20 238 A319_DL
3 KSLC KCLT 17:25 23:16 522 A319_DL
3 KSAN KSLC 10:10 13:07 2295 A319_DL
3 KSLC KSAN 8:30 9:34 2295 A319_DL
1 CYYZ KSLC 15:59 18:23 2833 A319_DL
1 KSLC CYYZ 9:35 15:19 2797 A319_DL
1 KLAX KSLC 5:45 8:44 1404 A319_DL
7 KSLC KMSP 15:15 18:53 12 A320_DL
7 KMSP KSLC 11:30 13:25 929 A320_DL
7 KBWI KMSP 8:35 10:26 2513 A320_DL
6 KATL KBWI 19:20 21:13 2024 A320_DL
6 KBWI KATL 16:30 18:33 1425 A320_DL
6 KATL KBWI 13:55 15:41 1425 A320_DL
6 KMCI KATL 10:14 13:05 513 A320_DL
6 KATL KMCI 8:20 9:33 513 A320_DL
6 KCMH KATL 5:30 7:08 2197 A320_DL
5 KATL KCMH 22:35 0:06 1736 A320_DL
5 KDTW KATL 19:10 21:14 1130 A320_DL
5 KSLC KDTW 11:05 16:43 1512 A320_DL
5 KRDU KSLC 7:15 10:02 2790 A320_DL
4 KSLC KRDU 17:17 23:14 2791 A320_DL
4 KMSP KSLC 14:25 16:22 596 A320_DL
4 KSFO KMSP 6:25 12:02 1101 A320_DL
3 KMSP KSFO 15:26 17:40 460 A320_DL
3 KBWI KMSP 12:07 13:54 1857 A320_DL
3 KDTW KBWI 9:55 11:27 1536 A320_DL
3 KLGA KDTW 7:15 9:10 1073 A320_DL
2 KMSY KLGA 17:34 21:30 1311 A320_DL
2 KLGA KMSY 13:55 16:25 2598 A320_DL
2 KMSP KLGA 9:05 12:43 1743 A320_DL
2 KDEN KMSP 6:04 9:07 1716 A320_DL
1 KSLC KDEN 20:31 22:10 1471 A320_DL
1 KSAN KSLC 16:48 19:44 50 A320_DL
1 KSLC KSAN 15:06 16:04 1794 A320_DL
1 KOAK KSLC 11:35 14:18 537 A320_DL
1 KSLC KOAK 9:50 10:55 537 A320_DL
1 KMSP KSLC 7:00 9:04 2649 A320_DL
7 KLGA KIND 14:40 17:58 3362 ERJ_175_DL
7 KIAH KLGA 8:00 12:45 3397 ERJ_175_DL
6 KLGA KIAH 18:25 21:40 3289 ERJ_175_DL
6 KSYR KLGA 15:20 16:43 3351 ERJ_175_DL
6 KLGA KSYR 13:35 14:49 3368 ERJ_175_DL
6 KCMH KLGA 11:08 12:55 3316 ERJ_175_DL
6 KLGA KCMH 8:30 10:38 3330 ERJ_175_DL
6 KCMH KLGA 6:00 7:45 3286 ERJ_175_DL
5 KLGA KCMH 20:24 22:27 3374 ERJ_175_DL
5 KBOS KLGA 18:00 19:39 2739 ERJ_175_DL
5 KLGA KBOS 16:00 17:28 2738 ERJ_175_DL
5 KBOS KLGA 14:00 15:25 2741 ERJ_175_DL
5 KLGA KBOS 12:00 13:24 2744 ERJ_175_DL
5 KDFW KLGA 7:00 11:35 3375 ERJ_175_DL
4 KLGA KDFW 15:00 18:26 3294 ERJ_175_DL
4 KBOS KLGA 12:00 13:25 2749 ERJ_175_DL
4 KLGA KBOS 10:00 11:25 2743 ERJ_175_DL
4 KBOS KLGA 8:00 9:25 2747 ERJ_175_DL
4 KLGA KBOS 6:00 7:04 2745 ERJ_175_DL
3 KIAH KLGA 18:50 23:25 3417 ERJ_175_DL
3 KLGA KIAH 15:00 18:19 3299 ERJ_175_DL
3 KIAH KLGA 9:46 14:20 3326 ERJ_175_DL
3 KLGA KIAH 6:10 9:16 3371 ERJ_175_DL
2 KDFW KLGA 19:10 23:34 3400 ERJ_175_DL
2 KLGA KDFW 15:05 18:31 3294 ERJ_175_DL
2 KIAH KLGA 9:51 14:25 3326 ERJ_175_DL
2 KLGA KIAH 6:10 9:16 3371 ERJ_175_DL
1 KIAH KLGA 18:35 23:05 3417 ERJ_175_DL
1 KLGA KIAH 14:40 17:58 3299 ERJ_175_DL
1 KIND KLGA 11:59 14:00 3406 ERJ_175_DL
1 KLGA KIND 8:55 11:28 3362 ERJ_175_DL
1 KIND KLGA 6:10 8:15 3335 ERJ_175_DL

 

[tgibson]

Hi,

The MRAI Compiler does not work that way for me. If I set it to use Local time (Timetable use GMT Times box UNchecked), then the local times are converted to UTC according to its AirportDB.txt file found in the Database folder.

Bob, when that happened to me only one aircraft had been found by AIFP, not all of them. Only the one found by AIFP was assigned to flight plans. Are you saying that every aircraft type in the drop down box in Step 4 of my post above (the "search box") listed all of the relevant planes without you having to press the Add button?