WPR10LA345

NTSB accident investigation · Cessna 177 · Chino, CA · July 11, 2010

Accident · No injuriesLimited investigationFinal report
Date
July 11, 2010, 14:00 local (21:00 UTC)
Place
Chino, CA
Injuries
1 uninjured
Damage
Substantial damage
Phase of flight
Enroute
Aircraft
N3295TCessna 177
Defining event
Enroute-descent: Fuel exhaustion
Weather
Visual (VMC) · Day
Status
Completed · report July 12, 2011
Report
Approved by Office Director
NTSB office
Western Pacific Region
Parties
FAA FSDO
FAA report
20100711040099A
Case key
76597

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 pilot’s inadequate fuel planning which resulted in a loss of engine power during cruise flight due to fuel exhaustion.

Findings · 4

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.

Fluids: fuelAircraft › Fluids/misc hardware · Fluid levelCessna 177: 13 casesAll aircraft: 1,695 casesProbable cause
Action: incorrect action performancePersonnel issues › Action/decision · PilotCessna 177: 7 casesAll aircraft: 1,386 casesProbable cause
Object/animal/substanceEnvironmental issues › Physical environment · Effect on equipmentCessna 177: 2 casesAll aircraft: 224 cases
Planning/preparation: fuel planningPersonnel issues › Task performance · PilotCessna 177: 12 casesAll 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.

Analysis

The pilot reported that he prepared a flight plan the night before his departure which included three legs, with a fuel stop planned after the second leg. On the day of the accident, the pilot performed a preflight inspection on the airplane and determined that he had sufficient fuel to make the planned 2-hour trip with the appropriate fuel reserve. He flew to the first planned airport, and then amended his flight plan and flew to a different airport, not originally on his flight plan. He did not preflight or consider how this leg would affect his fuel calculations. After the second stop, he did an abbreviated preflight, which consisted of visually checking the fuel and oil levels. He looked into the fuel tanks, but did not physically measure the amount of fuel. He estimated the amount of fuel on board, but did not recognize that the fuel level was too low to make the flight. He then departed for the planned fuel stop airport. The airplane was over a housing tract a few miles northwest of the destination airport when the fuel supply was exhausted and the engine lost power. The pilot made a forced landing on a golf course, but could not stop the airplane before it collided with ground obstacles.

Factual narrative

On July 11, 2010, about 1400 Pacific daylight time, a Cessna 177, N3295T, collided with objects during an off airport forced landing near Chino, California. The pilot/owner was operating the airplane under the provisions of 14 Code of Federal Regulations (CFR) Part 91. The private pilot was not injured. The airplane sustained substantial damage to the fuselage and wings by impact forces. The local personal flight departed Kernville, California, about 1245, en route to Corona, California. Visual meteorological conditions prevailed, and no flight plan had been filed. The pilot reported that he prepared a flight plan the night before his departure. He was going to depart Brackett Field, La Verne, California, and meet a friend at Tehachapi, California. He would then fly to Corona to fuel the airplane prior to returning to Brackett. The pilot conducted a preflight, and determined that the airplane had sufficient fuel to make the planned 2-hour trip and have appropriate reserves. He flew to Tehachapi, and secured the airplane. After discovering that his friend was at Kern Valley Airport, Kernville, the pilot departed to that location. He did not preflight or consider how this leg would affect his fuel calculations. After completing his visit at Kernville, the pilot did an abbreviated preflight, which consisted of visually checking the fuel and oil levels. He looked into the tanks, but did not physically measure the amount of fuel. He estimated the amount of fuel on board, and stated that he did not recognize that his fuel level was too low to make the flight. He departed for Corona. The pilot stated that the airplane was over a housing tract in Chino Hills, California, which was a few miles northwest of Corona, when the fuel supply was exhausted and the engine lost power. He made a forced landing on a golf course, but could not stop the airplane before it collided with ground obstacles.

Aircraft

Registration
N3295T
Reported as
Cessna 177
Category
Airplane
Serial number
17700595
Airframe hours
1,964
Engine
Lycoming O-360-A1A, 180 horsepower, reciprocating
Damage
Substantial damage
Flight
Personal · Part 91
Operator
Phil Samuelian
Registered owner
Phil Samuelian
Airworthiness certificate
Standard, Normal
Last inspection
Annual · March 20, 2010
Departed
L05 · Kernville, CA
Destination
AJO · Corona, CA

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
52
Injuries
None
Certificate
Private
Airplane ratings
Single-engine land
Medical
Class 3, With waivers/limitations
Last flight review
June 29, 2010
Seat
Left
Flight hours
449 total · 364 in this make and model · 318 as pilot in command · 37 in the last 90 days · 7 in the last 30 days · 3 in the last 24 hours

Weather

Conditions
Visual (VMC) · Day
Wind
260° at 9 knots
Visibility
8 statute miles
Lowest ceiling
11,000 ft broken
Temperature
84 °F, dew point 57 °F
Altimeter
29.90 inHg
Observed at
KCNO

Docket · 1

The files NTSB released with the investigation on May 12, 2011, on NTSB’s docket system: statements, records, photos and specialists’ reports. 577 KB 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.