The 1935 B-17 Crash That Invented the Checklist
A prototype bomber crashed at Wright Field with a gust lock still engaged. The response wasn't more training. It was the pilot's checklist.
On 30 October 1935, at Wright Field in Dayton, Ohio, the Boeing Model 299 — the prototype of what would become the B-17 Flying Fortress — lifted off, climbed to about three hundred feet, stalled, and crashed. Two of the five aboard were killed, including Major Ployer P. Hill, the Army Air Corps chief of flight testing. The airplane had lost the Air Corps competition before it had finished burning.
The airplane was mechanically sound. The cause was a control gust lock — a ground-only device that mechanically pinned the rudder and elevator — that the crew had failed to release before takeoff. Contemporary reports concluded the 299 was "too much airplane for one man to fly." It had four engines instead of two, and enough new systems that any crew, however skilled, was going to miss items on some flights.
The response was not more training. The response was the checklist. Test pilots at Wright Field developed a printed sequence of items covering takeoff, flight, before-landing, and after-landing — a page of items to be read aloud and confirmed, in the same order, on every flight. It replaced the assumption that a good pilot would remember with a discipline that made remembering unnecessary.
The Model 299 went on to become the B-17. Twelve thousand were built. And every certified airplane that has flown since carries the descendants of that Wright Field response: normal checklists, emergency checklists, memory items, and the challenge-and-response discipline that keeps human error from becoming a headline. A checklist is not paperwork. It is the answer to a specific historical failure.