Principles of Safety and Reliability Learned from US Navy Landing Signal...
summary
Aircraft carrier recovery runs every 45–60 seconds with planes stacked by altitude and timed to the minute; Landing Signal Officers use a gyroscopic meatball, the ICLS crosshair video, and a handheld pickle switch to open/close the deck and issue silent light wave‑offs. Pilots target a 12 ft hook height and try to catch the three‑wire; grades record every trap and drive retraining. The concrete practices are specific jargon, hard limits, paired observers, and a debriefing culture that turns every landing into measurable feedback.
AI-written summary · about
chapters (14)
- 0:00US Navy landing introduction
- 1:31Aircraft carrier flight deck
- 4:38Naval landing protocols
- 9:30Final approach sequence
- 13:38Daytime landing demo
- 15:50Night/weather landing challenges
- 20:04Landing Signal Officers role
- 23:52LSO tools and techniques
- 27:18LSO team roles
- 29:57Pilot grading and safety culture
- 34:05LSOs vs software reliability
- 36:33Navy reliability principles
- 41:45Building expertise and learning
- 44:30Conclusion and Q&A
related talks
53mMayday! Software lessons from aviation disasters
25mLessons from flying for engineering leadership
50mLearning in Production (or Why the Apollo 11 Landing Nearly Failed)
09mSpeaking Planely for the Grounded Professional
01h 01mSwiss cheese, teamwork and other things we should learn from the aviation industry
01h 01mFly the Enterprise: Applying Aviation Lessons to DevOps Teams
37mLost and alone over the Pacific
42mHow to not kill people