Estimated passenger itinerary data for calendar year 2007 can be downloaded via http from:

• http://web.mit.edu/nsfnats/www/PassengerItineraries_2007_I.tar.gz for the allocation based on the Fixed Effects Model
• http://web.mit.edu/nsfnats/www/PassengerItinararies_2007_II.tar.gz for the allocation based on the Random Effects Model

Please note that the file is approximately 2.5G, so the download could be quite slow. In the uncompressed file, there will be a CSV for each calendar month, with the filenames:

• PassengerItineraryData_2007_01.csv
• PassengerItineraryData_2007_02.csv
• PassengerItineraryData_2007_03.csv
• PassengerItineraryData_2007_04.csv
• PassengerItineraryData_2007_05.csv
• PassengerItineraryData_2007_06.csv
• PassengerItineraryData_2007_07.csv
• PassengerItineraryData_2007_08.csv
• PassengerItineraryData_2007_09.csv
• PassengerItineraryData_2007_11.csv
• PassengerItineraryData_2007_12.csv

In total, the uncompressed files take up approximately 27G of disk space. Each monthly data file has a header row describing the data columns. Each data row provides identifying information for the itinerary, including the first flight, and in the case of one-stop itineraries, the second flight, along with the estimated seating capacities for each flight. The last piece of information is the number of passengers estimated to have traveled on the itinerary. Note that the estimated number of passengers may be non-integral, because we allow non-integral estimates of the seating capacities. In order to consider integral seating capacities and passenger counts, these values should be rounded appropriately. For reference, we have listed and briefly described each of the data columns below. Using these fields, the itineraries can be easily joined with the ASQP flight data provided by BTS.

• First_Flight_ID - a unique integer identifier for referencing the first flight in the itinerary.,
• First_Operating_Carrier - the two character code for the carrier operating the first flight in the itinerary,
• First_Origin - the origin of the first flight in the itinerary,
• First_Destination - the destination of the first flight in the itinerary,
• First_Month - the month of departure for the first flight,
• First_Day - the day of the month of departure for the first flight,
• First_Departure - the local time of departure for the first flight in HH24:MI:SS,
• First_Capacity - the estimated number of seats on the first flight (may be non-integral),
• Second_Flight_ID - a unique integer identifier for referencing the second flight in the itinerary,
• Second_Operating_Carrier - the two character code for the carrier operating the second flight in the itinerary,
• Second_Origin - the origin of the second flight in the itinerary,
• Second_Destination - the destination of the second flight in the itinerary,
• Second_Month - the month of departure for the second flight,
• Second_Day - the day of the month of departure for the second flight,
• Second_Departure - the local time of departure for the second flight in HH24:MI:SS,
• Second_Capacity - the estimated number of seats on the second flight (may be non-integral), and
• Number_Passenger - the estimated number of passengers traveling on this itinerary.

If there are any problems with the data, please contact Douglas Fearing (dfearing "at" mit.edu) or Vikrant Vaze (vikrantv "at" mit.edu). The First_Flight_ID and Second_Flight_ID columns identify the flights within the NSFNATS internal database, so please include these values when describing the problem.