Legal authority of a pilot-in-command

GON

$175 Site Donor 2026
Joined
Nov 28, 2014
Messages
12,418
Location
White Sands, NM
Interesting story of a 757 Captain who deadlined an aircraft as it was boarding, because his 25 years of experience as a 757 pilot told him something may still be wrong/ uncorrected, yet everything indicated no issue.

The issue was a concern over an elevator surface. This captain had flown this aircraft a day earlier. After the captain reported the problem, the maintenance crew spent nine hours looking for the problem, but no issue was found. The maintenance crew put the aircraft back into service/ signed off the aircraft was fit to fly.

The captain reported to have confidence in his maintenance crew, but regardless didn't have confidence the issue he reported the prior day was resolved. So the captain "deadlined" the aircraft, deboarded the passengers, and waited for a replacement aircraft to arrive.

More details from the event:
The incident took place on Delta flight DL466. The captain, whose first name was reported as Shane, had flown the same aircraft the day before and had logged a maintenance request for a potential issue with the elevator surfaces, which are crucial for controlling the plane's pitch. After a nine-hour inspection, maintenance teams were unable to find any mechanical problem and cleared the aircraft for flight.

However, the pilot, a veteran with over 25 years of experience flying the Boeing 757, was not satisfied. He explained to a passenger and then over the public address system that his "gut feeling" told him something was still wrong. He stated that while he trusted the maintenance team, his extensive experience led him to believe that a problem, even if hidden, still existed. He then announced that he was rejecting the aircraft, a decision he said he had not made in 22 years. The first officer also backed the decision, stating his last rejection was seven years ago.

The Results and Inconveniences
The captain's decision led to the immediate suspension of boarding and the deplaning of a few passengers who had already boarded. The passengers waiting at the gate reportedly applauded the captain's announcement, appreciating his transparency and prioritization of their safety.


A replacement Boeing 757-200 was dispatched to a nearby gate, and the flight departed approximately one hour and three minutes behind schedule. The passengers, despite the delay, were largely reassured and grateful for the pilot's actions. The incident highlighted the legal authority of a pilot-in-command, who has the final say on the safety of a flight, a responsibility protected under U.S. law. While the delay caused an inconvenience, the overall sentiment was that it was a small price to pay for the crew's commitment to ensuring a safe journey."
 
Last edited:
Interesting story of a 757 Captain who deadlined an aircraft as it was boarding, because his 25 years of experience as a 757 pilot told him something may still be wrong/ uncorrected, yet everything indicated no issue.

The issue was a concern over an elevator surface. This captain had flown this aircraft a day earlier. After the captain reported the problem, the maintenance crew spent nine hours looking for the problem, but no issue was found. The maintenance crew put the aircraft back into service/ signed off the aircraft was fit to fly.

The captain reported to have confidence in his maintenance crew, but regardless didn't have confidence the issue he reported the prior day was resolved. So the captain "deadlined" the aircraft, deboarded the passengers, and waited for a replacement aircraft to arrive.

More details from the event:
The incident took place on Delta flight DL466. The captain, whose first name was reported as Shane, had flown the same aircraft the day before and had logged a maintenance request for a potential issue with the elevator surfaces, which are crucial for controlling the plane's pitch. After a nine-hour inspection, maintenance teams were unable to find any mechanical problem and cleared the aircraft for flight.

However, the pilot, a veteran with over 25 years of experience flying the Boeing 757, was not satisfied. He explained to a passenger and then over the public address system that his "gut feeling" told him something was still wrong. He stated that while he trusted the maintenance team, his extensive experience led him to believe that a problem, even if hidden, still existed. He then announced that he was rejecting the aircraft, a decision he said he had not made in 22 years. The first officer also backed the decision, stating his last rejection was seven years ago.

The Results and Inconveniences
The captain's decision led to the immediate suspension of boarding and the deplaning of a few passengers who had already boarded. The passengers waiting at the gate reportedly applauded the captain's announcement, appreciating his transparency and prioritization of their safety.


A replacement Boeing 757-200 was dispatched to a nearby gate, and the flight departed approximately one hour and three minutes behind schedule. The passengers, despite the delay, were largely reassured and grateful for the pilot's actions. The incident highlighted the legal authority of a pilot-in-command, who has the final say on the safety of a flight, a responsibility protected under U.S. law. While the delay caused an inconvenience, the overall sentiment was that it was a small price to pay for the crew's commitment to ensuring a safe journey."
Anything come from follow-up inspections ?
 
Ultimately a pilot is responsible for their crew and passengers but I never saw where it said what the issue was or how it was resolved.
 
Since this "story" seems to originate from a reddit post and can only be found on other forums, I assume it's a fabrication.

If I spent 9 hours (how many man hours?) troubleshooting a problem based on a pilot's "feeling," (pilots have experience with how an aircraft "feels" to fly, fine) then pilot refused the aircraft without flying it because he didn't trust me, I'd want to clock him.
 
When I used to drive a truck and found it to be unsafe, it would be the union president that would make the final decision.
 
Since this "story" seems to originate from a reddit post and can only be found on other forums, I assume it's a fabrication.

If I spent 9 hours (how many man hours?) troubleshooting a problem based on a pilot's "feeling," (pilots have experience with how an aircraft "feels" to fly, fine) then pilot refused the aircraft without flying it because he didn't trust me, I'd want to clock him.
The difference is, and always has been, this - you’re not the one who is going to have a problem in flight. At 35,000 feet, with 200 people counting on you.

You say it’s good? Then, how about you take it flying. You assume the risk. You manage the airplane that has a flight control problem or engine problem.

I’ve been given an airplane many times with an assurance that, after hours of troubleshooting, the airplane is good.

And it wasn’t. And it became my problem in flight. In fairness, this was in the Navy. I haven’t had that experience at my airline.

But, when somebody says it will be fine, and you have to do a night carrier landing with a degraded airplane, the person who deserves the decking isn’t the pilot - it’s the maintenance guy who got it wrong and put my life and that airplane at risk.

Alaska Airlines 261 comes to mind when maintenance guys tell me the airplane is good - is it? Is it really? If I don’t like what I am hearing, or feeling, or even smelling, I have both the authority, and the responsibility, to refuse to fly that airplane.
 
Last edited:
The Captain is the full and final authority for the safe operation of the airplane.

In the execution of that authority, the Captain directs the actions of all other crew members, and may choose to deviate from any regulation or procedure if he deems it necessary for the safest course of action.
 
The story says it was this captain who experienced the control issues and wrote it up in the maintenance log. Had he just read it from another's entry, he'd probably think all was good.

Haven't there been recent crashes due to maintenance issues where the problem couldn't be reproduced, so the aircraft continued to fly... until it didn't?

Added: How many times are cars taken to dealerships for problems which the technician said they couldn't reproduce?
 
The difference is, and always has been, this - you’re not the one who is going to have a problem in flight. At 35,000 feet, with 200 people counting on you.

You say it’s good? Then, how about you take it flying. You assume the risk. You manage the airplane that has a flight control problem or engine problem.

I’ve been given an airplane many times with an assurance that, after hours of troubleshooting, the airplane is good.

And it wasn’t. And it became my problem in flight. In fairness, this was in the Navy. I haven’t had that experience at my airline.

But, when somebody says it will be fine, and you have to do a night carrier landing with a degraded airplane, the person who deserves the decking isn’t the pilot - it’s the maintenance guy who got it wrong and put my life and that airplane at risk.

Alaska Airlines 261 comes to mind when maintenance guys tell me the airplane is good - is it? Is it really? If I don’t like what I am hearing, or feeling, or even smelling, I have both the authority, and the responsibility, to refuse to fly that airplane.
Refusing an aircraft after a fault was written up, laboriously troubleshot, and returned to service because you're not happy With "NFF" as this "article" describes... Is usually an issue of pride. The pilot couldn't possibly be wrong.

Now, I don't work at an airline, I work in HEMS. And my first response when an issue is reported is usually "let's go fly it." I'm not risk averse. That's my helicopter. That's the medical crew's office. The pilot just steers it.

That said, I have had discrepancies that are inadequately described, discrepancies that are pilot error, discrepancies that are advisory messages written up as cautions "so maintenance will do something," and others.

And I have had pilots act indignant when the corrective action is entered, because they're the smartest, right?

So forgive me if I interpret this article differently, as I'm the person who gets called in at 3 AM because the "pedals feel weird" on take off because the pilot missed a step in both post and pre flight checklists.

I'm also the person who has had to drive 100 miles to clear an engine torque split because the pilot forgot that there was a trim switch.

We read "articles" like this differently. I still the "article" is a fabrication.
 
Refusing an aircraft after a fault was written up, laboriously troubleshot, and returned to service because you're not happy With "NFF" as this "article" describes... Is usually an issue of pride. The pilot couldn't possibly be wrong.

Now, I don't work at an airline, I work in HEMS. And my first response when an issue is reported is usually "let's go fly it." I'm not risk averse. That's my helicopter. That's the medical crew's office. The pilot just steers it.

That said, I have had discrepancies that are inadequately described, discrepancies that are pilot error, discrepancies that are advisory messages written up as cautions "so maintenance will do something," and others.

And I have had pilots act indignant when the corrective action is entered, because they're the smartest, right?

So forgive me if I interpret this article differently, as I'm the person who gets called in at 3 AM because the "pedals feel weird" on take off because the pilot missed a step in both post and pre flight checklists.

I'm also the person who has had to drive 100 miles to clear an engine torque split because the pilot forgot that there was a trim switch.

We read "articles" like this differently. I still the "article" is a fabrication.
There are several differences here.

First, while you object to the “pilot is always right” attitude, your whole post is about how “the mechanic is always right.”

Well, sometimes they’re not.

Next, you work in helicopter emergency medical services, a field of aviation that has an extraordinarily high crash rate.

Airlines on the other hand, have an extraordinarily low crash rate, so the perception of risk between the two disciplines, and the acceptable risk between the two disciplines could not be more different.

Next, you can get in the aircraft and go fly. That does not happen at Airlines. Mechanics don’t take the airplane flying to see if they can duplicate a gripe. They troubleshoot on the ground, and sign the aircraft off.

So, the airplane goes flying with a full load of passengers. It is “tested“ with hundreds of people on board.

It is a fundamentally different approach than the environment in which you operate, and it is a very, very different risk analysis.

And this story happened in an environment in which the mechanic takes zero risk.
 
Did this actually happen?
An educated guess would have to be that the aircraft was operated by Delta, since only Delta and United still operate the 757 passenger aircraft in the US and Astro would know about this were the airline United, and the departure airport would have to have been Atlanta, since where else would the airline just happen to have a spare 757 sitting around?
A quick search of "delta pilot refuses to fly 757" comes up with this having been Delta flight 466 to LAS on 8/16/25.
There were only social media sources cited though, nothing authoritative, which seemed odd.
 
Did this actually happen?
An educated guess would have to be that the aircraft was operated by Delta, since only Delta and United still operate the 757 passenger aircraft in the US and Astro would know about this were the airline United, and the departure airport would have to have been Atlanta, since where else would the airline just happen to have a spare 757 sitting around?
A quick search of "delta pilot refuses to fly 757" comes up with this having been Delta flight 466 to LAS on 8/16/25.
There were only social media sources cited though, nothing authoritative, which seemed odd.
Brilliant deduction Watson 🧐
DL466 was mentioned …

https://www.msn.com/en-us/travel/ne...tenance-log-saying-no-issue-found/ar-AA1KTcQ4
 
Back
Top Bottom