So why did I go to the trouble of writing my own flight tracking application rather than just use an existing one? My primary reason was to gain experience in a new programming language, but the reason I decided to write a flight tracker rather than any other project was that I disagreed with the way the available flight trackers count airports.
Wichita opened a completely new terminal last June, meaning that my trip this past week was the first time I’ve been in the new terminal.
Baggage claim area of the new terminal of Wichita Eisenhower National Airport
Wichita, though having a rich aviation history, is not a huge air travel market. The new terminal completely replaces the old one.
Old terminal of Wichita Mid-Continent Airport
I did really like the old terminal; seeing that much brick in a functioning airport (both inside and outside) is rare nowadays.
Interior of the old terminal
However, the old terminal was absolutely showing its age. In particular, this was an airport that was designed before modern security, meaning they had to wedge it in wherever it would fit, which in practice was the base of the T junction. This led to some extremely narrow hallways, crowded checkpoints, and a best-they-could-do TSA PreCheck that shared the X-ray with the standard checkpoint.
What’s left of the main “T” junction of the old terminal, looking from the new one. The entire security checkpoint fit in what’s still standing.
So while I’m sorry to see the old terminal go, the airport needed a new terminal, and I’m just glad that I got to see the old building one last time.
What remains of the old terminal is left and center, and the new terminal is behind and to the right.
