VANS AIRCRAFT INC RV-12IS near Scappoose, OR — 2024-07-02

Probable cause

The pilot’s failure to remove the seat belt used as a flight control lock from the right control stick before takeoff, which resulted in a loss of control, an aerodynamic stall, and a collision with terrain during takeoff. Contributing to the accident was the failure of the pilot to adequately check the flight controls before takeoff to ensure they were able to move without restraint.

Contributing factors

Contributing to the accident was the failure of the pilot to adequately check the flight controls before takeoff to ensure they were able to move without restraint.

NTSB narrative

The pilot departed after a quick stop during a cross-country flight. Flight data from the avionics unit installed in the airplane revealed that on takeoff, the airplane lifted off the ground and reached a maximum altitude of about 81 ft above ground level (agl). After liftoff, the airplane pitched up to a maximum angle of about 43° nose up and continuously rolled left, ultimately reaching a maximum of 60° of bank. The airplane’s pitch decreased rapidly over the next several seconds to 33° nose down, consistent with an aerodynamic stall. The airplane’s stall warning system activated 3 seconds before liftoff and deactivated about 1 second before impact. The airplane was airborne for about a total of 14 seconds before impacting terrain. Witnesses at the airport reported that they observed the airplane in a hard left-banked turn, in a nose-down attitude, until it impacted terrain. A review of pictures taken after the accident revealed that the right seat belt was looped around the right control stick, and it was secured to the full left and aft position. Flight data, impact damage around the control stick, and witnesses’ statements were all consistent with the right seat’s control stick being locked in the full left and aft position during the takeoff. It is likely that the pilot secured the right control stick with the seat belt acting as a flight control lock during his stop at the airport and failed to check that it was removed before takeoff. According to the pilot’s operating handbook for the accident airplane, the Before Takeoff Run-Up checklist calls for the flight controls to be checked. The recorded flight data did not reveal evidence of an engine run-up before takeoff, indicating that the pilot did not complete this checklist, and so did not benefit from the methodical self-assessment that the checklist provides. Postaccident examination of the airplane revealed no evidence of preimpact failures or malfunctions that would have precluded normal operation.

NTSB coding

• Loss of control in flight · Takeoff
• Loss of control in flight · Maneuvering
• Loss of Control While Maneuvering
• Loss of Control on Takeoff/Initial Climb
• Checklist Use
• Preflight Inspection

Evidence available

• Photos
• 8 docket documents

Docket documents8

• PARTY FORMform
• PILOT/OPERATOR AIRCRAFT ACCIDENT REPORT, NTSB FORM 6120.1form
• RELEASE OF AIRCRAFT WRECKAGE, NTSB FORM 6120.15form
• GARMIN FLIGHT DATAother
• MEMORANDUM FOR RECORDS (RECORD OF EMAILS)other
• RV-12 POH EXCERPTother
• ACCIDENT PHOTOGRAPHSphotos
• AIRFRAME AND ENGINE EXAMINATION REPORTreport

Related mishaps

• CESSNA 170B

  2026-07-10 · Hartwell, GA

• CASSUTT IIIM

  2026-07-05 · Odessa, TX

• BELLANCA 7GCBC

  2026-05-30 · Jonesboro, AR

• CESSNA 172H

  2026-05-25 · Berryville, AR

• COMMANDER AIRCRAFT CO 114TC

  2026-05-23 · Woodruff, WI

• BELL 206-L4

  2026-05-23 · Cedar City, UT