5 ms·

It's very likely that they're an AvHerald reader. It's the absolute de facto gold standard website in its field, and sensationalism and drama is not appreciated

It's very likely that they're an AvHerald reader. It's the absolute de facto gold standard website in its field, and sensationalism and drama is not appreciated -- a large chunk of the usual audience are aviation professionals. My dad was a pilot, and I've got some few hours myself. You can bet that if either of us watched this event happen, we'd mentally be documenting it as best as we possibly can, both to try to predict any useful information (e.g should we try to move!), and for any subsequent investigation. The excellent safety record of aviation originates from a detailed and pedantic paper trail that is written in blood. It's by learning as much as possible from every incident, without fear of censure or blame, that makes the skies safer for everybody.

lrossi 6y ago
I can draw some parallels between that and a healthy SRE culture. Except for the casualties, of course. Wondering if the first SREs who created the guidelines had aviation industry experience.
- kwertyoowiyop 6y ago
  Aviation regulations are written in blood. SRE regulations are written in lost weekends.
  - Xylakant 6y ago
    Depends on what systems the SRE is managing or even on the downstream clients relying on their work. Around Y2K a bug took the out the emergency call application for the fire department in Berlin at midnight New Year’s Eve. People died because dispatch was not available. It’s an IT system where people die if you mess up. AFAIR in one of the earlier prolonged AWS outages, some sort of medical provider failed and people were at risk. It’s not all just display ads on websites.
- jeffrallen 6y ago
  Brent Chapman was one, and he worked in volunteer search and rescue.
- dzhiurgis 6y ago
  low key feel opposite - chaos engineering (to an extent obvs) would benefit flight controls... it's like that old experiment that i cant find source for - wall st traders switched with military guys and wall st outperformed mils because they are used to dealing with uncertain information...
kortilla 6y ago
> aviation originates from a detailed and pedantic paper trail that is written in blood The saying is “aviation regulations are written in blood” because each new regulation is usually in response to crash. https://aviation.stackexchange.com/questions/13081/why-do-people-say-aviation-regulations-are-written-in-blood https://aviation.stackexchange.com/questions/13081/why-do-pe... You don’t keep a “paper trail written in blood”.
billfruit 6y ago
Only looked up Aviation Herald after you mentioned. Very informative, almost HN like, but even more dense and topical.
bananasbandanas 6y ago
There is a now a comment on that article where the ground observer identifies himself and gives a few more details, so looks like you're right. > 1) I was giving Simon a heads up to look for a report out of DEN - if it was anything, I thought it was just something like a (big) compressor stall. That was why so many caveats were there - I wasn't sure at the time that the aircraft had had a problem. I didn't realize it was going to be widely reported until my mother texted me a couple of hours later asking if any of the plane parts came down close to me > 2) Something I omitted that I should have put in: After I got home I imagined how many thumb-widths at arm's length it would take to occlude it (from memory), and plugged that into similar triangles and the length of a 737 (didn't realize it was a 777) to get an estimated altitude and got 2-4 thousand meters. I thought the cloud deck was only 2000 feet AGL or so, so I didn't believe the numbers. I did change "a couple" to "a few" though. Turns out it was ~8000 feet AGL. I should have believed more in the math!

lrossi 6y ago

I can draw some parallels between that and a healthy SRE culture. Except for the casualties, of course. Wondering if the first SREs who created the guidelines had aviation industry experience.

kwertyoowiyop 6y ago
Aviation regulations are written in blood. SRE regulations are written in lost weekends.
- Xylakant 6y ago
  Depends on what systems the SRE is managing or even on the downstream clients relying on their work. Around Y2K a bug took the out the emergency call application for the fire department in Berlin at midnight New Year’s Eve. People died because dispatch was not available. It’s an IT system where people die if you mess up. AFAIR in one of the earlier prolonged AWS outages, some sort of medical provider failed and people were at risk. It’s not all just display ads on websites.
jeffrallen 6y ago
Brent Chapman was one, and he worked in volunteer search and rescue.
dzhiurgis 6y ago
low key feel opposite - chaos engineering (to an extent obvs) would benefit flight controls... it's like that old experiment that i cant find source for - wall st traders switched with military guys and wall st outperformed mils because they are used to dealing with uncertain information...

kortilla 6y ago

> aviation originates from a detailed and pedantic paper trail that is written in blood The saying is “aviation regulations are written in blood” because each new regulation is usually in response to crash. https://aviation.stackexchange.com/questions/13081/why-do-people-say-aviation-regulations-are-written-in-blood https://aviation.stackexchange.com/questions/13081/why-do-pe... You don’t keep a “paper trail written in blood”.

billfruit 6y ago

Only looked up Aviation Herald after you mentioned. Very informative, almost HN like, but even more dense and topical.

bananasbandanas 6y ago

There is a now a comment on that article where the ground observer identifies himself and gives a few more details, so looks like you're right. > 1) I was giving Simon a heads up to look for a report out of DEN - if it was anything, I thought it was just something like a (big) compressor stall. That was why so many caveats were there - I wasn't sure at the time that the aircraft had had a problem. I didn't realize it was going to be widely reported until my mother texted me a couple of hours later asking if any of the plane parts came down close to me > 2) Something I omitted that I should have put in: After I got home I imagined how many thumb-widths at arm's length it would take to occlude it (from memory), and plugged that into similar triangles and the length of a 737 (didn't realize it was a 777) to get an estimated altitude and got 2-4 thousand meters. I thought the cloud deck was only 2000 feet AGL or so, so I didn't believe the numbers. I did change "a couple" to "a few" though. Turns out it was ~8000 feet AGL. I should have believed more in the math!