HudsonMath
Why HudsonMath Exists

208 seconds. Two hundred and eight.

From the bird strike to splashdown, Captain Sully Sullenberger had less than three and a half minutes to run the math that saved 155 lives. He did not pull out a calculator. He did not consult a chart. He thought.

Subject  US Airways 1549 Date  January 15, 2009 Reading time  9 minutes

Captain Sully's mental math during those 208 seconds was not improvised. It was the surfacing of thousands of hours of reflexive arithmetic, internalized so deeply that under load it ran without conscious thought. Every commercial pilot is supposed to carry this same math. Most do not. HudsonMath exists to fix that — and to give pilots in interview prep, recurrent training, and active line flying the same kind of cognitive scaffolding that put US Airways 1549 safely on the water instead of into a residential neighborhood.

What follows is the precise math Sully ran, the rules of thumb he relied on, the parallel calculations his first officer was running in the right seat, and the NTSB simulator data that proved the answer he arrived at in his head was the right one. Read it once. Then think about whether your own mental math could survive the same 35-second reaction tax.

I — TimelineThe 208 Seconds

The entire event lasted less than three and a half minutes. Every critical mental calculation and every physical action happened inside this compressed window.

Flight 1549 · January 15, 2009
0 — 20sStrike & Diagnosis

Bird strike at 3,000 feet

The aircraft hits a flock of Canada geese. Both engines fail catastrophically. Sully takes manual control and pushes the nose down to hold an optimal glide speed of about 185 knots — roughly 213 mph. His first calculation is reflexive: speed equals life. Slow the plane to stretch the glide, and it stalls and falls out of the sky.

21 — 60sAirport Elimination

LaGuardia rejected

Air Traffic Control offers Runway 13 at LaGuardia. Sully initiates a left turn to assess the visual sight picture. He looks out the window, checks his altimeter, and runs his internal geometry. The plane is dropping at roughly 1,000 feet per minute. He cannot clear the structures between him and the runway. Decision made.

61 — 105sTeterboro Calculation

Teterboro rejected

Control offers Teterboro Airport in New Jersey. Sully cross-references his heading, altitude, and distance. He mentally subtracts the altitude loss required to alter course toward New Jersey. Crossing the Hudson to reach a runway five miles away is a high-risk gamble that almost certainly ends in a residential neighborhood. He rejects Teterboro and commits to the river.

106 — 160sEnergy Management

South, parallel to the Hudson

Sully steers the plane south, parallel to the Hudson River. His mental math shifts entirely to managing his remaining energy. The descent has to be timed perfectly. He clears the George Washington Bridge with less than 900 feet to spare.

161 — 208sFlare & Impact

Touchdown

Sully prepares for impact. Wings level. Nose pitched up to precisely 11 degrees. Too low and the plane digs into the water and flips. Too high and the tail breaks off. He uses the visual horizon to judge the final aerodynamic calculation. Splashdown at 3:31 PM. All 155 souls survive.

II — Rules of ThumbThe Memorized Math

Every aircraft manual has exact glide performance charts. Pilots do not look at charts during low-altitude emergencies. They use memorized mental math shortcuts — the same kind of speed-arithmetic the AA Pilot Selection Test demands, the same kind every airline interview measures, the same kind that gets a plane on the water instead of into a building.

Sully ran three of them.

Rule 1
The 3:1 Glide Ratio
For every 1,000 feet of altitude, a typical commercial jet glides roughly 3 nautical miles forward under ideal conditions. Starting at 2,800 feet after the strike, Sully's maximum theoretical straight-line glide distance was about 8.4 miles. He arrived at that number instantly.
Rule 2
The Turn Tax
A standard 180-degree turn costs a gliding aircraft roughly 300 to 500 feet of altitude and strips away forward momentum. Sully mentally subtracted this tax from his 8.4-mile theoretical limit, which brought his realistic runway options down to zero.
Rule 3
Wind Factor Estimation
Headwinds shorten glide distance. Tailwinds extend it. Sully quickly compared his groundspeed against his airspeed to make sure he wasn't overestimating his reach. A miscalculation here puts the plane short of any survivable surface.

The math itself is not exotic. Multiply altitude in thousands by 3. Subtract 400 for any 180-degree turn. Compare against the distance to the runway. What is exotic is the speed at which it has to happen — and the certainty with which the pilot has to trust the answer before committing 155 lives to it.

"I calculated that the runway was a fixed point. My altitude was a shrinking variable. And the two lines on my mental graph simply would not intersect."
— Captain Chesley B. "Sully" Sullenberger

III — The Right SeatWhat the First Officer Was Doing

While Sully focused on flying, energy management, and spatial math, First Officer Jeff Skiles was running a parallel mental track focused entirely on the aircraft systems. Two streams of math, two cognitive loads, one cockpit.

The QRH Checklist

Skiles immediately pulled out the Quick Reference Handbook to find the Engine Dual Failure checklist. The checklist was not designed for an event at 3,000 feet. It assumed a higher-altitude failure with time to spare. He ran it anyway, condensing what was intended as a multi-minute procedure into the seconds available.

The Airspeed Math for Restart

The checklist required a minimum airspeed of 300 knots to attempt a windmilling engine restart without the auxiliary power unit. Skiles and Sully ran the trade-off: to get to 300 knots, they would have to pitch the nose down steeply, trading altitude for speed. They did not have the altitude to spare. They committed to the slower battery-assisted starter instead.

System Prioritization

Skiles successfully started the Auxiliary Power Unit early in the timeline. This single calculation saved the flight. It kept the fly-by-wire computers powered, which meant Sully could fly the plane with precise, computer-assisted control all the way to the water.

IV — The VerdictHow the NTSB Validated His Math

After the ditching, the National Transportation Safety Board ran an extensive investigation to verify whether the aircraft could have realistically made it to LaGuardia or Teterboro. They put veteran pilots into full-motion engineering flight simulators and asked them to recreate the exact flight profile.

The Unrealistic Successes

In early simulator trials, several pilots successfully turned back and landed at LaGuardia or diverted to Teterboro. But these trials lacked one critical human element: reaction time. The simulator pilots knew the bird strike was coming. They skipped the entire diagnostic phase and initiated an immediate bank turn at the exact millisecond the engines failed.

The 35-Second Real-World Tax

To account for human processing — the time it takes a brain to realize both engines are dead, evaluate options, and take control — investigators introduced a mandatory 35-second delay before allowing the simulator pilots to turn.

NTSB Final Determination
With the 35-second reaction tax applied, every single simulator flight crashed.
Every aircraft that attempted to return to LaGuardia or divert to Teterboro flew into the buildings of Queens, into the suburbs of New Jersey, or stalled into the river short of the runway. The data officially validated Sully's rapid mental math. The NTSB concluded that attempting a runway landing was too high-risk and that the Hudson River provided the highest probability of survival.

V — The Silent Co-PilotWhat the Airbus Did

The Airbus A320 uses a digital Fly-By-Wire flight control system. Instead of a direct physical cable connecting the side-stick to the wings, the pilot's inputs are sent to computers, which calculate exactly how to move the control surfaces. During the ditching, this automation acted as an invisible third crew member.

Alpha Protection

The stall-prevention software monitored the aircraft's speed and angle of attack continuously. It would not allow Sully to pull the nose up so high that the wings stalled. This cushioned the glide — he could pull back completely on the stick to maximize range without fearing a fatal aerodynamic stall.

Pitch and Roll Attenuation

The flight computers balanced the aerodynamic forces during turns automatically, preventing the wings from tilting beyond safe limits. This stabilized the descent and minimized altitude loss in banking turns, neutralizing part of the Turn Tax that purely manual aircraft suffer from.

The Ram Air Turbine

When the engines died, a small propeller called the Ram Air Turbine deployed from the belly of the plane, capturing the passing wind. It generated just enough hydraulic and electrical power to keep the flight computers running all the way to the water. Without it, the fly-by-wire system would have been a dead box.

The One Drawback

Sully later noted one minor cost of the automation. Because the plane was flying slowly right before splashdown, the computer's stall-prevention software artificially limited how high he could raise the nose. He wanted to flare a fraction higher to soften the impact. The fly-by-wire system overrode him to protect against what it perceived as an oncoming stall. The touchdown was slightly harder than he intended.

VI — Why This MattersThe Reason HudsonMath Exists

The story of Flight 1549 is usually told as a story about Sully's calm. That is half the story. The other half — the part that does not make the movie — is the math that ran underneath the calm.

You cannot stay calm running calculations you have not internalized. The 3:1 ratio. The turn tax. The 35-second reaction window. The wind factor. These are not facts to look up. They are reflexes. Either they fire before you can think, or they do not fire at all.

Most pilots learn this math once in training and never drill it again. The American Airlines Pilot Selection Test, the Delta Quotient, and the United Cognitive Battery exist in part to expose this gap — to find the candidates whose math is automatic versus the candidates whose math is performative. The gap shows up in cockpits too. Every accident report that begins with "the pilot had time to act but did not" is a story about math that did not fire under load.

HudsonMath is a training system, built around the principle that speed math is not arithmetic — it is recognition. The eye learns to see the shape of the problem before the brain ever computes it. The four-step rule, the rounding shortcuts, the percentage tricks, the cross-checks — every drill in the system is engineered to put one more reflexive pattern under your conscious thought.

Whether you are preparing for an airline interview, refreshing before a check ride, or simply staying sharp because your seat is the one with 155 lives behind it, the math has to be ready before the moment arrives.

The Hudson River was not Sully's choice. The math eliminated every other option. We built this site so the math is on your side too.

— HudsonMath Editorial · May 2026
Start Today

Make the math reflexive.

Eleven problem types. Four-step recognition. Seven training rungs. A Hobbs meter that knows when you skip a day. Begin where every pilot should — with the arithmetic that fires before you think.

Start Training See the Method