Due to the system delays caused by Winter Storm Pax, my flights home on 14 February went through rather a lot of transition:
When I first started flying frequently, I didn’t have any particular goals in mind. I vaguely wanted to visit places I hadn’t been before, but I had nothing that I could hold myself to. Once I got the flight log up and running, though, I had a much larger set of information about how I’d flown in my travels, and that allowed me to make my goals much more concrete.
Hence the title of the blog, and the meter in the sidebar. At the time of this writing, I’ve visited 42 airports, and I’d like to reach 100.
This will be a challenging goal to meet; I’ve already picked a lot of the low-hanging fruit by taking layovers in different hubs. My travel is largely within the United States, and looking at the FAA’s 2012 enplanement stats, I’ve been to 23 of the 29 large hubs in the US – I’m only missing IAH, MIA, FLL, MDW, SAN, and TPA. My home airport of DAY doesn’t serve any of these airports, so I’d have to fly out of CMH or CVG, making them a little harder to pick up as layovers. Also, particularly for MIA, FLL, and TPA, there aren’t many reasons for me to have a layover in Florida on domestic travel from Ohio, so I’d probably only pick them up as a layover on a multi-city itinerary.
So a lot of my remaining airports will have to come as destinations. This is a long term goal.
The airlines page shows a list of airlines I’ve flown and the number of flights on each, sorted by number of flights.
15 SEPTEMBER 2013 UPDATE: I have since found an error in my data, and the two flights that I had listed as Continental Airlines were actually flown on American Airlines. This screenshot is now slightly incorrect, but the flight log has incorporated the correction.
When codeshares are involved, I use the airline and flight number of the operator of the flight.
Regional subsidiary airlines are listed as the parent airline. For example, all American Eagle flights are listed as American Airlines, and all flights branded as United Express are listed as United flights, regardless of which subsidiary airline actually operates it.
Airlines which have gone through a merger since my last flight are still listed as the airline they were on the date I took the flight. Thus, my flights on Continental and Northwest are not now considered United and Delta flights.
Clicking on any airline brings up a Great Circle Mapper map and list of all flights I’ve taken on that airline:
The aircraft families page shows a listing of all aircraft families I’ve flown.
A large portion of my flights are on regional jets; a hazard, I suppose, of living near Dayton, Ohio.
Note that I do not know the aircraft for every flight I’ve taken (particularly older flights), so those flights are not included in this listing.
As expected, clicking on an aircraft family brings up a map and list of the flights using it:
While flights are the most visible aspect of the Flight Log, airports are equally important.
On my airports listing, I start out with some maps showing all airports I’ve been to, but the heart of the page is the list of airports.
This lists each airport I’ve been to, and the number of times I’ve visited it. The number of visits is automatically determined from the flight data in the database; every flight has an airport visit at either end of it.
My code also has to look at trip sections to determine if a flight arriving at an airport and the next flight departing from the same airport is a layover or not. If both flights are in separate sections (for example, I land in Dallas/Fort Worth, do some business there, and then depart from DFW later) it is not a layover and counts as two visits. However, if they’re in the same section, it’s a layover, and only counts as a single visit.
This visit calculation is how I determined when my 100th airside visit to the Dayton airport, allowing me to celebrate accordingly.
Clicking on any airport brings up its details, starting with a list of all flights involving the airport:
As always, the flight log’s code generates a list of flights and passes it on to the Great Circle Mapper to draw the maps.
The page also figures out which trip sections and trips involve the airport in question, and generates maps for those, too:
Clicking on any airline or aircraft family will bring up details about each, which will be discussed in the next entry.
The most prominent item on the flights listing is a pair of maps showing every flight I’ve taken since age 18.
I have a database of all the flights I’ve taken, and I wrote some code to take all of this flight route data and transform it into a format that the the Great Circle Mapper understands, and the Great Circle Mapper generates me a map like the one above. This means that when I add a new flight to the database, my maps are updated automatically.
(As an aside, when I add a flight to the database, it’s hidden at first – only I can see it. This allows me to enter my flights without having the general public aware that I’m traveling until I return home and unhide those flights.)
Of course, while maps are useful, sometimes more details are needed, and for that I’ve included a listing of all of my flights.
Clicking on any flight in the list brings up a flight details page:
This page shows a map of the flight and a number of details. Many of these details are links – so clicking on First Class, for example, brings you to a page listing all of my first class flights. (The various details will be covered in future posts.) The page also shows some maps of trips (and parts of trips) which have a flight involving these two cities, so this is as good of a time as any to describe how trips work.
At its core, a trip is a complete set of flights, from an origin airport, with a stop at one or more destinations. Often, but not always, the final destination is the same as the origin, which in everyday speech is a “round trip.”
For the purpose of my flight log, a trip can be divided into one or more sections. A section is simply all the flights between the origin and the first destination, or between any two consecutive destinations. So, let’s say that I have a round trip from my home in the Dayton, Ohio area to Los Angeles, with a layover at Dallas/Fort Worth both ways. This trip would then have two sections – the first containing all of my flights to Los Angeles (the DAY to DFW flight and the DFW to LAX flight) and the second containing all of my flights home (the LAX to DFW flight and the DFW to DAY flight).
If I had a multi-city trip from Dayton to Los Angeles to Seattle to Dayton, there would be three sections – All flights between DAY and LAX, all flights between LAX and SEA, and all flights between SEA and DAY.
All that said, clicking on the Trips link at the top of any Flight Log page will show a list of trips:
Clicking on any of those will show a trip details page:
This particular trip was a multi-city trip, starting and ending in Dayton with stops in Oklahoma City and Rapid City. As you can see, the map highlights destinations with a ring around a dot, while airports that are simply layovers are just shown as a black dot.
Below the map, all the flights for this trip are shown, grouped by trip section. Clicking any of the airlines and flight numbers will bring up the flight details page as described above. If you’d like to just see one particular section of the trip, clicking the section number to the left of the flights will do so:
Between the flights and trips pages, my travels are well-described. However, there are still more in-depth flight details included in the Flight Log, which will be covered in my next entry.
I travel reasonably often, and I consider myself a bit of a transportation nerd. It’s only logical that I would keep track of where I’ve flown.
For a while, I used a giant text file, and later an Excel spreadsheet, to track all of my flights; I created maps manually using the Great Circle Mapper. But by the time my flights began numbering in the hundreds, I needed a more automated solution, so I created Paul Bogard’s Flight Log.Over the next several weeks, I’ll go into detail about the Flight Log’s features.