The day the checklist was born
- Retell how the pilot's checklist began.
- Explain why the fix was a procedure, not more skill.
Too much airplane for one memory
In October 1935, Boeing's Model 299 — the prototype of the B-17 — crashed on a demonstration flight at Wright Field in Ohio. The pilot was one of the Army Air Corps' most experienced test pilots.
The cause wasn't a broken part. The crew had taken off with the elevator gust lock still engaged — a single item, easy to forget among the many things a new, complex aircraft demanded.
The response is the important part. Nobody concluded that pilots needed to try harder. Instead, test pilots wrote down the critical items for takeoff, landing and taxi on a short card. With that discipline the aircraft went on to fly safely, and the checklist became a permanent part of aviation.
When a task outgrows memory, the answer is a better system, not a better memory. Checklists exist because skill and experience are not enough on their own.
What did the Model 299 investigation show most clearly?
It isn't only aviation
Other high-stakes fields borrowed the idea. In 2008–2009 the World Health Organization tested a short Surgical Safety Checklist in eight hospitals around the world. Deaths and major complications after surgery fell substantially once teams used it (Haynes et al., New England Journal of Medicine, 2009).
The checklist didn't teach surgeons anything new. It made sure the team paused at the right moments to confirm things everyone already knew mattered.