Forums59
Topics1,038,937
Posts13,955,833
Members144,183
|
Most Online39,925 Dec 30th, 2023
|
|
Houston Amazon 767 Crash 23 Feb 19
#13123493
04/14/19 10:44 PM
|
Joined: Jun 2005
Posts: 44,554
a777pilot
OP
TFF Guru
|
OP
TFF Guru
Joined: Jun 2005
Posts: 44,554 |
Subject: Houston Amazon 767 Crash 23 Feb 19
From the net, courtesy of a reliable source.
Just FYI weve heard the full cockpit audio and seen the data. Heres... what really happened (name redacted to protect the innocent!):
During the approach, at about 6,000 FT (being flown by the first officer), the Captain reached around the throttle quadrant to extend the flaps to the next position after being called to do so by the first officer (pilot flying) very normal.
In many aircraft including the 767, thats a very odd/difficult repositioning of your hand (from the left seat, all the way around to the right side of the center console), and requires intimate familiarity and slow deliberate motion to do successfully.
Well in any case, it was not done so this time. The captain accidently hit the go around switch while bringing his hand around for the flaps, which brought both engines up to full power. In the landing configuration, as this aircraft was transitioning into, that obviously causes a vast increase in lift and the first officer (pilot flying) used everything he had to force the nose back down. Still not sure why that occurred, as the crew should have just gone around and tried it again when properly configured but they did not. And that started in motion a chain of events that lead to tragedy.
As the First Officer over-rotated downward, again with the engines at full power, the aircraft quickly accelerated and approached something were all trained to handle (at least in good training environments) an upset recovery, countered by NON-AUTOMATION and basic stick and rudder skills.
This captain however, in turn, grabbed the controls without using positive command (Ive got, My aircraft, or anything normally done), and countered the F/Os control input by completely hauling his control column full aft remember, while the F/O is pushing full forward.
In the process of doing that, he broke the shear pin on his control column (a device/mechanical safety interlock used to separate a control column from the innards of the control architecture in the event one control column is doing something it should not) and that occurred here.
The captain, a few seconds later, now accelerating downward out of the control envelope of the 767 (remember, all of this started at 6000 FT and probably took less time to get to the fatal point than it did to read this far), recognizes the has no control column and then asks the F/O to pull up, get the nose up, or something to that affect. It isnt 100% clear what he says. The F/O then tries to pull aft on his column (going from full forward to full aft), but isnt getting the response he needs, because the aircraft is out of the envelope of controllability and the controls are air-loaded in position.
At about 2000 FT, eventually the trim motors are able to start overcoming the air-load, and the aircraft begins to attempt to arrest its rate of descent but alas its far too little, far too late, and the aircraft impacts about 30-40 degrees nose down, with what is believed to be about 4-5000 FT / minute rate of descent.
All during this time the throttles arent touched until somewhere during that last few seconds of flight which is believed to be what enabled the trim motors to start working. Unclear who does it, and no audio indicates who it was.
Just FYI weve attempted in our 767 simulators to recover from the event with the exact same setup, and thus far weve only had success when starting at 8000 or higher meaning we are fully established in the out of control position at 8000, recognize it by then, and initiate recovery starting at 8000.
These guys started the whole thing at 6000 and were much lower when a true recovery attempt was initiated. No chance, and just shows you how quickly you can get out of the envelope when you dont follow procedure, try some completely erroneous recovery technique, and dont have a clue what youre doing.
So many things went wrong with crew coordination, basic flying skills, aircraft envelope awareness, basic procedures, and such that this will likely go down as one of the absolute worst pilot error events ever.
It needs to have serious impact throughout the Amazon flying circus (and associated partnerships), and show people that Jeff Bezos attempt to push the envelope at lower cost, all things else be damned, doesnt apply to aviation.
This accident no doubt was absolutely horrible, and three people lost their livesone of them (the jumpseater) through absolutely no fault of his own. But making an approach into Houston, TX, it could have been so much worse. In another few miles, they would have been over major population centers and who knows what would have happened then.
Know your aircraft. Know your procedures. And for God sakes, just FLY! Its not a video game!
Relayed by your PJP Editor Bert Botta Aviation Writer PJPFBO Editor Email: bert@privatejetpilots
Last edited by a777pilot; 04/14/19 10:44 PM.
Look! Up in the sky. It's a bird. It's a plane. No, it's an EMP!
|
|
Re: Houston Amazon 767 Crash 23 Feb 19
[Re: a777pilot]
#13123497
04/14/19 10:49 PM
|
Joined: Jun 2005
Posts: 44,554
a777pilot
OP
TFF Guru
|
OP
TFF Guru
Joined: Jun 2005
Posts: 44,554 |
Un-f.......-believable!
I have alway taught, when the system is not doing what you expect....auto pilot, OFF, auto throttles, OFF. FLY the aircraft!
What these two did is what I would expect of third world trained pilots.
Look! Up in the sky. It's a bird. It's a plane. No, it's an EMP!
|
|
Re: Houston Amazon 767 Crash 23 Feb 19
[Re: a777pilot]
#13123504
04/14/19 11:01 PM
|
Joined: Oct 2004
Posts: 16,903
SheldonS
TFF Guru
|
TFF Guru
Joined: Oct 2004
Posts: 16,903 |
Ill wait for the NTSB report but this was interesting.
|
|
Re: Houston Amazon 767 Crash 23 Feb 19
[Re: SheldonS]
#13123527
04/14/19 11:28 PM
|
Joined: Mar 2014
Posts: 29,828
Duck_Hunter
TFF Guru
|
TFF Guru
Joined: Mar 2014
Posts: 29,828 |
Ill wait for the NTSB report but this was interesting.
|
|
Re: Houston Amazon 767 Crash 23 Feb 19
[Re: a777pilot]
#13123582
04/15/19 12:32 AM
|
Joined: Jan 2003
Posts: 83,274
Pilothawk
Pumpkin Head
|
Pumpkin Head
Joined: Jan 2003
Posts: 83,274 |
So many opportunities to avoid tragedy missed.
At 6000 the aircraft is 20 miles plus from touchdown. Probably using flaps to slow. I have seen hundreds of approaches...inadvertently hitting the TOGA switches...no.
Both pilots should have acknowledged the FMA change. G/A...
When the power came in...the nose came up....approach profile is way wrong (if not before).
I HAVE THE AIRCRAFT. Capt is making hundreds of thousands to be a pilot....fly the damned airplane.
I cannot tell you how many times I have told pilots....when the world is turning brown and smelling nasty. Set the thrust to 70%, pitch to 4 degrees and airspeed to 230. Breathe.., breathe again, then take appropriate action.
Here is the untold story....left to its own devices...the 767 would have flown away from planet earth at a considerable rate.
KANSAS JAYHAWK BASKETBALL - Where tradition comes from 2008 NATIONAL BASKETBALL CHAMPIONS-ORANGE BOWL CHAMPIONS 2008 52 Conf Champs /5 Nat'l Champs
|
|
Re: Houston Amazon 767 Crash 23 Feb 19
[Re: a777pilot]
#13123632
04/15/19 01:11 AM
|
Joined: Feb 2004
Posts: 5,549
206champion
TFF Celebrity
|
TFF Celebrity
Joined: Feb 2004
Posts: 5,549 |
Wow I wandered what happened, I have worked on the 767 years ago.
|
|
Re: Houston Amazon 767 Crash 23 Feb 19
[Re: a777pilot]
#13123681
04/15/19 02:03 AM
|
Joined: Apr 2008
Posts: 12,332
PaulGrapevine
TFF Guru
|
TFF Guru
Joined: Apr 2008
Posts: 12,332 |
Im not a pilot but this sounds crazy. Will be curious to find out how much experience the pilots had.
|
|
Re: Houston Amazon 767 Crash 23 Feb 19
[Re: a777pilot]
#13123707
04/15/19 02:25 AM
|
Joined: Dec 2011
Posts: 8,966
H.Town_paddler
TFF Celebrity
|
TFF Celebrity
Joined: Dec 2011
Posts: 8,966 |
Thanks for the explanation. I have been told planes do not crash bc of one big problem. They crash bc of a series of really small problems.
|
|
Moderated by banker-always fishing, chickenman, Derek 🐝, Duck_Hunter, Fish Killer, J-2, Jacob, Jons3825, JustWingem, Nocona Brian, Toon-Troller, Uncle Zeek, Weekender1
|