Cessna R172K accident near Rosamond, California, October 2, 2016
On October 2, 2016 at about 9:45 pm local time, a 1977 Cessna R172K, registered N736LZ, was substantially damaged in an accident during takeoff near Rosamond, California (Rosamond Skypark airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 4 people were on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's improper use of the control lock, combined with his incomplete execution of two pre-departure procedures, which resulted in a takeoff with the control lock installed.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- October 2, 2016 · about 9:45 pm local time
- Place
- Rosamond, California · Rosamond Skypark · map
- Type
- Accident
- Injuries
- No one was hurt; 4 people were on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna R172K K, built 1977 · all R172Ks on the register
- Registration
- N736LZ · no longer on the register · serial R1722624
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot/owner and three non-pilot acquaintances decided to use the airplane to fly to another airport for lunch. The pilot had owned and operated the airplane about 10 years, and reported a total time of about 550 hours in that make and model. His normal procedures included hangaring the airplane, and using a yoke-mounted iPad "mini" for in-flight information. The outbound flight was uneventful. After landing, the pilot installed the flight control lock in the pilot-side yoke shaft. After lunch, the four persons returned to the airplane for the return trip. The pilot reported that the preflight inspection and taxi out to the run-up area were normal, but during the before-takeoff check process there, he noticed that the two fuel tank gauges indicated different quantities from one another, which was unusual for the high wing airplane. The pilot decided to interrupt the before-takeoff check process, shut down the engine, and physically "stick" the tanks to accurately determine the total fuel quantity. After the pilot measured the fuel quantities, which he determined were satisfactory, he re-boarded the airplane, re-started the engine, and taxied from the run-up area onto the runway for departure. The airplane lifted off about half-way down the 3,600 foot runway, but when it was at an altitude of about 20 feet above the ground, it stopped climbing. The pilot "immediately recognized something was wrong," aborted the departure, and the airplane landed on the remaining runway. The pilot was unable to stop the airplane on the runway, and it sustained substantial damage to the fuselage as a result. None of the occupants were injured. After the accident, the pilot determined that he had left the control lock in for the takeoff. The pilot reported that he normally used the airplane manufacturer's checklists on all his flights, including this one, but the evidence in this event contradicts that account. The manufacturer's checklists explicitly specified that the flight controls be checked for freedom of travel during two separate pre-departure phases; the walk-around preflight inspection, and the before-takeoff operational checks. For undetermined reasons, the pilot omitted those items from both of those phases, and deprived himself of two opportunities to detect the presence of the control lock. Investigation revealed that the manufacturer-issued control lock had been installed backwards by the pilot, which prevented it from accomplishing one of its primary design functions, that of inhibiting pilot access to the ignition switch. Further investigation revealed that the pilot rarely used the control lock due to the fact that he hangared his airplane, and that he was unaware that he had installed it backwards. The yoke-mounted iPad limited the pilot's view of the installed control lock, which reduced the potential for visual detection. The pilot reported that the winds were "light," which reduced the likelihood of the need for flight control inputs on the ground during taxi, and thus deprived the pilot of another opportunity for detection of the locked controls. Finally, after his impromptu physical check of the fuel quantity, the pilot did not re-commence the interrupted before-takeoff checklist from the beginning, and thus missed another opportunity to detect the locked flight controls.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Aircraft inspection event during prior to flight
- Preflight or dispatch event during prior to flight
- Flight control sys malf/fail during takeoff defining event
- Loss of control in flight during takeoff (rejected takeoff)
- Landing area overshoot during landing (landing roll)
- Landing gear collapse during landing (landing roll)
The NTSB's findings
- cause Personnel issues › Task performance › Use of equip/info › Use of checklist › Pilot
- cause Personnel issues › Task performance › Use of equip/info › Use of equip/system › Pilot
- cause Personnel issues › Action/decision › Action › Incomplete action › Pilot
Pilot
- Certificate: private
- Ratings: single-engine land
- Flight time: 591.7 hours in all; 553 in this make and model; 507 as pilot in command; 0 on instruments
- Last flight review: September 25, 2014
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: no injuries
The aircraft
- Airframe total time: 1,550 hours
- Last inspection: annual inspection, February 13, 2016; 17 hours since
- Maximum gross weight: 2,550 lb
- Landing gear: fixed
- Engine: Continental IO-360-K (piston); 1,567 hours total
The flight
- Departed from: L00 Rosamond CA at 9:45 pm
- Destination: CMA Camarillo CA
- Flight plan: none
- Runway 26, 3,600 ft by 50 ft
Weather at the time
- Light: daylight
- Wind: from 240° at 20 knots, gusting 26
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 77°F (25°C), dew point 41°F (5°C)
- Altimeter: 29.92 inHg
- Observation at 9:56 pm from WJF, 10 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 3 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
4 documents, released by the NTSB on October 25, 2016. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
| # | Document | What it is | |
|---|---|---|---|
| 1 | Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 | PDF, 9 pages | View Download |
| 2 | Pilot Responses to NTSB Questions October 7 | PDF, 2 pages | View Download |
| 3 | Pilot Responses to NTSB Questions October 19 | PDF, 1 page | View Download |
| 4 | Pertinent Images | PDF, 3 pages | View Download |
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
