Aviation Crash Map

Cessna R172K N736LZ

2 October 2016 · Rosamond, California, United States · No injuries

Summary

On 2 October 2016 at about 21:45 local time, a Cessna R172K registered N736LZ was involved in an accident near Rosamond, California, United States. 4 people were on board and nobody was injured. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.

The record

Date
at 21:45
Classification
Accident
Location
Rosamond, California, United States
Nearest airport
Rosamond Skypark (L00)
Coordinates
34.8706, -118.2119
Aircraft
Cessna R172K
Registration
N736LZ
Category
Airplane
Year built
1977
Engines
1
Operator
Not recorded
Operating rule
Part 91: General Aviation
Purpose of flight
Personal
Phase of flight
Not recorded
Route
Rosamond → Camarillo
Aircraft damage
Substantial
Weather
VMC
Light
Day
NTSB number
WPR17CA001

People

Nobody was injured.

On board Died Serious Minor Uninjured
4 0 0 0 4

Probable cause

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.

Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.

Read the full NTSB narrative

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.

Quoted verbatim from the NTSB record.

Other Cessna R172K accidents

Date Aircraft Location Operator Outcome Died
6 Mar 2017 Cessna R172K
N736AS
Nome, Alaska, United States - Fatal 1
18 Jul 2015 Cessna R172K
N5453V
Fairfield, North Carolina, United States TIM Whitfield Aviation Inc No injuries -
29 Dec 2018 Cessna R172K
N1095V
Chesaning, Michigan, United States - Fatal 1
21 Sep 2013 Cessna R172K
HC-BGT
Morona Santiago, Ecuador Aerosangay Fatal 3
19 Nov 2012 Cessna R172K
HK4890G
Cuchilla La Laja, Colombia Garcia B. Gabriel Fatal 1
1 Jul 2012 Cessna R172K
N758JQ
Greene, New York, United States Pecha James C No injuries -

All 125 records for this type

Other accidents in this area

Date Aircraft Location Operator Outcome Died
6 Oct 2016 Joe Salomone SUPER CUB SQ2
N786AB
Boca Reservoir, California, United States - No injuries -
12 Dec 2016 Cessna T210M
N761SZ
Mecca, California, United States - Serious injuries -
25 Aug 2016 Siai-Marchetti SF260
N16FD
Fullerton, California, United States Air Combat, USA Minor injuries -
15 Dec 2016 Bombardier CL 600 2B19
N986SW
San Francisco, California, United States Skywest Airlines Inc Unknown -
24 Aug 2016 Cessna 182
N4810N
Fallbrook, California, United States Civil Air Patrol Inc. Minor injuries -
8 Jul 2016 Cessna 172
N9488G
San Diego, California, United States - No injuries -

All 170,864 records in United States