denverpilot
Tied Down
There are plenty of new ground link products with individual keys per aircraft outside of Military.
Nifty. Good to hear.
[edit: People are apparently learning.]
There are plenty of new ground link products with individual keys per aircraft outside of Military.
If done right....the system should be fault tolerant....and continue with the last data upload.They're also ignoring how many times their computer blew up from bad code. LOL. A common mistake in computing and automation.
Meh.....they'll get that figured out. The military did....with TCDL.Not only that but you have an encryption and repudiation issue. You're going to need a really secure data channel to pull off the ground command thing.
Or we can be stupid and start with unencrypted, spoofable links. And learn that lesson the hard way.
Care to enumerate these failure modes? If you can so easily identify them, could you not just as easily come up with solutions? Why is flying an airplane from point to point too complicated for a computer to accomplish?
In the case of AF477, the pilots were in control and crashed. How could the computer do any worse? In that case, people say that nobody was flying the airplane. Could this not be a case where the computer steps in and flies the airplane when no one else is?
I was suggesting a symbiotic relationship. If the computer is screwing up due to software glitch, or bad data from a sensor, such as a pitot tube, the pilots would have the authority to identify, over ride and correct this problem. In addition, my proposal was to leave cockpit management and authority just as it is now with humans in control.
The HAL 9000 only takes over when it can identify stupid pilot behavior, like directing the airplane to fly into the ground, or using the controls to enter a spin, or flying over the ocean and pushing the button to dump fuel. It could also assist when the pilots are busy on their lap tops and fly 100 miles past their airport, or the pilots are making a terrible approach to an airport.
I'm sure I could be completely wrong and such a system will never be built due to the complexities and potential dangers, but I doubt it. If I thought of it, that means there are people already working on it.
AF447 was initiated by an instrumentation failure. The automation failed and the crew was not smart enough to compensate.
All automatic systems can suffer input problems. And hell no, I won't enumerate them all. That is EXACTLY the problem. Leave one out and everybody dies.
You're obviously not a systems engineer, as you don't seem to realize you've asked me to do several months of analysis for you. And Systems Engineering Question #1 is ALWAYS "Is this worth doing?" In this case it's obviously a very complex and risky solution to an exceedingly rare problem.
One failure mode is that the pitot tubes ice, so the computer thinks the pilot is trying to rip the wings off. Another is an emergency descent. What about disabled systems? Is it suicide to disable safety equipment because, say, it might be smoking or malfunctioning?
Truly half baked idea. I'm finding it hard to believe you're serious. You didn't post it on April 1,
...and it's already happening.No worries.....this will be a slow transition.
The NASA SPO project? We've been working on it in our office, too. You should read some on it. Not quite ground command for what we're working with, but more of the super dispatcher position.
The automatic ejection system in the Yak-141 It doesn't (didn't) just remove authority, it removed the pilot.So, nauga, which of these systems operating now REMOVE authority from pilots without possibility of override...
Interesting. Do you know of any published information on the project? I'd be curious to read it.Totally separate , was born in the 747-8 program and initiated somewhat by Boeing , more of a tech upgrade for avionics
How 'bout flight termination systems?So....is it time to start talking data-bus architecture and primary and secondary data links?
If done right....the system should be fault tolerant....and continue with the last data upload.
It's wildly premature to talk about architectures when you don't even have a sensible and complete use case. Agile techniques are not at all appropriate to safety critical systems.
If the use case is wildly stupid -- and it is in this case -- even the best architecture in existence will still produce a stupid system.
You gotta figure out what you're doing before figuring out how.
are we ready to go to fly by wire systems?....or are we still talking about cables and hydraulic assist?
FBWs are here, but it is debatable whether the added complexity really is such a great idea. But that has little to do with anything at hand.
Oh, quite contrare.....FBW systems are completely digital and ripe for datalink integration.
In fact the newer systems are all setup.....and almost ready to go.
Remote control with passengers may be possible or even easy, but it's still a stupid idea.
It's a huge engineering mistake to confuse ease with sensibility. You're skipping the first, most important, step.
This is one of those cases where you can work out the nominal behaviors easily. Nominal behaviors seldom kill. It's the off nominals where the problem lies. Good luck enumerating them.
And, just what problem are you trying to solve? One lone nutcase in 20 years? Nut cases can be on the ground, too, and with more critical pieces, they have more opportunities, and a much larger physical security problem.
Self driving cars are going to be awesome. You can leave instructions in your Will that the car will be programmed to go all the places you never got a chance to go when alive, and that until your money runs out, it'll pay for someone to arrange to have your car programmed to go to all those places and be refueled along the way, so the dead you can ride around, see the sights, and decompose the car.
Hahahaha.
Okay not as unlikely: we will see news reports of a self diving car or fully automated aircraft showing up somewhere with a dead guy in it.
They'll probably then require that the aircraft or car check our pulse through our asses or something and re-route to the closest emergency services location if we have croaked so cars and airplanes don't show up at loved one's houses with dead relatives in them or airports in equipped to handle a dead guy.
Heh. Twisted ain't it?
Rotor dude was right. This is a troll thread....
Who starts a thread and never comes back?
Brien started this one and the little ***** hasn't been back since. Troll fvcker.
I don't necessarily have a problem with it if there's a human who can take over. It could be a one pilot crew and he could just nap or read a book on the flight over but I think you'd need that before anyone would be ok with it.
Certification of flight critical software *requires* such consideration.too often people don't consider the new failure modes caused by technical solutions intended to address old failure modes.
I don't see a problem. People are obviously interested in the topic, and as far as I know, participation in the thread is voluntary.
Yep right on, there always are the little people who think badly of others, little people little minds, who judge other by them selves.
And there are people who let other people spit all over them and say 'thank you, may I have another?'
Be honest. Have you ever STARTED a thread and just abandoned it?
That's funny, I've checked all over myself, and I can't find any spit anywhere.
Why do you equate that with being spat on?
Basically, I just can't think of any reason to care what other people's reasons are for starting threads, and even less reason to care what other people think others' reasons are. I have no emotional investment whatsoever in whether a person who starts a thread participates in the discussion. The ONLY thing I care about when I look at a thread is whether there is an interesting discussion going on.
That's cool, but rotor dude pointed out don't feed the troll and I watched and waited and here we are eight pages later and the OP hasn't been back since... don't you find that a tad bit strange?
I'll ask you to be honest too. Have you ever started a thread and never looked at it again?
I could care less, automation is a hot topic obviously. I was just pointing out the queerness of starting a thread and then vanishing. I hope the dude isn't dead or worse ... .
No, but why does it matter?
Seems odd to me ..
Probably not, but we don't know whether he has looked at the thread again or not, and I still can't think of a reason to care.
Good for you.
Since you've switched from calling him names to being concerned for his well being, I can ease your mind on that point. If you check the statistics section of his user profile, you will see that he has accessed the forum as recently as this afternoon.
Be honest. Have you ever STARTED a thread and just abandoned it?
AF447 was initiated by an instrumentation failure. The automation failed and the crew was not smart enough to compensate.
All automatic systems can suffer input problems. And hell no, I won't enumerate them all. That is EXACTLY the problem. Leave one out and everybody dies.
And you're obviously not an engineer. You sound more like a corporate numbers cruncher. An engineer is tasked with , or identifies a problem and then creates a solution. They don't just give you 85 reason's not to even try. If it were up to you, the "systems engineer", the powered airplane as we know it, would never have flown.You're obviously not a systems engineer, as you don't seem to realize you've asked me to do several months of analysis for you. And Systems Engineering Question #1 is ALWAYS "Is this worth doing?" In this case it's obviously a very complex and risky solution to an exceedingly rare problem.
One failure mode is that the pitot tubes ice, so the computer thinks the pilot is trying to rip the wings off. Another is an emergency descent. What about disabled systems? Is it suicide to disable safety equipment because, say, it might be smoking or malfunctioning?
I find it hard to believe you call yourself an engineer. A truly half baked attitude it would seem. Seriously, open your mind and take on challenges. I guess it's the difference between middle management and the history books. That's OK. Everybody needs a job and an income, I get it.Truly half baked idea. I'm finding it hard to believe you're serious. You didn't post it on April 1,
now, why would you go and do that?Yes, I often ask questions and let the thread go where it will just to see others opinions.