7 ms·
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
by dfox 1y ago
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.
- deleted 1y ago[deleted]
- LeifCarrotson 1y agoIf you want to read the actual report, it's not linked from the CNN article, but it's available here: https://www.pacaf.af.mil/Portals/6/documents/3_AIB%20Report.pdf?ver=z-QJglR9Qm7slupMlo6zeA%3D%3D https://www.pacaf.af.mil/Portals/6/documents/3_AIB%20Report.... Edit: While CNN says the air force blamed the crash on ice in the hydraulic lines, it's obvious that ice can't be legally culpable. The report actually says: > Additionally, the [Accident Investigation Board] president found, by a preponderance of the evidence, that crew decision making including those on the in-flight conference call, lack of oversight for the Hazardous materials program, and lack of adherence to maintenance procedures for hydraulic servicing were substantially contributing factors. They note further down that "The 355th FGS hazardous materials program (HAZMAT) program suffered from insufficient manning and frequent supervision changes at times relevant to the mishap." Basically, they had a barrel of hydraulic oil that sat outside and no one took care of it. Also interesting is the 6 February 2025 incident, where another aircraft, barely a week after the one that crashed, had the same issue. They tested it inside a heated hangar, then outside in the 15F cold where they reproduced the weight-on-wheels sensor malfunctions, then brought it back in and drained the hydraulic fluid...there's a TON of water in those lines! I'm more familiar with industrial hydraulics in factories and earth-moving equipment, not with aviation...but we have water separators because a few drops of water can be enough to mess with the servo valves when you're near caviation limits. "...approximately one third of the fluid retrieved from the [landing gear] was water" is NOT RIGHT. Also, I chuckled on reading "...the barrel tested with more than 1024 parts per million (ppm) particulates, which is more than double the allowable limit for particulates in hydraulic fluid... It is important to note that the test does not accurately measure contaminates above 1024ppm, so the contamination was potentially far greater than 1024ppm" Gives strong "3.6 roentgen, not great, not terrible" vibes!
- themaninthedark 1y agoOf note to readers not familiar with hydraulic fluid, it is hygroscopic: >Passenger safety requires that in commercial airplanes hydraulic actuators be powered by fire-resistant hydraulic fluids. As a downside, such fluids are hygroscopic which means that these tend to accumulate humidity from the environment https://www.mdpi.com/2227-9040/8/4/131 https://www.mdpi.com/2227-9040/8/4/131
- halifaxbeard 1y agoThe hygroscopic nature of hydraulic fluid is there for the same reason it is in car brake fluid- it's better to evenly distribute water throughout the fluid, than to have it accumulate in a low point
- Bjartr 1y agoThat's actually a really cool way to deal with that problem!
- mrguyorama 1y agoIt is. Right up until you go to hit your brakes hard and it all boils out and removes your ability to apply brake pressure in an emergency and you had no idea how much water was in your line because there's no easy way to check, like a low spot with a sight glass. Or if you leave a barrel of hydraulic fluid outside until it is partially water and it's not easy to notice when you are handling it.
- wiml 1y agoI think my mental model of hydraulic brakes is too simple. Where is there a low pressure region in a brake line? When I stomp on the brakes, isn't the working part of the hydraulic system going to be at higher pressure?
- 1y ago
- diggan 1y ago> The article is somewhat sensationalistic somewhat sensationalistic?! The article clearly tries to give the impression the pilot was on the call: > 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 Knowing the quality of media these days, it wouldn't surprise me if it CNN just got it really wrong, but also wouldn't surprise me they'd do some brazen lie for clicks. Edit: Reading the report, it seems like you, dear fellow HN commentator, got it wrong in this case, sorry to say :) Seems indeed the pilot itself was on the call: > The mishap pilot (MP), assigned to the 354th FW, ejected safely before impact. [...] The MP initiated a conference call with Lockheed Martin engineers. The MA held for approximately 50 minutes while the team developed a plan of action Page 35 from https://www.pacaf.af.mil/Portals/6/documents/3_AIB%20Report.pdf?ver=z-QJglR9Qm7slupMlo6zeA%3D%3D https://www.pacaf.af.mil/Portals/6/documents/3_AIB%20Report....
- the__alchemist 1y agoSOF initiates Conference Hotel procedures, FYI. It's a (rarely used) checklist in their book. SOF is the pilot sitting in the tower to liase with ATC and handle emergencies from an ops perspective.
- mulmen 1y agoTo the uninitiated: SOF is Supervisor of Flying.
- esseph 1y agoThanks!
- CapricornNoble 1y agoClassic DoD with its overloaded acronyms. I first read the sentence thinking "what does this have to do with Special Operations Forces"?
- 1y ago
- ozim 1y agoStill interesting part is: them trying to fix the problem - made the plane crash. Of course it couldn’t land but still, tweaking stuff while flying was ultimately causing loss of control.
- LeifCarrotson 1y agoThe report actually says it could have landed. A week later, another F35 at the same base had the same problem, it landed with its nose gear 6 degrees off center and the pilot barely noticed. Basically, Lockheed Martin engineers told the air force to attempt re-centering with touch-and-go landings, but didn't realize that this could mess with the weight-on-wheels sensors and cause it to switch flight modes.
- stackskipton 1y agoI’ve always wondered why weight on wheel modes don’t have more checks, detecting weight on wheels but seeing 150+ Indicated Air speed and RALT is greater then 15ft, maybe issue caution instead of screwing with flight mode.
- LorenPechtel 1y agoYeah, they put too much faith in their sensors. Too many planes have crashed because of blind reliance on sensors that sometimes fail. Cross check whether things make sense before doing potentially catastrophic actions. And don't skimp on the maintenance budget. Sounds like they had too much to do, too few people to do it, leading to not taking proper care.
- LeifCarrotson 1y agoThere's value in simplicity. Every decision that a flight computer makes is based on a leaky abstraction of the world, and it's important to be able to reason about those states without excessive complexity. If a programmer, engineer, or pilot needs to think about when the aircraft will transition to "on ground" mode, and the answer is "when the weight on wheels sensors say the landing gear is not fully extended", that's simple. You can even extend this to reason about what might happen when the landing gear is not fully extended, or what happens if it does a belly crash-landing with the gear not deployed, or if it hops, etc. Furthermore, it's a perpetual signal, rather than an edge-triggered condition: You don't have to develop and remember and think about a state machine that transitions to the on-ground state, or worry about what happens if the flight computer gets reset, you can check the sensor state at any instant. Yes, there are a myriad of checks and alternate modes you could do, or information items you could communicate to the pilot - radar altimeters, GPS altimeters, barometric altimeters, indicated airspeed, speed over the ground, weight on wheels, landing gear deployment, accelerometer/gyro/IMU history, stick position, flight model response to control inputs, brake response, ABS wheel speed sensors (if they have those, which I doubt), cameras...the list goes on. With more data, you can potentially be more accurate if one or more sensors malfunctions. "Aircraft On Ground" could actually mean the aircraft is on the ground, rather than the abstract state that occurs when the weight-on-wheels sensors say the landing gear is not fully extended. But the more complexity you add, the more it gets difficult to understand! I deal with this all the time - I'm an industrial controls engineer, working with robots and CNCs and assembly equipment rather than aircraft. But the machines still need to reason about the world. It's an important judgement, borne out of years of experience, to decide when you need to have a laser distance sensor or inductive proximity switch that confirms the part is present in the fixture. Sometimes you can reason about it and assert that if the part was in the previous fixture and the machine cycled, it must be in the new fixture, sometimes you need to put together multiple sensors or live information like CNC spindle torque to confirm that you're actually cutting steel. But usually, when you've got an operator or maintenance tech 600 miles away, looking at the machine you programmed 2 years ago, calling on the phone to ask why the machine is stuck on "Step 34: Wait for Part Present in Fixture B, then start CNC job O312" (or conversely, why it's skipping past this check and cutting air if the sensor is covered in swarf) everyone involved in reasoning about this equipment for the next decade would rather it be just a digital part present sensor. This works in industrial automation where you can demand that the equipment's environment be precisely controlled, I'm less convinced that it will work well in fly-by-wire aircraft or (more pertinent to the average human) in level 3/4 self-driving cars. Simplicity has value, complexity adds cost..but is this cost worth the risk when there's a pilot who now has a thoracic spine fracture or a pedestrian crossing the road? I don't know.
- andy_xor_andrew 1y agoI 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"
- the__alchemist 1y agoDon't read the article; read the report.
- VerminOctopus1 1y agoI’m guessing you also didn’t read the report given that he was indeed on the conference call.
- eduction 1y agoOne 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.
- jasonlotito 1y agoFrom 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.pdf?ver=z-QJglR9Qm7slupMlo6zeA%3D%3D https://www.pacaf.af.mil/Portals/6/documents/3_AIB%20Report....
- CamperBob2 1y agoThe last paragraph of the article and seems to be missing a few words Something, something, mote in your neighbor's eye, mumble, something...
- grues-dinner 1y agoMuphry's Law strikes again: https://en.wikipedia.org/wiki/Muphry%27s_law https://en.wikipedia.org/wiki/Muphry%27s_law
- weaksauce 1y ago> Briefly stated, the Gell-Mann Amnesia effect is as follows. You open the newspaper to an article on some subject you know well. In Murray’s case, physics. In mine, show business. You read the article and see the journalist has absolutely no understanding of either the facts or the issues. Often, the article is so wrong it actually presents the story backward — reversing cause and effect. I call these the “wet streets cause rain” stories. Paper’s full of them. > In any case, you read with exasperation or amusement the multiple errors in a story, and then turn the page to national or international affairs, and read as if the rest of the newspaper was somehow more accurate about Palestine than the baloney you just read. You turn the page, and forget what you know. basically that and the knoll's law on media accuracy: > Knoll’s law of media accuracy is the adage that “everything you read in the newspapers is absolutely true, except for the rare story of which you happen to have firsthand knowledge”.
- banku_brougham 1y agoKnoll's law, I'll remember this.
- RyanOD 1y agoAnd, of course, CNN only links to their own articles. Why bother linking to the actual report? The rise in sites that only link to themselves 99% of the time really frustrates me.
- MostlyStable 1y agoJournalism's failure to adopt linking to sources etc in the internet age is kind of infuriating. I get it, back in physical newspaper/magazine days, linking wasn't possible, and it takes a while for new norms to change and habits to form, but articles have been internet-first for well over a decade at this point. It should be completely unacceptable not to have linking to sources whenever relevant. I'm not sure I have ever found a news article that makes finding the original source or subject of the article easy. Certainly not on mainstream news outlets.
- RyanOD 1y agoSites with no external linking are like highways with no exits.
- jjk166 1y agoBacked up, slow, and avoided by those familiar with the area?
- chiefalchemist 1y agoIf they’re not providing essential links then it’s not journalism. They shouldn’t be given credit for a title they are not earning. If you pet barks, do you still call it a cat? Of course not. Links make it journalism. Not linking makes it reporting. They should not be considered synonymous. The point is, people who should know better keep calling the likes of CNN journalism and those who don’t know any better keep believing they’re consuming content and forming understanding based on journalism.
- verdverm 1y agoThey complain about how social media links to them, while they are equally guilty of link shenanigans
- avs733 1y agoTo clarify because everyone is confused here. The report is a little vague and information is buried in a couple places. Using PDF page numbers > "The MP responded “14.5” ... and then opined a “conference hotel” was appropriate for this situation (Tab N-12)." (pg. 13) > "The MP, utilizing the on-duty supervisor of flying (SOF) in the air traffic control (ATC) tower, initiated a conference call with Lockheed Martin (LM)" (pg. 8) > "The SOF informed the MP he was on the phone with the conference hotel and Lockheed Martin were getting the LG subject matter experts (SME) on the line ...no transcript is available because the call was made on a personal phone rather than the legal voice recorder in the air traffic control tower" (pg. 13) in the last statement, he means that the SOF was informing the MP that the SOF was on the conference call and would relay information. The mishap pilot (MP) was speaking to the supervisor of flying (SOF), almost certainly via radio. He asked the SOF, in the control tower to set up a conference call. For reasons, maybe of expediency or technical failure, or norms or something, the SOF made that call on his personal cell phone. The MP was not 'on the phone' but the SOF would have primaily functioned as a relay between radio and phone. The purpose of the call was to get information from the pilot to the engineers and from the engineers to the pilot. Aviate, Navigate, Communicate* means he doesn't need to cognitive load of actually listening as the SOF and engineers think through what to do and decide on a plan. He needs to fly the plane and provide information necessary to help figure out how to aviate. If you want to harp on CNN for accuracy, I'm sure there are plenty of opportunities but this feels pedantic. It is like saying 'the astronauts weren't talking to mission control, they were talking to the capcom. Only the capcom talked to mission control'. I suspect that in the non-public version of this report there is more discussion of the decision and alternatives to doing that call on a personal cell phone for two reasons. (1) As noted in the report it means that conference isn't recorded and a transcript is not available to the investigators (thats shocking to me). (2) Detailed aircraft systems information, which is highly controlled, is being discussed on an open line. * Funny enough, the third time the report defines SOF, they have a typo "supervisor of lying" (pg. 36)
- jasonlotito 1y ago> If you want to harp on CNN for accuracy, I'm sure there are plenty of opportunities but this feels pedantic. It is like saying 'the astronauts weren't talking to mission control, they were talking to the capcom. Only the capcom talked to mission control'. Um, actually, they were talking to a mic. And the mic converted the noise... /s But yeah, excellent comment here.
- WalterBright 1y agoSounds like the sensationalistic and woefully inaccurate media reporting of the MAX crashes.
- pbasista 1y ago> The pilot was not part of the conference call! Thank you. If I cannot even trust one of the substantial parts of the headline to be true, then my interest to read or even care about such an article is reduced to almost zero.
- jasonlotito 1y ago"The pilot was not part of the conference call!" So, from the actual 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. Seems like he was at some level a part of the conference call. Even if they are on hold, it still sounds like they were a part of it at some level. Seems reasonable to me.
- etler 1y agoThe call was being relayed to the pilot by the flight supervisor. While he wasn't "on" the call, I think it's fair to say he was "part" of the call. He's still getting live tech support and trying to trouble shoot the plane while flying it. He had an intermediary but I don't think that totally changes the scenario.
- Gathering6678 1y ago"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." Did I misread that? I thought it meant an air-to-ground call, which I suppose is not that unheard of: I've definitely seen air accident videos saying the pilots were trying to debug in the air with engineers in the loop. *edit: never mind, I misunderstood your comment. I thought you meant the article was clickbait.