ANC24LA004

NTSB accident investigation · Piper PA-22 · Anchorage, AK · November 13, 2023

Accident · Minor injuriesClass 3 · LimitedFinal report
Date
November 12, 2023, 16:15 local (Nov 13, 2023, 01:15 UTC)
Place
Anchorage, AK
Injuries
1 minor
Damage
Substantial damage
Phase of flight
Approach
Aircraft
N8095CPiper PA-22
Defining event
Approach-VFR pattern final: Fuel exhaustion
Weather
Visual (VMC) · Dusk
Status
Completed
Report
Approved by Office Director
Investigation class
Class 3
NTSB office
Alaska Regional Office
Parties
FAA
FAA report
20231112020179A
Case key
193441

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

Probable cause

The loss of engine power during final approach due to fuel exhaustion, which resulted from the pilot’s inadequate preflight.

Findings · 3

NTSB’s coded findings. Those marked are part of the probable cause; the rest are factors or other findings. Under each, the cases with the same finding.

Use of equip/info: use of equip/systemPersonnel issues › Task performance · PilotPiper PA-22: 3 casesAll aircraft: 1,391 casesProbable cause
Fluids: fuelAircraft › Fluids/misc hardware · Fluid levelPiper PA-22: 5 casesAll aircraft: 1,695 casesProbable cause
Planning/preparation: fuel planningPersonnel issues › Task performance · PilotPiper PA-22: 1 caseAll aircraft: 719 casesProbable cause

Sequence of events

The events NTSB coded, in order, by phase of flight. The defining event is the one that best describes the accident. Under each, the cases with the same event anywhere in their sequence.

Fuel exhaustionApproach-VFR pattern finalPiper PA-22: 1 caseAll aircraft: 804 casesDefining event

Analysis

The pilot reported that he intended to conduct a short flight to run the engine to avoid a prolonged period between flights. He completed most of the preflight items earlier in the afternoon and then returned later to complete a final preflight check. The pilot stated that the airplane’s fuel tanks contained about 12 to 14 gallons of fuel. He stated that the airplane had large non-original fuel tanks and it was difficult to measure fuel quantities under 10 gallons, and he was also uncertain about how much unusable fuel each tank held. He departed and entered the traffic pattern. He performed a slip maneuver during the final approach to increase the descent rate. He then added power to arrest the descent rate; however, the engine did not respond and subsequently the engine lost total power. The pilot executed a forced landing short of the runway threshold, resulting in substantial damage to the fuselage and wing strut. After the accident, the pilot stated that the combination of low fuel and the forward slip may have un-ported the fuel in the fuel tank, resulting in the total loss of engine power. Postaccident examination of the airplane revealed that both fuel tanks were empty; however, fuel was found in the gascolator. The examination of the engine did not reveal evidence of any preimpact failures or malfunctions that would have precluded normal operation. Given that the airplane was equipped with larger, non-original fuel tanks, with limited unusable fuel data, a known low fuel state, and the pilot’s statement that he performed a uncoordinated slip maneuver, it is likely that the fuel unported from the right fuel tank during the slip maneuver, resulting in a loss of engine power due to fuel starvation.

Factual narrative

On November 12, 2023, about 1615 Alaska standard time, a Piper PA-22, N8095C, sustained substantial damage when it was involved in an accident near Anchorage, Alaska. The pilot sustained minor injuries. The airplane was operated by the pilot as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot reported that he intended to conduct a short flight to run the engine to avoid a prolonged period between flights. He completed most of the preflight items earlier in the afternoon when he cleared snow off the airplane. He returned later, unplugged the engine heater, removed the engine blanket, and completed a final preflight check. The pilot determined the airplane’s fuel tanks contained a total of about 12 to 14 gallons of fuel, about 7 gallons in each wing tank. He stated that the airplane had large non-original fuel tanks and it was difficult to measure fuel quantities under 10 gallons; he was also uncertain about how much unusable fuel each tank held. About 1610, he departed runway 32 and maintained a “close in” pattern with a climb to about 800 ft mean sea level. On the downwind leg he adjusted the engine power to 1500 rpm to start the approach. On final he placed the airplane in an uncoordinated slip to increase the airplane’s rate of descent. Close to the end of the approach, the pilot further reduced power, but then recognized that he was too low on the approach. He applied engine power to arrest the descent rate; however, the engine did not respond, and he realized that the engine had lost total power. He switched the fuel selector from the left tank to the both position in an attempt to restore engine power. He realized that the airplane did not have sufficient altitude to make the runway and he performed a forced landing short of the runway. The main landing gear impacted a berm along a roadway that ran across the approach end of runway 32, resulting in substantial damage to the fuselage and left-wing strut. After the accident the pilot stated that the combination of low fuel state and the forward slip may have un-ported the fuel in the fuel tank resulting in the total loss of engine power. A postaccident examination of the airplane revealed that the left and right fuel tanks were empty. The gascolator was full of fuel and the fuel was consistent with 100LL aviation gasoline. No fuel was observed in the lines entering or exiting the gascolator. The fuel strainer was clean and contained no water. A postaccident examination of the engine was performed. The throttle, mixture, and carburetor heat controls were checked for continuity with no discrepancies noted. The top spark plugs were removed and were in serviceable condition with normal electrodes. Both magnetos and all ignition leads were checked for operation; spark was observed at each end of the top ignition lead when the crankshaft was rotated. A thumb compression check of all four cylinders verified compression. The oil level was at the correct level and nodiscrepancies were noted with the oil’s condition. The air filter was removed and found to be serviceable; the carburetor throat was clear of obstructions.

Aircraft

Registration
N8095C
Reported as
Piper PA-22
Category
Airplane
Serial number
22-2241
Built
1954
Airframe hours
3,404
Engine
Lycoming O-320 B2B, 160 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Airworthiness certificate
Standard, Normal
Last inspection
Annual · October 23, 2023 · 0 hours before
Destination
Same as departure
Airport
PALH · Lake Hood, runway 32, 2,200 × 75 ft, gravel
Equipment
Unknown

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Flight crew

As NTSB recorded them. NTSB leaves out names.

Role
Pilot
Age
41
Injuries
Minor
Certificates
Airline transport, Flight instructor, Commercial
Airplane ratings
Multi-engine land, Single-engine sea, Single-engine land
Instrument ratings
Airplane
Medical
Class 1, Without waivers/limitations
Last flight review
September 12, 2023
Seat
Left
Restraint
4-point
Flight hours
7,745 total · 700 in this make and model · 5,104 as pilot in command · 159 in the last 90 days · 32 in the last 30 days · 1 in the last 24 hours

Weather

Conditions
Visual (VMC) · Dusk
Wind
60° at 7 knots
Visibility
2 statute miles
Lowest ceiling
None
Temperature
21 °F, dew point 19 °F
Altimeter
30.08 inHg
Observed at
PANC, 2 nm away
METAR
SPECI PANC 130108Z 06007KT 2SM BR SCT002 M06/M07 A3008 RMK AO2 I1000 T10561067

Docket · 5

The files NTSB released with the investigation on April 2, 2025, on NTSB’s docket system: statements, records, photos and specialists’ reports. 6.8 MB in all.

FAA reports on this event · 1

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.