Upgrade to Pro
— share decks privately, control downloads, hide ads and more …
Speaker Deck
Sign up for free
Menu
Search
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Features
All features
Private URLs
Password Protection
Custom URLS
Scheduled publishing
Remove Branding
Restrict embedding
Deck Collections
Notes
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Explore
Featured decks
Featured speakers
Programming
Technology
Storyboards
Pricing
Search
Sign in
Sign up for free
How to Crash a Plane
Search
Nickolas Means
November 16, 2015
Technology
480
1
Share
Embed
Copy iframe code
Copy JS code
Copy link
Start on current slide
How to Crash a Plane
Nickolas Means
November 16, 2015
More Decks by Nickolas Means
See All by Nickolas Means
The Magnitude 9.1 Meltdown at Fukushima
nmeans
0
160
Taking the 737 to the MAX!
nmeans
0
150
Who Destroyed Three Mile Island?
nmeans
0
1.2k
The Original Skunk Works
nmeans
0
1.9k
Warning: May Be Habit Forming
nmeans
1
220
The Building Built on Stilts
nmeans
1
560
The Original Skunk Works
nmeans
1
830
How To Code Like A Writer
nmeans
3
3.5k
You Are Not An Impostor
nmeans
11
18k
Other Decks in Technology
See All in Technology
Goodbye ShellScript, Hello File-based App
shunsock
0
390
CLIライブラリ開発を支える技術
htnabe
0
140
え、こんなに早く改修できるの?──新人エンジニアとスクラムマスターの2人が語る、AI×アジャイル開発の現場
ysasago
2
530
AI 時代のスタートアップエコシステ厶から考究する技術的負債との向き合い方
m3m0r7
PRO
3
2.3k
その Lambda、8分で 管理者権限まで奪われます
k1nakayama
6
3.2k
作って終わりじゃないサーバーレス 〜9年運用する大規模EC物流API基盤の設計・運用のリアル〜
zozotech
PRO
0
280
AIは推し活である。
kurazuuuuuu
1
850
Cloudflare Workers 向けアプリを C# で構築する ~WASM Native AOT への道~
nenonaninu
1
540
AIエージェントの自己改善をどう設計するか / How to Design Self-Improvement for AI Agents
22mi
25
16k
顧客に向き合う開発組織へ。リアーキテクチャとフィーチャーチーム化で挑む組織改革
safie
0
2.1k
品質と信頼性を地続きにする
grimoh
2
820
ADKで始める業務改善 - AIエージェント開発時の考えと設計
harappa80
2
240
Featured
See All Featured
We Have a Design System, Now What?
morganepeng
55
8.3k
Measuring Dark Social's Impact On Conversion and Attribution
stephenakadiri
2
280
The Limits of Empathy - UXLibs8
cassininazir
1
680
The B2B funnel & how to create a winning content strategy
katarinadahlin
PRO
1
530
Side Projects
sachag
456
43k
What’s in a name? Adding method to the madness
productmarketing
PRO
24
4.2k
Claude Code のすすめ
schroneko
67
230k
Creating an realtime collaboration tool: Agile Flush - .NET Oxford
marcduiker
35
2.6k
Building the Perfect Custom Keyboard
takai
2
880
SEOcharity - Dark patterns in SEO and UX: How to avoid them and build a more ethical web
sarafernandez
0
280
Between Models and Reality
mayunak
4
460
XXLCSS - How to scale CSS and keep your sanity
sugarenia
250
1.3M
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