How C-17 Pilots Handle Rejected Takeoffs

What Actually Triggers a Rejected Takeoff

Rejected takeoffs have gotten complicated with all the mythology flying around about what actually causes them. Engine fires. Sensor ghosts. Tire failures at 80 knots. The reality is messier — and faster — than most people realize.

As someone who has spent time watching check airmen run these scenarios in the C-17 simulator, I learned everything there is to know about how crews make the abort decision. Today, I will share it all with you.

The call happens between 40 and 100 knots. That’s the window. No negotiation phase, no committee vote — just a binary decision on an aircraft that might be hauling 585,000 pounds and converting jet fuel into forward momentum at an alarming rate. I’ve watched it play out in real time in the sim. No pause button. No rewind.

But what is an RTO, really? In essence, it’s a crew’s decision to abandon a takeoff roll and stop the aircraft on the remaining runway. But it’s much more than that. It’s a compressed chain of judgment calls under conditions specifically designed to make judgment difficult.

Engine failure is the textbook trigger — a fire warning light on the flight engineer’s panel, or a complete N1 RPM dropout on one of the four General Electric F117-PW-100 turbofans. The decision isn’t about complexity, though. It’s about one question: can this crew fly away safely on what’s left? Can they climb? Control the aircraft? The math shifts at every gross weight, every density altitude, every runway length. Some mornings the answer is yes. Some mornings it isn’t.

Tire blowouts force immediate aborts. Michelin wheels and tires on the C-17 are rated for landing speeds — not rejected-takeoff speeds. A catastrophic failure at 80 knots puts directional control immediately in question. Nosewheel steering gets unreliable. Rudder authority drops. The runway starts looking narrower. The pilot monitoring calls “ABORT” and the flying pilot moves. No second opinion requested.

Fire warnings are the same story. A main deck cargo fire warning isn’t something you fly through and sort out later. Neither is a wheel well fire or an engine bleed air leak. The threshold is binary: can you reach an airport and land? If not, you stop where you are.

The real danger, honestly, isn’t identifying the problem. It’s that two-second window where a pilot second-guesses himself — is that really an engine failure or just a sensor glitch? That hesitation is where crashes happen. By the time you’ve talked yourself into believing the problem is real, you’ve used runway you needed to stop.

The Crew Callout Flow When It Goes Wrong

Frustrated by vague communication in high-stress emergencies, military aviation long ago drilled a specific callout flow into every crew using deliberately simple, unrepeatable language. Two words. No ambiguity. That’s the standard.

Here’s how it flows in a real scenario.

The flight engineer is scanning instruments — temperature, pressure, vibration. Something goes wrong on engine number two. He calls it: “Fire warning, number two engine.” Not a question. A statement of fact delivered without hesitation.

The pilot monitoring cross-checks that on his own instruments. Checks landing gear warning lights. Checks airspeed. Checks runway remaining. Makes the decision in roughly three to four seconds.

“Reject. Reject.”

Those two words, and the flying pilot moves. Throttles to idle. The abort is called and that’s it — no asking “are you sure?”, no committee discussion. The flying pilot’s only remaining job is executing the stop.

That’s what makes clear communication endearing to us aviators. It removes the one variable that kills people: uncertainty.

Where crews fail is the ambiguous callout. A mumbled “something’s off.” A hesitant tone. A single call instead of the double-call standard. Communication failures during high-speed aborts rarely involve silence — they involve unclear speech, competing radio calls, or a pilot monitoring who isn’t confident enough to commit. The C-17 flight deck runs four crew members: two pilots, a flight engineer, and a loadmaster. The loadmaster stays out of the abort decision, but the flight engineer’s callout is critical. If it’s garbled or uncertain, the pilot monitoring will hesitate too.

Simulator evaluators know this. They deliberately inject communication failures — background noise, degraded interphone quality, overlapping ATC calls — and watch what happens. Crews that say “I think maybe we should consider aborting” are not the same as crews that say “Reject. Now.” One stops in 4,000 feet. The other might not stop at all. Don’t make my mistake of underestimating how much that difference matters.

What the Aircraft Is Doing While the Crew Acts

Probably should have opened with this section, honestly. Because understanding what the aircraft is doing during those seconds makes everything else make more sense.

Three systems activate simultaneously: thrust reversers, wheel brakes, and the Hydro-Aire anti-skid protection system.

The thrust reversers don’t deploy instantly. There’s a 1-2 second hydraulic lag while the cascade doors unfold and redirect exhaust flow. Once they’re open, they’re diverting 40,000-plus pounds of thrust rearward. That’s not nothing — but it’s also not immediate, and that lag matters at high speed.

At the same time, the Hydro-Aire anti-skid computer is modulating the wheel brakes — releasing pressure at the first sign of skid, reapplying when traction returns. Carbon-backed, steel-faced brake discs, same material you’d find on commercial aircraft. The difference is that a fully loaded C-17 at 585,000 pounds and 100 knots generates enough braking energy to heat those discs to visible red in infrared. I’m apparently sensitive to the smell of hot carbon compounds, and that particular combination of ozone and scorched brake material coming up through the ventilation is something you don’t forget.

The whole aircraft shudders. Nose loads up slightly as aerodynamic drag works on the fuselage. The anti-skid chattering feels chaotic if you haven’t been trained for it — the control yoke vibrates, reverse thrust rumbles through the airframe, and deceleration feels uneven. From 100 knots to 50 feels like it takes forever. From 50 to zero feels like seconds. The flying pilot has to hold back pressure on the yoke throughout — too much unloads the main gear and you lose braking friction, too little and you risk nose gear damage. It’s a continuous correction all the way to a full stop.

Weight changes everything here. A max-gross C-17 stopping at Tucson in July — density altitude somewhere around 3,200 feet on a hot day — is a completely different problem than the same aircraft stopping at McChord in February. The math is done before every single takeoff. It has to be.

Hot Brakes and What Happens After You Stop

The aircraft stops. That’s not the end of it.

First call goes to the tower: “[Callsign], rejected takeoff, currently on runway at [position], requesting emergency services standby.” Not a request for permission. A statement of fact plus a coordination call.

Then the crew stays put. No turning around, no taxiing to the ramp. They sit on the runway — engines at idle or completely shut down after a fire warning — and wait for the fire trucks. This is where crews make mistakes, and I’ve seen it happen in the sim more than once.

After a high-speed abort involving significant braking, those wheel assemblies can be at 400-plus degrees Fahrenheit. The crew holds the aircraft stationary without setting the parking brake — because a seized wheel combined with parking brake application causes brake fade across the remaining wheels, and you lose what little stopping force you still have. The anti-skid system is offline. The flying pilot uses differential thrust to hold directional control while emergency vehicles position. Slight forward throttle on specific engines. It’s a delicate thing.

Nobody deplanes. Cabin doors stay closed until emergency personnel are on scene and have physically cleared the aircraft. That waiting period — sometimes 20 to 30 minutes — is genuinely difficult. Passengers want off. The cabin crew wants guidance. The tower wants status updates. And the crew is sitting on an aircraft that might still be on fire somewhere they can’t see. There’s no thermal imaging from the flight deck. You’re trusting the fire truck’s assessment entirely.

After roughly 30 minutes, brakes cool enough to taxi slowly to parking or to an inspection area. That’s when you set the parking brake. Not before.

How Crews Train for Rejected Takeoffs in the Simulator

So, without further ado, let’s dive into where all this actually gets learned.

The Full Motion Simulator at Altus Air Force Base, Oklahoma, is a multi-million dollar motion platform — tilts, shakes, accelerates — realistically enough that your body is genuinely convinced you’re flying. Evaluators inject failures at random points during the takeoff roll. Engine fire at 50 knots. Nosewheel steering failure at 80. Tire blowout at 70. The crews don’t know what’s coming. They don’t know which runway they’re departing until they sit down.

What evaluators are grading isn’t stick-and-rudder work. It’s decision speed and communication clarity. Common failures include: holding off the abort callout while mentally troubleshooting whether the failure is “real”; delivering the abort call ambiguously enough that the flying pilot doesn’t immediately understand; or — rarely, but it happens — the flying pilot second-guessing the abort and continuing the roll anyway.

That last one is rare. By the time you’ve completed a six-week combat crew training course at Altus, the culture has absorbed into you: the pilot monitoring calls the abort, the flying pilot executes it. Full stop. No debate.

This new training emphasis took off several years into the C-17 program and eventually evolved into the rigorous sim evaluation culture enthusiasts know and respect today. Because the RTO is one of the few emergency procedures in aviation with exactly one outcome available. You stop or you crash. There is no third option — and that’s what makes it different from almost everything else crews practice.

Every C-17 crew has run these scenarios dozens of times. They’ll keep running them every couple of years for as long as they fly the jet. That repetition isn’t redundancy. It’s the whole point.