Sorry, right, always mixing up those two. Best lessons from the book for me are: 1- meet the designers, understand the "why"s and not only the descriptive post

Sorry, right, always mixing up those two. Best lessons from the book for me are: 1- meet the designers, understand the "why"s and not only the descriptive posthoc documentation 2- when you don't trust your instruments, keep following the procedures, checklists, (for this you need an excellent, trained, cold-headed team), and eventually try to reconstruct 'what aircraft you have' 3- trust the automated checklists but not too much! Crosscheck what's asked of you, with what you know of the aircraft. Since you know the 'why's you know the automated checklist system's designers probably never expected an aircraft with that much damage to keep flying... 4- there are no hall-passes for heroes. At the end De Crespigny fails his evaluation (the flight was an evaluation flight, with an instructor on board). All around a great, great book for systems people.