Turbulence Kills Pax on Private Challenger
03-04-2023, 09:11 PM
#1
Gets Weekends Off
Thread Starter
Joined APC: Dec 2017
Position: Retired NJA & AA
Posts: 1,918
Turbulence Kills Pax on Private Challenger
https://www.wfsb.com/2023/03/03/troo...adley-airport/
The Challenger 300 hit turbulence then diverted to BDL.
ADS-B data:
https://globe.adsbexchange.com/?icao...ace=2023-03-03
The Challenger 300 hit turbulence then diverted to BDL.
ADS-B data:
https://globe.adsbexchange.com/?icao...ace=2023-03-03
03-06-2023, 11:04 AM
#2
Gets Weekends Off
Joined APC: Oct 2021
Posts: 677
Now it is being reported that the crew mentioned something about a trim issue before they hit the "turbulence".
https://www.wmur.com/article/keene-n...-3623/43214810
"The National Transportation Safety Board revealed Monday that a "trim" issue was reported before the turbulence incident."
https://www.wmur.com/article/keene-n...-3623/43214810
"The National Transportation Safety Board revealed Monday that a "trim" issue was reported before the turbulence incident."
03-08-2023, 10:31 AM
#3
Gets Weekends Off
Joined APC: Feb 2010
Position: Bent Over
Posts: 225
Originally Posted by Pilot4000
Now it is being reported that the crew mentioned something about a trim issue before they hit the "turbulence".
https://www.wmur.com/article/keene-n...-3623/43214810
"The National Transportation Safety Board revealed Monday that a "trim" issue was reported before the turbulence incident."
https://www.wmur.com/article/keene-n...-3623/43214810
"The National Transportation Safety Board revealed Monday that a "trim" issue was reported before the turbulence incident."
03-08-2023, 01:59 PM
#5
Prime Minister/Moderator
Joined APC: Jan 2006
Position: Engines Turn Or People Swim
Posts: 39,273
Originally Posted by trip
I heard it was a laceration injury.
03-24-2023, 10:04 AM
#6
Gets Weekends Off
Thread Starter
Joined APC: Dec 2017
Position: Retired NJA & AA
Posts: 1,918
NTSB Update
https://apnews.com/article/private-p...a2af7bf95a3aec
-Pilots were responding to several warnings and disconnected a system used to stabilize the jet (stab trim). Th jet pitched abruptly upward when pilots turned off the stab trim switch while working thru procedures on a checklist. The jet violently oscillated up and down and the stick pusher activated.
-there was no turbulence
-pax died from blunt force injuries
Here's some interesting points about this flight:
-pilots aborted initial takeoff because no one removed a plastic cover from a pitot tube
-they took off with a rudder limiter fault alert on
-both pilots were experienced but both just got typed on the jet last October.
-Pilots were responding to several warnings and disconnected a system used to stabilize the jet (stab trim). Th jet pitched abruptly upward when pilots turned off the stab trim switch while working thru procedures on a checklist. The jet violently oscillated up and down and the stick pusher activated.
-there was no turbulence
-pax died from blunt force injuries
Here's some interesting points about this flight:
-pilots aborted initial takeoff because no one removed a plastic cover from a pitot tube
-they took off with a rudder limiter fault alert on
-both pilots were experienced but both just got typed on the jet last October.
03-24-2023, 12:43 PM
#7
Gets Weekends Off
Joined APC: May 2010
Position: Baja Vermont
Posts: 5,177
The crew ran the wrong checklist in response to the EICAS message AP STAB TRIM FAIL and AP HOLDING NOSE DOWN, they went to PRI STAB TRIM FAIL. They also departed with a RUDDER LIMITER FAULT, which is a NO-GO item in the Dispatch Guide. When the system posts anything like AP HOLDING….; time to get a grip on the yoke, think thru what it’s telling you BEFORE using the AP Disconnect. The PRI STAB TRIM FAIL started by switching off the Stab Trim, immediately disconnecting the AP. Oops, instant pitch oscillations.
03-24-2023, 08:45 PM
#8
Gets Weekends Off
Joined APC: Nov 2011
Position: Volleyball Player
Posts: 3,982
Originally Posted by galaxy flyer
The crew ran the wrong checklist in response to the EICAS message AP STAB TRIM FAIL and AP HOLDING NOSE DOWN, they went to PRI STAB TRIM FAIL. They also departed with a RUDDER LIMITER FAULT, which is a NO-GO item in the Dispatch Guide. When the system posts anything like AP HOLDING….; time to get a grip on the yoke, think thru what it’s telling you BEFORE using the AP Disconnect. The PRI STAB TRIM FAIL started by switching off the Stab Trim, immediately disconnecting the AP. Oops, instant pitch oscillations.
03-25-2023, 09:43 AM
#9
Gets Weekends Off
Joined APC: Dec 2022
Posts: 263
Really troubling reading through how much went wrong here. They were doomed from the start IMHO since they decided to go with the no-go item and a lack of preflight. Reading the wrong checklist could definitely happen to anyone, but should be caught early enough to prevent further issues.
These two were doofuses that were in over their heads and had no business flying an aircraft. They should be ashamed of themselves to be honest. I am hoping the FAA/NTSB takes action against them. For anyone thinking that is harsh, these two clowns were 100% responsible for the pax's death. Not to mention they make all of us look like fools.
These two were doofuses that were in over their heads and had no business flying an aircraft. They should be ashamed of themselves to be honest. I am hoping the FAA/NTSB takes action against them. For anyone thinking that is harsh, these two clowns were 100% responsible for the pax's death. Not to mention they make all of us look like fools.
03-25-2023, 10:39 AM
#10
Gets Weekends Off
Thread Starter
Joined APC: Dec 2017
Position: Retired NJA & AA
Posts: 1,918
Also it was a green/green pairing. The pilots had 88 and 78 hours in type. The Washington Post has a good article on this but it's probably behind a paywall. I'll summarize a few facts:
-rudder limiter fault. Two test to clear the message were unsuccessful. According to the Chief Pilot the pilots continued the flight because the message was advisory and not a caution or warning. (never mind it couldn't be MEL'd).
-during the 2nd takeoff speed bugs weren't set so the PM called out one from memory
-at 6000 feet a barrage of additional alerts emerged including AP Stab Trim Failure
-another caution indicated the AP was "Holding nose down"
-the pilots were employed by Executive Flight Services which also managed the jet.
Link to the article:
https://www.washingtonpost.com/trans...530100007F0D81
-rudder limiter fault. Two test to clear the message were unsuccessful. According to the Chief Pilot the pilots continued the flight because the message was advisory and not a caution or warning. (never mind it couldn't be MEL'd).
-during the 2nd takeoff speed bugs weren't set so the PM called out one from memory
-at 6000 feet a barrage of additional alerts emerged including AP Stab Trim Failure
-another caution indicated the AP was "Holding nose down"
-the pilots were employed by Executive Flight Services which also managed the jet.
Link to the article:
https://www.washingtonpost.com/trans...530100007F0D81
Thread
Thread Starter
Forum
Replies
Last Post
