new flight plan not seen in fsx...ai replacemnt AA

Your PHNL/KFLL flight plan is out-of-range for the Traffic X aircraft. Since it is out of range, the aircraft will never take off from its initial departure airport.

Here's a way both to eliminate all the old Merican liveries and to put all of your new liveries into already-existing flight plans. It requires downloading and installing TexPad. TextPad is shareware, but it has no time limitations, and the trial version is fully functional. (It's a very good program, and I purchased it). You also need to create and save one flight plan within Traffic Control Centre for each new aircraft that you have added. Doing so will put each new correct aircraft's description into the AAL.tcc file. After doing the above, open and sort Traffic X's AAL.tcc file in TextPad. (The AAL.tcc file contains all current American Airlines flight plans). (This technique can be used with the .tcc flight plan file of any airline/carrier).

R E A D   T H E S E   T I P S   F I R S T

A. Before beginning, and as a precaution, create a backup copy of your existing AAL.tcc file.

B. Prior to beginning the below numbered steps, remember to manually create and save
   one flight plan within the Traffic Control Centre for each new aircraft that you have
   added. In Step 6, you will be highlighting and copying a portion of the new aircraft's
   description as it exists in the .tcc file. Without at least one manually created flight plan,
   there would be no description of the new aircraft in the .tcc file.

C. For the portion of the registration number that is enclosed in braces (as shown in the
   EXAMPLE under Step 8), I recommend using 3-digit numbers. Particularly with American  
   Airlines, there could easily be over 100 flight plans for a single model such as the Boeing
   737. If that is the case, enter a registration number such as N100AN when you manually enter
   the registration number for the first American Boeing 737 flight plan in the Traffic Control
   Centre. A low 3-digit number such as 100 provides plenty of headroom for the numbers to
   increment without reaching 1000. The number 100 series could be used again for American
   models other than the Boeing 737 providing at least one character outside the braces differs
   from other American models that use a 100 series. For example, after using N100AN for a 737,
   you could use N100AA for a 767 when manually entering your first 767 flight plan. (For most
   airlines, I prefer not to reuse a series, but you may find you already have so many flight
   plans for AAL that reusing a number series is inevitable if you want to limit the
   incrementing numbers within braces to 3 digits).

R E P L A C I N G   A I R C R A F T   I N   F L I G H T   P L A N S

1. After sorting the .tcc file with TextPad, highlight the incorrect
   aircraft's description (highlighting from the left edge of the line
   over to the right and through the aircraft's registration number).
   Right-click, and select "Copy."

2. Click on TextPad's "Search" button in the top menu, and on the "Search"
   dropdown menu, select "Replace." (If the "Find what" field in the
   "Replace" window is not empty, click in the field, and press your
   keyboard's "Delete" key to clear the field).

3. In the small "Replace" window, be sure that "Text," "Active document,"
   and "Regular expression" are the only items checked. Right-click in the
   "Find what" field, and select "Paste."

4. Change the aircraft's registration number in the "Find what" field of
   the "Replace" window to periods. (The periods function as wildcard
   characters). The number of spaces preceding the first period should be
   kept the same as the number of spaces (if any) that preceded the
   registration number, itself, when the registration number was present.

5. If the "Replace with" field is not blank, click in the field, and press
   your keyboard's "Delete" key to clear the field of any contents.

6. Highlight and copy the correct aircraft's description over through the
   aircraft's registration number.

7. Paste the copied description of the correct aircraft into the small
   "Replace" window's "Replace with" field.

8. In the "Replace with" field, change the registration number of the
   correct aircraft from a constant to an automated sequence. How is that
   done? Here is an example of how to enable Textpad to automatically
   assign a sequence of unique registration numbers to the new aircraft
   for each flight in which the new aircraft is replacing the incorrect
   aircraft:

   EXAMPLE

   If the correct aircraft (the aircraft that will replace each of the
   aircraft that had been used for a group of flights) had a registration
   number of JA308J, change it to something like JA\i{309}J. (In this
   example, I am changing the registration number in the "Replace with"
   field from 308 to 309 since 309 is the next number in the sequence
   of registration numbers that we are creating). The \i must be present
   and must be placed immediately before the braces. The \i tells
   TextPad to automatically increment the number within the braces with
   each iteration. The number within the braces tells TextPad which
   number to use for the registration number of the first newly-assigned
   aircraft. Each aircraft that replaces an old aircraft will be given a
   registration number that follows in the sequence that begins with - in
   this particular example - 309. Only the part of the registration number
   that is within the braces will change. The choice of which part of the
   original registration number to enclose in braces is up to you. The
   starting sequence number is also your choice. The number of digits
   in the number is up to you, too. However, the entire registration number
   (excluding the braces and the \i but including the part of the
   number outside the braces) should not exceed a total of seven
   alphanumeric characters. Be aware that, as numbers increment,
   the number of digits could increase (depending upon the number of
   aircraft being given new registration numbers) and cause the
   registration number to exceed the maximum number of alphanumeric
   characters allowed for registration numbers.

9. The magic moment has arrived. Click the "Replace All" button.

10. You may find a few rows that contain columns that don't align
    perfectly with columns above and below. If so, click on TextPad's
    "View" button, and, on the drop-down menu,  select "Visible Spaces."
    Check the rows that are correctly aligned to find out if they are
    using spaces or tabs for alignment. Make any desired changes to the
    misaligned rows.

11. Save the modified .tcc file, and run the compiler from within the
    Traffic X Traffic Control Centre.

Note that you will be replacing all of a particular model's (a "model" being a Boeing 737, for example) Merican liveries with your new aircraft livery for that model in a single "replace" action. That's the power of it.

Also note that the above procedure to replace all old aircraft in all flight plans for a particular model with a newly-installed aircraft could be done by using Excel or by using a quality text editor other than TextPad if the other text editor provides a function for incrementing. Only the specifics of doing so would be different. The basic idea would remain the same.

Dan

Thanks so much for your help,guys..Soranden..I will try your procedure..but I noticed in the flight plans of the Traffic X center..if I double clicked on the aircraft name, it would give me a drop down a/c list and  let me change the a/c..so I changed a couple of fligjts with the WOAI planes. Havent had a chance to see if it worked tho. Dont I need a complete aircraft.fg file for the WOAI to work? When I installed WOAI planes was missing the "[fltsim.X]" section in its aircraft.cfg file but the flaght planner did see all my WOAI installed planes. As far as out of range goes...I did get an out of range error and the flight plan of one of the American Airlines flight did change to red when I tried to replace it with the same plane but the WOAI version.so I will change the range on that plane. Thanks for the tip! Lastly..I had made a flight plan of an FA-18 taking off from KFLL and doing circuits up to a specified time..the jet never showed up at kfll  to do the circuits. When I do a compile..do I save the compile as the original Traffic X bgl or can I make up my own? How would FSX know which one to use..or does it use all bgl files?  Thanks again for your help....Yoram 

yoram512 wrote: Dan,       Where do I find the AALtcc  file?  Thank you

I am seeing the AAL.tcc file for American Airlines and the .tcc files for other airline's flight plans at:

...Microsoft Flight Simulator X\Just Flight\TrafficX\Presets\Data\Schedules\Flight Plans

If you use the method I recommend, you won't need to change aircraft one-at-a-time for each flight plan. It takes longer to learn my method than it does to use it. After you become familiar with the method, you will be able to replace all aircraft of a particular aircraft model in all of that aircraft model's flight plans for a specific airline in around 3 minutes...even if there are a hundred flight plans involved. That sure beats making the changes one-at-a-time by opening each flight plan in the TCC (Traffic Control Centre). (I usually do--rather than creating a new flight plan for a newly-added aircraft livery--make one manual change to an existing flight plan using the TCC, since after saving a flight plan with the new aircraft livery the .tcc file will have the description of the new aircraft that can be copied for use by the "replace" procedure). Only one manual change is needed for each aircraft livery using the TCC. The alternative to changing one existing flight plan for each livery, of course, is to create one new flight plan for each new livery. Either way, the description of the new aircraft livery gets saved to the airline's .tcc file.

Since the method is new to you, back up an airline's existing .tcc file before making any changes.

Im so overwhelmed by all the diff AA planes that Traffic X uses and all the flights. I thought I had  all The "Merican" planes converted, and the ones I didnt I got  from WOAI..but it seems there are yet more that need to be repainted. Anyone have a "completed" AA fleet with all the plans using American and not Merican? Id be willing to pay if you sent them to me.  Thanks...Yoram

Thanks for  your reply,Dan. It seems kind of ridiculous that all the other flight sim companies dont have a problem using the "American" name..only JustFlight. Ill prob just repaint some more Merican planes to make it complete. ne last question..why cant I replace just the ac  name in note  pad with replace all..why do I have to change the reg. nbr too? Thanks..youve nbeen very helpful.

Dan, I followed your instructions to replace the "Merican" liveries, but when I went to compile, nothing happened. I made the edits, went into the TCC, selected "Traffic Movements", "Compile Traffic X Flight Plans", selected the existing TrafficX.bgl file and clicked yes to replace it. It simply went back to the Traffic Movements" screen. Did I miss something, or could I have somehow screwed up the AAL.tcc so that it won't compile anything? By the way, just to test that theory I replaced the modified AAL.tcc file with a back-up of the original and tried again. Still nothing.

Thanks,
Michael

Freddy, I am running on Vista and normally run as Administrator (requires a confirmation for every #%@^! operation), but I tried it your way and got the same result. I installed Traffic X (sans FSX) on my XP laptop thinking it might be some weird Vista thing, but got the same result. I also looked on Just Flight's website to see if maybe there's an update, but found nothing there. Any other suggestions are welcome.

No, I literally see no activity on the orange screen after I confirm replacing the Trafficx.bgl file. I was looking for some kind of messages or progress bar or something. I'll check with Support. Thanks, anyway.

Just for the heck of it, let me propose an alternative way to replace the "merican" aircraft.  You have already installed all of the WOAI American aircraft.   WOAI provides flightplans that utilize those aircraft (and are more realistic than the TrafficX ones) so why not use those.  The problem with the WOAI flightplans are that they are compiled in FS9 format, not FSX.   You can recompile the WOAI flightplans using AI Flight Planner into FSX format.  Then the only thing you would need to do is remove all of the "merican" flightplans from TrafficX.  It this approach interests you, take a look at the recent thread entitled "TrafficX and WOAI" where I have described the process of recompiling the WOAI flightplans.  BTW, this was the very first thing I did after installing TrafficX and seeing those Merican aircraft.

I am glad it worked for you.  It is not an approach that would work for everyone, but if you are willing to take the extra steps you end up with a much more realistic environment.  I continue to add WOAI packages to my AI environment and as long as I remember to erase the FS9 format traffic file (I forgot recently) things work great.