Cessna 172 N63931
14 May 2020 · Tucson, Arizona, United States · No injuries
Summary
On 14 May 2020 at about 16:50 local time, a Cessna 172 registered N63931, operated by Skylens LLC, was involved in an accident near Tucson, Arizona, United States. One person was 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 16:50
- Classification
- Accident
- Location
- Tucson, Arizona, United States
- Coordinates
- 32.2514, -110.7056
- Aircraft
- Cessna 172
- Registration
- N63931
- Category
- Airplane
- Year built
- 1981
- Engines
- 1
- Operator
- Skylens LLC
- Operating rule
- Part 91: General Aviation
- Purpose of flight
- Aerial Observation
- Phase of flight
- Not recorded
- Route
- Tucson → Tucson
- Aircraft damage
- Substantial
- Weather
- VMC
- Light
- Day
- NTSB number
- WPR20LA147
People
Nobody was injured.
| On board | Died | Serious | Minor | Uninjured |
|---|---|---|---|---|
| 1 | 0 | 0 | 0 | 1 |
Probable cause
The pilot improper fuel management, which resulted in running the left fuel tank empty and a subsequent total loss of engine power due to fuel starvation.
Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.
Read the full NTSB narrative
The pilot reported that about 3.5 hours into an aerial observation flight, the engine started to sputter. He stated that he double checked the fuel selector, enriched the mixture, checked the magnetos, and looked at the gauges. The left tank fuel gauge indicated it was empty and the right tank fuel gauge indicated it was full. He immediately turned away from nearby mountains and initiated an off-field landing toward a roadway. During short final, he encountered a downdraft, and the airplane landed short of the roadway in heavy brush, substantially damaging the right wing. A postaccident wreckage examination and engine run did not reveal any anomalies with the airframe or engine that would have precluded normal operation. The accident flight was the first flight post-maintenance. The maintenance facility’s standard policy for mechanics is to place the fuel selector on the left fuel tank after conducting maintenance. In addition, the mechanic who conducted the work recalled moving the selector to the left when the airplane was moved to the tie-down area and secured. The operator reported that he specifically instructs pilots to fly with the fuel selector in the BOTH position at all times. He further mentioned that the end of the “busy” season is May 31, 2020, and that it is not uncommon for pilots to get “burned out” or “complacent” toward the end of a season. When the NTSB IIC contacted the pilot to ask additional questions about the event, he reported that he had been flying the same airplane for the last 6 months and knew it well. He said that the fuel selector was in the BOTH position before and during the flight. He said he did not note anything abnormal with the fuel gauges during the flight. Nor did the engine make any abnormal noises prior to it starting to sputter, he said it sounded as if the engine was “choking.” He further reported that after the engine quit, he noticed that the left fuel gauge indicated empty and the right indicated full, but he did not turn the selector to the right fuel tank when attempting to restart the engine. He used primer and throttle; the engine got some fuel, but it would not continue to run. When the pilot was informed of the maintenance facility’s standard procedures regarding the fuel selector placement, he stated that he saw the fuel selector was on the left tank and he switched it to BOTH before the flight. Despite the pilot saying that the fuel selector was on the BOTH position both before and during the flight, he never mentioned that it was ever on the left tank until after learning about the maintenance facility’s standard procedures. In addition, a postaccident engine examination revealed fuel in the fuel lines throughout the airframe all the way to the carburetor inlet, and the engine ran with no issue. Therefore, it is likely that the pilot did not ensure the fuel selector was in the BOTH position after it came out of maintenance, nor was he properly monitoring the fuel gauges during the flight which resulted in a total loss of engine power due to fuel starvation.
Quoted verbatim from the NTSB record.
Other Cessna 172 accidents
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 30 Sep 2020 | Cessna 172 | Higginsville, Missouri, United States | University of Central Missouri | No injuries | - |
| 6 Feb 2020 | Cessna 172 | Palmer, Alaska, United States | - | No injuries | - |
| 2 May 2020 | Cessna 172 | Fresno, California, United States | - | Minor injuries | - |
| 2 Aug 2020 | Cessna 172 | Conway, Arkansas, United States | Barrett Aviation | No injuries | - |
| 3 Oct 2020 | Cessna 172 | Hinckley, Minnesota, United States | - | No injuries | - |
| 31 Dec 2020 | Cessna 172R | Hope, Alaska, United States | Elmendorf Air Force Base Aero Club | Minor injuries | - |
All 12,209 records for this type
Other accidents in this area
| Date | Aircraft | Location | Operator | Outcome | Died |
|---|---|---|---|---|---|
| 13 Mar 2020 | Piper PA 28-180 | Tucson, Arizona, United States | - | No injuries | - |
| 5 Oct 2020 | Cessna 150 | Rimrock, Arizona, United States | - | No injuries | - |
| 13 May 2020 | Mooney M20J | Phoenix, Arizona, United States | - | No injuries | - |
| 5 Jul 2020 | Beechcraft 23 | Sedona, Arizona, United States | - | No injuries | - |
| 24 Oct 2020 | Cessna 172 | Carefree, Arizona, United States | - | No injuries | - |
| 24 Oct 2020 | Lancair 235 | Cordes Lakes, Arizona, United States | - | Fatal | 2 |