Some define statistics as the field that focuses on turning information into knowledge. The first step in that process is to summarize and describe the raw information – the data. In this lab we explore flights, specifically a random sample of domestic flights that departed from the three major New York City airports in 2013. We will generate simple graphical and numerical summaries of data on these flights and explore delay times. Since this is a large data set, along the way you’ll also learn the indispensable skills of data processing and subsetting.
In this lab, we will explore and visualize the data using the tidyverse suite of packages. The data can be found in the companion package for OpenIntro labs, openintro.
Let’s load the packages.
The Bureau of Transportation Statistics (BTS) is a statistical agency that is a part of the Research and Innovative Technology Administration (RITA). As its name implies, BTS collects and makes transportation data available, such as the flights data we will be working with in this lab.
First, we’ll view the nycflights
data frame. Type the
following in your console to load the data:
The data set nycflights
that shows up in your workspace
is a data matrix, with each row representing an
observation and each column representing a variable. R
calls this data format a data frame, which is a term
that will be used throughout the labs. For this data set, each
observation is a single flight.
To view the names of the variables, type the command
## [1] "year" "month" "day" "dep_time" "dep_delay" "arr_time"
## [7] "arr_delay" "carrier" "tailnum" "flight" "origin" "dest"
## [13] "air_time" "distance" "hour" "minute"
This returns the names of the variables in this data frame. The codebook (description of the variables) can be accessed by pulling up the help file:
One of the variables refers to the carrier (i.e. airline) of the flight, which is coded according to the following system.
carrier
: Two letter carrier abbreviation.
9E
: Endeavor Air Inc.AA
: American Airlines Inc.AS
: Alaska Airlines Inc.B6
: JetBlue AirwaysDL
: Delta Air Lines Inc.EV
: ExpressJet Airlines Inc.F9
: Frontier Airlines Inc.FL
: AirTran Airways CorporationHA
: Hawaiian Airlines Inc.MQ
: Envoy AirOO
: SkyWest Airlines Inc.UA
: United Air Lines Inc.US
: US Airways Inc.VX
: Virgin AmericaWN
: Southwest Airlines Co.YV
: Mesa Airlines Inc.Remember that you can use glimpse
to take a quick peek
at your data to understand its contents better.
## Rows: 32,735
## Columns: 16
## $ year <int> 2013, 2013, 2013, 2013, 2013, 2013, 2013, 2013, 2013, 2013, …
## $ month <int> 6, 5, 12, 5, 7, 1, 12, 8, 9, 4, 6, 11, 4, 3, 10, 1, 2, 8, 10…
## $ day <int> 30, 7, 8, 14, 21, 1, 9, 13, 26, 30, 17, 22, 26, 25, 21, 23, …
## $ dep_time <int> 940, 1657, 859, 1841, 1102, 1817, 1259, 1920, 725, 1323, 940…
## $ dep_delay <dbl> 15, -3, -1, -4, -3, -3, 14, 85, -10, 62, 5, 5, -2, 115, -4, …
## $ arr_time <int> 1216, 2104, 1238, 2122, 1230, 2008, 1617, 2032, 1027, 1549, …
## $ arr_delay <dbl> -4, 10, 11, -34, -8, 3, 22, 71, -8, 60, -4, -2, 22, 91, -6, …
## $ carrier <chr> "VX", "DL", "DL", "DL", "9E", "AA", "WN", "B6", "AA", "EV", …
## $ tailnum <chr> "N626VA", "N3760C", "N712TW", "N914DL", "N823AY", "N3AXAA", …
## $ flight <int> 407, 329, 422, 2391, 3652, 353, 1428, 1407, 2279, 4162, 20, …
## $ origin <chr> "JFK", "JFK", "JFK", "JFK", "LGA", "LGA", "EWR", "JFK", "LGA…
## $ dest <chr> "LAX", "SJU", "LAX", "TPA", "ORF", "ORD", "HOU", "IAD", "MIA…
## $ air_time <dbl> 313, 216, 376, 135, 50, 138, 240, 48, 148, 110, 50, 161, 87,…
## $ distance <dbl> 2475, 1598, 2475, 1005, 296, 733, 1411, 228, 1096, 820, 264,…
## $ hour <dbl> 9, 16, 8, 18, 11, 18, 12, 19, 7, 13, 9, 13, 8, 20, 12, 20, 6…
## $ minute <dbl> 40, 57, 59, 41, 2, 17, 59, 20, 25, 23, 40, 20, 9, 54, 17, 24…
The nycflights
data frame is a massive trove of
information. Let’s think about some questions we might want to answer
with these data:
Let’s start by examing the distribution of departure delays of all flights with a histogram.
This function says to plot the dep_delay
variable from
the nycflights
data frame on the x-axis. It also defines a
geom
(short for geometric object), which describes the type
of plot you will produce.
Histograms are generally a very good way to see the shape of a single distribution of numerical data, but that shape can change depending on how the data is split between the different bins. You can easily define the binwidth you want to use:
Insert your answer here
The histograms have different width bars. This changes the way the data points are distributed among them. The wider the bars are, the more data points each bar represents. The narrower bars provide information about how the data is distributed within the wider bars. Whether you want narrow or wide bars will depend on how much you care about the differences between the values that would lie within a single wider bar.
If you want to visualize only on delays of flights headed to Los
Angeles, you need to first filter
the data for flights with
that destination (dest == "LAX"
) and then make a histogram
of the departure delays of only those flights.
lax_flights <- nycflights %>%
filter(dest == "LAX")
ggplot(data = lax_flights, aes(x = dep_delay)) +
geom_histogram()
Let’s decipher these two commands (OK, so it might look like four
lines, but the first two physical lines of code are actually part of the
same command. It’s common to add a break to a new line after
%>%
to help readability).
nycflights
data frame,
filter
for flights headed to LAX, and save the result as a
new data frame called lax_flights
.
==
means “if it’s equal to”.LAX
is in quotation marks since it is a character
string.ggplot
call from earlier
for making a histogram, except that it uses the smaller data frame for
flights headed to LAX instead of all flights.Logical operators: Filtering for certain
observations (e.g. flights from a particular airport) is often of
interest in data frames where we might want to examine observations with
certain characteristics separately from the rest of the data. To do so,
you can use the filter
function and a series of
logical operators. The most commonly used logical
operators for data analysis are as follows:
==
means “equal to”!=
means “not equal to”>
or <
means “greater than” or “less
than”>=
or <=
means “greater than or
equal to” or “less than or equal to”You can also obtain numerical summaries for these flights:
## # A tibble: 1 × 3
## mean_dd median_dd n
## <dbl> <dbl> <int>
## 1 9.78 -1 1583
Note that in the summarise
function you created a list
of three different numerical summaries that you were interested in. The
names of these elements are user defined, like mean_dd
,
median_dd
, n
, and you can customize these
names as you like (just don’t use spaces in your names). Calculating
these summary statistics also requires that you know the function calls.
Note that n()
reports the sample size.
Summary statistics: Some useful function calls for summary statistics for a single numerical variable are as follows:
mean
median
sd
var
IQR
min
max
Note that each of these functions takes a single vector as an argument and returns a single value.
You can also filter based on multiple criteria. Suppose you are interested in flights headed to San Francisco (SFO) in February:
Note that you can separate the conditions using commas if you want
flights that are both headed to SFO and in February. If
you are interested in either flights headed to SFO or
in February, you can use the |
instead of the comma.
sfo_feb_flights
. How
many flights meet these criteria?Insert your answer here
sfo_feb_flights <- nycflights %>%
filter(dest == "SFO", month == 2)
sfo_feb_flights %>%
summarise (n = n())
## # A tibble: 1 × 1
## n
## <int>
## 1 68
## [1] 68
68 flights meet these criteria. I double checked that my answer was correct by using a second method.
Insert your answer here
## # A tibble: 1 × 3
## median_ad iqr_ad n
## <dbl> <dbl> <int>
## 1 -11 23.2 68
## [1] -4.5
## [1] 0.6617647
Most flights to SFO in February arrive early (the median arrival delay is -11, corresponding to an arrival 11 minutes earlier than scheduled). The flights are pretty tightly clustered around this median, with an inter-quartile range of only 23.2 minutes. I selected median and interquartile range to describe this data set because there are a few significant outliers on the right-hand side of the histogram, which would cause the mean to be of questionable representative value. As you can see from the second half of my code block, the mean arrival delay is -4.5, which is greater than about 66% of the data points. Depending on your purposes, the difference between -11 and -4.5 minutes might not be meaningful enough to matter, of course.
Another useful technique is quickly calculating summary statistics
for various groups in your data frame. For example, we can modify the
above command using the group_by
function to get the same
summary stats for each origin airport:
sfo_feb_flights %>%
group_by(origin) %>%
summarise(median_dd = median(dep_delay), iqr_dd = IQR(dep_delay), n_flights = n())
## # A tibble: 2 × 4
## origin median_dd iqr_dd n_flights
## <chr> <dbl> <dbl> <int>
## 1 EWR 0.5 5.75 8
## 2 JFK -2.5 15.2 60
Here, we first grouped the data by origin
and then
calculated the summary statistics.
arr_delay
s of flights in in the
sfo_feb_flights
data frame, grouped by carrier. Which
carrier has the most variable arrival delays?Insert your answer here
sfo_feb_flights %>%
group_by(carrier) %>%
summarise(median_ad = median(arr_delay), iqr_ad = IQR(arr_delay), n = n())
## # A tibble: 5 × 4
## carrier median_ad iqr_ad n
## <chr> <dbl> <dbl> <int>
## 1 AA 5 17.5 10
## 2 B6 -10.5 12.2 6
## 3 DL -15 22 19
## 4 UA -10 22 21
## 5 VX -22.5 21.2 12
UA and DL are tied for the widest interquartile range for arrival delays, with 22-minute interquartile ranges.
Which month would you expect to have the highest average delay departing from an NYC airport?
Let’s think about how you could answer this question:
group_by
months, thensummarise
mean departure delays.arrange
these average delays in
desc
ending order## # A tibble: 12 × 2
## month mean_dd
## <int> <dbl>
## 1 7 20.8
## 2 6 20.4
## 3 12 17.4
## 4 4 14.6
## 5 3 13.5
## 6 5 13.3
## 7 8 12.6
## 8 2 10.7
## 9 1 10.2
## 10 9 6.87
## 11 11 6.10
## 12 10 5.88
Insert your answer here
nycflights %>%
group_by(month) %>%
summarise(median_dd = median(dep_delay)) %>%
arrange(desc(median_dd))
## # A tibble: 12 × 2
## month median_dd
## <int> <dbl>
## 1 12 1
## 2 6 0
## 3 7 0
## 4 3 -1
## 5 5 -1
## 6 8 -1
## 7 1 -2
## 8 2 -2
## 9 4 -2
## 10 11 -2
## 11 9 -3
## 12 10 -3
I’m not sure if this is meant to be a trick question, since the mean and median departure delay are minimized in the same Month (October), so the two options will produce the same result with this data. More generally, the mean departure delays vary a little bit (from about 6 minutes in October to about 21 minutes in July, a range of about 21 minutes) while the median departure delays hardly vary at all (from -3 minutes in October to 1 minute in December, a range of 4 minutes). This suggests that what changes from month to month are the magnitude of the outliers, not the relative frequency of delays. With that in mind, the question is whether your goal is to avoid being delayed at all (minimize the median) or minimize your chances of being seriously delayed (minimize the mean).
Suppose you will be flying out of NYC and want to know which of the three major NYC airports has the best on time departure rate of departing flights. Also supposed that for you, a flight that is delayed for less than 5 minutes is basically “on time.”” You consider any flight delayed for 5 minutes of more to be “delayed”.
In order to determine which airport has the best on time departure rate, you can
Let’s start with classifying each flight as “on time” or “delayed” by
creating a new variable with the mutate
function.
The first argument in the mutate
function is the name of
the new variable we want to create, in this case dep_type
.
Then if dep_delay < 5
, we classify the flight as
"on time"
and "delayed"
if not, i.e. if the
flight is delayed for 5 or more minutes.
Note that we are also overwriting the nycflights
data
frame with the new version of this data frame that includes the new
dep_type
variable.
We can handle all of the remaining steps in one code chunk:
nycflights %>%
group_by(origin) %>%
summarise(ot_dep_rate = sum(dep_type == "on time") / n()) %>%
arrange(desc(ot_dep_rate))
## # A tibble: 3 × 2
## origin ot_dep_rate
## <chr> <dbl>
## 1 LGA 0.728
## 2 JFK 0.694
## 3 EWR 0.637
You can also visualize the distribution of on on time departure rate across the three airports using a segmented bar plot.
Insert your answer here
## # A tibble: 3 × 2
## origin ot_dep_rate
## <chr> <dbl>
## 1 EWR 0.637
## 2 JFK 0.694
## 3 LGA 0.728
LaGuardia Airport has the highest percentage of departures on time, so I would choose that one.
avg_speed
traveled by the plane
for each flight (in mph). Hint: Average speed can be
calculated as distance divided by number of hours of travel, and note
that air_time
is given in minutes.Insert your answer here
nycflights <- nycflights %>%
mutate(avg_speed = distance / air_time * 60)
#travel_time <- nycflights$air_time
#travel_distance <- nycflights$distance
#travel_speed <- travel_distance / travel_time * 60
#nycflights$avg_speed <- travel_speed
I was able to use mutate to accomplish this but wanted to try another method as well, you can see it in the code block above as comments.
avg_speed
vs. distance
. Describe the relationship between average
speed and distance. Hint: Use
geom_point()
.Insert your answer here
ggplot(data = nycflights, aes(x = distance, y = avg_speed)) + ggtitle("Average Flight Speed vs. Distance") + xlab("Flight Distance (Miles)") + ylab("Average Speed (mph)") + geom_point()
Broadly speaking, flight speed increases as flight distance increases. However, this effect is more pronounced for shorter flights than for longer ones, the longest flights are barely faster than the medium-distance flights, and although the slowest flights are also the shortest, the fastest flights are not the longest.
color
ed by
carrier
. Once you replicate the plot, determine (roughly)
what the cutoff point is for departure delays where you can still expect
to get to your destination on time.Insert your answer here
question_9_frame <- nycflights %>%
filter(carrier == "AA" | carrier == "DL" | carrier == "UA")
ggplot(data = question_9_frame, aes(x = dep_delay, y = arr_delay, color = carrier)) + scale_color_manual(values = c("#FF4493", "#1FF5C8", "#919CFE")) + geom_point()
I replicated the plot but made the colors a little more vivid to practice the formatting for manually setting the colors. From the plot, it appears that after about a one-hour-15-minute departure delay flights always arrive late, so I would say that to have any hope of arriving on time you need to leave within 75 minutes of your scheduled departure time.