Case Study 2 — Second-and-Goal at the 1, Twenty-Six Seconds: The Most Argued-About Goal-Line Call in Super Bowl History
This case uses a real, widely documented game. It sticks to the publicly known facts of the situation and the call, and it treats the arguments made afterward as arguments — not as settled truth. No quotes are attributed to anyone involved.
Setup
The game. Super Bowl XLIX, played on February 1, 2015. The New England Patriots led the Seattle Seahawks 28–24 in the final minute of the fourth quarter.
The drive. Seattle drove into New England territory, helped by a juggling catch by receiver Jermaine Kearse that put the ball near the 5-yard line. On first-and-goal from the 5, running back Marshawn Lynch, one of the league's most punishing power runners, carried to about the 1.
The situation. Second-and-goal at the New England 1, Seattle trailing by four, so a field goal was useless: only a touchdown would win. The clock was running. Seattle had one timeout left. Neither team stopped the clock after Lynch's run, and Seattle snapped the ball on second down with about 26 seconds remaining.
The call. Seattle threw. Quarterback Russell Wilson threw a quick slant to receiver Ricardo Lockette, who was working inside from a pair of receivers aligned close together on one side of the formation. New England cornerback Malcolm Butler, an undrafted rookie, drove on the route, beat Lockette to the ball at the goal line, and intercepted it. New England ran out the clock and won.
Within minutes, the call was being described as one of the worst in football history. Within days, a counter-argument was being made just as loudly. Both sides are worth understanding, because the decision sits exactly on the fault lines this chapter teaches: clock arithmetic, run-versus-pass at the goal line, the difference between the decision to pass and the choice of which pass, and judging a decision by its outcome.
What happens — the decision tree
Put yourself on Seattle's headset at 0:26 (approximately), second-and-goal at the 1, one timeout. You need one touchdown. You have up to three downs. The question isn't just "what's the best play?" It's "how many plays can I guarantee myself?"
Work through the clock.
| Second-down call | If it fails | Third down | If that fails | Fourth down? |
|---|---|---|---|---|
| Run | Clock keeps running; use your only timeout | Run or pass | If it's a run that fails, the clock runs with no timeout left — you may not get a fourth snap off | Uncertain |
| Pass | Incomplete: clock stops, timeout saved | Run; if stopped, use the timeout | Fourth-down run | Yes — three snaps guaranteed |
| Pass, then pass | Incomplete: clock stops | Pass; incomplete stops the clock | Run or pass | Yes, but with fewer runs |
The argument for passing on second down, made by many defenders of the call afterward, starts here: an incompletion stops the clock for free, preserving the timeout and, with it, the chance to run on both third and fourth down. If Seattle ran on second down and was stopped, it would have to spend its timeout immediately, and a failed third-down run would leave the clock running with no way to stop it.
Notice what that argument assumes: that the second-down pass will be either a touchdown or an incompletion. An interception is the one outcome the clock argument doesn't price in, and on a quick throw into traffic at the goal line, it's not a zero-probability outcome.
The defensive picture
New England had matched Seattle's personnel and was in man coverage near the goal line, with defenders tight to the line. That's exactly the picture this chapter describes: no deep zones, every defender within a few yards of the ball, man responsibilities.
Here's a simplified, illustrative version of the concept family — a stacked pair of receivers against goal-line man coverage. It is not a frame-accurate drawing of the play; it shows the idea Seattle's call relied on and the technique that beat it.
ILLUSTRATIVE: a stacked pair vs. goal-line man coverage
(the concept family, not a frame-accurate drawing)
===================== GOAL LINE (1 yd) =========================
C2 (off, reads
C1 (press) the stack)
M W
E T T E
O O O O O #1 (front)
Q R #2 (back)
Intended: #1 releases and occupies C1; #2 slants inside of him,
and C2, trailing from depth, is caught behind the traffic.
What beats it: C1 jams #1 at the line (no traffic is created);
C2 reads the inside break and drives on the slant
window -- arriving at the catch point first.
📊 Diagram (described): Two receivers line up stacked on one side, one in front of the other, against two defenders in man coverage: one pressing the front receiver and one aligned a few yards off, reading the stack. The design hopes the front receiver's release will occupy the press defender and create traffic, so the back receiver can slant inside with his defender trailing behind it. The defense beats it when the press defender jams the front receiver at the line, so no traffic is created, and the off defender reads the inside break and drives on the slant window, reaching the catch point first.
On the actual play, the defender across from the front receiver got his hands on him at the line, and Butler, reading the slant, drove on it and won the race to the spot. Whether you call the concept a "rub" or route spacing, it depended on traffic that never developed.
Analysis
Separate the three decisions
A goal-line call is really three decisions stacked on top of each other, and the arguments about this one mostly happened because people collapsed them into one.
Decision 1 — Run or pass on second down? The clock arithmetic gives a real reason to pass on one of the three downs. Many analysts who studied the situation afterward argued that passing on second down, specifically, was defensible for exactly that reason. Others argued that with one of the league's best short-yardage runners and a yard to go, the run's conversion probability was high enough that the clock risk was worth taking. Reasonable people with the same facts disagree. That's what a close decision looks like.
Decision 2 — Which pass? This is where much of the criticism concentrated, and it's where this chapter's principles bite hardest. A goal-line pass has to do two things on second down in that situation: give a real chance at a touchdown, and fail safely — incomplete, not intercepted. Different passes trade those off differently. A fade or back-shoulder to the corner of the end zone, or a quarterback sprint-out with a throw-it-away option, can fail safely: the ball goes where only your receiver (or nobody) can catch it. A quick slant into the middle of a crowded goal line is a high-percentage completion when it's open, but when a defender jumps it, the ball is right in front of him. The clock argument favored "a pass." It didn't favor every pass equally.
Decision 3 — Execution. The defense won the play. The press technique took away the traffic, and the off defender read the route and closed. A great defensive play is not proof of a terrible offensive call, any more than a touchdown would have proved a brilliant one.
Outcome versus process
If the slant had been caught for a touchdown, the call would have been celebrated as bold and clever. The decision would have been identical; only the result changes. That's the lesson Lyle draws from our own Game 1 fourth-and-goal at the 3: one outcome doesn't grade a decision. The right way to grade this call is to ask, before the snap, what the probabilities of touchdown, incompletion, and interception were for this pass versus the alternatives — and how many plays each choice guaranteed. Those are uncomfortable numbers to estimate, and nobody outside the building can know them precisely. But that's the conversation.
What it teaches about building a goal-line package
Seattle's situation is the purest version of this chapter's "four runs and two passes" problem. With twenty-six seconds and one timeout, the offense needed:
- a run it trusted from the 1,
- a pass that fails safely to stop the clock if needed, and
- a sequence that fit inside the clock.
Every team should have its version of that answered on Friday, not on Sunday. What's your second-and-goal-at-the-1 call with under thirty seconds and one timeout? Which pass is your "safe incompletion" pass? Our Green panel has a line for it.
🏫 Any level: The clock rules differ by code (for example, how the clock restarts after certain stoppages), and high school and college offenses often have more timeouts left in these moments because of how they manage the half. Run the same table with your code's rules. The structure of the decision — how many snaps can I guarantee, and which of my plays fail safely — is the same at every level.
Discussion Questions
- Using the clock table, explain in your own words why a second-down pass preserves more snaps than a second-down run in this situation. What assumption does that argument make about the pass?
- Rank three possible second-down passes — a quick slant inside, a fade to the back corner, and a quarterback sprint-out with a run option and a throw-away — by (a) touchdown chance and (b) safety if it fails. Which would you call, and why?
- Suppose the slant had been caught for the winning touchdown. Would the call have been a better decision? Explain using the idea that a call is a bet on a distribution.
- How does goal-line man coverage change the risk of a rub or stack concept compared with the same concept on third-and-6 at midfield?
- What would you want on your Friday goal-line script so that this exact situation is a rehearsed decision rather than a live one?
Your Turn
Build a "last thirty seconds, goal-to-go" card for your offense. Assume second-and-goal at the 1 with 0:26 and one timeout, trailing by four. Write the three calls you'd use on second, third, and fourth down, and for each, write: (1) what happens to the clock if it fails, (2) its "fail-safe" outcome, and (3) the defensive look that would make you switch it. Then do the same card for two timeouts and for none.