Ah, then there's a fundamental misunderstanding of what the mission is. Yes, the point is to deliver the people and do so reasonably on time, but the overwhelming mission is "don't kill anyone."
I do whut I wont when I wont… DAMN!
Ah, then there's a fundamental misunderstanding of what the mission is. Yes, the point is to deliver the people and do so reasonably on time, but the overwhelming mission is "don't kill anyone."
Yeah. I think it's easy to get in a "gotta get on the ground" mindset. In their case, that's exactly what happened.
Newton and Bernoulli say, in unison, "Here son, let me help you with that" *WHAP!*
Ah, then there's a fundamental misunderstanding of what the mission is. Yes, the point is to deliver the people and do so reasonably on time, but the overwhelming mission is "don't kill anyone."
Short of being on fire or out of gas, there are very few situations that are helped by a hurried approach and landing.Yeah. I think it's easy to get in a "gotta get on the ground" mindset. In their case, that's exactly what happened.
Short of being on fire or out of gas, there are very few situations that are helped by a hurried approach and landing.
No, sir, of course.No argument from me there man. I'm not defending their decisions.
No argument from me there man. I'm not defending their decisions.
No, sir, of course.
Y'know, before we let any- and everyone on The Internettes, this was the norm, not the exception. Acrimony is, to me, a relatively new phenomenon.What? Understanding on the internet!?
One of you must VANQUISH the other.
View attachment 30489
FINISH HIM!
What? Understanding on the internet!?
One of you must VANQUISH the other.
View attachment 30489
FINISH HIM!
In my limited experience:True, though at my last company there are plenty of examples where metal was bent, and the crew was retrained, even with some very poor judgement.
The CHA windshear event comes to mind. Crew elected to continue in the face of a microburst with tower issuing multiple microburst alerts, in addition to a HUGE storm crossing the field. They got a massive wind shear at 30 feet, pusher, left wing stalled and contacted the runway. The only reason they didn't roll inverted and crash was the wind shear was so low that the runway "caught" them.
This was a case where you could say they were negligent. They made a bad decision, and continued in the face of red flags. But when you talked to the crew, they were so mission focused that they allowed themselves to get into a situation where they believed it was too late to go-around because the storm was "right there" and so big they thought it was safer to land than to go-around.
I guess my point with that example is that it's rarely just "cut and dry." They made some bad choices, and arguably the wrong choices at every single point, but they intended to do the right thing. They just effed it up. Repeatedly. So they were given some heavy retraining, and put on back to the line.
Their attitude factored heavily into the decision. They were shocked at the outcome and that it could happen to them. They thought they had made the best decisions possible "in the heat of the moment." They were open to retraining.
To be honest, I'm just tired of hearing all the ride report requests while I'm sitting at FL450 drinking my Dr. Pepper. I'm not do bothered with such nonsense.![]()
Ahhh....the fun of never having to talk to or listen to an ARTCC anymore, ever.![]()
Are you guys allowed to use max auto braking when landing? We are not...medium only.We get a lot of updates that are not all that useful, this one is. It's max auto-brake setting Ref+5 data for all Airbus at those two airports with "Fair Braking" reported. One quick look at the graph gives you an idea if you are good to go or not.
Safety, accomplished through regulatory fiat and a stroke of the Vice President Flight Operations or System Chief Pilot's pen, and then distributed through the series of tubes!Via the miracle of cyberspace and an ipad my company has issued new information on runway landing distances for "fair braking" at DCA and LGA. This revision was dated Feb 15 and is included in the airport advisory pages.
An interesting note for the A321 is a very large blacked out area of the chart for higher weights and also noticeably absent was any data for "poor" or lower braking for LGA and DCA for any aircraft. That means if it's below fair you don't land or takeoff.
We get a lot of updates that are not all that useful, this one is. It's max auto-brake setting Ref+5 data for all Airbus at those two airports with "Fair Braking" reported. One quick look at the graph gives you an idea if you are good to go or not. There is a 15% buffer built in. This is a good tool, a lot of charts are not user friendly but this one is.
In my limited experience:
Regional/Commuter - micromanaged on the day to day operation, however very lenient if you screw the pooch (like your example).
Major/Mainline - completely left alone by management, no second guessing, until you screw the pooch like your example. Then they don't mess around, and just fire you.
Both however are big on negligence, in other words if you intentionally disregard procedure etc. and it gets you in trouble, you're smoked. At a commuter it's time off without pay, at a major it's your job.
IMO, while I don't know the entire story of your example, I would've expected the company to fire those two guys up front making those bad decisions. There are numerous FOM violations in that story which bothers me. It shouldn't take a near death experience to "come to Jesus" and learn you shouldn't land in a thunderstorm with microburst warnings...(is that too harsh?).
Ahhhhhh, WHAT???
First, in my experience, while some regionals are great safety cultures, not many were until the Colgan Accident.
Majors/Mainlines (and I've been at two) have fantastic safety cultures and are really open to retraining a variety of incidents. I'm really surprised you would say something like that from where you are at. I thought they had a great safety culture.
Furthermore, just because you have multiple FOM violations doesn't mean you fire the crew. So yes, you are being to harsh.
True, though at my last company there are plenty of examples where metal was bent, and the crew was retrained, even with some very poor judgement.
The CHA windshear event comes to mind. Crew elected to continue in the face of a microburst with tower issuing multiple microburst alerts, in addition to a HUGE storm crossing the field. They got a massive wind shear at 30 feet, pusher, left wing stalled and contacted the runway. The only reason they didn't roll inverted and crash was the wind shear was so low that the runway "caught" them.
This was a case where you could say they were negligent. They made a bad decision, and continued in the face of red flags. But when you talked to the crew, they were so mission focused that they allowed themselves to get into a situation where they believed it was too late to go-around because the storm was "right there" and so big they thought it was safer to land than to go-around.
I guess my point with that example is that it's rarely just "cut and dry." They made some bad choices, and arguably the wrong choices at every single point, but they intended to do the right thing. They just effed it up. Repeatedly. So they were given some heavy retraining, and put on back to the line.
Their attitude factored heavily into the decision. They were shocked at the outcome and that it could happen to them. They thought they had made the best decisions possible "in the heat of the moment." They were open to retraining.