←back to thread

278 points Michelangelo11 | 4 comments | | HN request time: 0.001s | source
Show context
dfox ◴[] No.45040695[source]
The article is somewhat sensationalistic. If you read the actual report you will find out that:

The pilot was not part of the conference call!

What froze was not hydraulic fluid for actuators (in some hydraulic line), but hydraulic fluid in the shock absorbers.

The last paragraph of the article and seems to be missing a few words and reads as the investigators blaming the people directly involved, which is essentially a complete opposite of what conclusions of the report say.

replies(13): >>45041203 #>>45041205 #>>45041260 #>>45041299 #>>45041304 #>>45041313 #>>45041359 #>>45041599 #>>45041942 #>>45041944 #>>45042051 #>>45042571 #>>45044912 #
andy_xor_andrew ◴[] No.45041299[source]
I read the article (twice) and I still have the impression the pilot was in fact the one in the conference call

Opening line:

> A US Air Force F-35 pilot spent 50 minutes on an airborne conference call with Lockheed Martin engineers trying to solve a problem with his fighter jet before he ejected

Am I illiterate or misreading it?

> After going through system checklists in an attempt to remedy the problem, the pilot got on a conference call with engineers from the plane’s manufacturer, Lockheed Martin, *as the plane flew near the air base. *

Is this actually some insane weasel-wording by CNN? "We never said the pilot (he is in fact a pilot) was the one flying the jet, we just said 'as the plane flew', not 'as he flew the plane', using passive voice, so we're not wrong - but it was another pilot flying the plane"

replies(3): >>45041365 #>>45041446 #>>45041702 #
the__alchemist ◴[] No.45041365[source]
Don't read the article; read the report.
replies(2): >>45041410 #>>45041421 #
1. SalmoShalazar ◴[] No.45041410[source]
I’m guessing you also didn’t read the report given that he was indeed on the conference call.
replies(1): >>45041900 #
2. eduction ◴[] No.45041900[source]
One clear indication he was not, from PDF p14 (8 as numbered) ("MP"="mishap pilot"):

"At 21:12:52Z, the SOF informed the MP, “Alright the engineers uh are not optimistic about this COA but, extremely low PK [probability kill, meaning the probability this would fix the issue], but we’re going to try anyway is a touch-and-go on the runway, mains only, do not touch the nose gear, uh lift back off in all cases and have the uh have Yeti 4 reconfirm the nose gear position once your safely airborne.”"

No need for this if the pilot was on the call directly.

replies(1): >>45042640 #
3. jasonlotito ◴[] No.45042640[source]
From the Report:

> The MP initiated a conference call with Lockheed Martin engineers through the on-duty supervisor of flying (SOF). The MA held for approximately 50 minutes while the team developed a plan of action.

"though the SOF" implies a middle-man, but I imagine that's because you don't want literally hook up a conference call directly to the cockpit. That being said, seems like the pilot was effectively on the conference call.

Unless you want to suggest I don't trust the report?

https://www.pacaf.af.mil/Portals/6/documents/3_AIB%20Report....

replies(1): >>45043973 #
4. eduction ◴[] No.45043973{3}[source]
What I said is he was not on the call /directly/.

You can argue over whether he was “effectively” on the call because someone was summarizing it for him per what I quoted.

I just think it’s worth nothing he was not “on” the call the way someone is traditionally on a conference call.