Welcome to Flightinfo.com

  • Register now and join the discussion
  • Friendliest aviation Ccmmunity on the web
  • Modern site for PC's, Phones, Tablets - no 3rd party apps required
  • Ask questions, help others, promote aviation
  • Share the passion for aviation
  • Invite everyone to Flightinfo.com and let's have fun

Rejected Takeoffs CRJ900

Welcome to Flightinfo.com

  • Register now and join the discussion
  • Modern secure site, no 3rd party apps required
  • Invite your friends
  • Share the passion of aviation
  • Friendliest aviation community on the web
What's this? A genuine technical question on FI? It's like it's 10 years ago...


The book I read during my ground training said first and foremost that it is the PIC's decision. As a guideline, though, we abort for just about anything below 80 kts. Above 80 kts, abort only for engine fire or failure, loss of directional control, or the perception that the A/C is unsafe to fly. Again, I stress that the abort is the PIC's decision, not necessarily the PF's decision.

It is my personal technique to verbalize this at least once a pairing, regardless of whether or not I've flown with a guy before or not. Typically, I get blank looks and stuttering attempts to remember the criteria for a high speed abort at least once a month. Occasionally, this brings about a conversation that highlights things that I've either forgotten or not thought of; this is fine with me.

It's irritating for me to see memos from my company that suggest that crews are accomplishing too many high speed aborts. That being said, I see their point. The number of high speed aborts are up, while the necessity of these aborts, in hindsight, is often questionable.
 
"It's irritating for me to see memos from my company that suggest that crews are accomplishing too many high speed aborts. That being said, I see their point. The number of high speed aborts are up, while the necessity of these aborts, in hindsight, is often questionable. "

Remember, the vast minority of total abort is in the high speed regime, about 120 KIAS or more. An yet, the vast majority of abort incidents or accidents come from these aborts. Be careful out there.
 
High speed aborts can have very grave consequences and should only be considered for Fire, failure, control problems, or inadverdent TR deploys. Its seems that some think there are too many low speed aborts happening.
 
Last edited:
I'd rather abort at low speed and discover I over-reacted than NOT abort and wish I had.

Gup
 
MoreDaysOff said:
Remember, the vast minority of total abort is in the high speed regime, about 120 KIAS or more. An yet, the vast majority of abort incidents or accidents come from these aborts. Be careful out there.

Technically speaking, anything above 80kts (or whatever speed a particular operator uses) is in the high speed regime.

As for the BRAKE OVHT message...does it result in a red flashing MASTER WARNING with triple-chime? If so, and your brief including stopping for any red warning item above 80kts, then yes, you should reject the takeoff. If you briefed an abort above 80kts only for an engine fire/failure, loss of directional control or TR deployment, then continue because a master warning isn't one of your briefed abort criteria.

Again, I don't see the difficulty in flying as you brief...but what I don't understand is the logic of taking the time to look at a caution/warning, analyze it and its impact on the operation, decide a course of action and then execute that action (stop or go). Even a proficient, well-trained pilot is going to take at least one, and probably 2-3 seconds to go from chime/message to action initiation and that adds airspeed and gives up runway if you decide to stop.
 
The high speed regine has a floating definition. What's fast on one runway is slow on another. Just one part of the dynamics of this very important topic.

Bt the way, the BRAKE OVHT is a Warning Message, is not inhibited and decreases your braking capability (on which your RTO performance is based).
 
Last edited:
This is a debate that has gone on for years. There will never be an all encompassing list of what to abort for when under what conditions. My viewpoint is this. Aborting below 80 (or some other arbitrary number to signify a low speed abort) will not hurt you. It comes down to operational efficiency. Can the flight continue safely? Would the light have caused an air return, or just a write-up prior to the next flight. Either way...continue or abort, safety is served. High speed aborts are another animal entirely. Look at the stats...a high speed abort is a VERY RISKY MANEUVER. Whatever you abort for darn well better be for something riskier than the abort itself. What that might be can be debated to death, but it depends on the aircraft, the airport (overruns, runway length, braking action etc.), the weather, the crew (rested or not, experience etc.) I look at it like the doctors oath. "First do no harm". You never trade a small risk for a larger one.
 
XJ-I am with you for the most part but I'm not sure I like a philosophy that says there is really no need to abort for any amber cautions below 80 knots. To me there are some amber cautions in the 900 that I really dont wan't to deal with in the air when I knew about them at 30 knots.
 
XJ-I am with you for the most part but I'm not sure I like a philosophy that says there is really no need to abort for any amber cautions below 80 knots. To me there are some amber cautions in the 900 that I really dont wan't to deal with in the air when I knew about them at 30 knots.

I agree with you, and am not saying to never abort for an amber when below 80. All I am saying is it depends on which one. If I get an ice caution....I'm going, other ambers maybe not. My point is that the decision to abort when below 80 is almost always very low risk. Some however may 2nd guess the decision if it is a minor issue. Aborting for an ice caution may not be seen as "efficient" by management when it turns into delays etc. Above 80 has the potential to hurt people so it should be taken very seriously. The risk of the abort can never be greater than the risk of flying with the malfunction. If it is then you are better off to continue the take-off.
 
Last edited:
"stay on the ground "

Remember also that of the abort incidents or accidents over half could have been avoided by continuing the takeoff.
 
I was talking about below 80 knots and the guidance was don't abort for any ambers. One amber I would probably not abort for is L or R THROTTLE because that engine power is not going to reduce when you pull the power levers back. Now you have assymetrical thrust with an engine stuck at takeoff power and one you pulled to idle. (Better to takeoff and handle that one in the air) PROX SYS is one that I would think a pilot would want to abort for becasue now you are manually extending the gear and you will have no indication of down.

Just wondering what other guys thought about this topic

And your company standards manual gives no guidance on this?!?!?!

WTF?!
:eek:
 
Sorry about bringing up this dead thread again.....

What's the correct term at your company?
For instance, I've heard "Rejected Takeoff", "Aborted Takeoff" and "Discontinued Takeoff". All terms seem to be interchangeable. I flew with a captain in a prior life at a different airline who went nuts if you used the word "ABORT" when you informed tower of the reject. His reasoning was that something about the word "abort" triggers an automatic phone call to the FAA by tower personnel. I guess he didn't want the FAA to know for whatever reason. He preferred "discontinued" when informing tower.

My manual says it's a "Rejected Takeoff", but the captain calls "Aborting".
There is nothing in my manual as to what verbiage the first officer uses when informing the tower of the RTO. It just say's to inform them.
 
Sorry about bringing up this dead thread again.....

What's the correct term at your company?
For instance, I've heard "Rejected Takeoff", "Aborted Takeoff" and "Discontinued Takeoff". All terms seem to be interchangeable. I flew with a captain in a prior life at a different airline who went nuts if you used the word "ABORT" when you informed tower of the reject. His reasoning was that something about the word "abort" triggers an automatic phone call to the FAA by tower personnel. I guess he didn't want the FAA to know for whatever reason. He preferred "discontinued" when informing tower.

My manual says it's a "Rejected Takeoff", but the captain calls "Aborting".
There is nothing in my manual as to what verbiage the first officer uses when informing the tower of the RTO. It just say's to inform them.



Us whatever verbage you want as long as you stop the friggin' plane
 
My understanding is that anytime an aircraft takes the runway, but doesn't takeoff, it's considered an "abort takeoff." All aborts are reported to the FAA, even if an aircraft is cleared into position and hold and then instructed to exit the runway.
 
I'll abort when I'm god damned good and ready! You got that!
 
Anything above 80 knots is very critical and an abort should always be executed for anything happening above that speed.
 

Latest resources

Back
Top