Upgrade to Pro — share decks privately, control downloads, hide ads and more …

How to Crash a Plane

Nickolas Means
November 16, 2015
Technology
1
330

How to Crash a Plane

Nickolas Means

November 16, 2015
Tweet

More Decks by Nickolas Means

See All by Nickolas Means
The Magnitude 9.1 Meltdown at Fukushima
nmeans
0
71
Taking the 737 to the MAX!
nmeans
0
48
Who Destroyed Three Mile Island?
nmeans
0
750
The Original Skunk Works
nmeans
0
1.7k
Warning: May Be Habit Forming
nmeans
1
160
The Building Built on Stilts
nmeans
1
420
The Original Skunk Works
nmeans
1
610
How To Code Like A Writer
nmeans
3
3.3k
You Are Not An Impostor
nmeans
11
18k

Other Decks in Technology

See All in Technology
これまでの計測・開発・デプロイ方法全部見せます！ / Findy ISUCON 2024-11-14
tohutohu
3
370
Security-JAWS【第35回】勉強会クラウドにおけるマルウェアやコンテンツ改ざんへの対策
4su_para
0
190
OCI Security サービス 概要
oracle4engineer
PRO
0
6.5k
組織成長を加速させるオンボーディングの取り組み
sudoakiy
2
220
【LT】ソフトウェア産業は進化しているのか？ #Agilejapan
takabow
0
100
適材適所の技術選定 〜GraphQL・REST API・tRPC〜 / Optimal Technology Selection
kakehashi
1
710
ドメインの本質を掴む / Get the essence of the domain
sinsoku
2
160
OS 標準のデザインシステムを超えて - より柔軟な Flutter テーマ管理 | FlutterKaigi 2024
ronnnnn
1
300
安心してください、日本語使えますよ―Ubuntu日本語Remix提供休止に寄せて― 2024-11-17
nobutomurata
1
1k
SSMRunbook作成の勘所_20241120
koichiotomo
3
170
ExaDB-D dbaascli で出来ること
oracle4engineer
PRO
0
3.9k
【Pycon mini 東海 2024】Google Colaboratoryで試すVLM
kazuhitotakahashi
2
560

Featured

See All Featured
Design and Strategy: How to Deal with People Who Don’t "Get" Design
morganepeng
126
18k
Documentation Writing (for coders)
carmenintech
65
4.4k
The Psychology of Web Performance [Beyond Tellerrand 2023]
tammyeverts
44
2.2k
The Success of Rails: Ensuring Growth for the Next 100 Years
eileencodes
44
6.8k
Product Roadmaps are Hard
iamctodd
PRO
49
11k
The Power of CSS Pseudo Elements
geoffreycrofte
73
5.3k
Creating an realtime collaboration tool: Agile Flush - .NET Oxford
marcduiker
25
1.8k
Testing 201, or: Great Expectations
jmmastey
38
7.1k
Fight the Zombie Pattern Library - RWD Summit 2016
marcelosomers
232
17k
Building an army of robots
kneath
302
43k
Rebuilding a faster, lazier Slack
samanthasiow
79
8.7k
CoffeeScript is Beautiful & I Never Want to Write Plain JavaScript Again
sstephenson
159
15k

Transcript

  1. HOW TO CRASH A PLANE NICKOLAS MEANS / @NMEANS

  2. July 19, 1989

  3. Denver Stapleton International Airport

  4. United Flight 232 Denver Stapleton to Chicago O'Hare

  5. None

  6. McDonnell Douglas DC-10-10 N1819U

  7. None
  8. None
  9. None

  10. !

  11. None

  12. Captain Al Haynes

  13. Al, I can't control the plane!

  14. None

  15. We're rolling!

  16. None

  17. "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."
  18. None

  19. We've lost all our hydraulics.

  20. None
  21. None

  22. Elevators

  23. Ailerons

  24. None
  25. None

  26. The only question I had was how long it was

    going to take Iowa to hit me.
  27. None
  28. None
  29. None

  30. Phugoid

  31. Phugoid

  32. None
  33. None
  34. None
  35. None
  36. None
  37. None
  38. None

  39. GE CF6-6 Turbofan Engine

  40. None
  41. None
  42. None
  43. None
  44. None
  45. None
  46. None

  47. Brace! Brace! Brace!

  48. None
  49. None
  50. None
  51. None
  52. None

  53. Of 296 people on board, 185 survived.

  54. In the previous 25 years, no one had ever survived

    the complete loss of flight controls on an airliner.

  55. "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

  56. What made this crew different?

  57. None

  58. CREW RESOURCE MANAGEMENT

  59. NO HEROES

  60. EVERYONE HAS A VOICE

  61. SOFTWARE IS A TEAM SPORT

  62. THANKS! NICKOLAS MEANS / @NMEANS