About the Author

Peter Tyson spent his career at the intersection of two disciplines that rarely speak to each other: engineering rigor and human judgment. His professional formation as an aeronautical engineer was shaped by the culture of flight test — an environment in which the quality of reasoning is not an abstract virtue but a practical requirement, measured in whether the aircraft returns.

He holds a Bachelor of Science and a Master of Science in Aeronautical Engineering, and is a graduate of the Naval Test Pilot School. He served as a military helicopter pilot before transitioning to a career as a lead systems engineer and program manager in Naval aviation. In that capacity, he was responsible for the full life-cycle management of aircraft and weapon systems — requirements definition, contractor oversight, flight testing, configuration management, and the continuous stream of risk-based decisions that complex aviation programs generate daily.

For fifteen years, he led critical thinking and risk-based decision making workshops with thousands of well-educated professionals in the U.S. Naval aviation workforce, using case studies to challenge engineers, program managers, and safety professionals to examine the quality of their own reasoning under pressure. The consistent finding — that the same thinking failures appeared across every organization, every program, and every era — became the organizing observation of this book.

He is also a helicopter pilot with direct experience of real-time system failure diagnosis under pressure. That experience informs the authorial voice throughout the book: not the voice of a scholar analyzing disasters from a comfortable remove, but of an engineer and pilot who has been in the cockpit when the machinery failed and who understands, from the inside, what it costs to think clearly when the instruments are contradicting each other and the aircraft is not cooperating.

Standards Under Pressure is his second book. His first, Flight Test: The Discipline, examined the methods, culture, and intellectual demands of the flight test profession.

I grew up in Hatboro, Pennsylvania, approximately 100 miles southeast of Three Mile Island, during the years the plant was under construction and in its early years of operation. The accident happened when I was nine years old. I do not recall the event itself, but I recall the adults around me being worried in a way that registered as significant even to a child who did not understand the details.

Writing the final chapter of this book was an exercise in returning to that moment with the perspective of an engineer who has spent a career thinking about how complex systems fail and, occasionally, how they succeed despite the failures within them. The operators in the Unit 2 control room on March 28, 1979, faced something I understand differently now than I did as a frightened child watching the news — a system giving contradictory signals, time running out, and decisions made with incomplete information. That is not an abstract scenario for an engineer who has flown.

My parents later lived near Harrisburg. I have driven on the Pennsylvania Turnpike across the Susquehanna River many times, and on clear days I still look south to see the Three Mile Island cooling towers in the distance. They have a place in history. They are the reason this book ends where it does.

Flight Test: The Discipline examines the methods, professional culture, and intellectual demands of flight test engineering and evaluation — the discipline that stands between a design and a deployed aircraft. It is written for engineers, pilots, and program managers who want to understand what flight test actually is, what it demands, and why it matters.