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 engine out inflight on 8/19

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
By the way does anyone suppose that FLOPS made the required NTSB 830 report? Things that make you go "Hmmmmmm......"


It really depends on the failure mode of the engine, but I don't believe they're required to make a report for an "ordinary" engine failure. Even if the engine grenaded due to compressor or turbine blade failure, it still doesn't meet the criteria for generating an immediate notification.
§ 830.5 Immediate notification


(3) Failure of structural components of a turbine engine excluding compressor and turbine blades and vanes;​


(7)(iii) Sustained loss of the power or thrust produced by two or more engines​
 
I find it sad that I have to find out about an engine failure on one of our aircraft on a public board, and not a word about the incident from the company.
 
I find it sad that I have to find out about an engine failure on one of our aircraft on a public board, and not a word about the incident from the company.


Sad...look at our present management....look at our worthless safety department. have we heard anything about the dual engine failures from the safety department? I've learned more from AIN than FLOPS. But we do have a "cookbook commitee".

ps. for those of you not at FLOPs , yes I said cookbook commitee
 
Amazing...

After the outstanding job the crew did in safely getting the BeechJunk on the ground, the lead pax was PO'd about being late for his meeting. Talk about misdirected priorities.

This event was finally acknowledged in a FLOP's inter-company communication yesterday 8-23-07.
 
After the outstanding job the crew did in safely getting the BeechJunk on the ground, the lead pax was PO'd about being late for his meeting. Talk about misdirected priorities.

This event was finally acknowledged in a FLOP's inter-company communication yesterday 8-23-07.


I think you got some bad info. Lead pax was a woman and definitely not going to a meeting. Don't think she was pissed off.
 
Thanks

for the correction. Still heard that someone in the party was miffed that they were going to be late for their meeting.
 

Latest resources

Back
Top