WPR22FA022 · Cessna 172 M
Mike Smith Aviation Cessna 172 M · Accident: fuel related during takeoff
From Napa County Airport (APC) to an unrecorded destination
Event
- NTSB case
- WPR22FA022
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 1 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Cessna 172 M
- Aircraft type
- Cessna 172
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N1870V
- Operator
- Mike Smith Aviation
- Onboard fatalities
- Unknown
- Route
- From Napa County Airport (APC), Napa Municipal, CATo not recorded
- Aircraft age
- About 47 years (built 1974)
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- Takeoff
- Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Fuel related
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Aircraft › Aircraft systems
- Aircraft › Fluids/miscellaneous hardware
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The student pilot was making his second solo cross-country flight.
The pilot used an onboard camera to record the ground run, takeoff, and initial cruise segments of the flight and then turned it off. The recordings showed those portions of the flight were uneventful, but he was heard talking to himself about dropping a pen and a pencil.
The pilot turned the camera back on as he approached the destination airport, which was moderately busy with multiple aircraft in the traffic pattern. During the approach, the pilot’s performance of the pre-landing checklist was interrupted due to a close encounter with a bird, and he did not complete the step of checking that his seatbelt was fastened. During the landing flare, the pilot transmitted on the local frequency his intention to perform a go-around. The airplane began to climb and reached about 60 ft above ground level (agl) when a change in the stroboscopic effect of the propeller was recorded, which likely indicated an engine speed change. The airplane leveled off, and the pilot said, “whoa, whoa, whoa,” before the recording ended.
Airport security video footage revealed that after reaching midfield, the airplane pitched down and struck the ground in a nose-low attitude, collapsing the nose gear. Thereafter, the propeller struck the ground, and the airplane continued under power for an additional 700 ft until it nosed over in a grass area and came to rest inverted. Sound spectrum analysis of the security video revealed that the engine was operating throughout the video and continued to operate after impact.
The airplane’s cabin sustained minimal damage during the accident sequence; however, the pilot, who was not restrained by a seat belt, was partially ejected through the windshield and sustained fatal injuries. The pilot was likely incapacitated from the initial impact and therefore unable to reduce engine power after the nose gear collapsed.
During the week before the accident, the airplane was stored outside during heavy rain. Postaccident examination revealed water in the left tank and the gascolator, although both the accident pilot and the pilot who flew the airplane earlier in the day followed the correct procedure for draining contaminants.
Examination of the left fuel tank revealed that a longstanding leak in the left fuel tank filler neck assembly had allowed water into the tank. Pre-accident internal damage and buckling of the tank’s lower skin appeared to have trapped water and prevented it from reaching the drain port. It is likely that this water moved and entered the engine’s fuel supply system as the pilot maneuvered the airplane in the traffic pattern. The change in the stroboscopic effect of the propeller observed shortly after the pilot began the go-around was consistent with a power interruption due to water entering the engine. With sufficient runway remaining, the pilot likely decided to abort the go-around and land.
The airplane manufacturer had issued a service bulletin that recommended the installation of additional drains in the fuel tanks. If installed, these drains may have revealed the water; however, the additional drains had not been installed, nor was this required per Federal Aviation Administration (FAA) regulations.
The engine did not experience a total loss of power at any point during the video-recorded portions of the flight. Examination revealed that the cam lobes of the engine exhibited excessive wear; however, such damage is progressive in nature and typically occurs over an extended period. The wear would have resulted in a gradual reduction in engine performance over that time, rather than an immediate or intermittent power loss.
According to the pilot’s flight instructor and his spouse, the pilot was a strong advocate of seatbelt usage. Although the reason for his failure to wear a seatbelt could not be determined, it is possible that when he dropped his writing implements during the flight, he released his seat belt to recover them and failed to resecure it. When his pre-landing checklist was interrupted due to the proximity of a bird, he became preoccupied by the busy airport environment and did not finish the checklist.
Autopsy results indicated that the pilot had severe coronary artery disease; however, based on available medical and operational evidence, it is unlikely that the heart disease contributed to the accident. Although toxicology samples revealed codeine and morphine in the pilot’s urine, there was no detectable codeine or morphine in his blood, and it is unlikely that effects of those substances contributed to the accident.
Probable cause
A power interruption due to water-contaminated fuel, which resulted in the student pilot aborting the takeoff and landing hard. Contributing to the accident were a leak in the left fuel tank that allowed water to enter and damage to the fuel tank that prevented water from being properly drained during the preflight inspection.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR22FA022
- Event ID
- 20211028104177
- Case number
- WPR22FA022
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates, cause areas. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: 710ecc81292cebded59f7bb5c54c289a03aeced510b2d649977f970c45568165; retrieved 2026-09-15T07:36:24.061Z.