Welcome to Flightinfo.com

  • Register now and join the discussion
  • Friendliest aviation Ccmmunity on the web
  • Modern site for PC's, Phones, Tablets - no 3rd party apps required
  • Ask questions, help others, promote aviation
  • Share the passion for aviation
  • Invite everyone to Flightinfo.com and let's have fun

FLOPS 2 400a Flameouts

  • Thread starter Thread starter pamed19
  • Start date Start date
  • Watchers Watchers 17

Welcome to Flightinfo.com

  • Register now and join the discussion
  • Modern secure site, no 3rd party apps required
  • Invite your friends
  • Share the passion of aviation
  • Friendliest aviation community on the web
Ok, there was no prist in the plane. So, has the actual ntsb report come out stating that the actual reason for the dual flameout was no prist? Why were the motors running just fine until they pulled the power back to start decent?? Did the ice just decide to form and at that very moment be released??? Why do they preach to jet drivers to not slam the power levers back at altitude?? I'm just suprised that the only problems with the beechjet having dual flameouts is Floptions!! All the military and all the corporate beechjets and not one has had a flameout with the final verdict from the ntsb being no prist!! There is another reason, but no prist isn't it. Netjets has had not one problem. JMHO!
 
Scary

pamed19 said:
Anything new on this ? Any reports on a cause?.I fly as a FLOPS passenger on the 400a and the incidents worry me.

Suggestion: Sell your share in the 400A and buy a Sovereign.

QUICK!

You will not regret it.
 
My two Beechjet Stories

Both of these incidents happened in RK330

#1 – Filled up at LWM, and then headed for the west coast. The fuel truck that filled us up had a prist injector pump that needed to be primed, so it wasn’t pumping any prist. I found out about this when I got back from my west coast trip. We were about 5 minutes from our TOD, going to FAR for fuel, when the left fuel filter bypass light came on. I confirmed that the filter was bypassing by pulling back the power lever slightly, which made the light go out. Pushing the lever forward made the light come back on. The light stayed on at progressively lower power settings, and it was on at idle by the time we landed in FAR. The engines ran fine without incident. The mechanics in FAR were on lunch break, so there was about an hour delay before the fuselage filters were removed. They both looked like new. I think that the ice crystals that had blocked the filter had melted and “re-entrained” into the jetfuel. There was no water or sediment in the bottom of either filter bowl. We replaced both filters, and had no further issues. After that incident, I became better about monitoring the fuel truck, and ensuring that Prist is really being pumped.

#2 – Flying from FMY to BED, in the clouds most of the way because of T-storm activity along the east coast. We started our descent over NYC, and got a yellow A/S miss-compare light after a few hundred feet. I checked the two PFD’s and found a 40kt difference. Let me back up and say that this incident occurred after Raytheon’s loss of airspeed AD, which requires a flight manual supplement, and adds the memory items to the checklist. However, at the time of my incident, (or was it an occurrence?), Flight Safety was not teaching “loss of airspeed” and had no reference to it in any of their manuals or checklists. So anyway… back to my story – There we were, over NYC, IMC, moderate turbulence when the Pilots PFD went black. To be totally accurate, it wasn’t all black, it had a bunch of cool looking red X’s all over it! No, it wasn’t just the airspeed and altitude that went black, it was everything; no attitude, heading, airspeed or altitude. After the requisite “OH ********************”, I began to search for something to turn on to solve this dilemma. The only thing I came up with was the engine, wing and hstab heat, so I turned them all on. Just about that time, the airplane started a moderate dutch roll, and the hstab fail light came on. Now I’m really scratching my head trying to figure out what the heck is going on with the airplane. Then the radar shut down, which wouldn’t have been a big deal except we were using it to pick our way around some level 4 and 5 T-Storms. I thought that the PF may have kicked the yaw damper off when he disengaged the A/P, but I checked it three times, and the switch was on. So I declared an emergency, got some vectors, and we kept on going down. The right side PFD never went black, but the data it was displaying was definitely not reliable. So we were left to descend with the peanut attitude and altitude. The peanut A/S was on 0. As we descended through the low 30’s, things started coming back online, and by the time we were down to 25K, everything was back to normal. In case your wondering, the ADC has an output to the AHRS computer, the YD computer, the Hstab heat computer and the radar. All of those systems will probably be affected during “loss of airspeed”.

So now to the relevant point of this long rant. I was recently at SimuFlite DAL for recurrent, and told this story. There was a FLOPS pilot there who had a very similar experience. The only additional thing he experienced was a “loud bang” from the rear of the aircraft near the top of the descent. He didn’t have any engine issues, and maintenance never found anything wrong with the airplane.

Then I was reading the NTSB prelim report of the second “dual flameout”:
http://www.ntsb.gov/ntsb/brief.asp?ev_id=20060104X00004&key=1
and noticed that the pilots said:

“The pilots reported that after completing the checklists after the engines lost power, they noted that the standby air speed indicator had gone to zero until the airplane had descended through FL 330 where it resumed indicating an airspeed.”

I believe that the only way for the standby airspeed to go to zero is for the right side pitot tube to be clogged/frozen.

So is it possible that there might be a connection between “loss of airspeed” and “dual flameout”? Does any part of the engine get any input from the ADC?

Could frozen pitots be causing engine flameouts? My guess is probably not, but its at least as plausible as methane gas! J
 
Choppy said:
Ok, there was no prist in the plane. So, has the actual ntsb report come out stating that the actual reason for the dual flameout was no prist? Why were the motors running just fine until they pulled the power back to start decent?? Did the ice just decide to form and at that very moment be released??? Why do they preach to jet drivers to not slam the power levers back at altitude?? I'm just suprised that the only problems with the beechjet having dual flameouts is Floptions!! All the military and all the corporate beechjets and not one has had a flameout with the final verdict from the ntsb being no prist!! There is another reason, but no prist isn't it. Netjets has had not one problem. JMHO!

So...why don't you tell us your theory, oh enlightened one... By the way....Netjets has not been operating the Beechjet nearly as long as Options, nor do they have nearly as many of them...therefore, they have not flown anywhere near as many hours.

I have no idea what caused either dual flameout. I can speculate, but I'm not that much of an idiot to think that I can determine the cause without knowing all pertinent information...but, apparently, you feel you can...so enlighten us.
 
Dear Worried Passenger,

pamed19 said:
I certainly will not correct you.I am just a worried passenger!What can I do to make sure the sumping has been done?many thanks

By all means ask the crew if they have drained the sumps and if they checked to see if the fuel had Prist injected! Ask them to show you the prist meter in the cockpit, too. If they pretend they don't know, insist!

Then ask them how many hours they have, and how much experience in the Beechjet. Crews love to talk about how many flying hours they have!

But if you really want to get scared, ask them how long they have been on duty. Or when the last time they had a meal, or a good night's sleep. And be sure to ask how many MEL's are on the plane.

;)
 
Last edited:
What I heard last week while talking to a FLTOPS crew:

Prist was not an issue on the first one, although commonly reported as such.
Second one was not a prist issue either. They said Raytheon believes it is a stator icing issue (no stator AI on the Beechjet) disturbing airflow into the LP compressor and thus the flameouts. By the way, I guess the guys on the second dual-flamout dead-sticked it into JAX with peanut gyro only and a 1000' ceiling and only blew one main gear tire. Nice job guys. By the way, sometime after landing the engines were restarted with no problems.
 
Coool Hand Luke said:
What I heard last week while talking to a FLTOPS crew:

Prist was not an issue on the first one, although commonly reported as such.
Second one was not a prist issue either. They said Raytheon believes it is a stator icing issue (no stator AI on the Beechjet) disturbing airflow into the LP compressor and thus the flameouts. By the way, I guess the guys on the second dual-flamout dead-sticked it into JAX with peanut gyro only and a 1000' ceiling and only blew one main gear tire. Nice job guys. By the way, sometime after landing the engines were restarted with no problems.
I would be happy to fly with both sets of pilots anytime.I do believe my heart would not have kept going after what they went through.Many thanks to all for their comments.
 
The Truth

Coool Hand Luke said:
What I heard last week while talking to a FLTOPS crew:

Prist was not an issue on the first one, although commonly reported as such.
Second one was not a prist issue either. They said Raytheon believes it is a stator icing issue (no stator AI on the Beechjet) disturbing airflow into the LP compressor and thus the flameouts. By the way, I guess the guys on the second dual-flamout dead-sticked it into JAX with peanut gyro only and a 1000' ceiling and only blew one main gear tire. Nice job guys. By the way, sometime after landing the engines were restarted with no problems.
Yes, this is what I heard from talking to the pilot that was flying. If it was due to prist/ lack of sumping, etc, there would be jets flaming out all over the place. How many corporate/charter guys do you see out draining their jets' sumps every morning? You guys can say whatever you wish but I've been flying jets for a while at multiple companies and it just is not done by crews.

And Pamed19... No offense, but if you feel like you have to double check your flight crews' preflight then you need to be flying somewhere else. Like somebody said, you should be worried more about their duty day, how much they had to rush to pick you up on time, how they have to rush your flight to get to the next one on time, proper feeding, etc, etc, etc...

HS
 
Last edited:
FracCapt said:
So...why don't you tell us your theory, oh enlightened one... By the way....Netjets has not been operating the Beechjet nearly as long as Options, nor do they have nearly as many of them...therefore, they have not flown anywhere near as many hours.

I have no idea what caused either dual flameout. I can speculate, but I'm not that much of an idiot to think that I can determine the cause without knowing all pertinent information...but, apparently, you feel you can...so enlighten us.

Well, now you get a couple of other people that have talked to the pilots and they have said also that it was not prist! The reason that I am wound up about this is because Raytheon doesn't want to face reality that they might have a problem. They just want to blame it on the pilots about the prist issue. They have sold hundreds of beechs to forgein countries and not one has flamed out. Yes, flops flys alot but just try and firgure out how many hours this airplane has on it and you have to go all the way back to the diamond. I just don't buy the prist issue, that's all! As I said before, there is something really strange about it only happening to Floptions. I know a lot of operators that put 500 to 650 hours on the beechs a year so don't start with the "They fly more than anyone else" theory!
 
Last edited:
Choppy said:
Well, now you get a couple of other people that have talked to the pilots and they have said also that it was not prist! The reason that I am wound up about this is because Raytheon doesn't want to face reality that they might have a problem. They just want to blame it on the pilots about the prist issue. They have sold hundreds of beechs to forgein countries and not one has flamed out. Yes, flops flys alot but just try and firgure out how many hours this airplane has on it and you have to go all the way back to the diamond. I just don't buy the prist issue, that's all! As I said before, there is something really strange about it only happening to Floptions. I know a lot of operators that put 500 to 650 hours on the beechs a year so don't start with the "They fly more than anyone else" theory!

I am wondering who else besides FLIOPS has experienced the flameouts ??? I have only heard of the Flight Options ones. I just think it is sort of odd that it has happened to on operator twice. Sure they put a lot of hours on the ones they have, but it still seems strange to me.
 
Choppy said:
As I said before, there is something really strange about it only happening to Floptions. I know a lot of operators that put 500 to 650 hours on the beechs a year so don't start with the "They fly more than anyone else" theory!

I'll say it again....enlighten us with YOUR theory on what's happening. You indicate that it's something that Options crews are doing wrong...what would that be?

As for the 500-650 hours per year thing....all I was getting at is that when you compare a flight department that puts 500-650 hours a year on a Beechjet, as opposed to a company that puts 50,000+ hours per year on many Beechjets....who do you think is bound to have more issues?
 
Other dual flameouts

I have read that a 400a had the same problem in Brazil and a CitationII with the same engines did the same thing last summer in Alaska.
 
FracCapt said:
I'll say it again....enlighten us with YOUR theory on what's happening. You indicate that it's something that Options crews are doing wrong...what would that be?

As for the 500-650 hours per year thing....all I was getting at is that when you compare a flight department that puts 500-650 hours a year on a Beechjet, as opposed to a company that puts 50,000+ hours per year on many Beechjets....who do you think is bound to have more issues?

Well, it is obvious who you work for! I haven't had any theories but you seem to think that I have all the answers! That's why there are question marks at the end of my lines??? All I was doing was stating the obvious... All aircraft were beechjets, not the only ones with jt15D's and it was the same company.. Floptions. Does that p#ss you off that I can state the facts and you or your company can't debate it??? Does it P#ss you off that your company is going down the tubes and you can't get union on board??

I was not going to attack you personally but you brought me in here stating that I have all the answers... maybe you are closer to the company and can tell us what you company's NEW procedure is for TOD??? It's a doozie!!
 

Latest resources

Back
Top Bottom