Go Back  Airline Pilot Central Forums > Airline Pilot Forums > Major > Delta
Delta 56 Severe Turbulence >

Delta 56 Severe Turbulence

Search

Notices

Delta 56 Severe Turbulence

Thread Tools
 
Search this Thread
 
Old 08-09-2025 | 06:50 AM
  #361  
Meme In Command's Avatar
Leaves Biscoff crumbs
Veteran: Army
Loved
On Reserve
Line Holder
 
Joined: Jan 2020
Posts: 3,265
Likes: 941
From: Blue Juice Taste Tester
Default

Originally Posted by MasterOfPuppets
it’s not about the maneuver I have 100% confidence an FO could safely reject. I have seen it hundreds of times in the SIM on FO/FO training pairings.

it’s about the decision and the execution. I have a go mindset. If you say generator failure to me we are going airborne because it is safer. However if an Amber caution illuminates and the FO rejects before I have the opportunity to say continue I can no longer stop him. And I gurantee you CAs will try to stop their FOs which is extremely dangerous.

or as I mentioned previously I as the Captain call reject and the FO either doesn’t hear me because Audio is gone or hearing issues without an intercom or doesn’t react now I have to TAKE the airplane which is much different than a positive transfer of controls.

if the Captain has undisputed reject or continue authority (which is different than actually saying Reject by the FO when there is a perceivedsafety issue) then the Captain needs to perform the maneuver for safety
The audio argument I'm not a huge fan of because these are issues that could easily affect both. What if the FO calls out something that's within the normal abort criteria and the captain does nothing? "Oh well I'm not allowed to abort so f#$k me I guess"

Like I said, if abort criteria and maneuver was something that was standard and periodically trained by both pilots just like go arounds and V1 cuts, it would be a non-issue (and I don't mean the physical maneuver alone, I mean the identification and execution through proper decision making). This is my first flying job where the authority to abort is strictly the Captain's.

I would even argue that starting to train FO's to properly identify and execute better prepares them for when they upgrade. Then it doesn't become some new, added responsibility.

And what if the captain is the solely responsible? Who's going to get in trouble for backing their FO after an abort? This line of thought would have more teeth of FOs were aborting for erroneous indications and putting aircraft in unsafe conditions. That's not happening anywhere.
Reply
Old 08-09-2025 | 06:55 AM
  #362  
On Reserve
 
Joined: Nov 2010
Posts: 26
Likes: 1
From: Airbus 320 / Captain
Default

I remember being an FO getting all spun up about this reject decision and who gets to call it.

Everyone needs to relax, follow the guidance the company has given us to execute the abort. Do you really think Flight Ops has this policy because they are just stubborn and don't want to give FO's more control? Seriously? Relax. You'll be in the captains seat soon enough arguing against the points you are making today.

It isn't a hit against your ego and no one is saying you aren't ace of the base and can make those decisions. We get it. You guys rock and you keep us out of trouble ALL THE TIME, but the reject policy is what it is because of past incidents and accidents.



Reply
Old 08-09-2025 | 06:59 AM
  #363  
MasterOfPuppets's Avatar
Gets Weekends Off
 
Joined: Feb 2012
Posts: 3,599
Likes: 205
From: 787
Default

Originally Posted by Meme In Command
The audio argument I'm not a huge fan of because these are issues that could easily affect both. What if the FO calls out something that's within the normal abort criteria and the captain does nothing? "Oh well I'm not allowed to abort so f#$k me I guess"

Like I said, if abort criteria and maneuver was something that was standard and periodically trained by both pilots just like go arounds and V1 cuts, it would be a non-issue (and I don't mean the physical maneuver alone, I mean the identification and execution through proper decision making). This is my first flying job where the authority to abort is strictly the Captain's.

I would even argue that starting to train FO's to properly identify and execute better prepares them for when they upgrade. Then it doesn't become some new, added responsibility.

And what if the captain is the solely responsible? Who's going to get in trouble for backing their FO after an abort? This line of thought would have more teeth of FOs were aborting for erroneous indications and putting aircraft in unsafe conditions. That's not happening anywhere.
I would have no problem with the FOs being trained to properly identify. Make a decision and execute a Reject.

so let’s go further why not let the FO conduct an autoland to CAT3/Land3 mins? Why not let the FO takeoff at 300/500 RVR? Why not let FOs land at special airports when less than 100 hours? Why not let FOs fly into CA only airports?

the answer is above my pay grade whether it’s insurance, FAA requirements or simply money for proper training.

if the company came out tomorrow and said we are going to add a week to training so the FOs can do all of this then I would have no problem with it.
Reply
Old 08-09-2025 | 07:37 AM
  #364  
Meme In Command's Avatar
Leaves Biscoff crumbs
Veteran: Army
Loved
On Reserve
Line Holder
 
Joined: Jan 2020
Posts: 3,265
Likes: 941
From: Blue Juice Taste Tester
Default

Originally Posted by Delta 320Driver
I remember being an FO getting all spun up about this reject decision and who gets to call it.

Everyone needs to relax, follow the guidance the company has given us to execute the abort. Do you really think Flight Ops has this policy because they are just stubborn and don't want to give FO's more control? Seriously? Relax. You'll be in the captains seat soon enough arguing against the points you are making today.

It isn't a hit against your ego and no one is saying you aren't ace of the base and can make those decisions. We get it. You guys rock and you keep us out of trouble ALL THE TIME, but the reject policy is what it is because of past incidents and accidents.
This might blow your mind, but I upgraded and I didn't start thinking I was gods gift to aviation. I have upgraded on two fleets here. I'm fine with the idea of FO's aborting as PF. I know it's not how we do it and I stick to the manual, but if it changes tomorrow and FOs could do it I would lose zero sleep.
Reply
Old 08-09-2025 | 07:48 AM
  #365  
notEnuf's Avatar
Gets Weekends Off
 
Joined: Mar 2015
Posts: 13,230
Likes: 677
From: ir.delta.com
Default

Originally Posted by Trip7
It’s not a question of skill—the FO is fully capable of performing RTOs. However, the rejected takeoff is a rare, extreme case where removing any uncertainty, ambiguity, or decision-sharing is paramount. This is reflected in both safety reports and industry best practices.

The Captain is the designated pilot-in-command, legally and operationally responsible for the safety of the flight. During a high-risk event like a rejected takeoff—where milliseconds count and consequences can be catastrophic—the decision must rest with the individual who bears this overarching liability and authority

Takeoff is the most critical phase of flight, with few opportunities for error. Assigning the RTO decision and maneuver to the Captain eliminates ambiguity and delays caused by cross-cockpit communication—there’s no time to debate or cross-check during a high-speed abort scenario. This streamlines response, ensuring one person acts without hesitation.

High-pressure decisions with life-or-death implications require clear lines of authority.
This is why the CA is designated to decide and execute. The ultimate responsibility dictates the CA be the one executing an abort. If the FO does it and messes it up the fault still lies with the CA. This is also why CAs are encouraged to land single engine. The reason we have a highspeed regime is to simplify the decision and speed the execution of an abort. Anything distracting from this adds additional risk unnecessarily. It's not about the FOs experience or ability but about a methodical approach to eliminating risk.

As PIC the option always exists to take control of the airplane. CFIs who train new students are good at identifying and intervening because they have a much wider SA and are trained to react when the aircraft (by malfunction or pilot action) is not performing as anticipated. The transfer of controls should be a non-issue. The only thing that has made it an issue is automated RTOs. The captain has to decide if the spoilers are up and the brakes are working. I actually default to manual brakes and grab for the spoilers more than DAL would like because that's the way my primary training was in a non-autobrake and spoiler airplane. A hesitation after saying "abort I have the airplane" doesn't mean incapacitation. It is likely tracking center line or being corrected to it and if the systems are working the airplane is slowing itself when thrust is idle and then emergency reverse. It is difficult to stay off the brakes and allow the spoilers to deploy automatically.

Last edited by notEnuf; 08-09-2025 at 08:02 AM.
Reply
Old 08-09-2025 | 07:52 AM
  #366  
Gets Weekends Off
 
Joined: Jul 2013
Posts: 12,480
Likes: 1,052
Default

Originally Posted by MasterOfPuppets
I would have no problem with the FOs being trained to properly identify. Make a decision and execute a Reject.

so let’s go further why not let the FO conduct an autoland to CAT3/Land3 mins? Why not let the FO takeoff at 300/500 RVR? Why not let FOs land at special airports when less than 100 hours? Why not let FOs fly into CA only airports?

the answer is above my pay grade whether it’s insurance, FAA requirements or simply money for proper training.

if the company came out tomorrow and said we are going to add a week to training so the FOs can do all of this then I would have no problem with it.
First, your argument does not apply because in all of those scenarios, the FO isn't flying then suddenly handing the controls to the captain to accomplish the landing portion of a Cat3. And a FO doesn't ever land or take off in lower than standard visual conditions. It makes sense not to certify them to autoland in lower than standard conditions purely from a training cost perspective.

It does not take additional training (a week, really?) to know the criteria on an RTO. FOs already accomplish 90% of the maneuver. By the time the captain takes control during an RTO, the vast majority of the maneuver is already accomplished. Every FO should already know the abort criteria. I know I do.
Reply
Old 08-09-2025 | 08:04 AM
  #367  
DWC CAP10 USAF's Avatar
Gets Weekends Off
Veteran: Air Force
Liked
Gets Weekends Off
 
Joined: Apr 2016
Posts: 3,985
Likes: 187
From: Looking left
Default

Originally Posted by cencal83406
At United or just in your cockpit? It’s been plainly spoken for 2 airlines now that the FO has no decision making authority regarding RTO. The FO shall not call reject. The FO is merely to point out an observation (engine failure, fire, etc,) but if the CA chooses to continue, CAs authority dictates the CA is correct and you should not overrule.

In every other instance besides reject they make it clear that you may usurp authority if you feel it’s a safety issue. RTO is crystal clear.

Not sure about the consternation about two people on the controls either. You are PF until relieved by the phrase “I have the aircraft.
But you aren't relieved by the phrase (which was my gripe earlier)....you aren't relieved until you feel said Captain come on the control to take the rudder from you.

IMO it *should* be the phrase....don't say it until you are actually ready to do it.
Reply
Old 08-09-2025 | 08:16 AM
  #368  
Gets Weekends Off
 
Joined: Jul 2013
Posts: 12,480
Likes: 1,052
Default

Originally Posted by notEnuf
This is why the CA is designated to decide and execute. The ultimate responsibility dictates the CA be the one executing an abort. If the FO does it and messes it up the fault still lies with the CA. This is also why CAs are encouraged to land single engine. The reason we have a highspeed regime is to simplify the decision and speed the execution of an abort. Anything distracting from this adds additional risk unnecessarily. It's not about the FOs experience or ability but about a methodical approach to eliminating risk.

As PIC the option always exists to take control of the airplane. CFIs who train new students are good at identifying and intervening because they have a much wider SA and are trained to react when the aircraft (by malfunction or pilot action) is not performing as anticipated. The transfer of controls should be a non-issue. The only thing that has made it an issue is automated RTOs. The captain has to decide if the spoilers are up and the brakes are working. I actually default to manual brakes and grab for the spoilers more than DAL would like because that's the way my primary training was in a non-autobrake and spoiler airplane. A hesitation after saying "abort I have the airplane" doesn't mean incapacitation. It is likely tracking center line or being corrected to it and if the systems are working the airplane is slowing itself when thrust is idle and then emergency reverse. It is difficult to stay off the brakes and allow the spoilers to deploy automatically.
Re: captains are encouraged to SE Land, this is absolutely not true. In fact, I've been here quite awhile and I've never heard a single person say the CA will land single engine. Every single brief is that the FO lands in every abnormal.
Reply
Old 08-09-2025 | 08:38 AM
  #369  
symbian simian's Avatar
Line holder
 
Joined: Nov 2013
Posts: 4,167
Likes: 226
From: Aircraft & Seat: old & hard
Default

So much of this is based on the historical "the captain is the one that has experience". There is plenty of experienced FOs flying with less experienced captains. I am an FO, and I have over 10k TPIC. Most of the captains I fly with have less than that. So the whole "the FO might freeze" does not sit right. And when I was the experienced captain flying with low time FOs I felt the same. If we have an engine failure after V1 we don't hand over controls, why do we do it when we have an engine failure before V1? I can see where in the high speed regime the call should be made by the captain, but I see no reason to hand over controls at that point. I flew pax abroad for a company where everything including starting engines and taxiing was PF/PM (dual tillers). Only the captain could call for the abort, emergency descent and evacuation, but the role did not change. Still feel strongly that was the best way.
Reply
Old 08-09-2025 | 08:46 AM
  #370  
symbian simian's Avatar
Line holder
 
Joined: Nov 2013
Posts: 4,167
Likes: 226
From: Aircraft & Seat: old & hard
Default

Originally Posted by MasterOfPuppets
I would have no problem with the FOs being trained to properly identify. Make a decision and execute a Reject.

so let’s go further why not let the FO conduct an autoland to CAT3/Land3 mins? Why not let the FO takeoff at 300/500 RVR? Why not let FOs land at special airports when less than 100 hours? Why not let FOs fly into CA only airports?

the answer is above my pay grade whether it’s insurance, FAA requirements or simply money for proper training.

if the company came out tomorrow and said we are going to add a week to training so the FOs can do all of this then I would have no problem with it.
The reason for all of that is that historically the captain had more experience. When I was new, had a green/green pairing where the captain had to do the landing due to winds. We both had less than a 100 hours on type, he was a 787 bunkie for the 2 years prior, and a regional FO before. I just came of 10 years as a NB captain......
Reply
Related Topics
Thread
Thread Starter
Forum
Replies
Last Post
Kilroy
ExpressJet
10796
01-11-2016 06:49 AM
Quagmire
Major
253
04-16-2011 06:19 AM
JiffyLube
Major
12
03-07-2008 04:27 PM
RockBottom
Major
0
09-15-2006 09:50 AM

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



Your Privacy Choices