Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Features
Speaker Deck
PRO
Sign in
Sign up for free
Search
Search
How to Crash a Plane
Search
Nickolas Means
November 16, 2015
Technology
1
360
How to Crash a Plane
Nickolas Means
November 16, 2015
Tweet
Share
More Decks by Nickolas Means
See All by Nickolas Means
The Magnitude 9.1 Meltdown at Fukushima
nmeans
0
81
Taking the 737 to the MAX!
nmeans
0
63
Who Destroyed Three Mile Island?
nmeans
0
910
The Original Skunk Works
nmeans
0
1.8k
Warning: May Be Habit Forming
nmeans
1
170
The Building Built on Stilts
nmeans
1
500
The Original Skunk Works
nmeans
1
730
How To Code Like A Writer
nmeans
3
3.4k
You Are Not An Impostor
nmeans
11
18k
Other Decks in Technology
See All in Technology
オープンソースのハードウェアのコンテストに参加している話
iotengineer22
0
520
新卒から4年間、20年もののWebサービスと向き合って学んだソフトウェア考古学 - PHPカンファレンス新潟2025 / new graduate 4year software archeology
oguri
2
350
テストを実施する前に考えるべきテストの話 / Thinking About Testing Before You Test
nihonbuson
PRO
13
2k
AIの電力問題を概観する
rmaruy
1
210
コードの考古学 〜労務システムから発掘した成長の糧〜
kenta_smarthr
1
1.1k
技術書典18結果報告
mutsumix
2
180
大事なのは、AIの精度だけじゃない!〜1円のズレも許されない経理領域とAI〜
jun_nemoto
10
5.1k
Eight Engineering Unit 紹介資料
sansan33
PRO
0
3.2k
AIとSREの未来 / AI and SRE
ymotongpoo
1
640
“新卒らしさ”を脱ぎ捨てて 〜1年を経て学んだこと〜
rebase_engineering
0
130
SmartHRの複数のチームにおけるMCPサーバーの活用事例と課題
yukisnow1823
2
1.1k
Machine Intelligence for Vision, Language, and Actions
keio_smilab
PRO
0
490
Featured
See All Featured
It's Worth the Effort
3n
184
28k
Code Review Best Practice
trishagee
68
18k
Statistics for Hackers
jakevdp
799
220k
Design and Strategy: How to Deal with People Who Don’t "Get" Design
morganepeng
129
19k
The MySQL Ecosystem @ GitHub 2015
samlambert
251
12k
Building an army of robots
kneath
306
45k
Designing for Performance
lara
608
69k
Creating an realtime collaboration tool: Agile Flush - .NET Oxford
marcduiker
30
2.1k
Improving Core Web Vitals using Speculation Rules API
sergeychernyshev
15
890
GitHub's CSS Performance
jonrohan
1031
460k
Embracing the Ebb and Flow
colly
85
4.7k
GraphQLの誤解/rethinking-graphql
sonatard
71
11k
Transcript
HOW TO CRASH A PLANE NICKOLAS MEANS / @NMEANS
July 19, 1989
Denver Stapleton International Airport
United Flight 232 Denver Stapleton to Chicago O'Hare
None
McDonnell Douglas DC-10-10 N1819U
None
None
None
!
None
Captain Al Haynes
Al, I can't control the plane!
None
We're rolling!
None
"Ladies and gentlemen, we've lost our tail engine, but this
aircraft can fly fine with the two remaining engines. We're going to descend and continue on to Chicago."
None
We've lost all our hydraulics.
None
None
Elevators
Ailerons
None
None
The only question I had was how long it was
going to take Iowa to hit me.
None
None
None
Phugoid
Phugoid
None
None
None
None
None
None
None
GE CF6-6 Turbofan Engine
None
None
None
None
None
None
None
Brace! Brace! Brace!
None
None
None
None
None
Of 296 people on board, 185 survived.
In the previous 25 years, no one had ever survived
the complete loss of flight controls on an airliner.
"The Safety Board believes that under the circumstances the UAL
flightcrew performance was highly commendable and greatly exceeded reasonable expectations." — NTSB Aircraft Accident Report, United 232
What made this crew different?
None
CREW RESOURCE MANAGEMENT
NO HEROES
EVERYONE HAS A VOICE
SOFTWARE IS A TEAM SPORT
THANKS! NICKOLAS MEANS / @NMEANS