News for hackers. Stuff that matters.
Re:USS McCain collision ultimately caused by UI confusion by tlb on Thursday November 02, 2017 @05:52PM (#15614627)
Amazing that someone would design in multiple steering wheels, only one of which is active, and no big indicator to make it super-obvious which one it is.

Also amazing that there's a mode where moving a control sometimes controls all engines, sometimes just one.

Re:USS McCain collision ultimately caused by UI confusion by mschuster91 on Thursday November 02, 2017 @07:37PM (#15615373)
> Also amazing that there's a mode where moving a control sometimes controls all engines, sometimes just one.

This is a fallback in case the primary rudder fails. You can still shift left or right, but you will take more time and it will be far less precise than using the rudder.

This is also valid for aircraft, where not only the rudder can be compensated but also the elevator (aka up/down) by simultaneously modifying the power of all engines. You can see a list at https://en.wikipedia.org/wiki/Flight_with_disabled_controls.

Re:USS McCain collision ultimately caused by UI confusion by azernik on Thursday November 02, 2017 @08:31PM (#15615696)
The UI issue being that ganged control should have been the default, but separate control was instead.
Re:USS McCain collision ultimately caused by UI confusion by dTal on Saturday November 04, 2017 @02:09PM (#15626179)
The difference being that aircraft throttles are not modal and are always 1 throttle = 1 engine.
Re:USS McCain collision ultimately caused by UI confusion by digi_owl on Thursday November 02, 2017 @06:17PM (#15614803)
Happens more often than we like.

I know of a ferry that a local warf built that had two bridges, and a combined throttle and rudder in each.

The thing is that when moving from one bridge to the other, the crew had to flip a switch to indicate what direction was forward. And quite often they forgot.

End result was a long history of damaged because ferry would ram the pier when the crew was actually attempting to move away from it.

Re:USS McCain collision ultimately caused by UI confusion by theyregreat on Thursday November 02, 2017 @06:31PM (#15614911)
That is super dumb and dangerous. They should just flip the inputs on one end.

EDIT (since some people obviously don’t understand the problem): ... so that each set of controls is always correct for the respective side on which it is located. No switch is necessary.

Re:USS McCain collision ultimately caused by UI confusion by scott_karana on Friday November 03, 2017 @11:59AM (#15620141)
Even better, make the stations operable from either side. Then the yokes always orient in reality, and it's just the frame of reference of the pilot that changes.

Eg, if you're facing the dock, and push forward, you'll hit the dock. Take the other side and point your body to sea. Intuitive.

Re:USS McCain collision ultimately caused by UI confusion by nicwolff on Thursday November 02, 2017 @06:48PM (#15615047)
No, they just have a big button by each wheel marked "MAKE THIS THE BOW".
Re:USS McCain collision ultimately caused by UI confusion by LeifCarrotson on Friday November 03, 2017 @09:28AM (#15619009)
When would you ever not press that button?
Re:USS McCain collision ultimately caused by UI confusion by theyregreat on Thursday November 02, 2017 @07:02PM (#15615165)
You’re bikeshedding on a switch versus a button, still an extra, unnecessary step to forget. Same problem. You failed. Try again.
Re:USS McCain collision ultimately caused by UI confusion by Jtsummers on Thursday November 02, 2017 @05:59PM (#15614679)
Check out the recent O'Reilly book Tragic Design for more situations exactly like this.

Poor UI design is remarkably common, even on controls that are essential for safe operations.

http://www.tragicdesign.com

Re:USS McCain collision ultimately caused by UI confusion by csours on Thursday November 02, 2017 @06:41PM (#15614987)
Also the classic Field Guide to Understanding Human Error.

Amazon: https://www.amazon.com/Field-Guide-Understanding-Human-Error...

Older PDF (paperback is well worth it, in my opinion): http://www.leonardo-in-flight.nl/PDF/FieldGuide%20to%20Human...

Re:USS McCain collision ultimately caused by UI confusion by ams6110 on Thursday November 02, 2017 @08:51PM (#15615838)
In my view, on screen UI instead of physical controls is a big factor. If the throttles had been levers it would be instantly discernable if one or both were being moved. This is also why I dislike touch screen controls in cars. I want levers and knobs that give tactile, physical feedback.
Re:USS McCain collision ultimately caused by UI confusion by mjevans on Friday November 03, 2017 @03:54AM (#15617379)
Agreed on this. The more important controls should be operable by a suited astronaut, and should also try to express the current 'feedback' of the system state.
Re:USS McCain collision ultimately caused by UI confusion by JshWright on Thursday November 02, 2017 @07:03PM (#15615170)
Decent odds you've flown on an airplane with a similar UX for primary flight controls.

Airbus uses two "side stick" controllers that are on opposite sides of the cockpit. This was a contributing factor in the Air France 447 crash.

Re:USS McCain collision ultimately caused by UI confusion by inferiorhuman on Thursday November 02, 2017 @07:20PM (#15615275)
> > Amazing that someone would design in multiple steering wheels, only one of which is active, and no big indicator to make it super-obvious which one it is.

> Decent odds you've flown on an airplane with a similar UX for primary flight controls.

Ah, well Airbus does a few things. 1.) A "dual input" warning is issued if there is an attempt at using both controls simultaneously. 2.) There are lights to indicate when your sidestick is active and when it is not.

Re:USS McCain collision ultimately caused by UI confusion by cyberferret on Thursday November 02, 2017 @07:42PM (#15615407)
I believe the warning can change depending on which of the 3 flight modes the aircraft is in at the time. Big contribution to AF447's demise was that the aircraft was in 'alternate flight' mode and the crew assumed it was still in 'normal flight' mode and made a lot of their judgement calls accordingly.

For an industry that is so safety conscious, I believe this is a huge flaw in disaster control. To put it in context that most readers here can understand - lets say your everyday computer uses OS X as its operating system, but one day, with deadlines to meet, you have a huge crash, and the OS reverts to Windows, and you have to find the problem and remember the appropriate commands under intense pressure...

Re:USS McCain collision ultimately caused by UI confusion by inferiorhuman on Thursday November 02, 2017 @08:25PM (#15615659)
I'd argue it's more like getting dropped into single user mode. No friendly GUI, but the underlying systems are the same. The flaw with any sort of safety net is that you get used to it and forget the basics of aviation.

The big problem was that the pilot-in-command simply forgot (or did not know) how to fly the plane. He overcorrected in reaction to turbulence and the rest is history. Normal law does not allow the pilot to set an angle of attack that would lead to a stall. In the alternate law modes this protection is not there and so when the PIC didn't adhere to the rule of "don't pull up while in a stall" there was no safety net to prevent him from exacerbating the situation. In fact he kept pulling back when the stall alarm went off.

A better UI would not have solved the self-inflicted problems. From the findings sections in the wiki entry:

- The pilots apparently did not notice that the aircraft had reached its maximum permissible altitude

- The pilots did not read out the available data (vertical velocity, altitude, etc.)

- the crew made inappropriate control inputs that destabilized the flight path;

- the crew failed to follow appropriate procedure for loss of displayed airspeed information;

- the crew lacked understanding of the approach to stall

- the crew lacked practical training in manually handling the aircraft both at high altitude and in the event of anomalies of speed indication

- the two co-pilots' task sharing was weakened both by incomprehension of the situation at the time of autopilot disconnection, and by poor management of the "startle effect", leaving them in an emotionally charged situation

- the crew did not respond to the stall warning

A better cockpit may have given the pilots a better chance of surviving but definitely wouldn't have guaranteed a better outcome. One only needs to look at Asiana to see that even Boeing, with their contrasting approach to UX, can't save pilots who lack basic airmanship. My understanding is that most long-haul pilots will fly a fairly small number of segments each month, and that most of those segments are going to involve a huge amount of time spent in the middle of nowhere with autopilot on. This leads to atrophying of skills needed to manually fly a plane.

Conversely, one only need to look at Qantas' QF32 incident to see that good airmanship can absolutely make catastrophic failure survivable. Yes, there is a lot of information to process in an emergency... but the Qantas crew took that information and delegated appropriately. The Air France pilots lost their cool and fucked up.

Re:USS McCain collision ultimately caused by UI confusion by gsnedders on Friday November 03, 2017 @06:58AM (#15618155)
> The big problem was that the pilot-in-command simply forgot (or did not know) how to fly the plane.

The pilot flying wasn't the pilot-in-command. Half the problem was the PIC was out of the cockpit at the time and the lack of any clear command structure between the two first officers in the cockpit. You can also argue that it may have been recoverable if the PIC took over as PF when he returned to the cockpit (had he acted rationally, etc.), instead of being confused by the situation they were in and unable to get out of, likely without knowing what the PF was doing.

> My understanding is that most long-haul pilots will fly a fairly small number of segments each month, and that most of those segments are going to involve a huge amount of time spent in the middle of nowhere with autopilot on. This leads to atrophying of skills needed to manually fly a plane.

Much flying nowadays is through RVSM (reduced vertical separation minima) airspace, and you're not allowed to hand-fly the aircraft there (in general, modern autopilots can maintain altitude better than a pilot can).

Re:USS McCain collision ultimately caused by UI confusion by dredmorbius on Friday November 03, 2017 @12:40PM (#15620466)
"PIC", pilot in control, refers to the pilot actually flying the plane. Not the command or seniority structure amongst pilots.

There were a Captain and two co-pilots aboard AF445. The junior co-pilot was PIC for much of the incident.

Re:USS McCain collision ultimately caused by UI confusion by gsnedders on Friday November 03, 2017 @06:28PM (#15622593)
PIC is in command, not in control. In plenty of short-haul flights, the FO can be PF, but they aren't competent to be PIC.

See also <https://aviation.stackexchange.com/questions/33414/who-is-th....

As in the AF447 case, the PIC will delegate to an acting PIC while they are on their rest break, but ultimate responsibility still remains with them.

Re:USS McCain collision ultimately caused by UI confusion by dredmorbius on Saturday November 04, 2017 @06:39AM (#15624481)
My error. I was getting confused on the BAE terminology:

PF Pilot Flying

PNF Pilot Not Flying

https://www.bea.aero/docspa/2009/f-cp090601.en/pdf/f-cp09060...

Re:USS McCain collision ultimately caused by UI confusion by triangleman on Friday November 03, 2017 @11:52AM (#15620090)
Good points all around. Obviously it's up to the human beings to do the best they can in the face of limited information and control.

But where does your viewpoint meet up with someone like Chesley Sullenberger who says the pilots would have probably not crashed if the plane was a Boeing rather than an Airbus, because it would have had an angle-of-attack indicator?

Re:USS McCain collision ultimately caused by UI confusion by isaacdl on Thursday November 02, 2017 @08:57PM (#15615878)
QF32 had 5 (!) rated pilots in the cockpit and managed to communicate and delegate effectively. That's truly an amazing accomplishment.
Re:USS McCain collision ultimately caused by UI confusion by dredmorbius on Friday November 03, 2017 @12:42PM (#15620474)
Right, I was thinking of making the same point.

The initially-designated co-pilot also was virtually fully occupied simply clearing alerts from the aircraft's control and diagnostics systems -- for about 45 minutes as I recall.

That's a near-deadly case of TMI, I suspect.

Re:USS McCain collision ultimately caused by UI confusion by JshWright on Thursday November 02, 2017 @07:57PM (#15615497)
And as the Air France 447 cockpit voice recordings demonstrated, those are not sufficiently obvious in all circumstances (particularly in high stress situations when you're already several steps down the path to disaster).
Re:USS McCain collision ultimately caused by UI confusion by theyregreat on Thursday November 02, 2017 @06:29PM (#15614900)
Redundant affordances are needed:

Controls that are active should be illuminated in a particular color, say red.

Controls that are disabled should be extinguished, physically-locked or track active controls, and sound a warning when manipulated.

Re:USS McCain collision ultimately caused by UI confusion by nostrademons on Thursday November 02, 2017 @06:56PM (#15615111)
I can imagine the requirements doc that led to that, where some Pentagon wonk was thinking "What happens if the helmsman is shot? If there's engine damage? If the helmsman is shot and there's engine damage?" and wrote all of those cases in, and completely forgot about the case where the bridge crew gets super confused because they triggered an edge case in the software and have no idea how to regain control of the ship.
Re:USS McCain collision ultimately caused by UI confusion by user5994461 on Thursday November 02, 2017 @09:44PM (#15616090)
Well, it's a warship. In their defense, they really have to plan for people dying and part of the ship being destroyed.
Re:USS McCain collision ultimately caused by UI confusion by dx034 on Friday November 03, 2017 @03:30AM (#15617267)
But if it leads to them not being able to steer through a busy area in peacetime where thousands of ships go through every day (many larger than this destroyer), this clearly failed. With this happening I'm not sure if they would've reacted better if they had suddenly been under enemy attack. Would they've been less confused then?
Re:USS McCain collision ultimately caused by UI confusion by oasisbob on Thursday November 02, 2017 @06:14PM (#15614786)
Having differential engine control isn't too surprising - it's just another way to maintain a course in addition to the rudder.

Jetliners have gangable throttle controls for their engines, albeit with what is probably a much better interface.

Re:USS McCain collision ultimately caused by UI confusion by cyberferret on Thursday November 02, 2017 @07:39PM (#15615388)
Airliners usually have a hardware clip to 'gangload' all throttles together, and the 'interface' of having two or more separate levers next to each other makes it obvious if you missed one while moving them, or notice that the clip is flipped so the levers now work independently instead of all as one.

Then again, in high stress situations even totally obvious signs like this can be missed, as evidenced by the Qantas 747 crew on the famous runway overrun in Thailand some years ago. I believe in that case, a large contributing factor was when the captain went to pull the levers back over the rear detents for reverse thrust after landing on the wet runway, he only grabbed three of the levers, and left one engine running at just over idle speed.