CACD Failure?!

[Conure]

Hey all,

 

Just did a standard startup and was parked on the ramp setting up my mission WP's when suddenly I get a CADC failure...Any idea what could cause that at a standstill??

 

Cheers

[RogueRunner]

Random failure generator, and no, AFAIK you cannot turn it off.

[luza]

if you left pitot heat on the ground on for too long...

[Kenan]

I get a CADC failure...Any idea what could cause that at a standstill??

 

Dear Sir,

 

That specific component you're inquiring about, is made in China and as such it is prone to breaking and malfunctioning. Please send us a serial number of your faulty CADC device, along with the device itself and we will send you the replacement parts as soon as possible.

 

Thank you,

 

Kenan Hou Chou

Chow Phow Industries & A10 parts Lmt. CEO

[Conure]

Random failure generator? Surely not..you'd expect these aircraft to be maintained, quite literally, with military precision...Surely my 14th hour of flight would not involve such an incident! Also, Pitot was off..I only switch it on just prior to take off and whilst taxing after landing! hmmm...

[Steel Jaw]

I get this as well at times but cannot figure it out.

[Speed]

I have random failures turned off in my missions and I still get random CADC failures. I can get them at 20,000 WITH MY PITOT HEAT ON. It makes absolutely no @#$#in sense. Another day, one guy in our squad was flying low, and for no reason at all, his HUD just died. It's like there is a random failure generator turned on, but I've never heard of one you can't turn off. Maybe there is a bug where you cannot turn off random failures?

[GGTharos]

This one you can't turn off. At least for now.

 

And yes, stuff fails that often. Each component has a % chance of failure modeled based on real component MBTFs.

 

That doesn't mean there isn't some sort of bug (random generator not being so random, % failure chance incorrectly calculated, etc).

 

Also realize that random failures are not counted in terms of YOUR flight time, but flight time of all these virtual components anywhere.

[Speed]

This one you can't turn off. At least for now.

 

And yes, stuff fails that often. Each component has a % chance of failure modeled based on real component MBTFs.

 

That doesn't mean there isn't some sort of bug (random generator not being so random, % failure chance incorrectly calculated, etc).

 

Also realize that random failures are not counted in terms of YOUR flight time, but flight time of all these virtual components anywhere.

 

Ok thanks for the info. This is the first I've heard of it.

[Smokin Hole]

In 20 years and 10000 + hours of flying modern jets with Air Data Computers just like those in the A-10, I have never had one fail. In the severest of icing I have never had a modern pitot system become blocked. I have only had the pitot system overheat once and that was in LAS in July when the FO mistakenly turned it on during the Recieving flow and not during the After Start flow (and it was easily reset once it cooled). In other words, in one month of flying this sim, I've experienced this failure enough for 20 lifetimes. Please fix it.

[EinsteinEP]

In 20 years and 10000 + hours of flying modern jets with Air Data Computers just like those in the A-10, I have never had one fail. In the severest of icing I have never had a modern pitot system become blocked. I have only had the pitot system overheat once and that was in LAS in July when the FO mistakenly turned it on during the Recieving flow and not during the After Start flow (and it was easily reset once it cooled). In other words, in one month of flying this sim, I've experienced this failure enough for 20 lifetimes. Please fix it.

In testing F16s at Edwards, we had relatively frequent FCC failures - maybe two or three over a 6 month period? It would be interesting to know what failure statistics are being modeled in the simulation - it sure seems a lot higher than I would expect.

[effte]

Agreed. When we see components fail as frequently as the A-10 CADC, we take the aircraft out of service and leave it in the shop until the underlying failure has been found.

[hog_driver111th]

Aircraft components can fail even on brand new aircraft. I was a ramp agent for a brand new 737 BBJ (Boeing Business Jet) from here in Berlin heading back stateside. It was on its Third flight, basically (only 3 days old). The passenger... Boeing's Vice President Mr. Bell. Anyway, the plane taxiied to the runway (07 at EDDB) and had a generator failure. Fortunately they were able to repair it, but Mr. Bell took a different flight out since the plane had to sit around for a day or two being fixed.... and this from a 3 day old airplane.

 

Granted, in a sim we should be able to turn that sort of stuff off... it's a pain to start a mission and the first time in the jet I get the CADC failure or something else not working.

[Buzpilot]

They use failure statistic for russian planes?

[andysim]

I had a CACD failure and a Hud fail within 2 hours of each other. Was not being shot at either. Failure rate seems to be a little high, but then im not a real hog pilot so who knows.

[RichardG]

MBTFs?

What is failure based on? Mean time?

[GGTharos]

MTBFs. :P Mean time between failures. Sorry, I typoed the acronym.

 

MBTFs?

What is failure based on? Mean time?

[MrYenko]

I'd bet a doughnut that your MTBF data is based on logbook entries or work cards for non-routine maintenance, and not on complete system failures, as are modeled in the sim... :joystick:

 

Just because the system is un-airworthy doesn't mean its completely ka-putt.

[GGTharos]

For the most part, the mode of failure for a system in a flight sim is kaput. ;)

[Speed]

You get four people flying for two hours, and you're pretty much guarenteed to see a random HUD or a CADC failure, at least in my experience. So... HUD or CADC MTBF = 4 aircraft* 2 hours* 2 instruments = 16 HOURS?! It would mean that on, say, a redeployment overseas flight, by the time all the A-10s would land, pretty much all would have had either a HUD failure, a CADC failure, or both. I call BS.

 

Each A-10 airframe has flown like what, an average of 7000 hours? We have like what, 350 of them? That means that if the failure rate ED simulates is accurate, then an average A-10 has required something on the order of 450 HUD and 450 CADC replacements EACH, and in total, something like 150,000 replacements of both the HUD and CADC each have had to be done on the A-10 fleet. If ED's numbers are accurate, then I'm going into the replacement-HUD making business. I think that obviously, these numbers cannot be correct. Does something SMALL go wrong with aircraft as often as once every few hours? I can believe THAT. Total loss of HUD or CADC? Bull$#@&.

 

I believe that either there is a bug causes these problems to crop up more often than they should, or the failure rate needs to be adjusted. In any case, we should be allowed to turn this feature off.

Edited March 11, 2011 by Speed

[MrYenko]

For the most part, the mode of failure for a system in a flight sim is kaput. ;)

 

I know, Im just saying that youre simulating the overall squawk rate with complete failures... Its a bit much. :P

[Smokin Hole]

In testing F16s at Edwards, we had relatively frequent FCC failures - maybe two or three over a 6 month period? It would be interesting to know what failure statistics are being modeled in the simulation - it sure seems a lot higher than I would expect.

 

I've had several of those. They are far more complex and prone to failure (or more likely, one FCC disagrees with the other and the two decide to call it a failure). As you know the ADC is much simpler and far more necessary for a safe operation. They just don't fail.

[OutOnTheOP]

Speed, who said anything about the failures being of the nature to require a complete replacement? They could be emulating software failures, equipment overheats, or any manner of other failure that prevents the system from operating but does not require the replacement of major end items.

 

However, that aside, I agree. It's damn excessive, and I have a hard time believing such a high overall failure rate.

[Speed]

Speed, who said anything about the failures being of the nature to require a complete replacement? They could be emulating software failures, equipment overheats, or any manner of other failure that prevents the system from operating but does not require the replacement of major end items.

No, but with 450 HUD failures, you're going to end up replacing everything a few times, at least :D

[OutOnTheOP]

either that, or replacing one widget a billion times. In which case, you'll need to buy stock in "Microdyne Widgets, Inc. 5 ohm resistor, type B" :megalol: