SIC Rejected Takeoff Rights
Thread Starter
Join Date: Sep 2004
Location: Wichita Kansas USA
Posts: 31
Likes: 0
Received 0 Likes
on
0 Posts
SIC Rejected Takeoff Rights
A question for the PPRuNe group. Does your airline permit the SIC or First Officer to make the abort decision and/or execute the RTO maneuver when they are the Pilot Flying?
Thanks,
Rich Boll
Wichita, KS
Thanks,
Rich Boll
Wichita, KS
Join Date: Nov 2011
Location: E.U.
Posts: 21
Likes: 0
Received 0 Likes
on
0 Posts
RTO
In the airline I am familiar with, it used to be the case that the Capt made the RTO call and the PF, whichever that was, carried out the stopping actions.
It was found that a better RTO resulted when the Capt made both the call and took control to do the RTO actions.
The F/O then was PM for failure drills etc.
Not very familiar with any other system, so I can't comment whether this is the optimum scenario or not. Hope this helps.
It was found that a better RTO resulted when the Capt made both the call and took control to do the RTO actions.
The F/O then was PM for failure drills etc.
Not very familiar with any other system, so I can't comment whether this is the optimum scenario or not. Hope this helps.
Join Date: Apr 2008
Location: A tropical island.
Posts: 461
Likes: 0
Received 0 Likes
on
0 Posts
"Proceduraly" and in 99% of cases the PICs decision will be the correct one. Regardless of the FOs experience levels.
Practically the FO should take over the aircraft any time it's obvious their life is in danger (CA continuing with fire bell going off after 1 notification of the engine being on fire followed by 2 abort calls from me, luckily in a simulator). Also, years of experience on a particular air-frame has a way of "adding" performance, particularly in smaller A/C.
Practically the FO should take over the aircraft any time it's obvious their life is in danger (CA continuing with fire bell going off after 1 notification of the engine being on fire followed by 2 abort calls from me, luckily in a simulator). Also, years of experience on a particular air-frame has a way of "adding" performance, particularly in smaller A/C.
Join Date: Aug 2008
Location: Betwixt and between
Posts: 666
Likes: 0
Received 0 Likes
on
0 Posts
Nope, stop or go is PICs decision obviously unless incapacitated.
Join Date: Oct 2006
Location: Ankh Morpork, DW
Posts: 652
Likes: 0
Received 0 Likes
on
0 Posts
In the sim, I've had to demonstrate both auto-land go-arounds and rapid decompression/emergency descents with PIC incapacitation.
I guess PICs aren't allowed to be incapacitated during takeoff. It's probably in the regs somewhere. Unless you're in a Trident.
I guess PICs aren't allowed to be incapacitated during takeoff. It's probably in the regs somewhere. Unless you're in a Trident.
Moderator
Join Date: Apr 2004
Location: Rome
Posts: 792
Likes: 0
Received 0 Likes
on
0 Posts
In my current airline and in the airlines I have been working before the decision is taken by the Captain and the actions executed by the CM1, which is normally also the captain unless it is a training flight like a command upgrade. Obviously the Capt may become incapacitated anytime and it is therefore the FO duty (CM2 in normal ops) to carry out the RTO. Other than that I have never experienced SOPS where both the Capt and the FO had the authority to stop the takeoff, except in the above mentioned cases or in case the capt is obviously getting it really wrong like the examples that have been given above in other posts (emergency authority).
Boeing FCTM advice is the captain always makes the reject decision and conducts the reject manoeuver. It has been ever so in aviation although various operators empower the copilot to make the decision and the reject actions. Their problem...
I've flown with only PiC permitted to call "Stop!" and also with either permitted to do so.
My preference both as a FO and as a PiC is for the decision always to be made by the captain but, since I don't write the Ops Manual, I do what the company says.
My preference both as a FO and as a PiC is for the decision always to be made by the captain but, since I don't write the Ops Manual, I do what the company says.
Thread Starter
Join Date: Sep 2004
Location: Wichita Kansas USA
Posts: 31
Likes: 0
Received 0 Likes
on
0 Posts
Thanks for everyone's comments. I appreciate your assistance.
The question was not so much targeted at pilot incapacitation or failure to react, but rather who in the cockpit had the authority to call for a rejected takeoff and whether the RTO was to be performed only by the captain or by the first officer if he/she is the pilot flying the takeoff.
Sorry that I'm not familar with the differing nomenclature concerning captain & first officer. PIC & SIC and PF & PM, are terms that I'm most familar with.
Thanks again!
Rich Boll
The question was not so much targeted at pilot incapacitation or failure to react, but rather who in the cockpit had the authority to call for a rejected takeoff and whether the RTO was to be performed only by the captain or by the first officer if he/she is the pilot flying the takeoff.
Sorry that I'm not familar with the differing nomenclature concerning captain & first officer. PIC & SIC and PF & PM, are terms that I'm most familar with.
Thanks again!
Rich Boll
Join Date: Dec 2007
Location: France
Posts: 481
Likes: 0
Received 0 Likes
on
0 Posts
Hmmm...
The passengers think they are paying for two qualified pilots to be at the controls...
I've flown with both systems, and there is no doubt in my mind that the best operation is with full role reversal and both having the right to say and do 'stop', provided the RHS occupants are of high calibre and well trained and tested.
I've only had one genuine big engine problem before V1, and the FO, PNF, spotted it well before I did. He called stop and I did.
The points made above reflect the awkwardness of the system, there's history about qualification lost here, too, and there are few operators who meet my criteria above, these days...
The passengers think they are paying for two qualified pilots to be at the controls...
I've flown with both systems, and there is no doubt in my mind that the best operation is with full role reversal and both having the right to say and do 'stop', provided the RHS occupants are of high calibre and well trained and tested.
I've only had one genuine big engine problem before V1, and the FO, PNF, spotted it well before I did. He called stop and I did.
The points made above reflect the awkwardness of the system, there's history about qualification lost here, too, and there are few operators who meet my criteria above, these days...
Join Date: Aug 2005
Location: fl
Posts: 2,525
Likes: 0
Received 0 Likes
on
0 Posts
Barbados in the carribean in a 727 we were nearing V1 and lost the left generator. We had a rainy day so the runway was wet and we were at max takeoff weight. 1000 and 3. I told the FO flying to keep going and the FE would fix it. He had a check FE requalifying him on that flight. I told the FE to fix the problem knowing the fix was one pak off. He put essential power to number 1 engine and at V1 lost most of our instruments. I said they will fix it and continued. They finally got it sorted out and put essential power back on #3 engine. I don't know what the standard procedure would be then but felt I did the right thing. Sometimes doing what makes sense works.
Join Date: Apr 2008
Location: nowhere
Posts: 1
Likes: 0
Received 0 Likes
on
0 Posts
Barbados in the carribean in a 727 we were nearing V1 and lost the left generator. We had a rainy day so the runway was wet and we were at max takeoff weight. 1000 and 3. I told the FO flying to keep going and the FE would fix it. He had a check FE requalifying him on that flight. I told the FE to fix the problem knowing the fix was one pak off. He put essential power to number 1 engine and at V1 lost most of our instruments. I said they will fix it and continued. They finally got it sorted out and put essential power back on #3 engine. I don't know what the standard procedure would be then but felt I did the right thing. Sometimes doing what makes sense works.
As a FE in the mil I had authority to call stop but in civvy life I was suddenly incapable.
The captain was annoyed and said next time you call "STOP" make sure it is for a good reason. With that, the captain back-tracked for another take off and lined up. Meanwhile the F/E seethed with indignation.
Down the runway they went and again the F/E yelled "STOP".
True to SOP which gave the authority for the F/E to call "STOP" the captain hauled off the throttles and stood on the brakes. Turning to the F/E he said "WTF did you call "STOP" for this time?
The F/E said I called "STOP" because you did not use the full length of the runway and started the take off run well down the runway. That was illegal by RAF SOP so I called "STOP" as I am authorised to do so, SIR.
Draw your own conclusions...but it may explain why as a civilian F/E you are not authorised to make the decision to reject and why a crew member calling "STOP" should never mean the captain must therefore stop blindly without having any idea why the call was made in the first place...
The Boeing FCTM covers this nicely by stating "The PM should closely monitor essential instruments during the take off roll and immediately announce abnormalities such as "Engine Fire", "Engine Failure", or any adverse condition significantly affecting the safety of flight. The decision to reject the take off is the responsibility of the captain...
Join Date: Sep 1998
Location: wherever
Age: 55
Posts: 1,616
Likes: 0
Received 0 Likes
on
0 Posts
What a coincidence. These identical sentiments were echoed by a 727 F/E (former RAF Hastings flight engineer) of my acquaintance over a beer somewhere or other. He then gave an example of his awesome power (authority) to call an abort (Royal Air Force ). He was F/E on a RAF Hastings taking off from Darwin. Nearing lift off he noticed an oil pressure anomaly and called "STOP". The captain rejected the take off and after parking the brake said "Why did you call "STOP?" The F/E replied he thought he saw a falling oil pressure needle on one of the engines.
The captain was annoyed and said next time you call "STOP" make sure it is for a good reason. With that, the captain back-tracked for another take off and lined up. Meanwhile the F/E seethed with indignation.
Down the runway they went and again the F/E yelled "STOP".
True to SOP which gave the authority for the F/E to call "STOP" the captain hauled off the throttles and stood on the brakes. Turning to the F/E he said "WTF did you call "STOP" for this time?
The F/E said I called "STOP" because you did not use the full length of the runway and started the take off run well down the runway. That was illegal by RAF SOP so I called "STOP" as I am authorised to do so, SIR.
Draw your own conclusions...but it may explain why as a civilian F/E you are not authorised to make the decision to reject and why a crew member calling "STOP" should never mean the captain must therefore stop blindly without having any idea why the call was made in the first place...
The Boeing FCTM covers this nicely by stating "The PM should closely monitor essential instruments during the take off roll and immediately announce abnormalities such as "Engine Fire", "Engine Failure", or any adverse condition significantly affecting the safety of flight. The decision to reject the take off is the responsibility of the captain...
The captain was annoyed and said next time you call "STOP" make sure it is for a good reason. With that, the captain back-tracked for another take off and lined up. Meanwhile the F/E seethed with indignation.
Down the runway they went and again the F/E yelled "STOP".
True to SOP which gave the authority for the F/E to call "STOP" the captain hauled off the throttles and stood on the brakes. Turning to the F/E he said "WTF did you call "STOP" for this time?
The F/E said I called "STOP" because you did not use the full length of the runway and started the take off run well down the runway. That was illegal by RAF SOP so I called "STOP" as I am authorised to do so, SIR.
Draw your own conclusions...but it may explain why as a civilian F/E you are not authorised to make the decision to reject and why a crew member calling "STOP" should never mean the captain must therefore stop blindly without having any idea why the call was made in the first place...
The Boeing FCTM covers this nicely by stating "The PM should closely monitor essential instruments during the take off roll and immediately announce abnormalities such as "Engine Fire", "Engine Failure", or any adverse condition significantly affecting the safety of flight. The decision to reject the take off is the responsibility of the captain...
Or perhaps it's down to the generally lower selection and training standards in civil aviation?
Join Date: Feb 2012
Location: Earth
Posts: 14
Likes: 0
Received 0 Likes
on
0 Posts
No good answer.
In the past, they created CRM for a weak FO to keep the captain from killing everyone.
But with the airlines hiring the weakest FOs they can find, I suspect they just don't if they are in trouble short of aliens trying to shoot them out of the sky. So it's back to the captain having the experience to make the call.
In the past, they created CRM for a weak FO to keep the captain from killing everyone.
But with the airlines hiring the weakest FOs they can find, I suspect they just don't if they are in trouble short of aliens trying to shoot them out of the sky. So it's back to the captain having the experience to make the call.
Join Date: Jan 2006
Location: US
Posts: 2,205
Likes: 0
Received 0 Likes
on
0 Posts
FE Hoppy - oh puleeze. Some military SOP's are because they have inexperienced crews flying high performance and/or demanding a/c.
Because of that the military has numerous policies and SOP's that are dumbed down to the lowest common denominator, just like the civilian world.
Because of that the military has numerous policies and SOP's that are dumbed down to the lowest common denominator, just like the civilian world.
The real difference between Mil ops and Civil ops is the strict liability.
The Rules say:-
The Pilot in Command is responsible for xxxxxx (add in what ever you are talking about)
I have never seen "the first officer is responsible for xxxxx" in any of our rules.
So the first officer sees the big orange light on prior to V1 and screams "STOP". The pilot in command responds to the instruction, as we are conditioned from childhood to do, as well as being at a heightened state in a takeoff roll and poised to react. The aircraft slides off the end of the runway due to the big orange light being ANTI SKID INOP.
Who is responsible? The Captain is because the law says that the P in C is responsible! Yes the F/O made a dumb call but it is the P in C that carries the can!
Good training and respect between the seats will usually get a good outcome, but at the end of the day P in C is the one in Command!
The Rules say:-
The Pilot in Command is responsible for xxxxxx (add in what ever you are talking about)
I have never seen "the first officer is responsible for xxxxx" in any of our rules.
So the first officer sees the big orange light on prior to V1 and screams "STOP". The pilot in command responds to the instruction, as we are conditioned from childhood to do, as well as being at a heightened state in a takeoff roll and poised to react. The aircraft slides off the end of the runway due to the big orange light being ANTI SKID INOP.
Who is responsible? The Captain is because the law says that the P in C is responsible! Yes the F/O made a dumb call but it is the P in C that carries the can!
Good training and respect between the seats will usually get a good outcome, but at the end of the day P in C is the one in Command!