Thanks a lot dragoon17c for producing fresh data files! I know from my own experience how much work went into this

Here are a few notes on data files, since I was the original author of the tool.

The reason for the "assertion failed" error is a missing tab in the file airports.dat in the line for the LLO airport (between the longitude and the airport name). Columns should be separated by tabs, not by spaces. If you are not a programmer, you can easily see this by loading the file into Excel.

The "# Date:" comment in routes.dat is displayed by the tool as the "Data set date", so it should be updated to reflect the date when you collected/updated the data.

There is a hidden feature in the tool to help locate misplaced airports. In the filter dropdown box, select "Custom". Now, Instead of airline codes, enter the following and click OK:

*>2000

Then, select "all airlines" in the filter again. The tool will now select airports which do not have routes shorter than 2000 miles. This often happens with misplaced airports appearing in the wrong part of the world. For example, the SHO airport has a single route (to JNB) which is 7851 miles long. This can't be right. Of course, there are also correctly airports which only have long routes, e. g. IPC. So you have to review each case per hand. You can use a different number instead of "2000". E.g. "*>1000" followed by "All airlines" will select all airports with the shortest route exceeding 1000 miles.

Another useful trick for finding data errors is to open the "Options" dialog box, specify "Only show routes between 6000-9999 miles long", then uncheck all long-range aircraft and click OK. This will display suspiciously long routes flown by short-range aircraft. For example, the newest data file shows HGH-HOG (8749 miles) flown by an A320. This can't be right, even though both HGH and HOG are shown at correct location.

Keep up the good work