Sorry to get back so late on this.
I did a tutorial on it here;
http://www.aerodynamika.com/cgi-bin/yabb/YaBB.cgi?num=1197320359
Basic notes on an AI flight.
Decompiling one will leave you with 3 TXT files; airplanes list, airports list, and flightplans.
Flightplans are extremely easy when you take the time to see how they are written. Once you can read it from front to rear, its so easy then, that you can basically write them from scratch, but its faster to just copy/paste one from another, and then make the changes to make your own.
Flights are based on GMT time, so go into your FS and check local times.
A Flightplan starts off at the 'first destination'. The last flight is 'where you started from'. This means that flight plans are always looped (no one way tickets, always return flights eventually). So, your first flight is the 'first destination' which then makes total sense, and your last one brings you back home.
You can have, I think, up to 14 hops. But you only need 2 in your case, as you want these to be static. So have a base airport as your second FP (flightplan) and your destination airport as your first FP.
Use the 'Find airports program' in Traffic Tools to generate a list of all airports in your FS installation. Then search in the TXT file with 'Find' (control / F) and put in the airport code, and it will find it, then copy/paste that string (GPS coordinates) into a new airport list TXT file. (If only 2, then only 2 strings of GPS coordinates).
Airplanes are based on an exact 'registry', top line in a aircraft config file registry paragraph or block.
Example;
[fltsim.0]
title=Epic LT Prototype <<<<< USE THIS
sim=Epic_LT
model=
panel=
sound=
texture=
kb_checklists=EPIC CHECKLIST.htm
kb_reference=
atc_id_color=0x00ffffff
atc_id=N77691
ui_manufacturer=Epic
ui_type="Dynasty"
ui_variation="N77691"
atc_heavy=0
atc_id_font=Verdana,-11,1,600,0
visual_damage=0
Name of the plane is then 'Epic LT Prototype'
Here is an example of some planes I put in a fun little AI batch I made for a couple of airports I did..
AC#1870,275,"Epic LT Prototype 3"
AC#1871,130,"Bücker-131-B Jungmann A-43"
AC#1872,140,"ALPHA Rutan 61 Long-EZ O-320 00"
AC#1873,135,"Piper PA22 Tripacer Red/Cream"
AC#1874,100,"Piper Cub"
AC#1875,135,"Fairchild 24R-2 White"
AC#1876,120,"ERCO415 Ercoupe 1Pilot"
AC#1877,170,"Kodiak Passenger Yellow"
AC# is bogus.. I make them up.
Second entry figures are airpeeds I want them to max out at, such as 275 knots.
Third entry is of course, the Registry 'Title'.
Basic breakdown of a flightplan string;
Full string;
AC#820,F-DVOR,1%,2Hr,VFR,07:30:21,07:54:04,025,R,0000,EDTN,08:46:16,09:09:59,025,R,0000,EDTQ
Breakdown list;
AC#820, <<< From Aircraft list; assignment of the plane
F-DVOR, <<< N-Number assignment for ATC
1%, <<< Lowest setting for AI percentage in FS to appear
2Hr, <<< Cycles; every so many hours, 24, 4, 6, 8, week, etc.
VFR, <<< VFR or IFR
07:30:21,07:54:04,025,R,0000,EDTN, <<<<1st Destination Flight
08:46:16,09:09:59,025,R,0000,EDTQ <<<<2nd Destination Flight
On a FP string, you have
08:46:16, <<< GMT Start of Flight; 8:46AM GMT time
09:09:59, <<< GMT End of flight 'limit; 9:09AM GMT time
025, <<< Alt, this is 2,500 feet alt.
R, <<< I forgot.. arrghh
0000, <<< I forgot.. arrghh
EDTQ <<< Destination airport (from airport list TXT file)
So easy....
Once you see how they are written, you can almost write them by hand.
Copy/paste the airports and aircraft lists together. Compile all three in TTools, boot up FS, and check them out to see if they appear. Troubleshoot their times if necessary to ensure they are functioning properly.
Bill